-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kills my inverter connection #174
Comments
Having the same issue on my 5048ES. Removed and re-added the integration doesn't help. |
@oziee I had a similar issue, well maybe still have it. Initially I did not have any issues with the integration. Then some time later it started. I suspect, after I had the arm firmware updated to a newer version. My connection would completely drop, so bad, that even pv master wouldn't connect and SEMS data update stopped. I eventually got tired of changing the AP password on the wifi device away from the default 12345678 to what I use each time I completely shutdown inverter and reset wifi module. So in my case the conditions are: I have heard rumours the wifi module is more stable than the lan module at best of times, who knows why but I don't have personal experience with that as I dont have the lan module. |
@tinuva correct I too have read that the wifi is more stable than the LAN.. not sure about the firmware.. and yes when it dies out.. no PV master or PV go app connection.. SEMS connection.. just the web interface for wifi.. and have to do the whole shut right down and restart everything again.. |
Completely different versions here. Inverter: 5048D-ES |
Inverter: 5048D-ES |
Hello friends. |
I don't know if there was an update since, but it hasn't happened to me (touch wood) since I posted here last week sometime.? |
I have two inverters, an EM and an SDT G2 (both with WiFi). My guess: According to the documentation https://fccid.io/2ACSV-HF.../Users-Manual-3552381.pdf (chapter 2.6) there is a SOCKET B mode that supports the connection to multiple end devices. I suspect that the HF-LPT230 is active on the EM converter. But not with the SDT G2. I currently have the original firmware installed on Hi-Fly (not from Goodwe) (http://www.hi-flying.com/download-center-1/firmware-1/download-item-hf-lpx30-firmware). - Unfortunately, I have not been able to send AT commands to the WiFi chip with this one either. Disadvantage of the Hi-Fly firmware: The PVMaster or SolarGo app no longer works. Does anyone happen to have the original Goodwe firmware? |
Now, for the first time (have the inverter dor 2 months now), the problem started here . PS: it was the first time. After FULLY reset the inverter (not only the wifi dongle) started working Info: |
Same issue here - inverter inresponsive, admin page for Wi-Fi dongle is working. Inverter connected via lan. |
@JochenHa its been well talked about that the lan dongle causes lots of problem. I have both lan and wifi and the lan works 1 in very 100 or so ha calls and very problematic. Best to use the wifi dongle |
@oziee I'm afraid, Wi-Fi is not an option. HA connections works with LAN only. Maybe the renewal of dhcp leases are not handled correctly? Seems to be the only "signal" using a very long timeframe. |
I am running integration to HA on Wi-Fi and it is rock stable - not true it needs LAN. Check all DHCP settings and make reservation. |
@janchlebek interesting - I was not able to connect via Wi-Fi. Found some notes about it - maybe it's depending on the inverter type? |
Maybe - based on my experience and what I read the wifi module is considered to be more stable (at least on 10K-ET). |
I have a 10K-ET as well. I'm running HA in docker (on Windows) on a server in the same subnet as the inverter (has fixed IP, set on the dongle itself). Using both the LAN as well as the WiFi module, my connection is very spotty. it's not possible to send commands to the inverter (for example to put it in ECO CHARGE MODE) because it fails in 95% of times. |
Yes the WIFI modules and what they support are region dependant - in Australia i am not aware of any of the wifi modules that support Modbus to the older SBP5000/3600 or the ES 5048 series inverters. They do support the older AA55 protocol which is how SolarGo/SEMs/PV Master communicate with them |
Hello! This behaviour just started on my 5048D-ES yesterday around 8:50 in the morning as well, with no changes to the setup and no updates either Home Assistant or the integration (non-HACS). Symptoms:
Is there really nothing that can be done about this? Perhaps the timing of the integration initialisation is too aggressive for newer firmware versions, and Goodwe added some kind of rate limiting? I also wonder how I could detect whether Goodwe has updated the firmware on my inverter remotely around the times that the problems occurred? I also tried to remove the official integration and then added the HACS branch, but the same problems occur. Since I don't really care about the SEMS data, I also tried to block the inverter off the internet, to free up potential remote connections to SEMS and perhaps make a local connection possible. No luck there either. Thank you for your help!
|
I had terrible trouble with the inverter no longer accepting commands and also stopping updating SEMS portal after 1-2 days. The only way to recover was a full shutdown, solar, AC mains and batteries off - a complete cold restart. A Wi-Fi module reboot did not help. I'm using the Wi-Fi dongle. I managed to get GoodWe to update the firmware to:
It's now rock solid stable. SolarGo still works, SEMS portal and HA just work. It has been going great now for many months without a reboot. I use the HACS "GoodWe Inverter (experimental)" to switch from "General mode" supporting the house using battery power and I switch to charging the battery from grid mains at specific times using "Eco Charge Mode". I also do some great maths and calculate how hard to charge the batteries when on charge by manipulating the "Eco power power" percentage so that in a 3 hour charge period from mains the house batteries will come back to 100% with the lowest charge rate required. |
I have used this integration a lot. and it seems that newer version now cause the inverter connection to die and the sensors become unavailable.
I will take some time to test which version last worked fine for me, but my GoodWe SBP inverter can no longer use this integration as is.
I have the Wifi kit and the LAN kit.. (got the LAN kit recently as I thought the problem was wifi module - but turns out to be this integration)
the problem is that the inverter stops sending data to HA and to SEMS.. but I can still log into the inverter admin page and change those settings.
The only fix is to completely shut down the entire inverter and restart.
After this SEMS and HA work again..but not for long.. soon enough they both stop working again.
I have disabled this integration for 2 weeks, and the inverter and SEMS data have been working fine.. and last night re-enabled this integration and soon enough all the data has stopped working again.
This integration must be transmitting a code to the inverter that the inverter is not liking and is causing the problem.. When I get a chance I will start to send the codes on by one from the newer integration code to see what changed from when this integration once worked fine, somewhere back around v0.9.9.3 ish
I see other issues reported here that are seeing similar results in the integration, so would be good to hear from some other users if they have seen and tried what I have done in the last month
The text was updated successfully, but these errors were encountered: