I am suspicious that the Thermostat decided that it lost communications during one of my overnight power cycle sequences.
At 4:13 AM My Incontrol PC executes a full shutdown.
At 4:15 AM an old school lamp timer disconnects the power to the PC.
At 4:16 AM the lamp timer restors power to the PC.
A bios setting on the PC causes it to auto start when AC power is restored.
I do this because in the event the PC becomes unresponsive (blue screens or something) it would be unable to perform a scheduled restart.
Since this PC is running security cameras and other security related processes I need it to work, and to be able to recover itself, without me driving halfway across the state to restart it.
Now that I have a secondary Z-Wave controller running on another box (see my posting about "is this possible" elsewhere in this forum) I plan to install a Z-Wave controlled outlet to force the power off to the PC (from a secondary controller) if it becomes necessary. By doing this I hope to be able to dispense with the lamp timer and the nightly shutdowns. And with a little luck never experience this problem again.
It is also possible that with two controllers the thermostat may still see one of them and not think it has lost communications.
Thanks for your help!
N0VTN
Honeywell Thermostat turned itself off
- 105 Views
- Last Post 18 November 2013
I have a Honeywell Z-wave thermostat which had been working well for about 2 weeks. Yesterday it started showing up in my devices without the ability to adjust the temperature. It is also showing that it is OFF and the temperature is 0 degrees F. The thermostat is at a remote location so I cannot tell what the temperature actually is but since it hasn't been that cold outside I'm sure it isn't down to zero inside. I tried unsuccessfully to turn it back on.
I waited through an overnight power cycle of my InControl PC to see if it would begin working again, but it did not.
I enabled auditing for that device and I have a portion of my log file pasted below. The thermostat is about 15 feet from the controller with one wall in between and 2 other happy z wave devices nearby so communications should not be a problem.
I also ran a heal function which did not help.
I hope the thermostat didn't actually turn off as this will be a real problem in the very near future as winter really gets rolling.
Did my thermostat loose association with my network?
Any suggestions would be appreciated.
Thanks
N0VTN
The logs show that the Thermostat is there and responding, otherwise you'd see other errors in the log saying it didn't respond or that a timeout happened. I don't see anything in the logs suggesting the thermostat is sending back information though. Does anything further down show that it's replying with information?
That section of the log I posted is repeated over and over, there is nothing else except I have a bit of the log beginning immediately after the nightly restart below.
at MLS.HA.ZensysController.ZController.getDeviceLevel(IDeviceInfo deviceInfo, QueuePriority priority) in z:\work\mls\MLS.ZWave.Controller\MLS.HA.ZensysController\ZController.cs:line 3554
at MLS.HA.ZensysController.ZController.pollDevice(IDeviceInfo deviceInfo, QueuePriority queuePriority) in z:\work\mls\MLS.ZWave.Controller\MLS.HA.ZensysController\ZController.cs:line 3592
11/14/2013 4:13:39 AM: Service base running
11/14/2013 4:21:00 AM: Original FolderC:\Windows\system32
11/14/2013 4:21:01 AM: Changed to:C:\Program Files (x86)\Moonlit Software, LLC\InControl HA
11/14/2013 4:21:01 AM: Starting Service
11/14/2013 4:21:01 AM: Preparing service base
11/14/2013 4:21:01 AM: Original FolderC:\Program Files (x86)\Moonlit Software, LLC\InControl HA
11/14/2013 4:21:01 AM: Changed to:C:\Program Files (x86)\Moonlit Software, LLC\InControl HA
11/14/2013 4:21:01 AM: Running service base
11/14/2013 4:21:08 AM: Starting version 3.38.5028.18206
ZenLib: True
StickType:OpenZWave
ComPort:24
Service:True
11/14/2013 4:21:08 AM: Cloud: Attempting to connect to cloud server over chanId: cfa5e...
11/14/2013 4:21:10 AM: Loaded Plugin HaFoscamController
11/14/2013 4:21:10 AM: Loaded Plugin VirtualHaController
11/14/2013 4:21:10 AM: Loaded Plugin WeatherDevicePlugin
11/14/2013 4:21:11 AM: Controller knows about 14 nodes
11/14/2013 4:21:11 AM: Starting commandQueueProcessor
11/14/2013 4:21:12 AM: Cloud: Cloud connected!
11/14/2013 4:21:14 AM: Weather plugin using coordiates 46.849927, -94.792385
11/14/2013 4:21:35 AM: Audit: Command BASICGET entered queue at 11/14/2013 4:21:35 AM. Queue contained 0 commands already.
11/14/2013 4:21:35 AM: Audit for node 15: Command BASICGET being sent. Time in Queue: 0.0120007
11/14/2013 4:21:35 AM: No nodeInfo available for node id 15. This device may not communicate via Secure channels.
11/14/2013 4:21:35 AM: Audit: Command BASICGET completed with result CompleteOk. Time to send: 0.2070118 seconds
11/14/2013 4:21:45 AM: Error reading level from thermostat - System.Exception
Device did not respond.
At this point I have continuously repeating instances of the section I posted.
I have a red exclamation on the thermostat in the devices pane which reads;
Unable to determine if device received command THERMOSTATMODE_SET. Status from device: ResMissing
Would you like to reset this error message?
I have an update on this issue.
The thermostat was in fact in the off state. The temperature inside the cabin was 38 degrees Fahrenheit when I arrived last night. The thermostat was complaining that it had lost communication.
When I manually pressed the "heat" button on the display my heat came back on. But it still had no communication.
I cycled the power to the thermostat by turning off the circuit breaker for about 15 seconds before turning it back on and the device stopped complaining about communications being down. It took a few minutes before the full status of the device began to show up again in InControl, but it all seems to be working now.
I sure hope this doesn't happen again anytime in the next 4 months or so. No heat in an unoccupied building in northern Minnesota in January equals disaster.
Thanks again
N0VTN
I have an update on this issue.
The thermostat was in fact in the off state. The temperature inside the cabin was 38 degrees Fahrenheit when I arrived last night. The thermostat was complaining that it had lost communication.
When I manually pressed the "heat" button on the display my heat came back on. But it still had no communication.
I cycled the power to the thermostat by turning off the circuit breaker for about 15 seconds before turning it back on and the device stopped complaining about communications being down. It took a few minutes before the full status of the device began to show up again in InControl, but it all seems to be working now.
I sure hope this doesn't happen again anytime in the next 4 months or so. No heat in an unoccupied building in northern Minnesota in January equals disaster.
Thanks again
N0VTN
That could be a bad thing! Any idea why it went into offline mode? Perhaps if your t-stat supports it, you could set a lower end temp that would automatically kick it on when it gets low enough despite not having comms. I know my Trane z-wave t-stat can do this, not sure about the Honeywell though.
I am suspicious that the Thermostat decided that it lost communications during one of my overnight power cycle sequences.
At 4:13 AM My Incontrol PC executes a full shutdown.
At 4:15 AM an old school lamp timer disconnects the power to the PC.
At 4:16 AM the lamp timer restors power to the PC.
A bios setting on the PC causes it to auto start when AC power is restored.
I do this because in the event the PC becomes unresponsive (blue screens or something) it would be unable to perform a scheduled restart.
Since this PC is running security cameras and other security related processes I need it to work, and to be able to recover itself, without me driving halfway across the state to restart it.
Now that I have a secondary Z-Wave controller running on another box (see my posting about "is this possible" elsewhere in this forum) I plan to install a Z-Wave controlled outlet to force the power off to the PC (from a secondary controller) if it becomes necessary. By doing this I hope to be able to dispense with the lamp timer and the nightly shutdowns. And with a little luck never experience this problem again.
It is also possible that with two controllers the thermostat may still see one of them and not think it has lost communications.
Thanks for your help!
N0VTN
