Frequent & automated changes to registers

[cavalon]

Hi there!

I am planning to set up several HomeAssistant automations for my Solis S6 inverter. For example, I would like to dynamically control settings such as Backflow Power or Battery Max Charge Current based on various factors in my smart home.

This could mean that the relevant values/registers are changed and written several times per day. I expect roughly 5 to 100 changes per day.

Could frequently modifying of registers be harmful in any way?

In various places, I have read that inverters may distinguish between different types of memory, such as Flash/EEPROM or RAM. Flash/EEPROM memory has a limited number of write cycles...

Does anyone have experience with how Solis inverters handle this?

Cheers!

[julmnk]

so far I didn't see that Solis would disclose and present such information ....

[mkuthan]

You could try a new dispatch capabilities:

solis_modbus/custom_components/solis_modbus/services.yaml

Lines 201 to 422 in cb37e87

	solis_dispatch:
	name: Remote dispatch
	description: Real-time inverter dispatch (Ver3.4 44100 block) — goal-seeking grid/battery control with an inverter-side failsafe. Requires dispatch-capable firmware (register 34502 = 0xAA55).
	fields:
	mode:
	name: Mode
	description: What to control. grid_import/grid_export target the meter (PCC); battery_charge/discharge command battery power; battery_hold freezes the battery
	required: true
	example: grid_import
	selector:
	select:
	options:
	- grid_import
	- grid_export
	- grid_port_import
	- grid_port_export
	- battery_charge
	- battery_discharge
	- battery_hold
	- self_consumption
	- feed_in_priority
	power_watts:
	name: Power target
	description: Unsigned watts; direction comes from the mode
	default: 0
	selector:
	number:
	min: 0
	max: 240000
	step: 100
	unit_of_measurement: W
	mode: box
	pv_shutdown:
	name: PV shutdown
	description: Shut PV generation down for the duration of the dispatch (omit = leave unchanged)
	selector:
	boolean:
	allow_grid_charge:
	name: Allow grid charging
	description: Permit/deny grid-to-battery charging during the dispatch (omit = leave unchanged)
	selector:
	boolean:
	disable_discharge:
	name: Disable discharge
	description: Inhibit battery discharge during the dispatch (omit = leave unchanged)
	selector:
	boolean:
	soc_min:
	name: SOC lower limit
	selector:
	number:
	min: 0
	max: 100
	unit_of_measurement: "%"
	mode: box
	soc_max:
	name: SOC upper limit
	selector:
	number:
	min: 0
	max: 100
	unit_of_measurement: "%"
	mode: box
	import_limit_watts:
	name: Import limit
	description: System power-draw (grid import) upper limit. Omit to leave the inverter default; 0 is a valid cap
	selector:
	number:
	min: 0
	max: 240000
	step: 100
	unit_of_measurement: W
	mode: box
	export_limit_watts:
	name: Export limit
	description: System feed-in (grid export) upper limit. Omit to leave the inverter default; 0 is a valid cap
	selector:
	number:
	min: 0
	max: 240000
	step: 100
	unit_of_measurement: W
	mode: box
	failsafe_minutes:
	name: Failsafe interval
	description: The inverter reverts to normal operation by itself if no dispatch write arrives within this window
	default: 30
	selector:
	number:
	min: 1
	max: 1440
	unit_of_measurement: min
	mode: box
	host:
	name: Host
	selector:
	text:
	slave:
	name: Slave
	selector:
	number:
	min: 1
	max: 247
	mode: box
	solis_dispatch_stop:
	name: Stop remote dispatch
	description: Release remote dispatch — inverter returns to its normal storage-mode logic immediately
	fields:
	host:
	name: Host
	selector:
	text:
	slave:
	name: Slave
	selector:
	number:
	min: 1
	max: 247
	mode: box
	solis_dispatch_schedule:
	name: Program dispatch schedule period
	description: Write one of the six inverter-resident scheduled dispatch periods. The schedule executes on the inverter itself — it survives Home Assistant restarts (re-push within the failsafe window to keep it alive)
	fields:
	period:
	name: Period
	description: Schedule slot 1-6 (overlaps resolve to the lowest slot number)
	required: true
	selector:
	number:
	min: 1
	max: 6
	mode: box
	enabled:
	name: Enabled
	required: true
	selector:
	boolean:
	start_time:
	name: Start time
	example: "08:30"
	selector:
	time:
	end_time:
	name: End time
	example: "16:00"
	selector:
	time:
	mode:
	name: Mode
	default: battery_hold
	selector:
	select:
	options:
	- grid_import
	- grid_export
	- grid_port_import
	- grid_port_export
	- battery_charge
	- battery_discharge
	- battery_hold
	- self_consumption
	- feed_in_priority
	power_watts:
	name: Power target
	default: 0
	selector:
	number:
	min: 0
	max: 240000
	step: 100
	unit_of_measurement: W
	mode: box
	pv_shutdown:
	name: PV shutdown
	selector:
	boolean:
	allow_grid_charge:
	name: Allow grid charging
	selector:
	boolean:
	disable_discharge:
	name: Disable discharge
	selector:
	boolean:
	soc_min:
	name: SOC lower limit
	default: 0
	selector:
	number:
	min: 0
	max: 100
	unit_of_measurement: "%"
	mode: box
	soc_max:
	name: SOC upper limit
	default: 100
	selector:
	number:
	min: 0
	max: 100
	unit_of_measurement: "%"
	mode: box
	failsafe_minutes:
	name: Failsafe interval
	default: 1440
	selector:
	number:
	min: 1
	max: 1440
	unit_of_measurement: min
	mode: box
	host:
	name: Host
	selector:
	text:
	slave:
	name: Slave
	selector:
	number:
	min: 1
	max: 247
	mode: box

See also official Solis documentation: https://developer.soliscloud.com/guide/modbus.html#remote-dispatch-real-time-control

Real-time dispatch uses volatile registers, designed exactly for frequent/automated changes.

[cavalon]

hei @mkuthan

thank you for your reply!

As I'm not familiar with the remote dispatch services, I assume (?):

• One can setup an HA automation, triggering a service every x min (Failsafe Timeout, 1–1440 min.)
• The service may control 1 Battery Standby, 2 Charge/Discharge Control, 3 Grid Import/Export, 4 AC Port Import/Export - all values in [W] (in my usecase, I need to set Charge/Discharge Control)
• After the failsafe period, the value is set to it's origin automatically
• Example of the action of the HA automation:

action: solis_modbus.solis_dispatch
data:
  power_watts: 2500
  failsafe_minutes: 30
  mode: battery_charge

How does it behave, if I'd like to increase / decrease an already set value within the filesafe time frame? Is a new remote dispatch service call "overwriting" an existing value?

Anyone got remote dispatch services in action and may share an example?

cheers