This is pretty random, but has anyone happened to notice that these things have pretty inaccurate clocks? They seem to consistently check in at 12:12-13 rather than 12:00 - that is, they seem to lose about a minute or so per hour - not exactly a Rolex! It's no big deal, but I thought it was amusing. Pretty consistent across all of the ones that I have:
They do seem to lose time in between updates.
Either that or internally they don't do the calculation correctly on when to wake up. I've seen both happen in devices.
Since the exact timing on this device is not critical to its function it might be using some sort of very low powered time keeping mechanism that is not super accurate. If that's the case, good to save some battery.
I don't know why but with this driver, the sensor neve report his status in event tab. I go back with the built-in driver and the sensor report 2 times each days.
I use the app " Device activity check" and with the status report not receiving the zse42 is always in fault.
Interesting. Honestly it is probably better to use the in-box driver. This driver doesn't add much, and the in-box one is widely used and known to work well.
I use the in-box driver at this point myself.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
