-
Notifications
You must be signed in to change notification settings - Fork 34
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
modbus4mqtt errors out on SG5K-D #16
Comments
Hm, could you try a |
Is there anything else talking to the inverter? The wifi interface can only handle a few connections at once, and this includes the connection to iSolarCloud. |
there is only iSolarCloud talking. |
When I was using wifi I had one dropout every half an hour, all modbus comms was interrupted, and then it came back again. I switched to an ethernet connection and it's been solid since then. The SH5k-20 has an internal ethernet port. Note that the RJ45 socket the wifi dongle uses is not an ethernet port. It's a serial RS-485 that just happens to use the same connector as ethernet. |
changing
|
Can you please try upgrading to v0.3.4? I don't expect it will fix the issue but it may shed additional light on exactly what's going wrong in the internals thanks to some logging improvements. Could you also try a scan_batching value of 10? Some example documentation I've found for communicating with Sungrow inverters uses a read size of 10, so maybe their dodgy implementation of modbus expects that exact value and gets upset otherwise? |
Sure. Let's try to throw some lights:
|
My device is an SG5K-D. How do I get the firmware version? From the LCD? |
Yep! I'm not sure if the SG5k-D LCD interface is the same as the SH5k-20, but on mine the firmware version and serial number are available at the bottom of the "Run info" menu pages. I pressed ENT (menu), ENT (run info), then UP (device info). |
With the aid of the manual, I worked out how to drive the LCD screen. My firmware version is: CrysG2_V31_FW_V22 |
OK. |
I have missed this somehow... The firmware version of my device is: CrysG2_V31_FW-V22 (from LCD display). |
hey guys, this morning my inverter was 'shut', no more port 502 and 80, but cloud app still working. I think Sungrow disabled it all. |
They've added a new option to the app: live data. But the app says my model doesn't have it, can you believe it? I was getting live data, by myself, until yesterday :| |
Last night I was working on getting HomeAssistant to read directly from modbus. I was making some progress, and then it stopped. I traced backwards and found port 502 was closed. I was worried that I'd caused the inverter to crash from my polling, so was actually relieved to see your post! Same thing in my app too, no live data for me. |
This is dire news. Very disappointed in Sungrow. Does anyone running the new firmware have access to the web interface? Is it possible to re-enable the modbus interface in there? Is it possible to downgrade the firmware via the iSolarHome smartphone app? |
Well, this is very weird. Today my inverter came back to life. But still, all doors are closed. BUT my home assistant was connected to it and working flawlessly. I think they shut port 80 for good and 502 is shut after ONE connection is established. @entropical can you, please, check if this is also happening on your equipment? Thanks. |
Hm. I speculate this might be sungrow's fix for unreliable modbus performance when multiple clients are talking to the same host. The wifi dongle talks to the inverter via a modbus-485 connection. If the dongle can't safely multiplex multiple parallel requests from modbus-tcp to serial requests over modbus-485 then it makes sense to only allow one modbus-tcp connection to the dongle. |
Yeah, that's what I thought too.
Em seg, 21 de dez de 2020 21:07, Travis Howse <notifications@github.com>
escreveu:
… Hm. I speculate this might be sungrow's fix for unreliable modbus
performance when multiple clients are talking to the same host. The wifi
dongle talks to the inverter via a modbus-485 connection. If the dongle
can't safely multiplex multiple parallel requests from modbus-tcp to serial
requests over modbus-485 then it makes sense to only allow one modbus-tcp
connection to the dongle.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACX55SKIRUEAX6VTDELTR6TSV7PLPANCNFSM4TL3O73A>
.
|
This might be a problem depending on how pymodbus (or the app using it) handles tcp comms. You no longer can spawn several connections in parallel. Today my integration with home assistant was working, but the other day it was not. Most likely the connection was already in use and the dongle shut the modbus port. |
modbus4mqtt only opens a single modbus connection, I'm not sure about the
HASS modbus implementation.
…On Tue, 22 Dec 2020, 10:16 Roberto Panerai Velloso, < ***@***.***> wrote:
This might be a problem depending on how pymodbus (or the app using it)
handles tcp comms. You no longer can spawn several connections in parallel.
Today my integration with home assistant was working, but the other day it
was not. Most likely the connection was already in use and the dongle shut
the modbus port.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHWDUPVH6CEAIBLMUX5DEDSV7QN3ANCNFSM4TL3O73A>
.
|
Oh, it is good I have blocked SG5K-D on the router... |
@plague-doctor on my inverter (SG4K) is:
But this only reports the total injected power, some of it is used right away and what is left is injected back to the grid. I think you need an specific installation in order to know exactly how much you inject (or just trust the electric company measurements :D). |
If only I could have the right mapping for SG5K-D... |
I have a file sungrow sent me, it is supposed to work with all residential models. Its attached. |
Could you please share this file? |
Thank you kindly.
|
It is 'minus one' says in the document Note: Don't ask my why... |
Before I will fund a marble statue for you, can you double check this:
Is this right? |
I think those are the same registers I'm using too, looks about right. |
5016 is DC Power output from PV modules before AC conversion. |
So 5030 is what I get from the solar after AC conversion. |
What is left is measured by the electric company's meter. I don't keep tabs on it. |
Ok. Thanks a lot. The statue will be 4.5m but green marble ;-) |
If either of you has a YAML file for the SG5k-D I'd be very keen to include it in this repo. Feel free to raise a pull request or attach it to this issue. |
Here you are, but this is a very simple one... |
web and modbus interfaces are backup to normal. \o/ |
Interesting! Was there a dongle or inverter firmware update recently? Or did something else change? |
I can't perceive any changes in the web interface. They probably updated the FW again or rolled back. |
This is a different issue to #13 but related.
The module constantly throws errors:
and finally stops reporting (most of the cases at night). Memory leak?
My config SG5K-D.yaml:
The text was updated successfully, but these errors were encountered: