It also depends on PR Apollon77/daikin-controller#268 .
For now only the minimum needed for later control is exposed:
enabled: to be able to activate or deactivate demand control
mode: to be able to change the modes MANUAL, AUTO (, SCHEDULE)
max_power: to be able to change maximum power percentage of demand control
Not exposed:
type: meaning unknown; and must be always 1
schedule information: support is complex and is not really an automation use case in my opinion
Open Issue: at least "maxPower" (but possibly also "mode" and "enabled") will be writable later. In this PR they are placed in their own group "demandControl".
On the other hand, the current adapter bundles all writable data points within the "control" group.
With this PR I could replace the usage of "daikin-cloud.0..climateControl.demandControl.modes.fixed" in my dashboards.
Closes #183
It also depends on PR Apollon77/daikin-controller#268 .
For now only the minimum needed for later control is exposed:
Not exposed:
Open Issue: at least "maxPower" (but possibly also "mode" and "enabled") will be writable later. In this PR they are placed in their own group "demandControl". On the other hand, the current adapter bundles all writable data points within the "control" group.
With this PR I could replace the usage of "daikin-cloud.0..climateControl.demandControl.modes.fixed" in my dashboards.