🚑 Hotfix: set_schedule / clear_schedule returned a 500 error
A helper name collision made the new schedule services receive a tuple instead of the coordinator, so every call failed with AttributeError: 'tuple' object has no attribute 'api'.
Both services now work, and all schedule writes go through the coordinator's state-change wrapper (combi limit + auth handling), including the Scheduled start switch.