Thank you Caseda. It’s interesting because I also have an Aeotec Heavy Duty Switch and that is parsed and does show correctly…one would have thought it would handle the same brand in the same way!
A snapshot of the 2 different messages. Node 29 works, Node 51 does not. I wonder if they are using different versions of the message spec:
| 2020-05-27T19:50:52.620Z | Node[51]: [COMMAND_CLASS_METER] {“Meter Type (Raw)”:{“type”:“Buffer”,“data”:[161]},“Properties1 (Raw)”:{“type”:“Buffer”,“data”:[108]},“Properties1”:{“Size”:4,“Scale”:1,“Precision”:3},“Meter Value”:{“type”:“Buffer”,“data”:[0,0,13,239]}} |
|---|---|
| 2020-05-27T19:50:59.651Z | Node[29]: [COMMAND_CLASS_METER] {“Properties1 (Raw)”:{“type”:“Buffer”,“data”:[33]},“Properties1”:{“Meter Type”:1,“Rate Type”:1,“Scale bit 2”:false,“Meter Type (Parsed)”:{“value”:1,“name”:“Single-E electric meter”},“Rate Type (Parsed)”:{“value”:1,“name”:“Import”}},“Properties2 (Raw)”:{“type”:“Buffer”,“data”:[100]},“Properties2”:{“Size”:4,“Scale bits 10”:0,“Precision”:3},“Meter Value”:{“type”:“Buffer”,“data”:[0,16,148,246]},“Delta Time (Raw)”:{“type”:“Buffer”,“data”:[0,30]},“Delta Time”:30,“Previous Meter Value”:{“type”:“Buffer”,“data”:[0,16,148,246]},“Meter Value (Parsed)”:1086.71,“Previous Meter Value (Parsed)”:1086.71} |
That is indeed the difference, they use a different version number of that command class, though do find it strange that other devices never had this issue, as it is an older version, most likely used by other devices too.
