NOAH-mqtt via MQTT no longer works

Nero2025 · February 18, 2025, 4:10pm

Hello,

I have had a NOAH 2000 integrated into my HA for a few months now. I established the connection via MQTT and the noah-mqtt. Everything worked fine until yesterday. Since yesterday I no longer receive any data from NOAH. What have I already tried?

restarted HA
rebuild NOAH addon
uninstalled and reinstalled NOAH Addon
removed the NOAH in the ShinePhone app and set it up again
created a new system in the ShinePhone app and set up the NOAH there

I can see the NOAH in the app and can also customize everything. I can also view all the data on the Growatt website. So the access data is correct.
Does anyone have any more ideas about what I can do?

{"time":"2025-02-18T17:08:34.509015446+01:00","level":"INFO","msg":"set log level","level":"DEBUG"}
{"time":"2025-02-18T17:08:34.509507781+01:00","level":"INFO","msg":"noah-mqtt started","version":"0.0.28","commit":"1b938d958ba9abf1f9ea873842230b155b0ff9b6"}
{"time":"2025-02-18T17:08:34.509699407+01:00","level":"INFO","msg":"running as","username":"root","uid":"0"}
{"time":"2025-02-18T17:08:34.509908824+01:00","level":"INFO","msg":"connecting to mqtt broker","host":"core-mosquitto","port":1883,"clientId":"noah-mqtt","username":"addons"}
{"time":"2025-02-18T17:08:34.51561618+01:00","level":"INFO","msg":"connected to mqtt broker"}
{"time":"2025-02-18T17:08:34.516203015+01:00","level":"INFO","msg":"setting server url","url":"https://server-api.growatt.com"}
{"time":"2025-02-18T17:08:44.690094588+01:00","level":"ERROR","msg":"could not login to growatt account","error":"Post \"https://server-api.growatt.com/newTwoLoginAPIV2.do\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"}
{"time":"2025-02-18T17:08:44.690183255+01:00","level":"ERROR","msg":"PANIC ... waiting 15s to exit ..."}
panic: Post "https://server-api.growatt.com/newTwoLoginAPIV2.do": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
goroutine 36 [running]:
noah-mqtt/internal/misc.Panic({0x3c2ec0, 0x400059a690})
	/home/runner/work/noah-mqtt/noah-mqtt/internal/misc/panic.go:11 +0x98
noah-mqtt/internal/polling.(*Service).Start(0x400009e840)
	/home/runner/work/noah-mqtt/noah-mqtt/internal/polling/service.go:38 +0xdc
main.main.func1({0x3c7a48, 0x40000c0288})
	/home/runner/work/noah-mqtt/noah-mqtt/cmd/noah-mqtt/main.go:54 +0x16c
main.connectMqtt.func1({0x3c7a48, 0x40000c0288})
	/home/runner/work/noah-mqtt/noah-mqtt/cmd/noah-mqtt/main.go:72 +0x84
created by github.com/eclipse/paho%2emqtt%2egolang.(*client).startCommsWorkers in goroutine 21
	/home/runner/go/pkg/mod/github.com/eclipse/[email protected]/client.go:614 +0x5dc
{"time":"2025-02-18T17:09:01.792025784+01:00","level":"INFO","msg":"set log level","level":"DEBUG"}
{"time":"2025-02-18T17:09:01.792524827+01:00","level":"INFO","msg":"noah-mqtt started","version":"0.0.28","commit":"1b938d958ba9abf1f9ea873842230b155b0ff9b6"}
{"time":"2025-02-18T17:09:01.792736287+01:00","level":"INFO","msg":"running as","username":"root","uid":"0"}
{"time":"2025-02-18T17:09:01.792949787+01:00","level":"INFO","msg":"connecting to mqtt broker","host":"core-mosquitto","port":1883,"clientId":"noah-mqtt","username":"addons"}
{"time":"2025-02-18T17:09:01.798375392+01:00","level":"INFO","msg":"connected to mqtt broker"}
{"time":"2025-02-18T17:09:01.798490892+01:00","level":"INFO","msg":"setting server url","url":"https://server-api.growatt.com"}
{"time":"2025-02-18T17:09:11.979062515+01:00","level":"ERROR","msg":"could not login to growatt account","error":"Post \"https://server-api.growatt.com/newTwoLoginAPIV2.do\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"}
{"time":"2025-02-18T17:09:11.979164599+01:00","level":"ERROR","msg":"PANIC ... waiting 15s to exit ..."}

robertklep · February 18, 2025, 4:15pm

github.com/mtrossbach/noah-mqtt

plugin crashed

opened 02:36PM - 03 Feb 25 UTC

javamichi18

hey! thanks for writing such an awesome HA plugin for the growatt noah battery :…) I'm using the plugin now for roughly 2 weeks in my HA installation and it works very well. However ... it crashed during the weekend. I've attached part of my logs (having plantId and serialNr replaced). I'm a developer myself and as part of the debugging process I've tested the server-api.growatt.com API manually with a simple python script (based on growattServer lib) to ensure authentication and access to my battery data on the API works (which it did). (This little experiment affirmed my initial impression that the growatt API and firmware itself is odd (at best) and having a local API on the device itself would be really desirable. The Growatt API and/or web page seemed to have changed during the last days?) Having browsed the noah-mqtt logs I couldn't find a reasonable answer why the connection between my HomeAssistant (on a raspberry5) the the server-api.growatt.com was broken. My network + wifi setup is stable in general and it would not put that into suspicion first. In my case 2 things would be nice to have: * avoid the crash of the plugin (maybe by being able to configure/set longer timeouts) * not having the latest value continuously reported via mqtt (even after the connection to the API has broken) (it took me a while to notice that the plugin crashed, because it continuously kept reporting the latest value before the crash) ### log ``` {"time":"2025-01-28T11:02:43.832870758+01:00","level":"INFO","msg":"set log level","level":"INFO"} {"time":"2025-01-28T11:02:43.833556032+01:00","level":"INFO","msg":"noah-mqtt started","version":"0.0.28","commit":"1b938d958ba9abf1f9ea873842230b155b0ff9b6"} {"time":"2025-01-28T11:02:43.833999651+01:00","level":"INFO","msg":"running as","username":"root","uid":"0"} {"time":"2025-01-28T11:02:43.83406018+01:00","level":"INFO","msg":"connecting to mqtt broker","host":"core-mosquitto","port":1883,"clientId":"noah-mqtt","username":"addons"} {"time":"2025-01-28T11:02:43.999519782+01:00","level":"INFO","msg":"connected to mqtt broker"} {"time":"2025-01-28T11:02:43.999543212+01:00","level":"INFO","msg":"setting server url","url":"https://server-api.growatt.com"} {"time":"2025-01-28T11:02:44.180591862+01:00","level":"INFO","msg":"fetching plant list"} {"time":"2025-01-28T11:02:44.200785443+01:00","level":"INFO","msg":"fetch plant details","plantId":<my_plant_id>} {"time":"2025-01-28T11:02:44.21998022+01:00","level":"INFO","msg":"found device sn","deviceSn":"<my_serial_nr>","plantId":<my_plant_id>,"topic":"noah2mqtt/<my_serial_nr>"} {"time":"2025-01-28T11:02:44.248101979+01:00","level":"INFO","msg":"start polling growatt","interval":10,"battery-details-interval":60,"parameter-interval":60} {"time":"2025-01-28T17:00:20.58778992+01:00","level":"ERROR","msg":"could not get device data","error":"Post \"https://server-api.growatt.com/noahDeviceApi/noah/getSystemStatus\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)","device":"<my_serial_nr>"} {"time":"2025-02-02T12:46:38.000961316+01:00","level":"ERROR","msg":"could not get device data","error":"request failed: (HTTP 502 Bad Gateway) <html>\r\n<head><title>502 Bad Gateway</title></head>\r\n<body bgcolor=\"white\">\r\n<center><h1>502 Bad Gateway</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n\r\n\r\n\r\n\r\n\r\n\r\n","device":"<my_serial_nr>"} {"time":"2025-02-02T12:46:53.873226739+01:00","level":"ERROR","msg":"could not get parameter data","error":"Post \"https://server-api.growatt.com/noahDeviceApi/noah/getNoahInfoBySn\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)","device":"<my_serial_nr>"} {"time":"2025-02-02T12:46:58.00192189+01:00","level":"ERROR","msg":"could not get device data","error":"Post \"https://server-api.growatt.com/error.do?errorMess=errorNoLogin\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)","device":"<my_serial_nr>"} {"time":"2025-02-02T12:46:58.093003043+01:00","level":"ERROR","msg":"could not get battery data","error":"Post \"https://server-api.growatt.com/noahDeviceApi/noah/getBatteryData\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)","device":"<my_serial_nr>"} {"time":"2025-02-02T12:47:18.004555793+01:00","level":"ERROR","msg":"could not get device data","error":"Post \"https://server-api.growatt.com/error.do?errorMess=errorNoLogin\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)","device":"<my_serial_nr>"} {"time":"2025-02-02T12:50:58.831835996+01:00","level":"ERROR","msg":"could not get device data","error":"Post \"https://server-api.growatt.com/error.do?errorMess=errorNoLogin\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)","device":"<my_serial_nr>"} {"time":"2025-02-02T12:51:15.210751777+01:00","level":"ERROR","msg":"could not get battery data","error":"Post \"https://server-api.growatt.com/error.do?errorMess=errorNoLogin\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)","device":"<my_serial_nr>"} {"time":"2025-02-02T12:51:28.429672688+01:00","level":"ERROR","msg":"could not get device data","error":"Post \"https://server-api.growatt.com/noahDeviceApi/noah/getSystemStatus\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)","device":"<my_serial_nr>"} {"time":"2025-02-02T12:51:48.431852949+01:00","level":"ERROR","msg":"could not get device data","error":"Post \"https://server-api.growatt.com/error.do?errorMess=errorNoLogin\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)","device":"<my_serial_nr>"} {"time":"2025-02-02T12:52:13.646386124+01:00","level":"ERROR","msg":"could not re-login","error":"Post \"https://server-api.growatt.com/newTwoLoginAPIV2.do\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"} {"time":"2025-02-02T12:52:13.646413012+01:00","level":"ERROR","msg":"PANIC ... waiting 15s to exit ..."} panic: Post "https://server-api.growatt.com/newTwoLoginAPIV2.do": context deadline exceeded (Client.Timeout exceeded while awaiting headers) goroutine 87 [running]: noah-mqtt/internal/misc.Panic({0x3c2ec0, 0x400027cab0}) /home/runner/work/noah-mqtt/noah-mqtt/internal/misc/panic.go:11 +0x98 noah-mqtt/internal/growatt.(*Client).postForm(0x4000072380, {0x40003c0190, 0x41}, 0x4000249ca0, {0x2b8e00, 0x400013ab40}) /home/runner/work/noah-mqtt/noah-mqtt/internal/growatt/client_http.go:47 +0x548 noah-mqtt/internal/growatt.(*Client).GetNoahStatus(0x4000072380, {0x400000e610, 0x10}) /home/runner/work/noah-mqtt/noah-mqtt/internal/growatt/client.go:126 +0x140 noah-mqtt/internal/polling.(*Service).pollStatus(0x400006a600, {0x400000e610, 0x10}) /home/runner/work/noah-mqtt/noah-mqtt/internal/polling/service_steps.go:10 +0x38 noah-mqtt/internal/polling.(*Service).poll.func1() /home/runner/work/noah-mqtt/noah-mqtt/internal/polling/service.go:144 +0x60 created by noah-mqtt/internal/polling.(*Service).poll in goroutine 86 /home/runner/work/noah-mqtt/noah-mqtt/internal/polling/service.go:141 +0x21c ```

stevemann · February 18, 2025, 4:21pm

Install the MQTT Explorer add-on and see what the MQTT messages look like. It may not help but it’s worth knowing what the data looks like.

Nero2025 · February 18, 2025, 4:25pm

I have already tried, but I can’t get a connection or an answer either

stevemann · February 18, 2025, 4:26pm

That should be a clue. Connection to what? You connect the MQTT Explorer to the MQTT broker, then watch the data it handles.

robertklep · February 18, 2025, 4:27pm

Read the comment on Github I linked to, it’s a known issue with the Growatt API.

Nero2025 · February 18, 2025, 4:31pm

If I have understood correctly, there is no solution for this yet, is there? I also contacted Growatt support yesterday because the ShinePhone app no longer works when there is a WLAN connection. According to support, someone in China is currently working on the app, which can have such effects. It could take up to 2 days. My fear was that there is a connection here. However, other users of the NOAH apparently have no connection problems in the HA.

robertklep · February 18, 2025, 4:34pm

From what I understand from the message on Github, the NOAH-mqtt integration uses the same API as the Shine app, so that would explain why the Shine app also isn’t working and you’d have to wait until it gets fixed.

I don’t know why it would still work for others, could be a geographical thing.

Nero2025 · February 19, 2025, 5:25am

Today everything is working again and without any changes on my side. The problem with the ShinPhone app in the WLAN has also been solved. Obviously the work in China is finished.