#Zooz Q Sensor Illuminance reporting negative above a cutoff for some reason.

6 messages · Page 1 of 1 (latest)

jovial shale
#

I bought one of these last week and have it up and running and it works for the single automation using illuminance I have for it but when looking at the history of values it sends to HA for the current illuminance level it's all over the map. Why is it reporting negative lux at all?? It looks like once the reported lux is higher than about 32,600, it subtracts twice that amount from the current reading. Anybody have an idea why? If something's really screwy with the sensor I suppose a bodge would be create a custom math function to report the correct value if the lux is reported to be above that threshold.

image.png
tepid coral
#

32768 is the cut-off for a 15-bit number, almost certainly seems like some kind of signed vs unsigned int mismatch.

jovial shale
#

Felt like an int issue. There should be an easy way to use a helper or something (I haven't touched that kind of thing) to report "val if under 32768 else value + (32768*2) ?

tepid coral
#

yes that would be a template sensor

#

Feels like maybe good to report an issue to zwavejs as well