The idea is that the popup is launched by the fire event after `beginseq(Fire_seq)`
the idea of the popup (modal with the no close flag) is to force the user to acknowledge something if they are there.
After 2 minutes, the alarm takes action, and then snoozes for 5 minutes before resetting (at which point, if the temp hasn't lowered by enough, the cycle starts again)
It's less of just a snooze, and more of a delay + a snooze if that makes sense. Delay: (the 2 minutes in which the popup are active), snooze: (the 5 minutes after automated action, or the 1 hour after user acks/ignores the alarm)
The user if they are closely monitoring the system should however, have those 2 minutes to decide if they want to acknowledge that the system is overtemped, and ignore it for 1 hour (want to make the ignore/snooze time long enough so that in the future people don't disable the alarm because it inconveniences them too often). The button to ignore/ack the alarm also closes the popup and goes back to the main control page.
An original idea I had was after the 2 minutes, if automatic action is taken, the popup was closed and replaced with a system.messagebox() informing the user of the automatic action taken. However, this was difficult to manage because if you had an unacked message box starting the same sequence multiple times before it had ended lead to odd behavior.
However, replacing the message box with just keeping the popup open and having different components become visible after the automatic action being taken was easier to get running and looks nice as well.