Closed mlobstein closed 6 days ago
@mlobstein - many thanks! I'm wondering if it would be useful to split this into two separate channels, one for temperature and one for datetime? This would make it possible to make better use of this data, for example for automations.
@mlobstein - many thanks! I'm wondering if it would be useful to split this into two separate channels, one for temperature and one for datetime? This would make it possible to make better use of this data, for example for automations.
Good idea, I have updated the PR to have separate channels.
The PR adds one last missing feature from the old mobile app. The next scheduled set point temperature and time from the programmed heating or cooling schedule can now be displayed in their own channels.
Also the display name of the binding was normalized to have a space between Radio Thermostat in all places that were previously inconsistent.
Note to reviewer: The RadioThermostatScheduleJson class was renamed to RadioThermostatSchedule and the new file appears in the diff as a completely new even though the method signatures and much of the code is unchanged.