Recently I’ve been plagued with BOTH of my Honeywell YTH8320ZW1007 thermos failing with “communication lost”. When I mean both, I mean both - at the same time. These devices were added back in January of 2014, and have been very solid performers without any problems until recently.
I do not have range issues (never have) since these thermos have line of sight to several switches that are just within a few feet, and the hub is only 20 feet from 1 of the thermo’s. My zwave mesh is also large, I run a repair process frequently to keep it clean and optimized, and I have no other problems with any other zwave device - at all.
I have found the exact same error message on Vera’s forums for the same model thermo, as well as other sites passed along to me by ST support (which have been excellent in helping figure this out). The only way I get these working again is to pull them away from the mounting plate, wait a few seconds, and put it back. I’ve also excluded and reincluded many times. All to no avail as the dreaded “communication lost” message comes back within a day or two - again, on BOTH thermos.
I am convinced that this is a device problem, not a controller problem…
I think these thermos have a problem with large zwave mesh networks, and can’t handle/process the size of the routing table it has to store. It’s too coincidental for me that this all started when I began adding a lot more zwave devices over the last 2-3 months.
Having these devices go dead is not acceptable. Trying to work with Honeywell’s Customer Dissatisfaction Service Department has only led to agents and their supervision just reading from a playbook of “how can we make this person go away”. Coincidentally, my warranty just expired in the middle of trying to get this resolved - almost exactly a year after purchase; which Honeywell was keen to point out.
I’m left to removing these devices while I search for any replacement that doesn’t come from Honeywell. At the moment I have an Evolve T100r (v4.54) coming soon. I want to stick with zwave as much as possible before I go back to a wifi thermo (been there, done that).
For those with this model thermo, have you experienced this error message?