Could GroBro manage also MIN-TL-XH inverters?

[morettoc]

Hi all, many compliments for this exceptional job.

I have an inverter MIN3600-TL-XH. I tried to install grott and I got the "Grott - grottproxy - Invalid data record received, processing stopped for this record" message. Considering that the endpoint in the working ShinePhone app is "mqtt.growatt.com" and the port is "7006", do you think GroBro could work also for MIN-TL-XH inverters? I'm asking this because I'm not expert and I would avoid to loose time if some of you didn't get success with GroBro + MIN-TL-XH series. Thanks

[robertzaage]

Yes, I don’t think they change much on their side to support new products on their existing MQTT platform. We would need to work on a register mapping by analysing dumped messages over time. So, if you want to support the project basically give it a try. 😊

[NathanealV]

Tried with EMQX and the meter seems to connect successfully. I have received published MQTT payload data which seems to be shown as Hex Strings. How should I interpret this?

[robertzaage]

Nice job! Now you can connect GroBro (with log level debug) to EMQX so that GroBro can try to decode the encrypted messages. I'm unsure on which mapping GroBro falls back if any... Furthermore dumping these messages over a day or two could help this project to analyze them and create a mapping for the ShineWiLan-X2.

[NathanealV]

After changing GroBro to log level debug, it seems that it is receiving those MQTT packets but I keep getting unknown modbus function and unknown msg_type with different codes. How should I map these to registers? Can I simply upload the logs here?

[robertzaage]

I think at this point it would be good, if you could dump these messages into files and send them over by mail or via Matrix. 😄

[NathanealV]

No worries, just sent it through via Matrix

[morettoc]

I think so: with "openssl s_client -showcerts -connect mqtt.xxxxx.duckdns.org:7006" i get cert + intermediate + CA without errors. I'm also able to connect with MQTT Eplorer where I can see SYS$ topic. To highlight that I got from Letsencrypt a certificate signed by E5 intermediate + ISRGRootX1 CA, which has RSA key type, while in your guide you wrote to use E6 + ISRGRootX2 CA, which is ECDSA key type. Tomorrow I will try to get from Letsencrypt a new certificate signed by E6 + ISRGrootX2 Il giorno mar 19 ago 2025 alle ore 17:00 Robert Zaage < ***@***.***> ha scritto:

…

Did you configure TLS with a valid cert? — Reply to this email directly, view it on GitHub <#95 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIYUUWOR3GEV5YQA3ECQISL3OM3ZFAVCNFSM6AAAAACDCWCSUGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMJVGQYDENQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[NathanealV]

@morettoc Any updates from your end?

[morettoc]

Hi, here the default MQTT is mqtt.growatt.com, I'm from Italy. I will test EMQX in the next days and will let you know. Il giorno mar 26 ago 2025 alle ore 10:45 Robert Zaage < ***@***.***> ha scritto:

…

I suspect Growatt isn't following the MQTT spec here, but mosquitto enforces it. Could you try setting up EMQX <https://github.com/emqx/emqx> instance? AFAIK it even has a web interface which makes user creation and certificate import a little easier. Another way would be compiling a modified version of mosquitto yourself (Source: https://forum.cedalo.com/t/client-disconnected-due-to-malformed-packet/956 ) Install using a container: https://docs.emqx.com/en/emqx/latest/deploy/install-docker.html User configuration: https://docs.emqx.com/en/emqx/latest/access-control/authn/mnesia.html Enable TLS: https://docs.emqx.com/en/emqx/latest/network/emqx-mqtt-tls.html — Reply to this email directly, view it on GitHub <#95 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIYUUWM4Q4MYCA6W2SUQASL3PQNC5AVCNFSM6AAAAACDCWCSUGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMRRHEYTGMY> . You are receiving this because you were mentioned.Message ID: ***@***.***>