Battery integration

[sragas]

Are there any plans to integrate connected batteries?

[WillCodeForCats]

Yeah eventually. Right now I'm focusing on getting another integration released (my tekmar-482 integration) and once that's out I'll revisit this one. I'm planning to rewrite this integration since I'm finding how it was written is limiting to things I want to do with it, and he structure I used for the tekmar-482 integration is more flexible for me.

Edit: batteries are supported starting in v2.0.0 and StorEdge control starting with v2.2.7

[skl283]

+1 from me!
Will also appreciate the battery integration to use your Integration! :-)

[skl283]

@WillCodeForCats i just want to give you a quick info! I have switched from the single modbus Plugin to your plugin and everything works perfect! :-)

[WillCodeForCats]

The rewrite-for-2.0 branch is at a point where it should detect batteries and create device entries for them, but there aren't any sensor entities yet.

[WillCodeForCats]

Anyone who has batteries please try the rewrite-for-2.0 branch and report if it detects your batteries or not. It will have some basic diagnostic sensors and show a device for each battery (up to 2 per inverter for up to 32 inverters).

Because battery registers are not technically officially supported by SolarEdge, auto-detection for batteries is disabled by default. To enabled battery detection, go to the device options and enable it.

[doonga]

Hi, I gave this a shot, I got devices for the inverter and the 2 meters, but no batteries. I have the newer SolarEdge Battery Banks BAT-10K1P, there are two of them.

I rolled back to the normal version for now since I wasn't sure if all of the entity names changed. I'll need to go edit a bunch of stuff to keep things working.

[WillCodeForCats]

Inverter entity names will be the same, meter entities will be slightly different since auto detect will scan every inverter for all 3 meters, which means it's possible to have more than 3 meters, so it names the meter entities with the inverter ID and the meter ID instead of fixed numbers. (I should say the inverter entity names are supposed to be unchanged but I haven't double checked them in old vs. new yet so there could be mistakes since this is still pre-pre release).

If you set debug logging it will log something for batteries. Basically the way auto detect works is it tries to read some basic info registers and if the read is OK then it adds the device. If the read returns any kind of error it ignores that location. The battery registers have been taken from an engineering pdf for the LG batteries where only 2 batteries per inverter were supported.

To enable debug logging:

logger:
    default: warning
    logs:
        custom_components.solaredge_modbus_multi: debug

And then in my logs the important lines are:

DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Inverter 1 battery 1: Exception Response(131, 3, IllegalAddress)
DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Inverter 1 battery 2: Exception Response(131, 3, IllegalAddress)

Which means there aren't any batteries at the battery register, in my case because I don't have any so the address doesn't exist. If you see those exceptions and you're not using the old LG batteries, then that means it's likely SolarEdge changed the battery registers or isn't using them.

[WillCodeForCats]

I just pushed some updates to logging attributions so you'll need to re-download.

[doonga]

Hmm yep looks like the new ones aren't using the registers... That's very unfortunate...

2022-06-02 19:18:17 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Inverter 1 battery 1: Exception Response(131, 3, IllegalAddress) 2022-06-02 19:18:17 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Inverter 1 battery 2: Exception Response(131, 3, IllegalAddress)

[WillCodeForCats]

I assume you're using the new "Energy Bank" battery system?

Edit: you already said that you are

[WillCodeForCats]

Well, I'll keep an eye out for any information about registers for the new Energy Bank system. Otherwise it's anyone's guess if they moved to different addresses or what.

[doonga]

Yep, no worries. Hopefully somewhere down the road. Thanks!

[WillCodeForCats]

It's still possible I got the registers wrong since I can't test any battery stuff myself, hopefully someone with the older battery system will give it a test to confirm it's an LG vs Energy Bank difference.

[WillCodeForCats]

Pre-release v2.0.0-pre.1 is available now.

[muenchris]

I have two Inverter and each inverter has one battery attached. But I do not think SolarEdge is exposing the batteries via Modbus TCP at all. Using modbus test tools, there are no values exported where they should be according to the SunSpec. I guess the inverters are collecting the battery info via RS485 but do not copy the values into the Modbus TCP range. Luckily the LG batteries have a mini WebServer on board that can easily be used to read all BMS values

[WillCodeForCats]

LG batteries should be detected. My code may have been off by one count on the battery info read block, I will release a pre.7 with what I think might be the correct value.

[WillCodeForCats]

I'm looking for anyone with batteries who can test Release v2.2.5-pre.3 which contains new validation rules for battery sensor values.

Edit: v2.2.5-pre.2 contains a load error, use v2.2.5-pre.3

[gferen]

Tell me what to look for, logs, etc....

…

On Sun, Oct 9, 2022, 16:47 Seth ***@***.***> wrote: I'm looking for anyone with batteries who can test Release v2.2.5-pre.2 <https://github.com/WillCodeForCats/solaredge-modbus-multi/releases/tag/v2.2.5-pre.2> which contains new validation rules for battery sensor values. — Reply to this email directly, view it on GitHub <#63 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJ4FIEBRUIFNVXF6C5GCGLWCLEHXANCNFSM55CBRHIQ> . You are receiving this because you were mentioned.Message ID: <WillCodeForCats/solaredge-modbus-multi/repo-discussions/63/comments/3833218 @github.com>

[WillCodeForCats]

It should work the same as before. I've added some valid ranges for battery data points since the old way didn't work well enough as reported in issue #123 so it needed updating. You should still see the same sensor data in Home Assistant, but if a sensor shows "unavailable" after updating,I would need to know what the value was before so I can adjust the valid ranges.

[atarana]

Hi, I can't get the right information from battery: unknown or 0 are returned.

[muenchris]

My situation is even worse: my inverter some times just "forgets" its IP Address. It still communicates with the SolarEdge cloud but I can no longer ping my inverter. The only way I get the LAN port back is to switch the IP from DHCP to static or the other way. That seams to trigger a restart of the LAN interface and the inverter shows up again...but not for long. After a couple days, it drop the LAN interface again. As a result whenever the LAN interface is "dropped", Modbus will not longer work. I do have another inverter that is connected to SPAN via Modbus and does not show that behavior. But since the Modbus interface of SolarEdge only supports one connection, I cannot connect to that one either. I am trying to tell this to SolarEdge but so far I have not been able to reach any competent person at SolarEdge that even knows what a "LAN Interface" is :(

[atarana]

Another user had this problem and mentioned in issue #123 that they had to power cycle their entire system before the battery and inverter would communicate proper data values.

How can I do it?

[bertybuttface]

SolarEdge have this video about shutting the system down, can follow it in reverse to start back up

https://www.youtube.com/watch?v=7GJCzi7fqEg

Or this video (unofficial) shows how to restart the system:

https://www.youtube.com/watch?v=8yAHlD14oWY

[Djelibeybi]

FYI, this is because SolarEdge inverters decline DHCP offers that have previously been revoked. I've found a simpler to get the inverter to reset (using my UniFi gear) is just to unplug its cable or block it from the wifi for ~10 minutes.

[muenchris]

FYI, this is because SolarEdge inverters decline DHCP offers that have previously been revoked. I've found a simpler to get the inverter to reset (using my UniFi gear) is just to unplug its cable or block it from the wifi for ~10 minutes.

I also tried a static IP and have the same result. So far I could not find a stable way of keeping the Inverter online. If I switch between DHCP and static IP the inverter stays online for a couple hours, then disconnects again.

[goossensbas]

I'm also looking to integrate my system into my smart house (PLC based) but i can't find any doc on what the modbus registers are for the solaredge energy bank. Can anyone help me out with that?

[WillCodeForCats]

Only what's in the docs: WillCodeForCats/solaredge-modbus-multi/tree/main/doc

[mikedeluca]

So I just installed this integration and it works great except for the batteries. I have 3 Solaredge 7600H inverters, a backup interface (basically an energymeter/transfer switch) and 3 LG RESU16H Prime batteries. I'm getting the invalid address error in the debug log for the batteries.
The backup interface (or at least the meter inside it) i believe is showing as meter m2: SE-MTR-3Y-240V-A. Anything i can do to help get support for these batteries?

[muenchris]

@brde21 my system was setup in 2021 and is working since that time just fine - but with one big caveat: Since SolarEdge ModBus server only allows one client connection and SPAN is keeping this connection open all the time, I cannot access my SolarEdge Inverter directly anymore.
Even worse - my second inverter that also has Modbus enabled constantly loses its IP address. I filed this issue with SolarEdge multiple times but did not get any feedback from them.

When SPAN connected to my SolarEdge system, there was a young kid at SPAN that made all that happen. Unfortunately he left SPAN and now I dont have any engineering connections to SPAN anymore.

This year I am starting a new endeavor: I founded a new company "Hyviva" that will be developing Energy Backup Solutions based on Hydrogen. The system we are designing will also interface with SPAN and SolarEdge and my hope is that I can become a partner of both - giving them some guidance how to integrate with other systems including HA,

I am also involved with the IEC 62541 (OPC UA) and chair the working group to standardize the communication for Solar Installations via OPC UA <- NO MORE MODBUS!! There is already work going on to add OPC UA Support for HA: OPCUA for HA and https://community.home-assistant.io/t/opc-ua-interface-to-ha/45603

The IEC and OPC Foundation will be reaching out to SolarEdge to convince them to use OPC UA instead of SunSpec in the future. Although, I doubt that they will retrofit there existing devices with OPC UA and we might need a ModBus->OPC UA shim to "upgrade" older devices.

Once I have more information about our progress I will post an update here.

[brde21]

@muenchris Thanks for the response! Sadly that sounds like just more dead ends with this.

Best of luck in your new venture, I hope all goes well! And I hope you have better luck communicating with SolarEdge than I have, should you choose to try to partner with them. As far as I have seen their customer service and technical support is quite possibly the worst of any company I have ever dealt with.

[brde21]

@muenchris do you happen to know what firmware version your inverter is running? And do you know if it has been updated since span.io worked with SolarEdge to get it working?

I am wondering if they flashed an old firmware version that still has access to the battery registers.

[muenchris]

Both my inverters are on 4.19.39 (December 2023 release). I am in the US I hope that helps.
I see a new version 4.20.32 that just came out. https://www.solaredge.com/en/support/setapp-inverters-firmware but I dont see any significant changes relevant to my setup.
My Span Firmware is: spanos2/r202333/11.1
So far all is still working.

[brde21]

Okay, that's the same version I am on so it's not directly firmware related. I guess SolarEdge is just being a bunch of clueless a-holes towards me.

[muenchris]

Does anyone have have a Generator interface on the Backup Interface of SolarEdge? I had this installed with my initial installation back in 2021 and a generator is supposed to charge the batteries at times when the power is out and the batteries are low.
The SetApp is showing support for this under "Alternate Power Source". And I am also wondering if there is any indication in the Modbus signals when this "alternate power source" is in use - and even cooler how much energy is flowing into the SolarEdge system. this might all not be supported/enabled by SolarEdge but I was wondering if anyone has experience on this. I have a cryptic message from SolarEdge that this will be available in firmware 4.17 - but did not get final confirmation for it.

[muenchris]

Short update on this: I am no longer using a gas-generator but the new Ecoflow Delta Pro Ultra: https://www.ecoflow.com/us/delta-pro-ultra

There is a HASS integration for some of the Ecoflow products, but not for the DPU, yet.
https://github.com/tolwi/hassio-ecoflow-cloud
The main reason is that the DPU is using protobuf for its communication and the HA integration has not been updated to support this, yet.

The process to run this "solar+battery generator" in my house is still the same as with the gas-generator. Ecoflow has their own "transfer switch" called "Smart Home Panel" which is similar to the SPAN panel but much less featured. Ecoflow also has the Energy-Ocean which is a fully integrated battery+inverter system. My expectation is that these integrated and easy to setup systems will eventually replace the more complicated multi-device systems like SolarEdge or Enphase.

I do love the DPU and successfully integrated it with my EMS (based on the Home-Relay: http://stage.home-relay.com/)
which we will release soon. (its an alternative to HA running on .NET and using C-Sharp Plugins). In my home the HR and HA work together but moving forward most of my work will go into the HR and Energy-Relay.

The IO-Broker Community has made some great progress on the DPU integration - unfortunately its all in German (my native language) https://forum.iobroker.net/topic/66743/ecoflow-connector-script-zur-dynamischen-leistungsanpassung.

[cralwalker]

That is interesting. I visited a brand-new offgrid home last weekend with a rather small home battery. The rationale is to rely on solar mostly (Australia) and V2H in case of extended poor weather conditions, there is no other generation on site.

Out of curiosity, is home-relay intended to be a commercialised competitor?

[muenchris]

I am not a big fan of Python coming from the industrial automation space and do not want to compete with HA but rather extend the reach to the C-Sharp/.NET community. The core IoT Engine of the HR is the C-DEngine that was owned by TRUMPF, a big German Industrial Machine Manufacturer (https://www.trumpf.com). My company (C-Labs) has developed it and is now maintaining the engine on Github (https://github.com/TRUMPF-IoT). Its also used in industrial gateways such as the Enapter Electrolyzer Gateway https://handbook.enapter.com/software/gateway_software/ (for the OPC UA Server)

So far, we have not decided if we keep the HR free/open-source or go commercial. The HR comes with (free) cloud-access like HA but does costs us money to run. We might keep the HR free and commercialize the upcoming Energy-Relay which focuses more on integrated Energy Monitoring, Management and Optimization.
Data can flow between the HA and HR via MQTT and its very good possible that we come up with a better integration model of the two. (for example have all the "Things" in the HR exposed as devices in HA).

[WillCodeForCats]

I personally don't use Python at all outside of HA (my two HA integrations are the first time I ever used Python) but I do feel it opens contributions to a wider base. But it also makes it easy to insert lesser quality integrations that cause problems, so there are two sides to it being "easy". My other modbus stuff is in C using libmodbus.

For example: the original Open Z-Wave in HA (ozw) was written in C++ and suffered from a lack of support and contributors which ultimately led to its removal and replacement by Z-Wave JS. This Node.js based version has a significantly wider and more active contribution base than C++ Z-wave did since it's easier to jump into JS than C++.

[muenchris]

I am not saying that Python is bad - just that I don't like it :). It was originally received for Web Applications and not stationary or even IoT Drivers. It has a large community and therefore its important - just not my cup of tea.
Back in the days I started with C++ writing games, but I got tired of managing buffers and strings. But when it comes to low-level fast code there is no way around C++ or even C.

[WillCodeForCats]

If anyone has three batteries, please try manually installing this: https://github.com/WillCodeForCats/solaredge-modbus-multi/archive/refs/tags/b3-test-1.zip

It's a blind read test based on the existing battery for 2 batteries, and if that doesn't work I an try the "battery 1 mirror" location too.

Mirror b1 address for b3: https://github.com/WillCodeForCats/solaredge-modbus-multi/archive/refs/tags/b3-test-2.zip

[WillCodeForCats]

I didn't expect it would be able to see a third battery, but I wanted to try and see anyway.

If you only have one inverter it doesn't really matter what its ID is.

[cralwalker]

Okay.

I have three inverters but only see one of them. In the Options menu, I have Auto-Detect ticked for both meters and for batteries.

[WillCodeForCats]

If you have three inverters as long as the IDs are sequential it should be fine.

[WillCodeForCats]

If you don't see all of your inverters you have to make sure they are set up correctly with incrementing IDs, and that the integration is added with the lowest ID as the starting ID and the total number of inverters. So if you have 3 inverters then you would set number of inverters = 3 and the lowest ID number as the inverter modbus address.

https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Configuration#integration-configuration

[cralwalker]

All done. For some reason all three inverters (Leader and followers) had Modbus ID set to 1. The meters also had the same Modbus IDs set.

I retried test1 and test2, unfortunately with the same result as above.

[bdimcheff]

Does anybody have what, exactly, they asked solaredge to do in order to enable the modbus power control/battery registers? I scanned all my registers and it's pretty clear that the battery ones aren't enabled.

I sent this to support:

In case 3341908 I was attempting to access battery and power management modbus registers on my inverter, but they were unavailable. More recently, I spoke to other solaredge customers who said that those registers need to be enabled remotely by someone at solaredge. Can you please enable them for me? Thanks, Brandon

And I got this back:

We are unsure what settings you are are referring to . If you are talking about power control and meter settings these can only be access by an installer or Solar Edge. They are not on the homeowner app. Reply to this email with what exactly you want the system to do or to do, then we will have an idea what settings you need to be changed.

Obviously this person has no idea what I'm talking about, but I'm hoping someone here has had some luck asking for a particular department or person or something.

Thanks!

[bdimcheff]

@GregEdge I don't think it matters if you have installer access in order to access the modbus stuff once it's enabled, it's just that their support department is resistant to enabling the registers without a request from an installer. I've asked my installer a few times to ask SE to do it, and they're dragging their feet, I think mostly because they have no idea what I'm talking about 😂. I may take another run at SE directly via telephone or something, but I'll definitely post here when/if I manage to get someone to enable it.

[m01]

I read in a reply to one of the Google Play Store reviews of the mySolarEdge app that there was "early beta testing for the homeowner battery control feature"; the reply also mentioned how to ask to be included in this beta. I wonder if the Modbus power control is linked to that.
I sadly don't know how to link directly to the review, but it was dated March 2, 2023. (Disclaimer: Opinions my own)

[Ashpork]

It’s in the app now, doesn’t give too many clues how it works but it’s taking very much the SolarEdge approach in being suitable for hands off users.

the only real setting is to leave the system with the installers defined settings, or have the solarEdge logic of supposedly charging during off peak (if needed?). A screenshot from the app describing the settings below.

[brde21]

@bdimcheff @cpaquette63 Did either of you ever successfully figure out the magic words or the correct person to talk to in order to get the battery register enabled? I am in the same boat here. I am a certified installer and they still wont entertain my request. Every single person I talk to in tech support so far is complete clueless and useless on every issue I have submitted a ticket for, not just this scenario. Obviously at least one person there knows something about it though.

[bdimcheff]

nope! I have basically given up and check here every few months to see if anyone else has luck. I need to badger my installer again.

[cralwalker]

Ping, if there are any other tests I can do to help identify the integration of battery 3?

[WillCodeForCats]

Probably not. The modbus spec only defines 2 batteries, so any test I were doing were just "see what would happen" attempts, nothing I seriously expected to work. Unless SolarEdge revises their modbus support to define more batteries two will remain the limit.

[Thebasestar]

Ping, if there are any other tests I can do to help identify the integration of battery 3?

I've got 3 batteries as well, i'm unable to set correct sensor for energy dashboard (added 2 batt and missing data for the 3rd), can you please share your setup or give me advice??

[WillCodeForCats]

Read: #285

[Thebasestar]

Yes, i know, i'm just trying to find a workaround for the statistics, maybe using a calculated sensor to add a ghost 3rd battery to the energy dashboard,? I'd like to know, how people with 3 batteries like me are settings the energy dashbord, i'm a newbie on this......
Thanks
sunspec-implementation-technical-note 25.pdf
Found this updated, if it can help

[cralwalker]

If I had a statement their devs would get, I will lodge a product request? On Saturday, April 1, 2023, 2:00 am, Seth ***@***.***> wrote: Probably not. The modbus spec only defines 2 batteries, so any test I were doing were just "see what would happen" attempts, nothing I seriously expected to work. Unless SolarEdge revises their modbus support to define more batteries two will remain the limit. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[WillCodeForCats]

It's been reported in discussion #233 modbus may now support three batteries.

Please try Release v2.4.9-pre.2 if you have a third battery.

[WillCodeForCats]

Please report your firmware version too if it works.

[cpaquette63]

I have 2 SE batteries and a SE10000H-US (my second one due to failure on the first). I wish I had news to share but I have nothing. I keep hoping like everyone else in this situation.

…

On Thu, Feb 29, 2024, 5:23 PM brde21 ***@***.***> wrote: @jeremy-asher <https://github.com/jeremy-asher> Yes, I do have LG batteries. I don't think it would have anything to do with the battery manufacturer though. It appears, from what I understand, to be a setting or access permission in the inverter firmware itself. I would like to see the SetApp screens from an inverter that the battery access has been enabled on as well. Perhaps it would offer some clue. I keep hoping @rtlinux <https://github.com/rtlinux> or @bdimcheff <https://github.com/bdimcheff> or @cpaquette63 <https://github.com/cpaquette63> would see these posts or an auto-email notification and chime in, but no luck with that so far either. — Reply to this email directly, view it on GitHub <#63 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4T7HBBEAWDHD7CZ6P3ZUPTYV6U6DAVCNFSM55CBRHI2U5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TQNRTGYZTGMY> . You are receiving this because you were mentioned.Message ID: <WillCodeForCats/solaredge-modbus-multi/repo-discussions/63/comments/8636333 @github.com>

[brde21]

@cpaquette63 Thanks for the update though. Hopefully one of us will get a resolution soon. Sounds like @rtlinux is the only one who has had any success.

[cralwalker]

I now see the third battery, yayh.

• SolarEdge Modbus Multi v2.4.11-pre.1
• Inverter 0004.0019.0039
• Battery SMCU 1.1.29 DCDC 0.0.81 BMS 0.6.

[cyberkryten]

I am also seeing a third battery, now it is all connected up :)

Can you add a known issue to ensure people are aware that the Battery Firmware Version is truncated and so doesn't show the BMS value correctly.

The firmware of the battery is reported by the SolarEdge Integration as an attribute to sensor.solaredge_batteries which has the following text for the first battery in my system:

firmwareVersion: SMCU 1.1.35 DCDC 1.0.28 BMS 1.0.51

In this integration, this gets reported in sensor.solaredgemodbus_b1_version as:

SMCU 1.1.35 DCDC 1.0.28 BMS 1.0.

The last two digits (51) are missing

You can see the same issue present in cralwalker's report above, the BMS version is missing at least one digit after the period

Given there are 32 characters, it seemed suspiciously like there's a hard limit and reading through the spec for Power Control on Page 21 it does seem that the return is a 32 character string, so I assume there's nothing that can be done.

E220  16  R  Battery 2 Firmware Version  String[32]

Debug shows the value exactly the same as reported, so I think known issue is all that can be done as I can't see anywhere else to get the value from:

2024-03-22 15:20:39.824 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Registers received requested : 68 68
2024-03-22 15:20:39.824 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1B1: B_Manufacturer SolarEdge <class 'str'>
2024-03-22 15:20:39.824 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1B1: B_Model SE Energy Bank <class 'str'>
2024-03-22 15:20:39.824 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1B1: B_Version SMCU 1.1.35 DCDC 1.0.28 BMS 1.0. <class 'str'>
2024-03-22 15:20:39.824 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1B1: B_SerialNumber 63084CAB <class 'str'>
2024-03-22 15:20:39.824 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1B1: B_Device_Address 0x4cab <class 'int'>
2024-03-22 15:20:39.824 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1B1: B_RatedEnergy 0x46179000 <class 'float'>
2024-03-22 15:20:39.824 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Found I1B1

[WillCodeForCats]

Yes, only 32 characters are available for that value over modbus (16 registers at 2 characters per register).

[cyberkryten]

If only they'd looked at the data being returned and changed 'DCDC' to 'DC' it would have all fitted fine

[mikedeluca]

Does it have anything to do with Power Control settings? Some (old) documentation Power Control Open Protocol (photovoltaikforum.com)<https://www.photovoltaikforum.com/core/attachment/88445-power-control-open-protocol-for-solaredge-inverters-pdf/> seems to imply that if you dont have these set it wont work: To enable the dynamic power control mode, set the following:  AdvancedPwrControlEn on address 0xF142 to 1 (enable). It is disabled (0) by default.  ReactivePwrConfig on address 0xF104 to 4 (RRCR mode). It is set by default to 0 (Fixed CosPhi mode).  Issue a Commit Power Control Settings command on address 0xF100 in order to make this setting effective That said, I dont even seem to be able to read those registers to begin with. I set what i think were the right ones in setapp, but nothing changed.

…

________________________________ From: brde21 ***@***.***> Sent: Friday, March 29, 2024 11:58 AM To: WillCodeForCats/solaredge-modbus-multi ***@***.***> Cc: mikedeluca ***@***.***>; Mention ***@***.***> Subject: Re: [WillCodeForCats/solaredge-modbus-multi] Battery integration (Discussion #63) Okay, that's the same version I am on so it's not directly firmware related. I guess SolarEdge is just being a bunch of clueless a-holes towards me. — Reply to this email directly, view it on GitHub<#63 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEPAANQM4BJEUPTJA5VLV7LY2W2VVAVCNFSM55CBRHI2U5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TQOJVGQ4TKNI>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[WillCodeForCats]

I added those to the integration in v2.4.10.

But if you don't have the registers to begin with, no, they can't be set.

[brde21]

Not sure what exactly you're referring to by "it" but yeah, in my case I don't even have access to F142, F104, and F100 registers to set those values. The inverter just returns "illegal data address". Although with the latest firmware version, it doesn't return anything at all which is concerning.