Closed jacekpaszkowski closed 4 years ago
It is a device or network issue, the packet data received by OZW is:
0x8000016e
That is
-2147483282
And the scale factor is 100 so you get
-21474832.82
OZW faithfully reports what it gets from the Z-Wave network... Nothing we can do about that. It has even checksum and checksum matches (otherwise OZW would not accept the data).
It has been mentioned before (usually on Neo Wall Plugs):
https://github.com/OpenZWave/open-zwave/issues/1724
Try to unplug those devices an see if the report sane values again.
thank you for clarification
It seems to be a bug in this type of devices. I get these consecutive kWh metering values reported:
37.86 0x00000ECA
-21474798.43 0xFFFFFFFF80000EDD
38.26 0x00000EF2
-21474798.11 0xFFFFFFFF80000EFD
38.40 0x00000F00
So what happens I think is that the the most significant bit is randomly being set. OZW expects a 32-bit signed int, hence the negative readings. According to the docs of this device, the maximum report value is 21474836.47 kWh, which is 0x7FFFFFFF
. The only work around to this device bug would be that somewhere in the software stack this most significant bit is reset to 0. Then we would have:
37.86
38.05
38.26
38.37
38.40
Hi, im using Hass.io on RPi3 with Aeotec Z-Stick Gen 5. HA is using OpenZwave Version 1.4.3452. The problem is with these devices:
I have issues with negative values reported for power consumption (kWh) entities in HA. I also see those values in OZW_Log.txt file. I don't know if it is OZW or device issue? Or maybe there is a fix in never versions of OpenZwave?
Here is some log entries (and here is full log OZW_Log_08.01.2019.zip):
Hope somebody would help.
Jacek.