Describe the bug
When Predbat controls a Solis inverter via the SolisCloud API in TOU V2 mode, writing a new charge or discharge time window can fail if another slot still has stale (non-zero) times on the inverter from a previous cycle where the clear write failed. The SolisCloud API rejects writes that would create overlapping time windows across slots, even if the conflicting slot is disabled.
Expected behaviour
When a charge or discharge slot is disabled, its start and end times should be cleared to 00:00-00:00 on the inverter. This should happen before the active slot's new window is written, so there is no risk of an overlap rejection from the API.
Predbat version
8.36.3
Environment details
- Solis inverter with SolisCloud API integration (TOU V2 mode, i.e. CID 6798 enabled)
- Multiple charge/discharge slots previously set by Predbat or manually, leaving non-zero times in slots 2–6
- Standard HAOS installer or Docker
- Only affects
inverter_type: SolisCloud configurations using the V2 register layout
Describe the bug
When Predbat controls a Solis inverter via the SolisCloud API in TOU V2 mode, writing a new charge or discharge time window can fail if another slot still has stale (non-zero) times on the inverter from a previous cycle where the clear write failed. The SolisCloud API rejects writes that would create overlapping time windows across slots, even if the conflicting slot is disabled.
Expected behaviour
When a charge or discharge slot is disabled, its start and end times should be cleared to
00:00-00:00on the inverter. This should happen before the active slot's new window is written, so there is no risk of an overlap rejection from the API.Predbat version
8.36.3
Environment details
inverter_type: SolisCloudconfigurations using the V2 register layout