Solarman LSE module disconnection

[adnovea]

MartinNeurol says :

There is always a risk when you don't perfectly understand what you do. Read carefully all the instructions. This is not a "plug&play" module. It has not been tested with many inverters nor fully debugged. I just share what I'm currently using for my Deye Sun 5K but you must understand what you are doing. As long as you avoid writing to the inverter registers, the risk is limited. Do not use "switch/select" entities to prevent sending unexpected commands and keep only "sensor" registers.

Hi! I am using the Solarman LSE for my SUN-10K-SG04LP3-EU. Everytime I set up the interation, in less then 24 HRS, my inverter falls into COM error and has to be restarted. That never happens when the integration is off. As I am using LSE version and my neigbor literally has the same solution, but with standard Solarman integration and wireless logger working just fine, I am just asking - where to look, who to ask? Or ditch it? Many thanks, Martin

[adnovea]

Hi MartinNeurol,

I don't think you need to RESTART the inverter but only the LSE module (press the reset button under the RJ-45 cap or disconnect/reconnect the module to the inverter). To identify where the disconnection comes from, when disconnected try to access the the Solarman LSE module web interface (screenshot below). If you can display the screen below, there is a problem with the home assistant module.

What are the info in the log (Parameters > System > Log) ? If you do not identify info in the log related to the Solarman LSE, enable the add-on debugging (Parameters > Devices & Services > Solarman LSE and enable the log).

[MartinNeurol]

Hi! I finally found some time to test this. i Turned on the Solarman LSE this morning, about 12:35 my inverter stopped responding correctly. there was absolutely nothing in the log except this:

_Update of sensor.lse_pv1power is taking over 10 seconds this happened 117 times today.

and this: _Updating solarmanlse sensor took longer than the scheduled update interval 0:00:30

I can log into the logger web, but that too is showing the same data from 12:35 even now (18:55).

I have just enabled addon logs and this is appearing now: Logger: custom_components.solarman_lse.solarman Source: custom_components/solarman_lse/solarman.py:331 integrace: Solarman LSE (dokumentace, problémy) first appearance: 09:23:26 (97 appearances) last time logged: 18:55:27

Querying registers [514 - 558] failed, aborting. Querying registers [598 - 636] failed, aborting. Querying registers [644 - 653] failed, aborting. Querying registers [586 - 591] failed, aborting. Querying registers [3 - 89] failed, aborting.

I am using deye_sg04lp3.yaml and have SG04LP3 EU inverter.

Thank you for your cooperation,

Martin

[MartinNeurol]

More info, after soft restart of the logger clicked from the web, the logger still shows wrong data from 12:35.

The inverter too was showing wrong data and COMM error, but nothing in inverter logs.

I diconnected the logger, it reconnecd and started to show the same wrong data again (because inverter...)

So I had to do the full inverter turn off/ turn on to get it working again :/

Best regards,

Martin

[adnovea]

Maybe it comes from the Solarman_LSE add-on but unfortunately I have no clue what could be the problem. I just share what is working for me (Deye 5K ) and have only this inverter.

The fallback will be to use the SolarmanPV application if it works for you. There was applications for retreiving the data from SolarmanPV API to HA as far as I remember.

Here are some ways to investigate further :

1. Install GModBus and check each register manually. Maybe one or more are wrong in the deye_sg04lp3.yaml. It was the case with my Deye 5K so I created a specific YAML file.
2. There are some limitations when requesting Registers : Max number of registers per request is <123 and too frequent requests may also overload the comm. Try grouping the requests to reduce the number or requests.You are currently overlapping the registers and requesting several time the same values e.g.: [3 - 89], [514 - 586], [587 - 653]
3. Check if SolarmanPV is working fine over the time otherwise there is maybe a need for inverter F/W update.

Have a nice day

[MartinNeurol]

Thank you very much for your response. As I am only a dumb customer that knows nothing about modbus and have no intentions to set my house on fire while trying to "tweak" my inverter :D So I will probably just abandon the HA solution for the moment. Also, it seems that I am the only on to have similar issue, so... screw it.

Solarman Smart web pages give Bad gateway, But the app still somehow works. Many thanks, Martin