Aeotec energy meter assigning value of one meter to another meter

Hi @chris

I have 2 single phase energy meter node 28 and node 30.
Issue is that, at some point of time the value of node 28 assign to node 30, after few seconds value of node 30 again reverted to correct one.
I am not understanding why this happen…?
i am providing my items entry and events log when issue occurred…?

Number METER_28 {zwave=“28:1:command=METER,meter_scale=E_KWh,refresh_interval=0”}

Number METER_30 {zwave=“30:1:command=METER,meter_scale=E_KWh,refresh_interval=0”}

Events Log:

2016-11-29 23:22:45 - METER_28 state updated to 29.428
2016-11-29 23:23:50 - METER_30 state updated to 6.523
2016-11-29 23:24:55 - METER_28 state updated to 29.434
2016-11-29 23:24:55 - METER_28 state updated to 29.434
2016-11-29 23:24:55 - METER_30 state updated to 29.434
2016-11-29 23:24:55 - METER_30 state updated to 6.523

From above log you see that , at time 2016-11-29 23:24:55 value of node 30 is same as node 28 i.e 29.434 and in last log line again node 30 value changed to 6.523.

There are no logs for this in openhab.log file as debug logs are disabled.

Is there a bug in openhab or in energy meter ?

Thanks and regards,
shrikant

I would be surprised if there’s a bug in the binding that incorrectly allocates data from one node to another - this sort of thing would show up elsewhere if the node number wasn’t being correctly used in the binding. There’s no mechanism that I can think of that would allow this sort of cross node corruption. That said, given this appears to be two devices, it’s hard to say that the bug is in the device either.

Without a log though, I’m afraid I can’t say much more - I’d just be guessing - sorry.