Solis S6-EH3P20K-H with USB S2-WL-S and a separate RS485 port misbehaving :)

[DG-Lt]

Hi,
@Pho3niX90 First of all thank you for this integration. It has been working reliably while I was using it connected directly to the Solis Dataloggers IP address.

As described on this thread my inverter has a separate RS485 port. So I connected a Waveshare RS485 POE Gateway and switched from dataloggers IP to waveshare's.
I also updated the solis_modbus integration to 3.1.9 and chosen Waveshare as connection type in the Add Device dialog.

initially all seemed to be working ok. But after a day I noticed weird statistics:

I have found that the Battery energy sensors (kWh) are off by 10x or 100x
Other kWh sensors seem to be ok:

I have solved this by introducing a proxy template sensor that multiplies battery charge values by 10x and 100x when needed (also had to import the history from Solis sensors before the switch to waveshare) this of course cost a lot of time :(

- name: "Solis Total Battery Discharge Energy proxy"
      unique_id: fbaadc26-fafb-4ab4-b3fc-aaf24a9aa0bf
      unit_of_measurement: "kWh"
      device_class: "energy"
      state_class: "total_increasing"
      availability: "{{ states('sensor.solis_total_battery_discharge_energy') | is_number }}"
      state: >-
        {{ states('sensor.solis_total_battery_discharge_energy')|float*100 }}

So it fixed my statistics.

But maybe there is a possibility for a fix in the integration itself?
I have found only 4 sensors misbehaving:
Solis Total Battery Charge Energy
Solis Total Battery Discharge Energy
Solis Today Battery Charge Energy
Solis Today Battery Discharge Energy

[Pho3niX90]

Hey

The waveshare option is only to change the multipliers on some sensors, it doesn't aid in the connection to the device at all.

The reason being is that some waveshare devices/connections need adjusting for some reason, see the docs here https://solis-modbus.readthedocs.io/en/latest/sensors.html#solar-inverter-modes-in-solis-inverters

If it's not needed for your connection, you can just select the S2 option instead of waveshare in the config.

[DG-Lt]

Thank you.

It worked.

• And I had to restart the whole Home Assistant after changing the connection type. Reloading the integration, disabling/enabling the device was not enough.
• Removed the multipliers from my proxy sensors...

May I suggest adding some more nuances here, what different options on the Add Device dialog mean etc. ;)
also here could be mentioned that this applies to device setup.

Eventually I have resolved problem on my system after your advice, but I am really not sure how I could have connected these dots on my own.

[Pho3niX90]

Great suggestions, it has changed a lot since that intiall readme. Will update it

[Pho3niX90]

Also, if you made the condig chages, without restarting the integration try restarting it first.

[Pho3niX90]

Also, if you made the condig chages, without restarting the integration try restarting it first.