Avoiding external Growatt Cloud Server

[syngron]

Hi there,
Thanks for this awesome tool!

I was wondering if something like Grottserver can be used with the Noah battery.

At Grott there is already an open issue but the protocol needs to be deciphered with a MITM because a TLS connection is used.

I guess because noah-mqtt just uses the web API, we still have no way around that. But possibly there is somebody here who can decrypt the handshake between the battery and the Growatt server?

It would just be awesome to not rely on the cloud anymore to control our batteries!

johanmeijer/grott#560
https://github.com/johanmeijer/grott/wiki/Grottserver

[mtrossbach]

Hey @syngron,

Thanks for the kind words and for raising this interesting point! You're right, currently noah-mqtt relies on the web API, so we're also bound by Growatt's cloud infrastructure.

If anyone in the community has expertise in this area and is willing to explore this possibility and maybe even has a spare device to play with, please do share your insights! It would be a game-changer for open-source integration of Growatt batteries.

Cheers,
Markus

[tnosaj]

I appreciate the work being put into this project as well! it was the reason i went for this battery.

Did you happen to try and play with the urls being set on the initial setup of the battery?

I saw the official MQTT endpoint in the advanced part of the setup, but i just wanted to get it working initially and didnt try to point it to my server.

I also opened up the battery and saw it was using an esp32-s3 for wifi communication (and possibly more), it might have mtls certs on it... I have never played around with reading existing esp32s though, so i dont know if thats a possiblity.