wkearney99
Senior Member
For me the single biggest impediment to more elaborate home automation is delays incurred by rule processing. As in, you want the motion sensor to properly activate the lights, but do so based on a set of conditions. As in, it's after 10pm, only bring the lights up to 25%, or don't bother bringing them up to 100% if there's already enough daylight from the skylights and it's after 6:30am on a work day vs 9am on a weekend/holiday. Meanwhile, fire an alarm event if there's not supposed to be anyone in the space at all. Lots of variables/conditionals there.
Same thing for handling dimming changes done with a remote or other controls. If it takes too long to do interactive changes commands tend to get stacked up and you end up not being able to make the desired changes without a lot of fiddling.
Indeed, adjusting dimming levels is probably something that can be better handled by pre-programmed scenes, but there's usually a lot of time between using the space and knowing what kind of scenes would be most useful.
Automation has come a long way but recent detours to using cloud-based services has not done us any favors when it comes to responsiveness (or reliability for that matter). But processing times for hardware have dramatically improved in the last decade. Which (if any) automation systems taken effective advantage of this?
There's always the complication of "you can't do it all within one framework" and then it becomes a hodge-podge of lashed together hacks. Which very quickly fails the WAF. So don't think I'm not aware of that.
I ask this more as a discussion starter rather than a quest for a specific answer. But I'm curious as to what, if any, emphasis the different automation schemes have put on response times and interactive-ness? Which ones are already known to be quick, or too slow?
Same thing for handling dimming changes done with a remote or other controls. If it takes too long to do interactive changes commands tend to get stacked up and you end up not being able to make the desired changes without a lot of fiddling.
Indeed, adjusting dimming levels is probably something that can be better handled by pre-programmed scenes, but there's usually a lot of time between using the space and knowing what kind of scenes would be most useful.
Automation has come a long way but recent detours to using cloud-based services has not done us any favors when it comes to responsiveness (or reliability for that matter). But processing times for hardware have dramatically improved in the last decade. Which (if any) automation systems taken effective advantage of this?
There's always the complication of "you can't do it all within one framework" and then it becomes a hodge-podge of lashed together hacks. Which very quickly fails the WAF. So don't think I'm not aware of that.
I ask this more as a discussion starter rather than a quest for a specific answer. But I'm curious as to what, if any, emphasis the different automation schemes have put on response times and interactive-ness? Which ones are already known to be quick, or too slow?