I had a problem yesterday where the Pearl thermostat wasn't sending updates. I've since added a rule to have it refresh every 2 minutes.
This morning the thermostat is now not reporting it's correct OperatingState. I'm looking at the thermostat and it's in Heat mode and the little flame icon is on, which should be OperatingState = heating. Hubitat shows it as idle no matter what I do.
Any thoughts or ideas would be appreciated.
Is the source code to the Generic Thermostat Driver available somewhere?
While our zigbee devices may have worked well in the same configuration with other controllers, Hubitat really relies on a strong mesh for zigbee (and z-wave) devices to work well. There's a support document describing a recommended approach to build a strong mesh:
I had this problem.. I noticed the thermostat would randomly send the update in the wrong byte order causing it to always be idle. I ended up replacing them rather than fight it..
No. However, I think @bcopeland's experience indicates the Honeywell T6 zwave+ thermostat is more reliable than the Centralite Pearl.
Personally, I think the consistent communication failure you've experienced is more indicative of mesh issues rather than a sporadic malformed data packet that leads to a false "idle".
Ok, I should have looked at the zigbee logs before I messed with things, but after moving my WiFi APs to different channels and changing the zigbee channel and re-pairing my Xiaomi Temperature sensors I have one Keen vent with an RSSI of -85, one that's -72, several at -71 and the rest of my zigbee devices are below that.
I'll report back later about the OperatingState updating. Don't want to turn the heat on right now.