Goodwe inverter disconnected every day

Configuration
1

Hi,

I read allot of discussions but there seems to be no one that has my kind of problem or there is no clear answer to me what to do. so here it is:

I use the Goodwe inverter intergration. All seemed to be working after installation but the next day the sensor was not available. (SEMS is still working fine) I started to look at it a few days trying things. What i found out was that the service is back after connecting with the solarGo app. I dont even have to login but only the attempt will do the trick.

i read about yaml changes but there is no code for this. The codes i found to put there didnt do anything. Most are the because of the polling, i dont think thats my problem anyway.

The question now is what do i have to do that it is working in HA without everytime having to activate it.

2

Hi, I can confirm the problem. I sniffed the packet SolarGO is sending, which causes the data to re-appear in Home-Assistant.
It seems as if running echo "WIFIKIT-214028-READ"|nc -b -u -w1 255.255.255.255 48899 will resolve the issue, so I am adding a shell-command to HA:

shell_command:
    trigger_goodwe: echo "WIFIKIT-214028-READ"|nc -b -u -w1 255.255.255.255 48899

and add an automation to trigger this when the sensor value becomes unavaibable:

alias: Reconnect Goodwe on lost connection
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

I just created the automation, so it is not tested yet

1 Like
3

Did this work? I have the same issue. GoodWe disconnects daily from HASS and if I login to the SolarGo app it reconnects. Just wondering before I deploy your fix

4

Wondering the same…

5

I have the same issue. Manually executing your shell command on the raspi seems to wake the inverter up.
I want to try to execute the command via automation.
I know how to set up the automation. But I need help to set up the shell command. Where do you enter this in HA?

6

Hi all

I´ve got the same issue. Somebdy can help us??

Thanks in advance

7

I have the same problem and I can confirm, that triggering the command from shell: echo “WIFIKIT-214028-READ”|nc -b -u -w1 255.255.255.255 48899 re-enables the contact with the Goodwe inverter.

8

I have the same problem with ha and my Goodwe GW6000-ES-20, Âżany solution? any automation for do it? thanks

9

Sorry for the delay!
Well, I used a “brute force” solution…
Below, how I arrived (and which assumptions I made) to this solution and how I implemented it:

  1. As soon as you open the GoodWe app on your smartphone, the integration starts working and keeps working for almost a day, then stops;

  2. I sniffed the packets the app sends and discovered that it sends a string (WIFIKIT-214028-READ) to the network.

  3. Searching the Internet I found that other user (sorry, I don’t remember who to give him/her credit) had arrived to the same conclusion the same way I did, so the string was the same no matter what.

  4. The solution, thus, would be injecting the same string in my network, periodically.

  5. I assumed that one hour would be a good interval.

  6. Then I:

a. Put the following line on my CONFIGURATION.YAML, which would propagate the string to my network:

shell_command:
trigger_goodwe: echo “WIFIKIT-214028-READ”|nc -b -u -w1 255.255.255.255 48899
(only 2 lines!)

b. Created the following automation, which would call the line above every hour:

alias: GoodWe - Send string and reload
description: “”
triggers:

  • trigger: time_pattern
    minutes: “5”
    conditions:
    actions:
  • action: shell_command.trigger_goodwe
    data: {}
  • action: homeassistant.reload_config_entry
    metadata: {}
    data:
    entry_id: 01JS9EFJCZ3AHCN5CDMB2Z4K58
    target:
    device_id: 17d61b85a7e78f0fd4862ffce5af9911
    mode: single

You can, alternatively, use “Automations” from the Settings section. Below, an image of it:

image
image1495Ă—689 33.7 KB

As you see, it was a “hammer and screwdriver” solution, as we say here in Brazil…
Any doubts, please contact me!

1 Like
10

Hi,

Is this related to a specific Goodwe device because I don’t have issues?
I’m using;

afbeelding
afbeelding323Ă—210 7.84 KB

Edit:
I block communication to the world wide web for my Goodwe inverter. Local only.

11

My inverter disconnects at the end of the day because it essentially goes offline when it is dark and the solar system isn’t doing anything.

The integration automatically reconnects the following morning, however, without any intervention from me or the SEMS+ app on my phone.

image
image419Ă—260 10.2 KB

12

Hi,

Strange firmware mismatch between 2 identical devices…

13

Different regions might run different firmware to meet local electrical regulations, maybe… I’m in Australia.

1 Like
14

Check! Dutch man here :wink: thanks for responding.

15

keen to see if this works! will update after a few days if it works for me

16

I have the same issue on my Goodwe GW15K-ET. It stops responding each night at 2am (CET).
Using the following scripts seems to work so far

shell_command:
  trigger_goodwe: 'echo "WIFIKIT-214028-READ" | socat - UDP-DATAGRAM:255.255.255.255:48899,broadcast'

This goes into configuration.yaml

alias: Goodwe activation
description: replace with your description
triggers:
  - entity_id:
      - sensor.battery_state_of_charge_2
    from: null
    to: unavailable
    trigger: state
conditions: []
actions:
  - data: {}
    action: shell_command.trigger_goodwe
mode: single

This is the automation using the DC battery state but it could be any sensor available on the inverter

I am very much not in the programming/github business so if anybody knows how to commit this issue to the developers of the integration, please do so. It appears to be to something that needs to be a part of the default integration.

17

Corretion:

echo "WIFIKIT-214028-READ"|nc -b -u -w1 255.255.255.255 48899

That original line works so far!