search

WillCodeForCats / solaredge-modbus-multi

Modbus/TCP local polling to one or more SolarEdge inverters. For single inverters, multiple inverters, meters, and batteries.
Apache License 2.0
181 stars 15 forks source link

Values from Solaredge B1 missing #370

Closed requiemmg closed 1 year ago

requiemmg commented 1 year ago

Hi, I have a single inverter single battery (SolarEdge HomeHub SE8KRWB48 with SolarEdge StorEdge 9,2kWh Battery) setup. Your addon was always getting correct data from modbus. Modbus data comes thru the Modbus-Proxy Addon; Clients are your addon and my OpenWB Wallbox. I did a fresh install of Home Assistant this week and installed everything from scratch. Worked flawlessly. Today, I noticed that some values were suddenly missing from the B1 device: B1 DC Voltage, B1 Energy Export and B1 Energy import. Everything else is there. First, I restarted Home assistant - Exergy export and Import reappeared, but not B1 DC voltage. I have no idea why and I was not even at home at the time it stopped reporting, so I sure didnt change anything about the config.

Deleting the devices and adding and configuring them again afterwards doesnt change the problem. Will test a restart of the modbus device and inverter when I am at home.

Expected behavior Continuous reporting of the values to the entity.

Screenshots grafik grafik grafik

Logs

There are no logfiles in /config/custom_components/solaredge_modbus_multi Debug logs attached below, started debug logs and restarted HA.

This is a log from the Modbus-Proxy, 2 clients polling, no errors at all.

2023-07-25 15:01:38,424     INFO modbus-proxy.Client(192.168.0.170:34044): connection closed
2023-07-25 15:01:43,392     INFO modbus-proxy.Client(192.168.0.181:54529): new client connection
2023-07-25 15:01:43,634     INFO modbus-proxy.Client(192.168.0.181:54529): client closed connection
2023-07-25 15:01:43,634     INFO modbus-proxy.Client(192.168.0.181:54529): closing connection...
2023-07-25 15:01:43,635     INFO modbus-proxy.Client(192.168.0.181:54529): connection closed
2023-07-25 15:01:44,695     INFO modbus-proxy.Client(192.168.0.181:52551): new client connection
2023-07-25 15:01:44,926     INFO modbus-proxy.Client(192.168.0.181:52551): client closed connection
2023-07-25 15:01:44,926     INFO modbus-proxy.Client(192.168.0.181:52551): closing connection...
2023-07-25 15:01:44,927     INFO modbus-proxy.Client(192.168.0.181:52551): connection closed
2023-07-25 15:01:53,389     INFO modbus-proxy.Client(192.168.0.181:58663): new client connection
2023-07-25 15:01:53,693     INFO modbus-proxy.Client(192.168.0.181:58663): client closed connection
2023-07-25 15:01:53,694     INFO modbus-proxy.Client(192.168.0.181:58663): closing connection...
2023-07-25 15:01:53,696     INFO modbus-proxy.Client(192.168.0.181:58663): connection closed
2023-07-25 15:01:54,690     INFO modbus-proxy.Client(192.168.0.181:55255): new client connection
2023-07-25 15:01:54,991     INFO modbus-proxy.Client(192.168.0.181:55255): client closed connection
2023-07-25 15:01:54,992     INFO modbus-proxy.Client(192.168.0.181:55255): closing connection...
2023-07-25 15:01:54,993     INFO modbus-proxy.Client(192.168.0.181:55255): connection closed
2023-07-25 15:02:02,699     INFO modbus-proxy.Client(192.168.0.181:38789): new client connection
2023-07-25 15:02:02,973     INFO modbus-proxy.Client(192.168.0.181:38789): client closed connection
2023-07-25 15:02:02,973     INFO modbus-proxy.Client(192.168.0.181:38789): closing connection...
2023-07-25 15:02:02,975     INFO modbus-proxy.Client(192.168.0.181:38789): connection closed
2023-07-25 15:02:04,043     INFO modbus-proxy.Client(192.168.0.181:44031): new client connection
2023-07-25 15:02:04,290     INFO modbus-proxy.Client(192.168.0.181:44031): client closed connection
2023-07-25 15:02:04,291     INFO modbus-proxy.Client(192.168.0.181:44031): closing connection...
2023-07-25 15:02:04,294     INFO modbus-proxy.Client(192.168.0.181:44031): connection closed
2023-07-25 15:02:08,145     INFO modbus-proxy.Client(192.168.0.170:39042): new client connection
2023-07-25 15:02:08,339     INFO modbus-proxy.Client(192.168.0.170:39042): client closed connection
2023-07-25 15:02:08,339     INFO modbus-proxy.Client(192.168.0.170:39042): closing connection...
2023-07-25 15:02:08,340     INFO modbus-proxy.Client(192.168.0.170:39042): connection closed

Diagnostic File config_entry-solaredge_modbus_multi-ac9198dc514e43f1dc4670578282ecf2.json.txt

Debug Logs home-assistant_solaredge_modbus_multi_2023-07-25T13-12-44.814Z.log

Home Assistant (please complete the following information):

requiemmg commented 1 year ago

Addendum: Tried deleting the config, uninstall from HACS, reboot, Install 2.4pre4, reboot, reconfigured: still the same. And as I noticed, the value seems to appear and disappear periodically when I look at longer statistics (not too long as I said, fresh install of HA. Didnt see this before, though). grafik

WillCodeForCats commented 1 year ago

One of two things is probaby happening: the inverter stops providing that data point (which is a known issue) or the value is out of the configured valid range. I will look at the diagnostic file.

requiemmg commented 1 year ago

Known issue of SolarEdges modbus integration that is? If so, there'd be nothing you could do about it,right?

WillCodeForCats commented 1 year ago

Your diagnostic file says the battery entity is reporting over 800 volts DC, which is higher the current upper limit (600 volts).

I can change the upper allowed limit to something like 1000 volts and display it anyway, but the datasheet for your inverter model says battery voltage range is 40 - 62 volts, which should be nowhere near 800 volts. Since you're using a proxy the integration isn't seeing the true values your inverter is reporting so it's possible the proxy is altering the modbus values incorrectly.

Screenshot 2023-07-25 at 8 37 12 AM
requiemmg commented 1 year ago

Right,this is a low voltage DC system. To make sure it is not the proxy, i disabled it and connected directoy with your addon, but the result is the same, so it seems to be incorrect value from modbus (or incorrect interpretation of the data ar least with this model?)

WillCodeForCats commented 1 year ago

The value coming from the inverter is 0x444d5296 which is a floating point number, converted to decimal is 821.290405273

The only thing I can do is the upper limit to 1000 since that's what the modbus data coming from the inverter is.

requiemmg commented 1 year ago

I will ask SE support about this. Strange.

Seth @.***> schrieb am Di., 25. Juli 2023, 18:17:

The value coming from the inverter is 0x444d5296 which is a floating point number, converted to decimal is 821.290405273

The only thing I can do is the upper limit to 1000 since that's what the modbus data coming from the inverter is.

— Reply to this email directly, view it on GitHub https://github.com/WillCodeForCats/solaredge-modbus-multi/issues/370#issuecomment-1650143191, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACVECMFTYE4WVBMQ5CFMZETXR7WR3ANCNFSM6AAAAAA2XCAM7Q . You are receiving this because you authored the thread.Message ID: @.***>

WillCodeForCats commented 1 year ago

PR #371 will change the display max to 1000 volts and I will make a new pre-release with it.

requiemmg commented 1 year ago

Thanks for the support. I just have to keep in mind that the values are BS. Any idea why in first instance values for charged and duscharged kWh were probably missing? Never seen before. Sorry, no logs from that.

WillCodeForCats commented 1 year ago

The kWh counters resetting or going backwards is a known issue with batteries: wiki/Known-Issues#battery-energy

There is a configuration option to allow battery energy to reset and an option to set how many polling cycles for it.

WillCodeForCats commented 1 year ago

Release v2.4.0-pre.5 contains this change.