mletenay

It seems various inverter models and/or firmware versions slightly differ in the response data (resp. their lengths).
So I've replaced the primitive response length check with proper checksum and response type validation.
Now it should be more robust in respect to different inverters.

There's no real need for udp traffic sniffing anymore, I believe we have managed to understand most of the protocol.
The python library is still being tweaked here and there, but it is close to being stable.
Although java (which Openhab is written in) is my "native" language, to be honest, I don't have much intention (or time to be more precise) to port it there at the moment.
I was selecting between Home Assistant and OpenHab, decided for the HA and I'm happy so far.

 
 

Bit shift by 8, but it is a big endian encoding so the most significant byte is on the left.
Plus be aware some values need some (sign) conversion magic "if value > 32768 then value = value - 65535".
Look at the python sources, they are pretty self descriptive.
 

It seems various inverter models and/or firmware versions slightly differ in the response data (resp. their lengths).
So I've replaced the primitive response length check with proper checksum and response type validation.
Now it should be more robust in respect to different inverters.

It seems various inverter models and/or firmware versions slightly differ in the response data (resp. their lengths).
So I've replaced the primitive response length check with proper checksum and response type validation.
Now it should be more robust in respect to different inverters.