Meter data unreliable after firmware update

[moedi21]

Describe the bug

Recently, my inverter (Home Hub 3 phase, SE8K-RWB48BFN4) has been upgraded to firmware 4.19.36. Since then, the readings of the imported/exported energy counter in the connected backup interface (SE-RGMTR-1D-240C-A) are missing for most part of the day. Also, the energy counters are partly downcounting.
After the update, I saw also a jump in the values, from about 290 kWh to 1311 kWh.

From the log, repeated frequently:
2023-11-27 06:57:54.380 WARNING (MainThread) [homeassistant.components.utility_meter.sensor] Total Import received an invalid new state from sensor.solaredgemodbus_m1_imported_kwh : unknown

Additional issue in the log:
2023-11-27 11:37:01.506 WARNING (MainThread) [homeassistant.components.sensor.recorder] Entity sensor.solaredgemodbus_m1_exported_kwh from integration solaredge_modbus_multi has state class total_increasing, but its state is not strictly increasing. Triggered by state 1311.289 (1311.289) with last_updated set to 2023-11-27T10:22:17.346956+00:00. Please create a bug report at https://github.com/WillCodeForCats/solaredge-modbus-multi/issues

Expected behavior

Expected: Energy counters should be available without interruption, and also strictly upcounting

Screenshots

Diagnostic File

config_entry-solaredge_modbus_multi-6e741e04c7c2d26d5b83e1f2129d8572.json (1).txt

Debug logs

No response

Home Assistant Version

2023.11.3

solaredge-modbus-multi Version

2.4.6

Installation Type

HAOS

Read the Instructions

• I have read https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki
• My configuration follows https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Configuration
• This issue is not about a template error (template errors should not be reported as an issue, read https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Template-Design-Notes)

Additional Context

I have tried in parallel to read the data with pure Python and the 'solaredge_modbus' package available in pip. There I get continous readings, but also partly downcounting:

{'import_energy_active': 1017522}
{'import_energy_active': 1017526}
{'import_energy_active': 1017531}
{'import_energy_active': 1017531}
{'import_energy_active': 1017531}
{'import_energy_active': 1017454}
{'import_energy_active': 1017457}
{'import_energy_active': 1017462}
{'import_energy_active': 1017462}
{'import_energy_active': 1017470}
{'import_energy_active': 1017470}
{'import_energy_active': 1017457}
{'import_energy_active': 1017465}
{'import_energy_active': 1017473}

[WillCodeForCats]

Contact solaredge support, it shouldn't go backwards.

[WillCodeForCats]

I'm closing this because it's not an integration bug: if the change that caused the problem was the inverter firmware being updated, then the bug is in the inverter firmware not the integration

Contact solaredge and ask them to downgrade your firmware to an older version that doesn't have this problem.

[moedi21]

Partly agree - the downcounting is probably caused by the firmware update. I have raised a ticket with SolarEdge support.
However, I also do not get continous readings from your integration, whereas I can get them using solaredge_modbus Python module. Not sure, why.

Anyways - thank you for your great work!

[WillCodeForCats]

The integration rejects values that are less than the reading before it because Home Assistant expects total increasing.

[WillCodeForCats]

I will add debug log entries for the error conditions as part of my sensor entity check refactoring that I'm already working on. You can see them anyway if you turn on debug logging, but I can also have it log why it failed a check.

[moedi21]

Thank you for the explanation, makes sense.

[aakso]

Just chiming in that this happened to me too last night. Though, according to the history, the issue started before the version was upgraded. My meter is the same inline meter in a home backup interface (SE-RGMTR-1D-240C-A)

Nonetheless, the values don't seem accurate at all anymore. I have a P1 device hooked directly to my meter so it's easy to compare and it almost looks like Solaredge has messed up and are displaying some completely different register values in the meter offsets relating to Wh values. The instant power register values are correct.

[aakso]

@moedi21 if you are able, can you give an update if/when you get some response? I'm going to approach our representative if this issue can be seen in the mobile app as well.

We already have an outstanding issue open about the inline meter reporting two times the power and energy readings compared to reality. This issue, however, magically fixed itself.

[WillCodeForCats]

Reopening for visibility.

[WillCodeForCats]

The integration rejects values that are less than the reading before it because Home Assistant expects total increasing.

PR #482 will add logging for this condition.

[oimara79]

I have the same issue on a SE10K-RWS48BEN4 inverter after the upgrade to

All meter data for imported and exported kWh are not correct. Also the data shown on the Meter (SE-RGMTR-1D-240C-A) is not correct. It is approx 25% less than what is accumulated on the officia grid meter from the energy company.

However the integral of the imported Power results in the correct Energy.

In this picture you see, that at the time the version changed the meter data got unreliable and reseted to 0

[philjohn]

Chiming in with an "unnafected" datapoint for those talking with SE - upgraded inverter to 4.19.36 a few days ago and my import and export are continuous lines in HA.

[requiemmg]

Interestingly, I do have the same invertert as the thread opener @moedi21 and I do not experience any problems; just checked and it seems I have the same firmware version; not aware when it was updated.

I use the Modbus-Proxy addon (as my Wallbox depends on this data, too) and I only have the twice daily "connection refused" errors being logged during the inverters' reset periods.

[aakso]

@philjohn @requiemmg Interesting, do you guys have the same meter SE-RGMTR-1D-240C-A?

(This is the inline meter that is din rail mounted that apparently is contained in the Home Backup Interface, the one with CT clamps is different)

[requiemmg]

Yes, see Screenshots from both of us

[DragonQ]

Since the downgrade to 4.18.32 the modbus connection on my inverter has been stable for 36 hours, so I think that sorted it. I would advise people ask for a downgrade and avoid 4.19 firmwares for a while.

[requiemmg]

I wonder why some people have issued and others not. Still on 4.19.36.

My meters firmware value changed from 0 to 78 in the last days. Still getting correct readings....

[chofstaetter]

I have a 9.2 kWh battery and a "BI-NEUNU3P-01" backup interface installed in addition to my existing SE10K-RWB48BFN4 (FW: 0004.0019.0036) for two days. The SolarEdge Modbus Multi Integration immediately recognized the two new devices, the BI as "MTR-240-3PC1-D-A-MW" with FW: 1.0.15 and the battery as "SolarEdge Home Battery 9.2kWh" FW: 48V DCDC 3.2.9.
The values from the RWB48 and the batteries look good, but the BI provides partially no or incorrect values:

• AC Voltage AB, BC, CA and LL are always on "0.00 V",
• All 4 "Exported x kWh" and all "Imported x kWh" are on "Unknown" but sometimes provide single nonsensical values.
  Could it be that the backup interface is simply not supported correctly yet, since the values of the battery and the inverter are correct, or should I really go to an older FW?
  
  

[moedi21]

@chofstaetter I have a similar setup as you, and I can just tell you that everything worked ok before the firmware upgrade...

[moedi21]

Just a brief update - I received a mail regarding my support ticket with SolarEdge. It is now forwarded to 2nd level support...

[chofstaetter]

@chofstaetterIch habe ein ähnliches Setup wie Sie und kann Ihnen nur sagen, dass vor dem Firmware-Upgrade alles gut funktioniert hat ...

Perfect, thanks for the information, then I'll contact SE Support and ask them to downgrade the inverter.

[WillCodeForCats]

The integration rejects values that are less than the reading before it because Home Assistant expects total increasing.

PR #482 will add logging for this condition.

This PR is part of Release v2.4.8-pre.1

[victorwelling]

Just got an update they're working on a fix. No ETA unfortunately.

[Ojoachim71]

Same here! But firmware for backup interface is 1.0.2 (is it newer or older than 1.0.15?). Inverter is 4.19.36

[DennisPh1977]

There is a firmware update to version 4.19.39 which is not available on the Solaredge website but can be installed via the SetApp. This update has fixed the problems with the wrong data for me.

[m4v3r1ckNl]

Thank you very much for the heads-up.

https://www.solaredge.com/en/support/setapp-inverters-firmware#_Resolved_32111

[requiemmg]

Also thanks from me. But how do I force a firmware update? I do not have a SetApp Account, but thought functionality would be the same as when connecting to the inverter's WLAN and head to 172.16.0.1. But there I only have the option to update firmware via USB (but I do not have an USB port which is accessible from the outside.)
Does SetApp indeed offer any other options?

[DennisPh1977]

You must download the app from the Playstore or the Appstore and create an account in the app. The SetApp will then automatically download the latest firmware. The current Version is 4.19.39, this version is not yet displayed in the Changelog on the Solaredge homepage. Then you connect to your inverter and the app will show that there is a new firmware. A firmware update is not possible without the SetApp because Solaradge does not offer the firmware for download anywhere. I strongly assume that a firmware update via USB can only be carried out by a specialist in an emergency because you would have to unscrew the inverter for this because there is no USB port on the outside.

[moedi21]

Actually this firmware created the problem for me... 4.19.36 was released in November, and there it all started.In the meantime, Solaredge has downgraded the firmware on my inverter to 4.17.136, and my problem is gone. Never change a running system...

[victorwelling]

My SolarEdge 3-phase Home Hub inverter got automatically updated to v4.19.39, and it seems to have solved the issue. Will monitor over the next few days.

Interesting side effect is that the meter (part of the Home Backup Interface) now identifies itself as SE-RGMTR-1D-240C-A, whereas previously it was MTR-240-3PC1-D-A-MW. Unfortunately, its firmware is now reported as 0.

[chofstaetter]

Bei mir SE10k RWB48 ist es immer noch MTR-240-3PC1-D-A-MW, aber dafür funktioniert jetzt auch alles.

[chofstaetter]

I have now gotten the installer for the SetApp and also updated to 4.19.39.
As far as I can tell, the energy values ​​are now correct for me too. (SE10k RWB48 with Backup Interface))

[Ojoachim71]

Wie haben Sie denn Zugriff bekommen? Ich kann mich nicht mal anmelden (Seriennummer ungültig, obwohl richtig, vermutlich durch Installateur gesperrt).

[chofstaetter]

Ja das ist weil die Anlage im Account deines Installateurs hängt. Ich habe mich einfach als Installateur angemeldet und dann eine Mail bekommen, mit herzlich Willkommen..., sieh Anhang. Dann konnte ich mich mit dem Account vom Monitoring in der SetApp anmelden, da wurden dann die Firmware aufs Handy geladen, danach hab ich mich mit dem QR-Code am RWB angemeldet und das Update wurde automatisch durchgeführt.

[chofstaetter]

Der Irrtum ist vermutlich dass wir im Monitoring versuchen Zugriff als Admin zu bekommen, das hat mich auch eine halbe Stunde beschäftigt, das geht aber nicht weil das der Installateur hat. Aber in der SetApp muss es ja gehen, sonst müsste ich ja immer zum selben Elektriker gehen, was ich eh tun werde aber eben nicht wegen einem Update.

[victorwelling]

Unrelated to this topic, but very much related to the latest firmware update: anyone noticed their batteries seem to be capped at 1kW charging (at least from the grid)? The default used to be 5kW, but if I change it, it reverts back to 1kW.

[aakso]

The grid charging seems to limit itself to 1kW if you trigger that by adjusting the reserve percentage. However, if you set storage control mode to remote control and enable charging thru the storage command mode, it honours the set charging power. In this model, you have to deal with storage command timeout as well as the storage default mode to set what mode the inverter should switch into when the timeout is hit.

All this is a little bit involved to automate but it mostly works. Sometimes I do get inverter connection errors but I suspect this is due to the plugin itself as reloading it or HA fixes the issue.

[victorwelling]

It seems to have fixed itself out of the blue. Haven't been able to reproduce it.

Only thing I noticed was that it appeared to charge slower in colder temperatures, but I guess that's to be expected.

[cyberkryten]

I'm seeing both these issues on a new install: single inverter, three (two working) batteries and backup gateway MTR-240-1PC1-DW-MW on FW 1.0.15

I get issues with the reported values of generated and self consumed energy both locally and dispelled in the SE App. After hard resets (I've got an issue with the third battery not working) they started working for a while and then stopped but don't record solar energy correctly, so I now use values calculated from the optimisers.

I also noticed the charge rate issue when setting the reserve percentage in the SolarEdge App even before I'd setup anything to do with this integration or HA. Installer/SolarEdge answer was not to do it like that!

I have two batteries (third one is disconnected as broken) and got a charge rate of 2kW when setting the Battery Reserve value to higher than the current charge amount, 1kW to each battery.

When changing the Battery Mode to a Time of Use which triggered charging, it charges at the full rate - that's using the App and I see the same behaviour when setting values using Modbus.

[MikeTango]

Hi,

i have this problem, but only for the battery export/import sensor.