Battery export sensor incorrect #590
Replies: 16 comments
-
|
If you look in the debug file look for the The sensor values for battery energy are: These are hex integer values, so a value of The integration does not interpret these values, they are passed through as given by the inverter. You would need to either download diagnostic files or watch debug logs to check if that value is increasing or not. The data in the SolarEdge online platform is separate from modbus. |
Beta Was this translation helpful? Give feedback.
-
|
So if I understand you correctly, the integration reads the values as presented by the inverter and only converts the HEX to numerical value. Then I appologize for sending in the bug report and will try to solve on the inverter side. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, that's correct. The value is displayed. It checks other conditions but if it's showing a value that's the value it's getting from modbus. You can check the diagnostic files to see if the hex value is changing or not. |
Beta Was this translation helpful? Give feedback.
-
|
Did you find a solution for this?
I'm running off battery overnight, and the B1 Energy export level is not changing overnight |
Beta Was this translation helpful? Give feedback.
-
|
No, according to the developer it is not the integration, so no, there is no solution. |
Beta Was this translation helpful? Give feedback.
-
|
Download diagnostic files or check debug logs to see if the value of |
Beta Was this translation helpful? Give feedback.
-
|
Hi, i am having the same issue and will monitor the logfiles after it freezes, then reload and check the logfiles again Next chance to do that is tonight at 2200ish local which is the usual time it kicks out. . |
Beta Was this translation helpful? Give feedback.
-
|
With debug on, the values are not changing overnight, but I see the data in the solaredge app is changing.
although their website is showing 0W export for the time, but it does show battery dischange.
|
Beta Was this translation helpful? Give feedback.
-
|
here is all the data for 04:xx hour: grep custom_components.solaredge_modbus_multi.hub home-assistant.log |grep " 04:..:.." > /tmp/04.log |
Beta Was this translation helpful? Give feedback.
-
|
Step 1: Screenshot, state unknown since yesterday 2200ish Step 2: Activate logging Step 5: Download log The first lines in the log :
Correspond well with the battery sensor death, although i don't know whether they are zulu time or local (+2). I might have screwed up the logging/resetting process since the log shows nothing about the integration restarting. It also starts timestamping after my screenshot. Do i need to download the log before restarting? home-assistant_solaredge_modbus_multi_2024-04-21T09-35-53.544Z.log
|
Beta Was this translation helpful? Give feedback.
-
|
So first off, all I'm really doing here is proving this is not a bug in the integration: the integration just takes values the inverter gives, does some validation and checks for obviously wrong or invalid states that would mess up graphs/statistics, and passes them into Home Assistant. The SolarEdge app and monitoring platform is completely separate from modbus. If one of those works and the other doesn't, that's a bug in the inverter firmware that SolarEdge would need to fix. This integration can only use the data the inverter gives it over modbus. If the inverter keeps returning the same data every time it asks without increasing the values, that's an inverter bug and unfortunately there's nothing I can do about it except show you how it's not my problem to fix. You could try power cycling your entire system to cold boot it (turn off all AC and DC safety switches) to see if that re-syncs everything. That's been reported as a solution in the past and is mentioned in known issues. Battery energy sensors going unavailable can be several things which are already documented in known issues: https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Known-Issues If you have battery energy going unavailable you probably have the "backwards" data issue and need to turn on some of the options that are designed to allow that. Home Assistant expects that energy meters should not go backwards, so if they do the sensors will go into unavailable state. |
Beta Was this translation helpful? Give feedback.
-
|
hi,i am running an original SolarEdge battery so it seems to be either something different or they have this problem with their own batteries now. |
Beta Was this translation helpful? Give feedback.
-
Yes because logs are cleared when Home Assistant restarts. |
Beta Was this translation helpful? Give feedback.
-
|
I restarted the integration only, there was no new boot info in the log. |
Beta Was this translation helpful? Give feedback.
-
|
I'm not really seeing anything here that suggests a problem with the integration. I don't have batteries on my system, so I can't give any advice on them. |
Beta Was this translation helpful? Give feedback.
-
|
So i used the "reset" checkmark and it seems that my battery behaves like the LGs even though it says SE on the tin. |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
The battery export sensor indicates a battery discharge of only 3kWh/day while reality is approx. 12kWh/day
Expected behavior
correct data being read from the battery export sensor
Screenshots
Diagnostic File
config_entry-solaredge_modbus_multi-a150630511e990a73146f8eb62c16c53 (1).json
Debug logs
Home Assistant Version
2024.4.1
solaredge-modbus-multi Version
latest
Installation Type
HAOS
Read the Instructions
Additional Context
Up until recently, the battery export sensor functioned fine, although, due to a database change, I cannot dettermine when it started to go wrong, but it is clearly visible that the data is not correct.
Beta Was this translation helpful? Give feedback.
All reactions