NOAH 2000 ignores custom MQTT server, still connects to mqtt.growatt.com #172
-
|
Hi, I have GroBro and a TLS Mosquitto broker running with a valid Let's Encrypt certificate (via Cloudflare DNS challenge, domain: When I delete the NOAH 2000 in the ShinePhone app and re-add it via Bluetooth, I set the server to However, the NOAH still connects to There are no connection attempts visible in the Mosquitto logs either. I have two stacked NOAH 2000 units. I'm using iOS with the ShinePhone app. My question: Is there a known trick to force the NOAH to pick up the new server configuration? Do I need to wait until the battery wakes up in the morning and reconnects? Or is there something else I'm missing? Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
|
... battery wakes up in the morning...????? That make me think you are completely emptying your Noahs till they go offline? I had this behavior also, but only when the Noahs were completely discharged. As long as my Noahs stay online the changed Server config is saved and working. I set a discharge limit of 5% to have enough power till the sun is up and charging again. Maybe 5% is not enough in your configuration, but you can test and do not let the Noah go offline due to battery is empty. |
Beta Was this translation helpful? Give feedback.
-
|
sounds like a dns problem. Instead of entering mosquitto.jpra.de have you tried to enter the IP? |
Beta Was this translation helpful? Give feedback.
-
|
Update: After blocking The key was forcing the NOAH to fail connecting to |
Beta Was this translation helpful? Give feedback.
Update: After blocking
mqtt.growatt.comvia AdGuard Home and blocking internet access for the NOAH in FritzBox, the NOAH switched to my custom MQTT broker (mosquitto.jpra.de) on its next reconnect attempt. It is now successfully connected and sending data to GroBro and Home Assistant. 🎉The key was forcing the NOAH to fail connecting to
mqtt.growatt.com, so it had no choice but to use the configured custom server.