The general idea of my setup is very simple - to periodically turn ventilation On and Off providing fresh air into the house according to different conditions and also occasionally run air circulation fan (for better mixing up air on two floors).
I only have two devices to operate - Z-Wave modules "A1" and "A2" and they can be On and Off, can have delayed Off actions and can be included into recurring events.
What complicates my system is that I have too many conditions I would like to take into account - temperatures inside and outside, balcony door sensor status, air conditioner state, Home-Away status and some others). Those conditions create wide array of action patterns for my circulation and ventilation modules. Sometimes ventilation should run constantly and circulation would be recurring. If conditions changes ventilation might stop and only circulation would be engaged etc. There are also a couple conditional rules, for example, if air conditioner is On the circulation device must also be On.
What tactics should I use to implement my rules so they would not interfere with each other? I know that HS scans the setup every minute and if certain conditions are met the resulting event would run. I think that my problem is that all of my events are recurring, meaning there are delayed actions or wait commands involved.
What if during the next scan HS determines that conditions have changed and another event must run but some delayed actions might be pending from the previous event? How can the system trace what is pending and decide if the action can be left or must be canceled because it interrupts proper execution of the most recent event?
The diagram I attach is just a fraction of the scheme. I estimate that I might have around 50 different conditions that would result in about 6 different action patterns.
Thanks, Alex
I only have two devices to operate - Z-Wave modules "A1" and "A2" and they can be On and Off, can have delayed Off actions and can be included into recurring events.
What complicates my system is that I have too many conditions I would like to take into account - temperatures inside and outside, balcony door sensor status, air conditioner state, Home-Away status and some others). Those conditions create wide array of action patterns for my circulation and ventilation modules. Sometimes ventilation should run constantly and circulation would be recurring. If conditions changes ventilation might stop and only circulation would be engaged etc. There are also a couple conditional rules, for example, if air conditioner is On the circulation device must also be On.
What tactics should I use to implement my rules so they would not interfere with each other? I know that HS scans the setup every minute and if certain conditions are met the resulting event would run. I think that my problem is that all of my events are recurring, meaning there are delayed actions or wait commands involved.
What if during the next scan HS determines that conditions have changed and another event must run but some delayed actions might be pending from the previous event? How can the system trace what is pending and decide if the action can be left or must be canceled because it interrupts proper execution of the most recent event?
The diagram I attach is just a fraction of the scheme. I estimate that I might have around 50 different conditions that would result in about 6 different action patterns.
Thanks, Alex
Comment