Set Schedule Error when schedule includes slot containing midnight

[johnbradshw]

The Set Schedule service fails when any of the timeslots for the schedule span midnight (e.g 23:30 to 0:00 or 23:30 to 00:30) when using with a Hypervolt Pro 3 with firmware 2966.0

Now that we are in the cooler months, this is regularly a cheaper slot on Octopus Agile tariff. Relevant logs below for setting a schedule 23:30 to 0:00.

2024-10-23 08:56:00.750 DEBUG (MainThread) [custom_components.hypervolt_charger.hypervolt_api_client] Send_message_to_sync: {"method": "schedule.set", "params": {"enabled": true, "is_default": false, "type": "hypervolt", "sessions": [{"session_type": "recurring", "start_time": "23:30", "end_time": "00:00", "mode": "boost", "days": ["MONDAY", "TUESDAY", "WEDNESDAY", "THURSDAY", "FRIDAY", "SATURDAY", "SUNDAY"]}]}, "jsonrpc": "2.0"}
2024-10-23 08:56:00.754 INFO (MainThread) [custom_components.hypervolt_charger.service] Schedule applied. Reading back from API
2024-10-23 08:56:00.754 INFO (MainThread) [custom_components.hypervolt_charger.service] Read back shedule intervals
2024-10-23 08:56:00.768 DEBUG (MainThread) [custom_components.hypervolt_charger.hypervolt_api_client] notify_on_websocket sync, Task-161, recv: {"jsonrpc":"2.0","error":{"code":-32603,"message":"schedule.set failed: internal server error"}}

[johnbradshw]

To schedule slot 23:30 to 0:00 the schedule sent to hypervolt needs to be 23:30 to 24:00

[ptashek]

In the official app, the schedule needs to be setup as 23:30 -> 0+1:00, which suggests it may be a limitation of the API and they're using a workaround to span start/end across day boundaries.