Help with scheduling thermostats, while also using various event handlers.
-
Hi, I am trying to schedule numerous thermostats on my campus. I would like them to turn off after normal working hours and during weekends. Unless the ambient room temperature is outside of a specific range, say below 50 or above 80. And during working hours I want the thermostat to go into Heating mode if the temp is below ... lets say 60°F,go to auto mode if the outside temp is from 60°F to 75°, and go to cooling mode if the temp is above 75°F. I would also like to have a notification sent to me if the thermostats set temp is outside of a range but this isn't as important.
The problem I am running into ( or at least I believe this is the problem) is that my event handlers are basically working against each other. For the schedule I have a setpoint event handler setting the stat to auto if the schedule is active and off if the schedule is inactive, plus 2 event detectors on the space temp data point. These are a High and Low limit. This seems to be working for thwe most part, but when I add another event handler the set the stat to cool or heat, and link it to an event detector I created on our outside air temp sensor it seems to not update frequently enough. So as soon as the temp drops below 60°F it will set the stat to heating but if the schedule goes active and the temp is still below 60 it will switch to auto and not go back to heating mode until the outside temp raises above 60°F and then drops back below it, re-triggering the event.
Is there a way I can set some sort of scan rate for specific event handlers< in this case my outside air temp event handler needs to check the data point and respond accordingly more frequently.
FYI: These are mod-bus I/P data sources, and unfortunately I have 0 experience with any scripting language.
-
@kyle-Hughes might be worthwhile taking a closer look at your set up.
I'd probably look at writing something using a combination of scripts and handlers to hold your preferred settings and run at both selected times and on alert. In fact if the settings need to be shared between them it might be good to store the settings in the json data store as a single source of truth.Happy to look in closer detail for you if you like. Feel free to PM me
Fox
-
@kyle-Hughes its kind of hard for me to follow your configuration and identify what the actual problem is. Maybe you could do a diagram on how each Mango assets links together ?