Sending the “magic packet” did not prevent the daily disconnect from happening (so for me there was no point in running an automation like every 15 minutes). Since the disconnect happened exactly at the same time every day I could even send “magic packets” in the minutes before the expected disconnect. Didn’t matter. In the end I created an automation that ran just a minute after the known disconnect time. That worked for the few days the WI-FI/LAN KIT 2.0 was connected to the inverter.
I’m back to using the old “WI-FI KIT” (the not 2.0) now. No HA disconnects with that, but really unreliable SEMS connection (which I don’t need anyway) as I said. I’ll only plug in the 2.0 stick if support needs a connection.
Same issue here, after running stable after a long time. I think it is firmware related.
I use the WIFI/LAN kit (not sure which version, 3 years old) with gw6k-dt inverter (prod date 2020)
I used to block the internet for my inverter, as there was so much trouble initially to get modbus working (flashing ARM firmware by hand etc).
So i did not want it to update the firmware by itself and break my efforts (and i dont want others to have control over my inverter to begin with)
Unfortunately i messed up my firewall rule a while ago so it was connected to SEMS for a few weeks.
I found out and re-applied the firewall rule last week and for some reason the modbus connection stopped working the day after (after the nightly power-down)
I found that disabling the firewall rule, fixes this issue. Re-enabling it does not break the modbus connection.
Next day after the invertor starts up, it is not working anymore. I can re-produce this by manually powering the unit down and up.
I ruled out existing connections etc .
The only conclusion i have , is that goodwe updated my firmware and that the firmware now does not enable local modbus untill it had a connection with SEMS.
ARM is v16, i flashed v17 a few years ago which gave no issues.
The broadcast package does not fix my issue!
Anyone recognize this behaviour?
Going to try to downgrade manually now, will report about my findings.
Also ordered the old LAN kit so i dont have this insecure wifi kit anymore (anyone noticed that it acts as an actual AP / internet router when you connect it to your lan? totally flawed this ‘Shanghai High-Flying’ product…)
Ok, i kept my ARM at v16, but downgraded the DSP to v16. It was running somewhere in the 20s . This was not done by me but must have been over-the-air.
I just got some data in, briefly, and it stopped immediately after … very strange.
At least the behavior changed. But still not fixed.
I might just wait for my LAN adapter to arrive, see what that does.
Edit (new user so cannot reply more than 3 times):
Status update and conclusion so far:
tried upgrading to very latest ARM and DSP for G2 devices. did not work.
after downgrade from ARM24 and DSP23 to 16.16 , adapter did connect to network but did not initialize / access data.
wifi reload via inverter: everything started working.
I started to implement the firewall rules again, and only very briefly after initial start i am able to pull data locally.
After that, no connection locally.
Firewall shows every second two times a request to 47.254.143.217:20001 blocked as expected
Tried to change firewall rule to reject instead of block: does not help
Tried to block dns , block cloudflare timeserver which it apparently accesses, any combination. Did not help
Tried to change dhcp settings so the wifi stick does not get a gateway (basically not entering the network for its calls , effectively blocking connections ’ locally’ in the stick):
Did not help. In fact this broke the webinterface of the stick. Which does not make sense.
allowing internet for the stick: instant fix!
disabling internet: still works
restarting invertor: not working anymore
Fact is that i ran for 2 years straight blocking the internet for the inverter. Exact same firmware and exact same firewall rule does not work anymore…
The only conclusion i can draw is that SEMS portal connection messed with the inverter parameters.
Maybe the implementation of Sems+ app pushed some supportive settings?
I hope the old LAN stick i ordered helps with this.
I did read there are some registers that steer the update frequency to sems; 47006 for instance.
If the LAN stick is not working , i will go the full DIY route with the serial interface.
No way i want this device connecting to the internet, especially if the internet connection now is apparently needed for local access!!