I've been having some issues with my thermostat ever since the incontrol server updated to the newest version.
When using the app and changing the settings, the delay can be up to over a min if it goes at all. Sometimes I actually have
to close the app and redo the input again and it takes, but only after a long delay.
So example, my thermostat is set to 65 w/ the Heat On if it gets below 65. If I change the temmp to lets say 68 the app will allow me to change it but it won't update. I close the app and open it again and change it to 68 and then it updates. This also happens if i try to turn the heat off. I go into the app turn heat to off, and it does nothing. I close the app, go back into it, change it to off and maybe if it does work it shuts off 30-1min later.
Delay w/ thermostat
- 71 Views
- Last Post 06 November 2013
Just to add, my other light switches have no delay and I rarely see problems with them.
Just to add, my other light switches have no delay and I rarely see problems with them.
First of all, are you using the beta zwave controller? If you are able to you should switch to that -- it's in the tools/options menu.
Could you examine your logfile.txt and see if you have any type of devices showing a delay? You might also double click your thermostat and turn on the audit. The audit will let you see more complete information about what's going on, how long a command sits in the queue, etc. Be sure to restart your service after setting the audit by going offline/online again.
Once you do this, if you'd like, we can analyze your log file for you. Just use the contact us page to open up a support ticket with your logfile attached to it.
I am using the beta, I'll give it a try and see and let you know.
Thanks for the help!
can't seem to the contact us thing to work. gives me an error when I try to add the log file lol..i'm full of problems it seems.
Anyway here is some of the log if it helps.
11/5/2013 10:36:38 PM: Audit for node 3: Command BASICGET being sent. Time in Queue: 43.9505138
11/5/2013 10:36:40 PM: Audit: Command BASICGET completed with result CompleteOk. Time to send: 1.172067 seconds
11/5/2013 10:36:40 PM: Audit for node 3: Command THERMOSTATFANMODEGET being sent. Time in Queue: 35.2210145
11/5/2013 10:36:41 PM: Audit: Command THERMOSTATFANMODEGET completed with result CompleteOk. Time to send: 1.1730671 seconds
11/5/2013 10:36:41 PM: Audit for node 3: Command THERMOSTATMODEGET being sent. Time in Queue: 36.4930873
11/5/2013 10:36:42 PM: Audit: Command THERMOSTATMODEGET completed with result CompleteOk. Time to send: 1.1720671 seconds
11/5/2013 10:36:42 PM: Audit for node 3: Command BASICGET being sent. Time in Queue: 17.7640161
11/5/2013 10:36:43 PM: Audit: Command BASICGET completed with result CompleteOk. Time to send: 1.1730671 seconds
11/5/2013 10:36:44 PM: Audit for node 3: Command THERMOSTATSETPOINTSET being sent. Time in Queue: 16.8519639
11/5/2013 10:36:44 PM: Audit: Command BASICSET entered queue at 11/5/2013 10:36:44 PM. Queue contained 21 commands already.
11/5/2013 10:36:44 PM: Audit: Command BASICGET entered queue at 11/5/2013 10:36:44 PM. Queue contained 22 commands already.
11/5/2013 10:36:45 PM: Thermostat: Setpoint to 66
11/5/2013 10:36:45 PM: Audit: Command THERMOSTATSETPOINTSET completed with result CompleteOk. Time to send: 1.1750672 seconds
11/5/2013 10:36:45 PM: Audit for node 3: Command THERMOSTATSETPOINTSET being sent. Time in Queue: 17.9650275
11/5/2013 10:36:46 PM: Thermostat: Setpoint to 65
11/5/2013 10:36:46 PM: Audit: Command THERMOSTATSETPOINTSET completed with result CompleteOk. Time to send: 1.1740672 seconds
11/5/2013 10:36:46 PM: Audit for node 3: Command THERMOSTATFANMODEGET being sent. Time in Queue: 11.5856626
11/5/2013 10:36:47 PM: Audit: Command THERMOSTATFANMODEGET completed with result CompleteOk. Time to send: 1.1730671 seconds
11/5/2013 10:36:47 PM: Audit for node 3: Command THERMOSTATMODEGET being sent. Time in Queue: 12.8587354
11/5/2013 10:36:47 PM: Audit: Command THERMOSTATMODEGET completed with result ResMissing. Time to send: 0.0250015 seconds
11/5/2013 10:36:48 PM: Audit for node 3: Command BASICSET being sent. Time in Queue: 3.3251902
11/5/2013 10:36:49 PM: Audit: Command BASICSET completed with result CompleteOk. Time to send: 1.0460598 seconds
11/5/2013 10:36:49 PM: Audit for node 3: Command BASICGET being sent. Time in Queue: 4.476256
11/5/2013 10:36:50 PM: Audit: Command BASICGET completed with result CompleteOk. Time to send: 1.0610607 seconds
11/5/2013 10:36:50 PM: Audit for node 2: Command BASICGET being sent. Time in Queue: 86.5979531
11/5/2013 10:36:51 PM: Audit: Command BASICGET completed with result CompleteOk. Time to send: 1.067061 seconds
11/5/2013 10:36:51 PM: Audit: Command THERMOSTATSETPOINTGET entered queue at 11/5/2013 10:36:51 PM. Queue contained 17 commands already.
11/5/2013 10:36:51 PM: Audit: Command THERMOSTATSETPOINTGET entered queue at 11/5/2013 10:36:51 PM. Queue contained 18 commands already.
11/5/2013 10:36:51 PM: Audit: Command SENSORMULTILEVELGET entered queue at 11/5/2013 10:36:51 PM. Queue contained 19 commands already.
11/5/2013 10:36:51 PM: Audit: Command THERMOSTATOPERATINGSTATE_GET entered queue at 11/5/2013 10:36:51 PM. Queue contained 20 commands already.
Notice how it shows "time in queue: 34..."
That means the command was waiting to be sent for 34 seconds. It appears you've got a device in your network that isn't responding, so it's slowing everything down. Here's a few things to do:
- Make sure you are not polling any battery powered devices such as motion sensors or door/window sensors.
- If you are polling a lock, turn the poll time up as locks generate a lot of traffic
- Make sure you don't have a device that's too far out of range, as this can also slow your network down.
You can recognize that something is amiss if you watch the light on your USB stick. If it's waiting for something to communicate back, it'll usually go dark for a while. If this happens, something is wrong with the device being spoken to.
