Goodwe Integration can not connect

[xxLexanixx]

The problem

My Inverter can not connect to my Homeassistant since yesterday.

What version of Home Assistant Core has the issue?

core-2024.11.3

What was the last working version of Home Assistant Core?

core-2024.11.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

GoodWe Inverter

Link to integration documentation on our website

https://www.home-assistant.io/integrations/goodwe/

Diagnostics information

2024-11-26 19:28:46.794 DEBUG (MainThread) [goodwe] Connecting to ET family inverter at 192.168.178.10:8899. 2024-11-26 19:28:46.794 DEBUG (MainThread) [goodwe.protocol] Creating lock instance for current event loop. 2024-11-26 19:28:46.795 DEBUG (MainThread) [goodwe.protocol] Sending: READ 33 registers from 35000 (f70388b800213ac1) 2024-11-26 19:28:47.798 DEBUG (MainThread) [goodwe.protocol] Failed to receive response to READ 33 registers from 35000 (f70388b800213ac1) in time (1s). 2024-11-26 19:28:47.798 DEBUG (MainThread) [goodwe.protocol] Sending: READ 33 registers from 35000 (f70388b800213ac1) - retry #1/10 2024-11-26 19:28:48.799 DEBUG (MainThread) [goodwe.protocol] Failed to receive response to READ 33 registers from 35000 (f70388b800213ac1) in time (1s). 2024-11-26 19:28:48.799 DEBUG (MainThread) [goodwe.protocol] Sending: READ 33 registers from 35000 (f70388b800213ac1) - retry #2/10 2024-11-26 19:28:49.800 DEBUG (MainThread) [goodwe.protocol] Failed to receive response to READ 33 registers from 35000 (f70388b800213ac1) in time (1s). 2024-11-26 19:28:49.800 DEBUG (MainThread) [goodwe.protocol] Sending: READ 33 registers from 35000 (f70388b800213ac1) - retry #3/10 2024-11-26 19:28:50.801 DEBUG (MainThread) [goodwe.protocol] Failed to receive response to READ 33 registers from 35000 (f70388b800213ac1) in time (1s). 2024-11-26 19:28:50.801 DEBUG (MainThread) [goodwe.protocol] Sending: READ 33 registers from 35000 (f70388b800213ac1) - retry #4/10 2024-11-26 19:28:51.802 DEBUG (MainThread) [goodwe.protocol] Failed to receive response to READ 33 registers from 35000 (f70388b800213ac1) in time (1s). 2024-11-26 19:28:51.802 DEBUG (MainThread) [goodwe.protocol] Sending: READ 33 registers from 35000 (f70388b800213ac1) - retry #5/10 2024-11-26 19:28:52.803 DEBUG (MainThread) [goodwe.protocol] Failed to receive response to READ 33 registers from 35000 (f70388b800213ac1) in time (1s). 2024-11-26 19:28:52.804 DEBUG (MainThread) [goodwe.protocol] Sending: READ 33 registers from 35000 (f70388b800213ac1) - retry #6/10 2024-11-26 19:28:53.805 DEBUG (MainThread) [goodwe.protocol] Failed to receive response to READ 33 registers from 35000 (f70388b800213ac1) in time (1s). 2024-11-26 19:28:53.805 DEBUG (MainThread) [goodwe.protocol] Sending: READ 33 registers from 35000 (f70388b800213ac1) - retry #7/10 2024-11-26 19:28:54.806 DEBUG (MainThread) [goodwe.protocol] Failed to receive response to READ 33 registers from 35000 (f70388b800213ac1) in time (1s). 2024-11-26 19:28:54.807 DEBUG (MainThread) [goodwe.protocol] Sending: READ 33 registers from 35000 (f70388b800213ac1) - retry #8/10 2024-11-26 19:28:55.807 DEBUG (MainThread) [goodwe.protocol] Failed to receive response to READ 33 registers from 35000 (f70388b800213ac1) in time (1s). 2024-11-26 19:28:55.807 DEBUG (MainThread) [goodwe.protocol] Sending: READ 33 registers from 35000 (f70388b800213ac1) - retry #9/10 2024-11-26 19:28:56.809 DEBUG (MainThread) [goodwe.protocol] Failed to receive response to READ 33 registers from 35000 (f70388b800213ac1) in time (1s). 2024-11-26 19:28:56.809 DEBUG (MainThread) [goodwe.protocol] Sending: READ 33 registers from 35000 (f70388b800213ac1) - retry #10/10 2024-11-26 19:28:57.809 DEBUG (MainThread) [goodwe.protocol] Max number of retries (10) reached, request READ 33 registers from 35000 (f70388b800213ac1) failed. 2024-11-26 19:28:57.810 DEBUG (MainThread) [goodwe.protocol] Socket closed.

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @mletenay, @starkillerOG, mind taking a look at this issue as it has been labeled with an integration (goodwe) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of goodwe can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign goodwe Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

goodwe documentation
goodwe source
_{^{(message by IssueLinks)}}

[BCKouma]

Heya there @xxLexanixx
I had the ssame problem with my unit after switching to a new router.
I solved it by going into the goodwe integration, then clicking the 3 dots next to the current integration-entry and deleting it, followed by re-registering (New Entry) my inverter with its current ip-adress.

After that, everything works again.

I think the new router assigned a new IP adress without publicizing it to the integration, so it wasn't able to find the inverter.

I hope, that my solution helps :)

[visstro]

@BCKouma
I did not change the router and the inverter IP address remained the same... But it actually worked for me to add it again. Hope this will not happen on regular basis.
Thank you for the suggestion!

Not sure if @xxLexanixx faces the same issue.

[visstro]

Lost connection to the inverter again. No IP change.
Had to remove the integration and it was added again without issues.

[sgreenhill]

I suspect that Goodwe has added some authentication in recent inverter firmware.

My new Goodwe GW-5000-DNS-30 will not connect to HomeAssistant UNLESS I have logged into the WLAN device in the SolarGo app using the default password. Following this, it will continue to connect until it enters wait/stop mode at the end of the day. Following this, no connection until (as before) logging in to the SolarGo app.

The same behaviour can be reproduced using the following Python code which is independent of Home Assistant. Therefore the problem is likely due to changed protocol with the inverter. However, this issue will prevent any new or updated Goodwe inverters from using the current integration. A fix would probably involve reverse-engineering the authentication message and presenting this before attempting to connect.

import asyncio
import goodwe

async def get_runtime_data():
    ip_address = '192.168.1.178'      # <-- replace with your inverter's IP address

    inverter = await goodwe.connect(ip_address)
    runtime_data = await inverter.read_runtime_data()

    for sensor in inverter.sensors():
        if sensor.id_ in runtime_data:
            print(f"{sensor.id_}: \t\t {sensor.name} = {runtime_data[sensor.id_]} {sensor.unit}")

asyncio.run(get_runtime_data())

Before authenticating with SolarGo this code returns: ConnectionRefusedError: [Errno 111] Connection refused

After authentication with SolarGo, it returns the correct solar run-time data.

Data from my inverter (reported in SolarGo):
Connected via: Wifi/LAN Kit-20
Model: GW5000-DNS-30
Firmware Version V1.00.00
App Version: 5.8.1
DSP FW Version: 00.8004.00.14
ARM FW Versions: 07.53
Communication Module FW Version: 1.4.59

Note that this issue has been reported on the forums for other inverters: GW-15KET

@mletenay @starkillerOG,

[antonholtzhausen]

I am experiencing the exact same issue as @sgreenhill described above. When I log into the SolarGo app, everything works as expected, and Home Assistant can connect to the inverter. However, after a few hours, the connection drops and stays disconnected until I log back into the SolarGo app. Once I log in again, it works as expected.

To rule out network-related issues, I have set the inverter to a static IP address and even connected it via Ethernet to ensure it is not caused by Wi-Fi dropouts.

Here are the details of my inverter (as reported in the SolarGo app):

Connected via: Wifi/LAN Kit-20
Model: GW9900-MS-30
Firmware Version: V1.00.00
App Version: 5.8.0
DSP FW Version: 00.8004.00.14
ARM FW Versions: 07.53
Communication Module FW Version: 1.4.59

[abdulrehman1937]

I have a similar issue: Home Assistant disconnects after a few hours (8, maybe). Then, I need to open the SolarGo application and connect to my inverter (no need to add any password). After that, I need to reload my device in HA integrations and it starts working again.
Here are the details of my inverter:
Model: GW10K-ES-C10
DSP FW Version: 01.202
ARM FW Version: 10.435
Communication Module FW Version:1.3.53
AFCI FW Version:01

[t-oster]

Same for me. I do not even have to connect from Solar go, the device search it does at startup seems to be enough. When I have time I could try to capture the broadcast Solar go sends on startup and maybe reproduce it.

[DivinityNL]

Kind of glad to see there are more with the same problem. I have the same as sgreenhill. Triggering login with the solargo app is enough to restore the connection to HA. Hopefully there will be a solution soon.

Connected via: Wifi/LAN Kit-20 via Lan cable only and static ip
Model: GW3600-DNS-30
Firmware Version V1.08.05
App Version: 5.9.1
DSP FW Version: 00.8004.00.14
ARM FW Versions: 07.53
Communication Module FW Version: 1.4.59

Thanks in advance

[t-oster]

Hi,
I sniffed the Solar Go packet. It just sends WIFIKIT-214028-READ via UDP Broadcast on Port 48899.
It works for me to add this command to the configuration.yaml:

# Re-enables communication with goodwe inverter
shell_command:
  trigger_goodwe: echo "WIFIKIT-214028-READ"|nc -b -u -w1 255.255.255.255 48899

and add an automation, which triggers this command whenever my sensor value goes lost:

- id: '1736001853550'
  alias: Broadcast Goodwe when sensors are unavailable
  description: ''
  triggers:
  - entity_id: sensor.house_consumption
    to: unavailable
    trigger: state
  - entity_id: sensor.house_consumption
    to: unknown
    trigger: state
  conditions: []
  actions:
  - action: shell_command.trigger_goodwe
    metadata: {}
    data: {}
  mode: single

[t-oster]

but maybe this could be added to the integration itself

[abdulrehman1937]

Hi, I sniffed the Solar Go packet. It just sends WIFIKIT-214028-READ via UDP Broadcast on Port 48899. It works for me to add this command to the configuration.yaml:

# Re-enables communication with goodwe inverter
shell_command:
  trigger_goodwe: echo "WIFIKIT-214028-READ"|nc -b -u -w1 255.255.255.255 48899

and add an automation, which triggers this command whenever my sensor value goes lost:

- id: '1736001853550'
  alias: Broadcast Goodwe when sensors are unavailable
  description: ''
  triggers:
  - entity_id: sensor.house_consumption
    to: unavailable
    trigger: state
  - entity_id: sensor.house_consumption
    to: unknown
    trigger: state
  conditions: []
  actions:
  - action: shell_command.trigger_goodwe
    metadata: {}
    data: {}
  mode: single

Thanks a lot I can confirm it wokred for me.

[antonholtzhausen]

Hi, I sniffed the Solar Go packet. It just sends WIFIKIT-214028-READ via UDP Broadcast on Port 48899. It works for me to add this command to the configuration.yaml:

# Re-enables communication with goodwe inverter
shell_command:
  trigger_goodwe: echo "WIFIKIT-214028-READ"|nc -b -u -w1 255.255.255.255 48899

and add an automation, which triggers this command whenever my sensor value goes lost:

- id: '1736001853550'
  alias: Broadcast Goodwe when sensors are unavailable
  description: ''
  triggers:
  - entity_id: sensor.house_consumption
    to: unavailable
    trigger: state
  - entity_id: sensor.house_consumption
    to: unknown
    trigger: state
  conditions: []
  actions:
  - action: shell_command.trigger_goodwe
    metadata: {}
    data: {}
  mode: single

Thanks, I can confirm this is working for me too!