This means that the message that is received from the device is incomplete or corrupt and the binding is unable to process it. If you go a debug log we could confirm exactly what was wrong.
Try to reset the device - this is probably a problem with the data the device is sending, and not the binding. If you are sure it’s a binding issue, then please provide a debug logfile so I can confirm.
The 32 is the command class, and the 02 is the command, the 21 is the meter type - there is no data included, and this is why the binding complains that the command is too short to process. The 03 before this says that the frame is 3 bytes long (as we see) and this is too short for the meter data for starters. This length comes from the device, so we can confirm that the data was sent incorrectly from the device.
O.k., what does that mean? is the device broken?
what should I do? How can I perform a reset?
I’m grateful for hints and can also do a few experiments if it is helpful …
It means the device is sending incorrect data and you should reset it.
Reset the device and see if it sorts itself out - it probably will.
For starters I would suggest to just power it off and back on - I think that that normally resolves these sort of issues, but I don’t have this device, so can’t really be too specific - sorry.
Sorry - there’s not a lot I can do. This is not a binding problem as I explained previously - the device is sending invalid data. I could reduce the logging down from ERROR to INFO though.
@chris I hope that you will do that for all Greenwave devices, as there versions with country dependent powerplugs with 1, 5 or 6 plugs. Error indicates for me something I have to solve. Thank you for you great work on the bindings and happy season.
Sorry - there’s not a lot I can do. This is not a binding problem as I explained previously - the device is sending invalid data. I could reduce the logging down from ERROR to INFO though.
I was referring to your proposal to change ERROR to INFO for the messages in this thread.
I just checked - I updated this a couple of days back. I changed it to WARN… I could reduce it further, but as always there’s a compromise - I could nearly convince myself to make this DEBUG if there’s a consensus?
I have the exact same error on both my GWPN1 nodes.
The error does not always occur. But only sometimes. Any fix for the issue? Its not really critical as it is only a meter report.