What Ginlong Solis Inverter are you using?

[wills106]

I need a bit of help from the community.

I don't really know which versions Ginlong Solis Inverters this works with in the current state. There seems to be at least three versions of Modbus protocols in use..

The newer type has the Serial Number starting at input register 0x80EC / 33004
The older type has the Serial Number starting at input register 0xBF5 / 3061

Newer Inverters such as the Solis RHI-6K-48ES-5G use plugin_solis.py
The first two digits refer to the power rating, the 3rd to 6th digit of Serial Number will be '3105' although there will be other unknown Serial Numbers, for example for the Three Phase. 3105 is the model number of the Inverter.

Older Inverters will use plugin_solis_old.py
I don't know how these Serial Numbers will be formatted.

If you own a Ginlong Solis Inverter could you please test both plugins.
You will get three possible outcomes:
1 - Mostly working Integration
2 - Following error in your log "cannot find serial number, even not for other Inverter"
3 - Following error in your log "unrecognized inverter type - serial number : {your serial number}"

If you get 1 or 3 could you please let me know your Inverter type, Inverter rating, which plugin worked, first 4 digits of the serial number. We can then hopefully build from there and fully support your particular Inverter.

[vizkoze]

Hi
im using a solis RHI-5K-48ES-5G inverter
trying to connect trough tcp on port 8899 but no entities show up.
im very new to homeassistant and modbus so mistakes in setup might occur

here is my setup wile logging in directly into the logger:
Firmware version (main)003D
Firmware version (slave)0037
Inverter model3104

[vizkoze]

Hello Wills
that last update with modification
"native_unit_of_measurement = ENERGY_WATT_HOUR,"
breaks the plugin. try reverting that to ENERGY_KILO_WATT_HOUR

[wills106]

I forgot to add ENERGY_WATT_HOUR into const

[wills106]

const.py updated

[solarjones]

Hi,
I've got a Solis Hybrid RHI-6K-48ES-5G s/n 603105.... and have added this integration but not getting any entities found.

I'm using a Solis LAN stick (modbus TCP) and confirmed the Solax is using TCP and selected the Solis option. I've specified the IP & port (30003) of the logger are correct. Received Successfully Added but no entities are exposed.

Port 80 & 30003 are open not 8899. But I tried with 8899 and got the same.

HA v2022.11.2
Solax build was from yesterday.

This error originated from a custom integration.

Logger: custom_components.solax_modbus.plugin_solis
Source: custom_components/solax_modbus/plugin_solis.py:114
Integration: SolaX Inverter Modbus (documentation, issues)
First occurred: 23:16:51 (2 occurrences)
Last logged: 23:16:56

unrecognized solisHybrid inverter type - serial number : 6031050nnnnnnn

Note my inverter s/n is 16 digits long, not 14 as logged above.

Have I missed something or not setup it up correctly?

thanks!

UPDATE:
I updated the integration to 0.7.0b39 and now see code changed in plugin_solis.py and now logs error:
This error originated from a custom integration.

Logger: custom_components.solax_modbus.plugin_solis
Source: custom_components/solax_modbus/plugin_solis.py:97
Integration: SolaX Inverter Modbus (documentation, issues)
First occurred: 00:04:51 (1 occurrences)
Last logged: 00:04:51

unrecognized SolisHybrid inverter type - serial number : unknown

[wills106]

Do you have batterie's connected to your Inverter?
The reason being, if you try and connect to your Inverter at night when the Inverter is sleeping due to no Solar PV and no batteries to keep it energised you wont be able to communicate to anything. As the Inverter essentially shuts down, then when you get enough Solar PV the next day it wakes up again.

[solarjones]

I do have batteries connected. However, looking in plugin_solis.py it was missing my serial number type so I added it (it was there in a previous version)

if seriesnumber.startswith('603105'): invertertype = HYBRID | X1

Is this correct for my inverter type: RHI-6K-48ES-5G and I've 9.2kWh of Pylontech batteries attached.
And I got 92 entities now! I am very scared of changing any of the charging options (write_register) in case I send something my inverter doesn't like.

Thanks.

[wills106]

Your Inverter is already supported:

homeassistant-solax-modbus/custom_components/solax_modbus/plugin_solis.py

Line 90 in 794d356

if seriesnumber.startswith('6031'): invertertype = HYBRID | X1 # Hybrid Gen5 3105 / 3122 Model

So not sure why it didn't work yesterday for you?

[wills106]

I have a typo in the Serial Number check. I have a double if statement that breaks it.

I'll release 0.7.0b41 shortly.

[solarjones]

@wills106 this is amazing work. I've spend many months searching the web to get an integration that actually works with my Solis Hybrid inverter. So thank you!

Now I've started exploring the entities and functions, I'm a bit stuck on these options to control the batteries. Note these values haven't been touched and present once the integration fired up:

The Solis inverter has different time slots to either charge or discharge the batteries and controlling Amp limits for both. Unsure what to do with the SolaX/Solis options.
Thanks.

[wills106]

These still need looking at, each Inverter seems to return something different. The hours are only meant to be 0-23 and mins 0-59.
I would have expected your Battery Charge to be at the default 50A (I think that's the default?)

You also can't change the modes at the moment either, as that isn't implemented yet.

[wills106]

@solarjones I have just pushed out 0.7.0b46 0.7.0b51 Does it correct all those random values?
You times for example should be 0-23 hours and 0-59 mins.

[alienatedsec]

@solarjones what method are you using to connect? My WiFi stick is not working correctly or potentially not supported - weird as it is working with solismod and solismon - see #264

[solarjones]

Noticed lots of these logs...

Is it changing something on the inverter or reading the values for power factor?
Thanks.

[wills106]

The Inverter is updating the Integration. The Integration by itself can't write to the Inverter, unless you do an automation or manually change something.

[solarjones]

Ok thanks. I got a bit worried as there's a write.register function in the code. Perhaps have a toggle in the to enable write functions (default to read only)?

[wills106]

The Integration can't do anything by itself. So nothing to worry about!

[jone9618]

Hello

I'm getting "unrecognized Solis inverter type - serial number : 160F............." in my HA log

I have a Solis RHI-3.6K-48ES-5G

Let me know if you need other information.

Any help appreciated.

[wills106]

I have just added your Serial into release 2023.01.2b5

[jone9618]

FWIW that was with the plugin_solis.py

When I change to solis_old I get the following messages in the HA log:

"Solis: reading serial number from address 0xbf5 failed; other address may succeed"

followed by:

"Solis: cannot find serial number, even not for other Inverter"

And finally:

"unrecognized Solis inverter type - serial number : unknown"

[jone9618]

I have just added your Serial into release 2023.01.2b5

Thank you

[jone9618]

Fantastic. Integration working now. Thank you very much. Really appreciate your work on this, and for turning my query around so quickly.

[wills106]

It's ok, glad I could help.

[durkimat]

I have this working well with my solis S5-eh1p6k-l. Software version 3D0037. This is the latest series of single phase hybrids, installed late last year.

I tested changing charge times, current etc and that works, although I am not using it in an automation.

Is there a description of the 'energy storage control switch' modes? They seem to differ to what appears on the front panel of the inverter. I would very much like to switch the inverter to 'backup mode' during my overnight charge window (octopus go), as currently once it hits 100% battery, it starts discharging, which is a problem if my ev is charging. But I'm unsure if this control relates to this. I'm wondering if 'Battery Awaken' is same as Battery Backup mode, just different terminology, and 'auto' same as self-use?

[alienatedsec]

I'll test and make appropriate video and debugging posted here, but it will take some time - hopefully by the end of today.

[wills106]

A video isn't necessary.
The previous method didn't work for all Inverters, so a solution is being worked on to allow functionality on a wider set of Solis Inverters.

[alienatedsec]

The previous method didn't work for all Inverters, so a solution is being worked on to allow functionality on a wider set of Solis Inverters.

It seems to be the right approach to cover one with many (or many with one approach), and if that can be achieved, it would be a great success.

Hopefully, it is not too much for this view, but please see the below, which could be useful. Video at the very bottom.

2023-01-30 14:30:14.830 INFO (MainThread) [custom_components.solax_modbus] trying to load plugin - plugin_name: solis
2023-01-30 14:30:14.831 INFO (MainThread) [custom_components.solax_modbus.plugin_solis] SolisLAN: trying to determine inverter type
2023-01-30 14:30:14.944 INFO (MainThread) [custom_components.solax_modbus.plugin_solis] Read SolisLAN 0x80ec serial number: [REDACTED], swapped: False
2023-01-30 14:30:14.947 INFO (MainThread) [homeassistant.components.button] Setting up button.solax_modbus
2023-01-30 14:30:14.947 INFO (MainThread) [homeassistant.components.number] Setting up number.solax_modbus
2023-01-30 14:30:14.948 INFO (MainThread) [homeassistant.components.select] Setting up select.solax_modbus
2023-01-30 14:30:14.948 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.solax_modbus
2023-01-30 14:30:14.949 INFO (MainThread) [custom_components.solax_modbus.button] hub.wakeuButton: None
2023-01-30 14:30:14.950 INFO (MainThread) [custom_components.solax_modbus.sensor] newblock declaration found for empty block
2023-01-30 14:30:14.950 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0xa86c battery_chargedischarge_current to block with start 0xa86c
2023-01-30 14:30:14.951 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0xa86d battery_charge_current to block with start 0xa86c
2023-01-30 14:30:14.951 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0xa86e battery_discharge_current to block with start 0xa86c
2023-01-30 14:30:14.951 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0xa885 timed_charge_current to block with start 0xa86c
2023-01-30 14:30:14.951 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0xa886 timed_discharge_current to block with start 0xa86c
2023-01-30 14:30:14.951 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0xa887 timed_charge_start_h to block with start 0xa86c
2023-01-30 14:30:14.951 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0xa888 timed_charge_start_m to block with start 0xa86c
2023-01-30 14:30:14.951 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0xa889 timed_charge_end_h to block with start 0xa86c
2023-01-30 14:30:14.951 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0xa88a timed_charge_end_m to block with start 0xa86c
2023-01-30 14:30:14.951 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0xa88b timed_discharge_start_h to block with start 0xa86c
2023-01-30 14:30:14.951 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0xa88d timed_discharge_end_h to block with start 0xa86c
2023-01-30 14:30:14.951 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0xa88e timed_discharge_end_m to block with start 0xa86c
2023-01-30 14:30:14.951 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x80ec serialnumber to block with start 0x80ec
2023-01-30 14:30:14.951 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8105 power_generation_total to block with start 0x80ec
2023-01-30 14:30:14.952 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8107 power_generation_this_month to block with start 0x80ec
2023-01-30 14:30:14.952 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8109 power_generation_last_month to block with start 0x80ec
2023-01-30 14:30:14.952 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x810b power_generation_today to block with start 0x80ec
2023-01-30 14:30:14.952 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x810c power_generation_yesterday to block with start 0x80ec
2023-01-30 14:30:14.952 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x810d power_generation_this_year to block with start 0x80ec
2023-01-30 14:30:14.952 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x810f power_generation_last_year to block with start 0x80ec
2023-01-30 14:30:14.952 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8119 pv_voltage_1 to block with start 0x80ec
2023-01-30 14:30:14.952 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x811a pv_current_1 to block with start 0x80ec
2023-01-30 14:30:14.952 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x811b pv_voltage_2 to block with start 0x80ec
2023-01-30 14:30:14.953 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x811c pv_current_2 to block with start 0x80ec
2023-01-30 14:30:14.953 INFO (MainThread) [custom_components.solax_modbus.sensor] Starting new block at 0x811d
2023-01-30 14:30:14.953 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x811d pv_voltage_3 to block with start 0x811d
2023-01-30 14:30:14.953 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x811e pv_current_3 to block with start 0x811d
2023-01-30 14:30:14.953 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x811f pv_voltage_4 to block with start 0x811d
2023-01-30 14:30:14.953 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8120 pv_current_4 to block with start 0x811d
2023-01-30 14:30:14.953 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8121 pv_total_power to block with start 0x811d
2023-01-30 14:30:14.953 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8131 inverter_voltage to block with start 0x811d
2023-01-30 14:30:14.953 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8134 inverter_current to block with start 0x811d
2023-01-30 14:30:14.953 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8137 active_power to block with start 0x811d
2023-01-30 14:30:14.953 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8139 reactive_power to block with start 0x811d
2023-01-30 14:30:14.953 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x813b apparent_power to block with start 0x811d
2023-01-30 14:30:14.953 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8145 inverter_temperature to block with start 0x811d
2023-01-30 14:30:14.954 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8146 grid_frequency to block with start 0x811d
2023-01-30 14:30:14.954 INFO (MainThread) [custom_components.solax_modbus.sensor] Starting new block at 0x8166
2023-01-30 14:30:14.954 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8166 meter_total_activepower to block with start 0x8166
2023-01-30 14:30:14.954 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8168 meter_voltage to block with start 0x8166
2023-01-30 14:30:14.954 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8169 meter_current to block with start 0x8166
2023-01-30 14:30:14.954 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x816a meter_active_power to block with start 0x8166
2023-01-30 14:30:14.954 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x816c energy_storage_control_switch to block with start 0x8166
2023-01-30 14:30:14.954 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x816d battery_voltage to block with start 0x8166
2023-01-30 14:30:14.954 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x816e battery_current to block with start 0x8166
2023-01-30 14:30:14.954 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x816f battery_charge_direction to block with start 0x8166
2023-01-30 14:30:14.954 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8173 battery_soc to block with start 0x8166
2023-01-30 14:30:14.954 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8174 battery_soh to block with start 0x8166
2023-01-30 14:30:14.954 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8175 bms_battery_voltage to block with start 0x8166
2023-01-30 14:30:14.955 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8176 bms_battery_current to block with start 0x8166
2023-01-30 14:30:14.955 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8177 bms_battery_charge_limit to block with start 0x8166
2023-01-30 14:30:14.955 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8178 bms_battery_discharge_limit to block with start 0x8166
2023-01-30 14:30:14.955 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x817b house_load to block with start 0x8166
2023-01-30 14:30:14.955 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x817c bypass_load to block with start 0x8166
2023-01-30 14:30:14.955 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x817d battery_power to block with start 0x8166
2023-01-30 14:30:14.955 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8189 total_battery_charge to block with start 0x8166
2023-01-30 14:30:14.955 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x818b battery_charge_today to block with start 0x8166
2023-01-30 14:30:14.955 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x818c battery_charge_yesterday to block with start 0x8166
2023-01-30 14:30:14.955 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x818d total_battery_discharge to block with start 0x8166
2023-01-30 14:30:14.955 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x818f battery_discharge_today to block with start 0x8166
2023-01-30 14:30:14.955 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8190 battery_discharge_yesterday to block with start 0x8166
2023-01-30 14:30:14.956 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8191 grid_import_total to block with start 0x8166
2023-01-30 14:30:14.956 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8193 grid_import_today to block with start 0x8166
2023-01-30 14:30:14.956 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8194 grid_import_yesterday to block with start 0x8166
2023-01-30 14:30:14.956 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8195 grid_export_total to block with start 0x8166
2023-01-30 14:30:14.956 INFO (MainThread) [custom_components.solax_modbus.sensor] Starting new block at 0x8197
2023-01-30 14:30:14.956 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8197 grid_export_today to block with start 0x8197
2023-01-30 14:30:14.956 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8198 grid_export_yesterday to block with start 0x8197
2023-01-30 14:30:14.956 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8199 house_load_total to block with start 0x8197
2023-01-30 14:30:14.956 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x819b house_load_today to block with start 0x8197
2023-01-30 14:30:14.956 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x819c house_load_yesterday to block with start 0x8197
2023-01-30 14:30:14.956 INFO (MainThread) [custom_components.solax_modbus.sensor] Starting new block at 0x81e3
2023-01-30 14:30:14.956 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x81e3 meter_ac_voltage to block with start 0x81e3
2023-01-30 14:30:14.956 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x81e4 meter_ac_current to block with start 0x81e3
2023-01-30 14:30:14.957 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x81ef meter_activepower_total to block with start 0x81e3
2023-01-30 14:30:14.958 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x81f1 meter_reactive_power to block with start 0x81e3
2023-01-30 14:30:14.958 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x81f7 meter_reactive_power_total to block with start 0x81e3
2023-01-30 14:30:14.959 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x81f9 meter_apparent_power to block with start 0x81e3
2023-01-30 14:30:14.959 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x81ff meter_apparent_power_total to block with start 0x81e3
2023-01-30 14:30:14.959 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8201 meter_power_factor to block with start 0x81e3
2023-01-30 14:30:14.959 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8202 meter_grid_frequency to block with start 0x81e3
2023-01-30 14:30:14.959 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8203 meter_grid_import_total to block with start 0x81e3
2023-01-30 14:30:14.959 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0x8205 meter_grid_export_total to block with start 0x81e3
2023-01-30 14:30:14.959 INFO (MainThread) [custom_components.solax_modbus.sensor] Starting new block at 0xa88c
2023-01-30 14:30:14.959 INFO (MainThread) [custom_components.solax_modbus.sensor] adding register 0xa88c timed_discharge_start_m to block with start 0xa88c
2023-01-30 14:30:14.959 INFO (MainThread) [custom_components.solax_modbus.sensor] SolisLAN returning holding block: 0xa86c 0xa88f [43116, 43117, 43118, 43141, 43142, 43143, 43144, 43145, 43146, 43147, 43149, 43150]
2023-01-30 14:30:14.959 INFO (MainThread) [custom_components.solax_modbus.sensor] SolisLAN returning input block: 0x80ec 0x811d [33004, 33029, 33031, 33033, 33035, 33036, 33037, 33039, 33049, 33050, 33051, 33052]
2023-01-30 14:30:14.959 INFO (MainThread) [custom_components.solax_modbus.sensor] SolisLAN returning input block: 0x811d 0x8147 [33053, 33054, 33055, 33056, 33057, 33073, 33076, 33079, 33081, 33083, 33093, 33094]
2023-01-30 14:30:14.959 INFO (MainThread) [custom_components.solax_modbus.sensor] SolisLAN returning input block: 0x8166 0x8197 [33126, 33128, 33129, 33130, 33132, 33133, 33134, 33135, 33139, 33140, 33141, 33142, 33143, 33144, 33147, 33148, 33149, 33161, 33163, 33164, 33165, 33167, 33168, 33169, 33171, 33172, 33173]
2023-01-30 14:30:14.959 INFO (MainThread) [custom_components.solax_modbus.sensor] SolisLAN returning input block: 0x8197 0x819d [33175, 33176, 33177, 33179, 33180]
2023-01-30 14:30:14.960 INFO (MainThread) [custom_components.solax_modbus.sensor] SolisLAN returning input block: 0x81e3 0x8207 [33251, 33252, 33263, 33265, 33271, 33273, 33279, 33281, 33282, 33283, 33285]
2023-01-30 14:30:14.960 INFO (MainThread) [custom_components.solax_modbus.sensor] SolisLAN returning input block: 0xa88c 0xa88d [43148]
2023-01-30 14:30:14.969 INFO (MainThread) [custom_components.solax_modbus.sensor] computedRegs: {'battery_input_energy': SolisModbusSensorEntityDescription(key='battery_input_energy', device_class=<SensorDeviceClass.POWER: 'power'>, entity_category=None, entity_registry_enabled_default=True, entity_registry_visible_default=True, force_update=False, icon='mdi:battery-arrow-up', has_entity_name=False, name='Battery Input Energy', translation_key=None, unit_of_measurement=None, suggested_unit_of_measurement=None, last_reset=None, native_unit_of_measurement=<UnitOfPower.WATT: 'W'>, state_class=<SensorStateClass.MEASUREMENT: 'measurement'>, options=None, allowedtypes=4096, scale=1, read_scale_exceptions=None, blacklist=None, register=-1, rounding=1, register_type=1, unit='_uint16', newblock=False, value_function=<function value_function_battery_input_solis at 0x7f48a39df880>, wordcount=None, sleepmode=1, order16='>', order32='>'), 'battery_output_energy': SolisModbusSensorEntityDescription(key='battery_output_energy', device_class=<SensorDeviceClass.POWER: 'power'>, entity_category=None, entity_registry_enabled_default=True, entity_registry_visible_default=True, force_update=False, icon='mdi:battery-arrow-down', has_entity_name=False, name='Battery Output Energy', translation_key=None, unit_of_measurement=None, suggested_unit_of_measurement=None, last_reset=None, native_unit_of_measurement=<UnitOfPower.WATT: 'W'>, state_class=<SensorStateClass.MEASUREMENT: 'measurement'>, options=None, allowedtypes=4096, scale=1, read_scale_exceptions=None, blacklist=None, register=-1, rounding=1, register_type=1, unit='_uint16', newblock=False, value_function=<function value_function_battery_output_solis at 0x7f48a39df7f0>, wordcount=None, sleepmode=1, order16='>', order32='>')}
2023-01-30 14:30:52.492 INFO (MainThread) [custom_components.solax_modbus.number] writing SolisLAN timed_discharge_start_h number register 43147 value 0 after div by readscale 1 scale 1 <<< [I cant recall making this change, but maybe my lazy fingers]
2023-01-30 14:30:59.979 INFO (MainThread) [custom_components.solax_modbus] SolisLAN error reading holding registers at device 1 position 0xa86c
2023-01-30 14:31:56.636 INFO (MainThread) [custom_components.solax_modbus.number] writing SolisLAN timed_charge_end_h number register 43145 value 10 after div by readscale 1 scale 1 <<< [it didn't work for this value]
2023-01-30 14:32:28.945 INFO (MainThread) [custom_components.solax_modbus.number] writing SolisLAN timed_charge_end_h number register 43145 value 6 after div by readscale 1 scale 1 << [started working from here, you can see on the video]
2023-01-30 14:32:53.259 INFO (MainThread) [custom_components.solax_modbus.number] writing SolisLAN timed_charge_end_h number register 43145 value 11 after div by readscale 1 scale 1
2023-01-30 14:33:07.602 INFO (MainThread) [custom_components.solax_modbus.number] writing SolisLAN timed_charge_end_h number register 43145 value 3 after div by readscale 1 scale 1
2023-01-30 14:33:25.511 INFO (MainThread) [custom_components.solax_modbus.number] writing SolisLAN timed_charge_end_m number register 43146 value 18 after div by readscale 1 scale 1
2023-01-30 14:33:50.155 INFO (MainThread) [custom_components.solax_modbus.number] writing SolisLAN timed_charge_end_m number register 43146 value 31 after div by readscale 1 scale 1
2023-01-30 14:33:52.379 INFO (MainThread) [custom_components.solax_modbus.number] writing SolisLAN timed_charge_end_h number register 43145 value 4 after div by readscale 1 scale 1
2023-01-30 14:33:56.823 INFO (MainThread) [custom_components.solax_modbus.number] writing SolisLAN timed_charge_end_m number register 43146 value 32 after div by readscale 1 scale 1
2023-01-30 14:34:01.295 INFO (MainThread) [custom_components.solax_modbus.number] writing SolisLAN timed_charge_end_m number register 43146 value 31 after div by readscale 1 scale 1
2023-01-30 14:34:05.195 INFO (MainThread) [custom_components.solax_modbus.number] writing SolisLAN timed_charge_end_m number register 43146 value 30 after div by readscale 1 scale 1
2023-01-30 14:35:31.557 INFO (MainThread) [custom_components.solax_modbus] SolisLAN error reading input registers at device 1 position 0x8166

20230130.151437_3.mp4

[TartanEnergy]

Hi, I'm new to HA and Modbus. I have a Solis RHI-6K-48ES-5G inverter. I've installed the custom component and I can see plugin_solis.py in the file structure. My question is, how do I run a Modbus command in HA and use the entities, such as battery_charge_current (reg 43117) to change its value? I get HA's use of scripts and automation, but I can't see what Action and Service to invoke. Am I missing something... do I need to install Modbus as a component / add-on outside of installing Wills106 custom plugin? Any help appreciated. I've managed to get the Solis integration working just fine, and can read the inverter and battery data, I just haven't figured out how to change values on the inverter using the Modbus plug-in. Thanks!

[wills106]

This is on my SolaX Inverter, so names are different. But something like the following:

service: number.set_value
data:
  value: "30"
target:
  entity_id: number.solax_battery_charge_max_current

You just interact with the corresponding numbers, selects etc

[TartanEnergy]

Thanks Wills106. I was on that path, however entity number.solax_battery_charge_max_current isn't recognised in my repository. How do I make the entities visible and do I need modus added as a service? Then how do I "use" the Solax Modbus integration to talk to the Solis inverter, which is listed as a device?Apologies in advance, as both HA and Modbus is new to me.Sent from my Galaxy -------- Original message --------From: wills106 ***@***.***> Date: 12/03/2023 07:53 (GMT+00:00) To: wills106/homeassistant-solax-modbus ***@***.***> Cc: TartanEnergy ***@***.***>, Comment ***@***.***> Subject: Re: [wills106/homeassistant-solax-modbus] What Ginlong Solis Inverter are you using? (Discussion #188) This is on my SolaX Inverter, so names are different. But something like the following: service: number.set_value data: value: "30" target: entity_id: number.solax_battery_charge_max_current You just interact with the corresponding numbers, selects etc —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[TartanEnergy]

Solis RHI-6K-48ES-5G inverter. Connecting using the GinLong Solis PV portal integration, via the API (with key/secret).

[TartanEnergy]

Thanks @wills106 - I think the problem is that the entities that appear for my inverter, using the Solis Integration to discovery it, are limited to read only information - such as sensor.solis_remaining_battery_capacity. Therefore, the entity to write to /set isn't visible.

I am connecting to the Solis Inverter via TCP/IP. Using the S3 wifi datalogger and the associated key/secret.

Clearly there are more entities on the device than the current 39 I can see, via the Solis Integration.

Do you know if there is a way to read the register directly to expose the full set of entities?

[alienatedsec]

That makes sense - SolaX integration needs the Modbus TCP-compatible datalogger and yours isn't. Check this out
https://github.com/alienatedsec/solis-ha-modbus-cloud#supported-solis-dataloggers

Also, you will not be able to control anything from HA as your datalogger cannot handle local requests.

[TartanEnergy]

Thanks @alienatedsec - very useful and hadn't seen this. Helps clarify what works with what. Not sure I'm technically competent to get the Waveshare setup and working though. Given the S3-WIFI-ST allows remote control via SolisCloud, where I can manually change charge times and amps etc., isn't there a way to replicate these commends in HA? After all, I am connected (via API) to the datalogger in the same way - using the SolisCloud Integration.

[alienatedsec]

You will need to ask the author of the Solis Cloud integration; however, there are no known API instructions to remote control the inverter. It looks like Solis has kept it for their own use only. I suggest raising a ticket for remote control and it will appear in your dashboard and the solis mobile app.

[TartanEnergy]

Okay, thanks. I have the Remote Control activated and can send instructions to change the inverter manually, which is clearly not ideal.

[alienatedsec]

There will be no other way for you with the S3-WIFI-ST datalogger, I am afraid.

You could swap to other dataloggers (additional cost), and I think DLS-W is the most universal for cloud reporting (not remote control) and SolarMan integration with some custom automation using pysolarmanv5 for remote control capabilities.

You could also build what I did and have the SolaX integration, but it all depends on the budget and your technical abilities.

[TheAnt1dot3]

thanks for your awesome work.
I have a Solis RAI-3K-48ES-5G inverter which is mono-phase.
Serial number starts with 010F
After adjusting the inverter model if statement to map it to "HYBRID | X1" it seems most of the registers map correctly.
This is using the plugin_solis.py.

I have a register definition document for this model, let me know if you need it :)
i'll prob add some parameters myself to give it a go.
I'm also keen on working together on a forced charge & discharge for this model if you'd like to integrate.

Thanks

[wills106]

If you have a newer document that would be great. As the one I have is from 2018.
Does the document have registers that matches plugin_solis as there is a newer dated document that I have seen but contains the registers in plugin_solis_old

[alienatedsec]

I don't think there are many differences between HYBRID and non-HYBRID models regarding registers - I can be wrong here.

The below is the latest for HYBRID but excludes control functions (even those are mentioned)

https://213.136.68.177/assets/uploads/files/1619515984065-_without-control-hybrid-en-2020.9.15_rs485_modbus-esinv-33000id-hybrid-inverter.pdf

[wills106]

@TheAnt1dot3 Just added you Inverter in 2023.03.2b6

[TheAnt1dot3]

@TheAnt1dot3 Just added you Inverter in 2023.03.2b6

Awesome, thank you! I'll give it a go.
Regarding the document, the one AlienatedSec posted is more recent then what i have, i have the same 2018 document as you.

Thanks @alienatedsec !

[alienatedsec]

Hi @wills106

Would you feel comfortable updating your Wiki page and referencing my design, and the communication method to combine the Solis Cloud with HA where I also referenced SolaX integration?

In short:
Solis Cloud is the reporting platform for Solis inverters with a datalogger. There are several dataloggers where some present limitations and some will not work or coexist with HA. The benefits of a datalogger and Solis Cloud are remote support by Solis, the installer, and remote control, including alarm and error reporting.

I explained my design in detail in the following repo:
https://github.com/alienatedsec/solis-ha-modbus-cloud

Happy to clarify anything if needed.

[bilalhp]

It seems like buying "Exceedconn EC04681-2023-BF Male/Female for Solis/Ginlong Inverter RS-485 port" will be more difficult, as I cannot find a seller that ships to Belgium. Is there any alternative?

[wills106]

I thought you could mod a 4pin din connector?
There is a seller on UK ebay. Have you asked if they will post it to you as a one off?

https://www.thingiverse.com/thing:5338738

[bilalhp]

I finally have everything I needed, and will do the wiring this weekend.

My understand from the documentation here:

• I need 3 cables from outside the box that I will build: eth cable to home network, 1 pair for RS485 to inverter and power for Netgear switch. A ground cable is also needed?
• I need to two soldering operation: Solder 1 pair of cables to female plug (to be plugged in to the inverter) and solder 1 pair of cables from client waveshare to male plug. Can it be clamped without soldering?
• I don't understand where to get the ground from outside, and connect which terminal of waveshare. What is the difference between PGND and GND? What to connect each?
• I have plenty of XVB3G15 cables. Can I use it instead of twisted pairs of eth for RS485 wiring?
• If I have to use eth cable, should I use 1 twisted pair for one connection (A) and another pair for (B) or a single twisted pair: one wire for (A) and (B) each? That's confusing.

[alienatedsec]

I finally have everything I needed, and will do the wiring this weekend.

My understand from the documentation here:

It would be more beneficial for the community to discuss your understanding over there rather than here. Regardless of your choice, happy to help with your query.

• I need 3 cables from outside the box that I will build: eth cable to home network, 1 pair for RS485 to inverter and power for Netgear switch. A ground cable is also needed?

Up to you how you secure your installation. Mine has an earth cable at least.

• I need to two soldering operation: Solder 1 pair of cables to female plug (to be plugged in to the inverter) and solder 1 pair of cables from client waveshare to male plug. Can it be clamped without soldering?

The Waveshare connectors don't require soldering.

• I don't understand where to get the ground from outside, and connect which terminal of waveshare. What is the difference between PGND and GND? What to connect each?

The wiring diagram shows the symbol where you need to connect your earthing cable.

Some differences explained:

• I have plenty of XVB3G15 cables. Can I use it instead of twisted pairs of eth for RS485 wiring?

RS485 is better to use twisted pair cabling to reduce interference. If XVB3G15 has twisted pairs in it (doubt it), use it as you wish.

• If I have to use eth cable, should I use 1 twisted pair for one connection (A) and another pair for (B) or a single twisted pair: one wire for (A) and (B) each? That's confusing.

Just quoting my own work - I recommend using one of the pairs from the Ethernet cable for RS485 wiring. e.g., A twisted pair of blue for RS485(A) and white-blue for RS485(B). - those two cables are twisted together. A nice picture below:

[bilalhp]

Thanks. We can continue from here:

alienatedsec/solis-ha-modbus-cloud#10

[wills106]

Is there an option to set minimum SOC your Inverter will discharge to?
How does the Backup SOC differ?

[alienatedsec]

@wills106 there is a minimum SOC for backup and for the battery (manufacturer's guideline) itself. Let's say you have Backup SOC at 50%, then it will start using the grid when the battery reaches that level, but when you change the mode to Self-Use, it will carry on using batteries until the battery minimum SOC (e.g., 15%) is reached.

I guess there is not much difference, and people combine it with the Octopus Flux tariffs. I can't see the benefit, but it's me and others may find it useful - see this #354 (reply in thread)

[wills106]

I'm just adding them in. Do you know the min/max the Inverter will let you set? 10-100% for example?

Edit: Just noticed you mentioned 10-100% in that PR

[bilalhp]

Hello,

I have Solis RHI-3P10K Hybrid inverter and S3-WIFI-ST stick. I have created a setup with two Waveshares by following everything in https://github.com/alienatedsec/solis-ha-modbus-cloud. Unfortunately, it didn't work like a charm :(

S3-WIFI-ST works and I can access my data over Solis Cloud/App. Inverter Control over Solis Cloud/App also works.

However, homeassistant-solax-modbus doesn't work. I installed it with HACS and configured everything properly (I think). However, I get the following error:

Thus, somehow the Modbus TCP communication doesn't work

One thing I am not sure is the "The modbus address of the inverter" config option of the integration, which I left the default value 1.

Any ideas why it doesn't work? How can I debug further?

By the way, my RPI running HA is connected to the same home network with Waveshares over WiFi, but the quality of the link should be pretty decent. Can this be a problem?

[bilalhp]

@bilalhp Finally, which IP is used for the HA SolaX integration?

"1.251". That's the master.

I am also suspicious about this:

In your pictures it is 5088 but my device allows me to only set multiples of 32.

[alienatedsec]

@bilalhp That's my setup and it should be working fine with lower numbers. Try lower and higher numbers and check what is working best for you.

Also, when you ping them from the HA, are there any delays?

[bilalhp]

The delay is between 10-15 ms.

Tomorrow I will try different parameters and maybe also moving HA RPi to the same switch with eth cable. But I think delay is not there problem here, because even before enabling HA integration, Stick was not working very consistently.

Can it be interference? Because the cables are very close.

[alienatedsec]

@bilalhp hard to say without seeing the wiring installation.
All I can confirm at this moment is that I spoke to other people with the same datalogger and it was working for them with no issues. If not wiring, then settings will be your problem.

[bilalhp]

Factory reset everything and did the configuration from scratch. I think everything works as expected now.

Thanks.

[solarjones]

Hi,
I'm running a Solis RHI-6K-48ES-5G with 2x Waveshares (thanks @alienatedsec) for a couple of months now and all seems to be working (apart from 2x spikes in the last couple of days).

However, I've no idea what the Battery ChargeDischarge setting is for. I've not touched it and its set to 81 A.

Could someone explain what that setting does? I can understand the separate charge & discharge values, but not the combination.

[alienatedsec]

I don't think it is related. Those two are not linked together and Waveshare can handle more than one additional client querying the Server.
Even so, I am not in a position to isolate the Datalogger; especially since it was working fine for several days.

My observation is that the integration is not handling the waveshare's communication issues, and there are more examples with other inverter brands #401

[alienatedsec]

It still seems to be a problem to fix, so I will continue discussing this in #340

[solarjones]

I had an odd problem today. My Solis data logger hung @11:35am but HA and Solis integration worked with no issues. Since resetting the Waveshares the other week, I'd hoped everything would work nicely. I'd not had any spikes.

So to recover the Solis data connection I powered cycled my PoE hub to perform a reboot of the Waveshares + Solis data logger, and everything came back up just fine. Confused.

[alienatedsec]

@solarjones it will be a design rather than an integration issue

Let's discuss over at https://github.com/alienatedsec/solis-ha-modbus-cloud

[solarjones]

Updated Waveshare config as discussed https://github.com/alienatedsec/solis-ha-modbus-cloud and all worked for a few days until today, spiked again.

[ceemjay]

If you are still interested I am using a Solis S5-EH1P5K-L and the main metrics I use look very similar to the Solis App / Soliscloud.

Is there any more documentation on this eg how to set charge times? As I dont fully understand some of the settings eg Energy Storage Control Switch I am reluctant to play too much?

Thanks

[wills106]

If you are on 2023.05.1 or older you need to set the following times:
'timed_charge_start_h', 'timed_charge_start_m', 'timed_charge_end_h', 'timed_charge_end_m', 'timed_discharge_start_h', 'timed_discharge_start_m', 'timed_discharge_end_h', 'timed_discharge_end_m'
Then press the button "Update Charge/Discharge Times"

If you are on 2023.05.2b3 then it should display all of the times, then you just change the ones you want, by pressing the button "Update Charge/Discharge Times"

It's bit of a mess with separate hours and mins, but there is no proper support for time or date in integrations.
Although this will change with HA 2023.6.x then I can work on all of this time code. #200 (comment)

[ceemjay]

Thank you very much for coming back so quickly however with a hint from someone else on FB I managed to manually enter values into the appropriate entity and then update the inverter. Yippee - a major step forward.

Next step is to workout a way of deciding what charge times I want - probably outside of HA - and then using those to update the inverter.

I am running HA version 2023.5.2 but I can't see if displaying times in the main default card - I have created new cards for each of the entities and it is displaying the values then. Is that what you meant. Very new to HA - so much to learn and never enought time to devote to it!

[wills106]

What version of the Integration have you downloaded the Beta 2023.05.2b3?

Without pressing the "Update Charge/Discharge Times" button but changing a time value, does the value stick or revert back to the previous setting?

It won't actually change the Inverter without pressing the "Update Charge/Discharge Times" button, I just need to know if it stick or keeps jumping back to the previous value.

[Cabocab]

Hi, Integration running on a Solis RHI-5k-48ES-5G, fist 4 characters in the serial number is 110F.

Was able to make it work with the integration by manually adding the inverter to determineInverterType. Everything working as intended so far.

[wills106]

I'll add your Inverter in properly on the next release.

[wills106]

Just released 2023.05.2b4

[solarjones]

Spike yesterday (was running the previous beta version) and had to reset lots of statistics again. So I loaded the latest version 2023.05.02 and unfortunately its just spiked again :(

Any pointers?

[wills106]

I suspect some electrical interference.

I wonder if you need to add a termination resistor or at least ground the comms cable?

[alienatedsec]

@wills106 @solarjones I suspect it could be the opposite. Removing any grounding or earthing.

alienatedsec/solis-ha-modbus-cloud#13 (comment)

[solarjones]

I'll try removing the grounding from the Waveshares today.

Silly question now... The number of stats that I have to reset as a consequence of a 'spike event' spans multiple 5 minute time slices. Some valves are massive, others not, and some are negative. And it's never just one value, but dozens.

With this level of data corruption, why isn't this reflected on the Solis portal/app?

The inverter is Slave 01, the Waveshares are Master, Slave + Solis datalogger. Do we know if the data corruption is from the inverter or Waveshares?

Or do the Waveshares just hang (buffer overflow?) resulting in duff data?

[alienatedsec]

With this level of data corruption, why isn't this reflected on the Solis portal/app?

I still think it's the integration to manage data, but any interference on Waveshare is to disrupt comms. Also, it happens on other inverters. I'll get them to check earthing too.

[solarjones]

I'd forgotten that I'd already removed the earthly over a month ago. So for me, with or without earthing has made zero difference.

[benlancaster]

Solis S6-GR1P6K 6kW single phase hybrid inverter (model number in the range S6-GR1P(2.5-6)K.

s/n is 16 characters long and starts with 180206022A (followed by 6 more digits).

I have the 4-pin S2-WL-ST datalogger (LAN and WiFi?), some versions of which are supposed to expose ModBus TCP if The Internet™ is to be believed, but mine doesn't appear to do anything like that (in fact the status page has 0 for every value it displays on there), and nmap only reports Port 80 (HTTP) and 53 (DNS) being open. It does, however, talk to Solis Cloud just fine.

I've also hooked up the comm port to a Waveshare PoE Modbus TCP DIN device, but haven't had any success reading anything of it (yet).

I have a vague idea what I'm doing with ModBus (it's the protocol I used to hook up my heat pump to HA), but I am very new to solar PV as my system's only been generating for 2 days.

Unfortunately not much more I can provide right at this instant as it's gone midnight, it's dark outside, and the inverter seems to power off completely when the sun's not shining!

[alienatedsec]

@benlancaster I have the same datalogger and you made me check things. It's possible the Modbus port was removed with a newer data logger firmware. What is yours?

Regarding the Waveshare part, can you share the logs from HA when you configured the integration?

[wills106]

I have just raised #444 to work through the registers on this Inverter.

[benlancaster]

@alienatedsec I've added some more information in #444 (comment)

[tinhtran88]

Hi,
I'm using S6-EH1P5K-L-EU with S4-WiFi-ST. Hope to support this product soon.

[alienatedsec]

@tinhtran88 is that 4-pin or USB?

[tinhtran88]

this is USB dongle

[alienatedsec]

@tinhtran88 has it got any Web interface? Also, can you scan the IP with NMAP?

[tinhtran88]

Hi, here's screenshot.

[alienatedsec]

@tinhtran88 have you tried connecting SolaX integration on either of those two ports? 502 or 8899

What is in advanced section?