As I’ve been working on a Thermostat device handler for the Centralite ZigBee thermostat used with Xfinity, I’ve encountered an interesting issue that I’d love to get some feedback on. The handler itself is running smoothly, but I’ve noticed that ZigBee commands aren’t consistently reliable—maybe only 30% of the time. This isn’t just a minor inconvenience; when it comes to scheduling and away/home settings, a single failure can lead to some pretty uncomfortable situations, like the house getting too hot when the thermostat doesn’t adjust as planned.
I’ve observed that this inconsistency doesn’t seem to affect light switches, which use the same ZigBee protocol but rely on SmartThings methods rather than direct attribute writes. My current workaround is to send each command twice with a brief delay in between, but I’m curious if others have found more effective solutions.
Another observation is that while manual temperature adjustments via the UI sometimes require hitting the button twice, it’s the automated scheduling that really causes issues. I’d love to hear how others have tackled this to ensure consistent command execution.
If anyone has tips or alternative approaches, I’d be grateful to hear them! Let’s see if we can crack this together. 