springfall2008
Inverter Command Rate Limit
Is your feature request related to a problem? Please describe. My modbus connected Solis inverter can sometimes fail to set register values if commands are sent in quick succession. After running Batpred for the last week I have had two instances now where the overnight charge fails due to register values being inconsistent between HA and the Inverter.
Describe the solution you'd like In my own charging automations prior to Batpred I worked around this by adding a simple 1 second sleep between Inverter commands, to give the Inverter sufficient time to have completed the last command before executing the next. A configurable variable within Batpred would be a perfect alternative, allowing the introduction of a specific delay (500ms, 1000ms etc) according to the environment's need.
Describe alternatives you've considered While the root cause is likely due to the Modbus baud rate being used, but since I have other devices (unconfigurable) on that bus I cannot change this, and so I need a mechanism to handle this on the other end.
