Hello,
What are people's opinions regarding the best way to use a Honeywell Zwave thermostat?
It has a 7 day programming capability, so it is possible to simply use it as a regular thermostat, and then use HS to apply different setpoints for unusual situations (i.e. HS reckons no one is home for a while).
I'm not quite sure how best to use that approach, though, because there isn't an explicit zwave "run schedule" or "resume schedule" command. Neither is there a "hold temperature" command (as far as I can see).
I think it defaults back to the schedule at the next change if the setpoint is set by zwave, (but I need to check that). This would mean that holding for a long period of time would require re-setting the setpoint after each self-timed change of the thermostat. Ugly...
The alternative is to just dumb down the thermostat (which can be done in the advanced options). Then control the temperature completely with HS. I haven't done this in the past due to past HS2 flakiness, but I'm leaning towards doing this now.
Finally, if one is to consider complete HS control, like this, perhaps it makes most sense to install a bunch of cheap thermostats set to 60F as a back stop to keep the house save in winter if HS dies, and then simply override them with a set of relays in paralllel with the thermostats, controlled by an Arduino. This gives all the funtionality at a fraction of the cost, and furthermore would allow the use of smaller, less obtrusive, thermostats. Clearly temperature information mush be obtained elsewhere, such as from HSM100 units.
Thoughts?
Doug
What are people's opinions regarding the best way to use a Honeywell Zwave thermostat?
It has a 7 day programming capability, so it is possible to simply use it as a regular thermostat, and then use HS to apply different setpoints for unusual situations (i.e. HS reckons no one is home for a while).
I'm not quite sure how best to use that approach, though, because there isn't an explicit zwave "run schedule" or "resume schedule" command. Neither is there a "hold temperature" command (as far as I can see).
I think it defaults back to the schedule at the next change if the setpoint is set by zwave, (but I need to check that). This would mean that holding for a long period of time would require re-setting the setpoint after each self-timed change of the thermostat. Ugly...
The alternative is to just dumb down the thermostat (which can be done in the advanced options). Then control the temperature completely with HS. I haven't done this in the past due to past HS2 flakiness, but I'm leaning towards doing this now.
Finally, if one is to consider complete HS control, like this, perhaps it makes most sense to install a bunch of cheap thermostats set to 60F as a back stop to keep the house save in winter if HS dies, and then simply override them with a set of relays in paralllel with the thermostats, controlled by an Arduino. This gives all the funtionality at a fraction of the cost, and furthermore would allow the use of smaller, less obtrusive, thermostats. Clearly temperature information mush be obtained elsewhere, such as from HSM100 units.
Thoughts?
Doug
Comment