I have a problem where maybe once every 2 weeks, a scene that sets the thermostat sets it at the max (90 degrees). This is generally when we're going to sleep which sucks because by the time you wake up due to the heat, you are in a sauna.
I have no idea what causes this, it could be the thermostat (Honeywell YTH8320ZW1007/U), or an odd communications issue, but it keeps me from using my thermostat via z-wave.
My question is: Any quick fix?
-OR-
Is there a way to set up a rule to monitor current temp, and reset the scene if the temp is over a certain threshold?
Script to check thermostat/thermostat problem
- 61 Views
- Last Post 04 March 2013
Brian-R
posted this
23 February 2013
MadSci
posted this
23 February 2013
You might try deleting your scene or rule and then re-writing it. Maybe there is some confusion going on about which temperature setpoint is for cool and which is for hot. Is it going to the temperature you set for Cool?
I've also requested that there be the ability to write rules to watch the thermostat temperature and run scripts like email so alert me of a problem. This is one of the biggest features I wanted to have when first starting this home automation project.
Brian-R
posted this
24 February 2013
Well, it happens on both a 'wake' scene and a 'sleep', so I don't believe it's the actual scene, as it happens on both. I also have both the cool and heat temps set correctly. It's happens seemingly randomly, but only during a temp change.
Ryan-Scott
posted this
25 February 2013
Is there any mention of the value "90" anywhere in your scenes? It's an odd value to pick, that's for sure.
You could write a rule that checks it every X minutes and if it's at 90, it could set it down accordingly. Watch the YouTube video that is linked in the rules section of InControl as a sample guide. To sum up, here's what you'll want to do:
1 - Create a device from your t-stat's "Heating1" setpoint by selecting the t-stat and then clicking the blue button next to where you see Heating1
2 - Use the device you created in #1 as a condition for your new rule. The rule will basically check if that value = 90.
3 - Have the rule activate a scene to change your heating setpoint to a new value.
4 - Repeat the rule every X intervals (couple minutes should work)
If you wanted, you could create two duplicate rules and add time conditions to it and then have one of them activate wake while the other activates sleep.
Also, check your logfile.txt and see if it says anything about setting the temp to 90. You should see a line like this in there:
Sending THERMOSTATSETPOINTSET command for x. Type: 2, New Temp: y
Brian-R
posted this
25 February 2013
I just checked, it sets it at 99 (max value)
I'm traveling this week, I'll look I to this more when I get home,
Thanks
Brian-R
posted this
03 March 2013
I don't see this blue button.
Also (thoughts?) [code]3/3/2013 8:19:58 AM: Error during Thermostat query and setup:The command timed out before a response was received. 3/3/2013 8:20:29 AM: ZWave Device Count: 14 3/3/2013 8:20:59 AM: Error in setSetPoint:The command timed out before a response was received. 3/3/2013 8:21:29 AM: Error polling device level. NodeId 2 - ControlThink.ZWave.CommandTimeoutException The command timed out before a response was received.[/code]
Ryan-Scott
posted this
03 March 2013
[quote=Brian R]I don't see this blue button.
Also (thoughts?) [code]3/3/2013 8:19:58 AM: Error during Thermostat query and setup:The command timed out before a response was received. 3/3/2013 8:20:29 AM: ZWave Device Count: 14 3/3/2013 8:20:59 AM: Error in setSetPoint:The command timed out before a response was received. 3/3/2013 8:21:29 AM: Error polling device level. NodeId 2 - ControlThink.ZWave.CommandTimeoutException The command timed out before a response was received.[/code][/quote]
Switch to the beta z-wave controller to get the blue button to show up (in your tools/options page).
You may have bigger issues though; it appears that your usb stick doesn't have a good communication link to your thermostat (that's what the time-out issues in your logs generally mean). You may need to add some more devices to your network between your usb stick and thermostat to boost your network strength. Sometimes it could help to exclude and then re-add the device again too, though this will mean you'll need to re-program any rule or scene related to your t-stat.
Brian-R
posted this
04 March 2013
[quote=rscott]I don't see this blue button.
Also (thoughts?) [code]3/3/2013 8:19:58 AM: Error during Thermostat query and setup:The command timed out before a response was received. 3/3/2013 8:20:29 AM: ZWave Device Count: 14 3/3/2013 8:20:59 AM: Error in setSetPoint:The command timed out before a response was received. 3/3/2013 8:21:29 AM: Error polling device level. NodeId 2 - ControlThink.ZWave.CommandTimeoutException The command timed out before a response was received.[/code]
Switch to the beta z-wave controller to get the blue button to show up (in your tools/options page).
You may have bigger issues though; it appears that your usb stick doesn't have a good communication link to your thermostat (that's what the time-out issues in your logs generally mean). You may need to add some more devices to your network between your usb stick and thermostat to boost your network strength. Sometimes it could help to exclude and then re-add the device again too, though this will mean you'll need to re-program any rule or scene related to your t-stat.[/quote]
I'll set up a rule to reset it, and remove/add it tot he network. The t-stat is almost line of site from my computer, about 25ft away with 4 devices between the 2.
