ggiesen / pynavilink Goto Github PK

It looks like there was a fair bit of progress made on this, but I was curious if you managed to discover any more details about the format of the binary API requests/responses?

I started down the path of attempting to decipher the communication protocol being used by the mobile app for my NPE water heater and initially found Matthew1471/Navien-API/issues/1, but this seems to use a different method of authentication than what is used with the current version of the Android app. However, it uses the same port 6001 for the binary protocol and at least the device ID position in the binary response payloads align. I later found PyNaviLink, and see that a bit more aligns with what I have observed in mitmproxy and Wireshark captures with my setup.

I noticed PyNaviLink references a "Channel Information" response and a "State" response and assume that these align with the initial 52 byte binary payload, and second 271 byte binary payloads received. Apart from the device ID, I haven't yet managed to decipher the Channel Information response binary payload, but the State response binary payload has a few other identifiable fields in it.

I am also curious how you were able to derive the parameters used here

In my case, I can see 0x07 0x99 0x00 0xa6 0x37 0x00 before the device ID in the request.

In any case, curious to get your thoughts.