I have a Honeywell ZWSTAT thermostat that had been working mostly fine with the GC2 panel running firmware 1.10, allowing thermostat monitoring and changes via the Alarm.com app. I recently upgraded the GC2 to firmware 1.17.3, and the thermostat fails to communicate, displaying “Lost Connection.” I’ve tried rebooting it several times, and each time it initially reconnects but loses connectivity within about an hour.
Any suggestions?
Looks like the thermostat has been deleted and hasn’t been added back yet, is that correct?
The ZWSTAT is not an officially supported thermostat, but upgrading firmware shouldn’t have any negative effect on compatibility. The Z-wave network may need to be repaired. Have any devices been added, removed, or moved?
When re-adding the Tstat, make sure to run a network rediscovery after all devices are in their permanent locations. I would suggest replacing the batteries as well. Any change?
Hi Warren,
Yes, I removed the thermostat via the GC2 panel. So far, however, I can’t seem to re-enroll it.
Also, what thermostats are officially supported? I can’t seem to find a list.
Warren, FWIW, I doublechecked and the thermostat I have is actually a Honeywell TH8320ZW.
Also, what thermostats are officially supported? I can’t seem to find a list.
A good guideline for device compatibility is the Alarm.com hardware page.
Yes, I removed the thermostat via the GC2 panel. So far, however, I can’t seem to re-enroll it.
Did you delete it from the panel as a failed device? Or did you use “Remove Devices” and perform the pair procedure at the Tstat?
Note that both the panel and the tstat save their Z-wave network link, and only using the following function will remove that link from both. The Thermostat could not be re-learned into another (or the same) network until its network link is cleared:
Services - Z-wave - Wrench Icon - Installer Code - Remove Devices - while the panel listens, perform the link procedure on the tstat.
Jason,
I think I did remove the thermostat as a failed device. Now,when I try to change the setting on the thermostat (by toggling the RF10 state from “1” to “0”,) it attempts to pair for about 30 seconds then says “Action Failed.” It still seems to think it’s device #5 on the network.
Ok, I found a blog posting with a factory reset procedure for the thermostat. Did that and then the panel was instantly able to re-add it as device #17. I’ll see if the connection is any more stable now.
No joy. I’m back to the thermostat showing “Connection Lost” within an hour of re-enrolling it.
Have you performed a network rediscovery at the alarm panel?
Diagnostics are showing the thermostat to have no neighboring nodes, which means it has no communication path other than straight to the panel.
Try running a rediscovery now if you have not as that is required after adding any non-NWI Z-wave device to map routes.
How close are the panel and thermostat when you are re-enrolling? They should be within 6-10 feet of one another to ensure the pairing is 100% successful. Thermostats and locks are heavily affected by this proximity rule.
I know the device may be discovered by the 2GIG panel, but that does not mean it was a successful pair.
Ok, I just tried running a rediscovery. Interestingly, the TS1 keypad and a ZWave lamp module are both within about 10 feet of the thermostat.
Admittedly, the panel and thermostat were a floor apart during the re-enrollment. I’m not sure how I would practicably get them to within a few feet of each other if I did the re-enrollment process.
I guess by followup question is how I would tell the difference between a “superficial” discovery and a truly successful (or unsuccessful) pairing between the panel and thermostat.
The thermostat now seems to have held it’s connection for 12 hours since the last network rediscovery, so I’m encouraged.
I’m not sure how I would practicably get them to within a few feet of each other if I did the re-enrollment process.
The 2GIG Panel can be unplugged and run on battery, brought to the device location to include into its network, then reinstalled in its permanent spot and a network rediscovery run.
I guess by followup question is how I would tell the difference between a “superficial” discovery and a truly successful (or unsuccessful) pairing between the panel and thermostat.
You really wouldn’t until problems occur. While you can get away with learning in devices further away from the controller some of the time, there is no benefit to skipping the proximity if the device is not an NWI device. (Network Wide Inclusion. The Device would be labeled as such, an example is the Remote Temp Sensor)
The thermostat now seems to have held it’s connection for 12 hours since the last network rediscovery, so I’m encouraged.
Yes, in this case I see the Thermostat is now reporting neighbor nodes. Always run a network rediscovery after adding a new Z-wave device to the network, or re-adding a device, as that will remap device communication routes and neighbor nodes.
It looks like it is communicating successfully at this time.
Ok, so, my thermostat has lost connectivity again with no other changes to the Zwave network.
Have you relearned the thermostat into the network with the panel nearby within 6-10 feet? You can unplug the control panel and run it on battery to pair the thermostat close by, then remount the panel, plug in power and run a network rediscovery.