This add-on will broadcast messages on your local network looking for Daikin air conditioning units and adding them to the queue of new items discovered.
You can also manually add a new item if you know the IP address.
A BRP072C42 adapter requires a registered UUID to authenticate. Upon discovery, a UUID will be generated but the adapter's key must be entered in the Thing configuration to complete the UUID registration.
| power | Turns the power on/off for the air conditioning unit. |
| settemp | The temperature set for the air conditioning unit. |
| indoortemp | The indoor temperature as measured by the unit. |
| outdoortemp | The outdoor temperature as measured by the external part of the air conditioning system. May not be available when unit is off. |
| humidity | The indoor humidity as measured by the unit. This is not available on all units. |
| mode | The mode set for the unit (AUTO, DEHUMIDIFIER, COLD, HEAT, FAN) |
| homekitmode | A mode that is compatible with homekit/alexa/google home (off, auto, heat, cool). Not tested for BRP069B41 |
| fanspeed | The fan speed set for the unit (AUTO, SILENCE, LEVEL_1, LEVEL_2, LEVEL_3, LEVEL_4, LEVEL_5) |
| fandir | The fan blade direction (STOPPED, VERTICAL, HORIZONTAL, VERTICAL_AND_HORIZONTAL) |
| cmpfrequency | The compressor frequency |
| specialmode | The special mode set for the unit (NORMAL, ECO, POWERFUL). This is not available on all units. |
| streamer | Turns the streamer feature on/off for the air conditioning unit. This is not available on all units. |
| energyheatingtoday | The energy consumption when heating for today |
| energyheatingthisweek | The energy consumption when heating for this week |
| energyheatinglastweek | The energy consumption when heating for last week |
| energyheatingcurrentyear-1 | The energy consumption when heating for current year January |
| energyheatingcurrentyear-2 | The energy consumption when heating for current year February |
| energyheatingcurrentyear-3 | The energy consumption when heating for current year March |
| energyheatingcurrentyear-4 | The energy consumption when heating for current year April |
| energyheatingcurrentyear-5 | The energy consumption when heating for current year May |
| energyheatingcurrentyear-6 | The energy consumption when heating for current year June |
| energyheatingcurrentyear-7 | The energy consumption when heating for current year July |
| energyheatingcurrentyear-8 | The energy consumption when heating for current year August |
| energyheatingcurrentyear-9 | The energy consumption when heating for current year September |
| energyheatingcurrentyear-10 | The energy consumption when heating for current year October |
| energyheatingcurrentyear-11 | The energy consumption when heating for current year November |
| energyheatingcurrentyear-12 | The energy consumption when heating for current year December |
| energycoolingtoday | The energy consumption when cooling for today |
| energycoolingthisweek | The energy consumption when cooling for this week |
| energycoolinglastweek | The energy consumption when cooling for last week |
| energycoolingcurrentyear-1 | The energy consumption when cooling for current year January |
| energycoolingcurrentyear-2 | The energy consumption when cooling for current year February |
| energycoolingcurrentyear-3 | The energy consumption when cooling for current year March |
| energycoolingcurrentyear-4 | The energy consumption when cooling for current year April |
| energycoolingcurrentyear-5 | The energy consumption when cooling for current year May |
| energycoolingcurrentyear-6 | The energy consumption when cooling for current year June |
| energycoolingcurrentyear-7 | The energy consumption when cooling for current year July |
| energycoolingcurrentyear-8 | The energy consumption when cooling for current year August |
| energycoolingcurrentyear-9 | The energy consumption when cooling for current year September |
| energycoolingcurrentyear-10 | The energy consumption when cooling for current year October |
| energycoolingcurrentyear-11 | The energy consumption when cooling for current year November |
| energycoolingcurrentyear-12 | The energy consumption when cooling for current year December |
| demandcontrolmode | The demand control mode (`OFF`, `AUTO`, `MANUAL`, `SCHEDULED`) |
| demandcontrolmaxpower | The maximum power when in `MANUAL` mode. Values between 40 and 100 are accepted in an increment of 5. In `SCHEDULED` demand control mode, this channel will be updated with the calculated maximum power based on the current active schedule. |
| demandcontrolschedule | A JSON string that contains the scheduled demand control settings. See below. |
| power | Turns the power on/off for the air conditioning unit. |
| settemp | The temperature set for the air conditioning unit. |
| indoortemp | The indoor temperature as measured by the unit. |
| outdoortemp | The outdoor temperature as measured by the external part of the air conditioning system. May not be available when unit is off. |
| mode | The mode set for the unit (AUTO, DEHUMIDIFIER, COLD, HEAT, FAN) |
| homekitmode | A mode that is compatible with homekit/alexa/google home (off, auto, heat, cool) |
| airbasefanspeed | The fan speed set for the unit (AUTO, AIRSIDE, LEVEL_1, LEVEL_2, LEVEL_3, LEVEL_4, LEVEL_5, AUTO_LEVEL_1, AUTO_LEVEL_2, AUTO_LEVEL_3, AUTO_LEVEL_4, AUTO_LEVEL_5) |
| zone1 | Turns zone 1 on/off for the air conditioning unit (if a zone controller is installed.) |
| zone2 | Turns zone 2 on/off for the air conditioning unit. |
| zone3 | Turns zone 3 on/off for the air conditioning unit. |
| zone4 | Turns zone 4 on/off for the air conditioning unit. |
| zone5 | Turns zone 5 on/off for the air conditioning unit. |
| zone6 | Turns zone 6 on/off for the air conditioning unit. |
| zone7 | Turns zone 7 on/off for the air conditioning unit. |
| zone8 | Turns zone 8 on/off for the air conditioning unit. |
Some units have a _demand control_ feature to limit the maximum power usage to a certain percentage.
This is set through the `demandcontrolmode` channel which accepts `OFF`, `MANUAL`, `SCHEDULED`, or `AUTO`.
When changing the mode from `MANUAL` to another mode, the maximum power setting will be saved in the Binding's memory and restored when switching the mode back to `MANUAL`.
Equally, when changing the mode from `SCHEDULED` to another mode, the current schedule will be saved in the Binding's memory and restored when switching the mode back to `SCHEDULED`.
### Manual Demand Control
Manual demand control requires setting the `demandcontrolmaxpower` channel to the desired limit.
The unit accepts values between 40% and 100% in increments of 5.
Sending a command to the `demandcontrolmaxpower` channel will automatically switch the demand control mode to `MANUAL`.
### Scheduled Demand Control
It is possible to set the demand control power limit based on day of the week and time of day schedules.
When the unit is in scheduled demand control mode, the binding provides the current schedule through the `demandcontrolschedule` channel.
In `SCHEDULED`, the `demandcontrolmaxpower` channel will provide the _current_ maximum power in effect, as defined within the schedule.
This information is not provided by the unit itself.
It is calculated by the binding based on the current schedule.
Therefore, it is important to ensure that openHAB's local time is in sync with the unit's date/time.
The schedule and associated max power settings can be set by sending a command to the `demandcontrolschedule` channel.
When doing so, the demand control mode will automatically change to `SCHEDULED`, if it wasn't already in that mode.
The schedule is specified in a JSON string in the following format:
```json
{
"monday": [
{
"enabled": true,
"time": <minutesfrommidnight>,
"power": <powerinpercent>
}
],
"tuesday": [
// Schedule entries for Tuesday
],
"wednesday": [
],
// more days up to Sunday
"sunday": [
]
}
```
Concrete example:
The JSON format doesn't actually support comments. They are provided for clarity.
```json
{
"monday": [
{
"enabled": true,
"time": 480, // 8 am
"power": 80
},
{
"enabled": true,
"time": 600, // 10 am
"power": 100
},
{
"enabled": true,
"time": 960, // 4pm
"power": 50
}
],
"tuesday": [
{
"enabled": true,
"time": 480, // 8 am
"power": 80
},
{
"enabled": true,
"time": 600, // 10 am
"power": 100
},
{
"enabled": true,
"time": 960, // 4pm
"power": 50
}
],
"wednesday": [
{
"enabled": true,
"time": 480, // 8 am
"power": 80
},
{
"enabled": true,
"time": 600, // 10 am
"power": 100
},
{
"enabled": true,
"time": 960, // 4pm
"power": 50
}
],
"thursday": [
{
"enabled": true,
"time": 480, // 8 am
"power": 100
}
]
// omitted days mean that they contain no schedules
}
```
Note:
- Each day can have up to 4 schedule entries
-`enabled` means whether this schedule element is enabled.
-`time` is the start time of the schedule, expressed in number of minutes from midnight.
-`power` a value of zero means demand power is disabled at the time defined by the `time` element.
- When there are no schedules defined for the current day/time, it is believed that the settings from the previous schedule will apply, bearing in mind that it is a weekly recurring schedule.
This is ultimately determined by the logic in the unit itself, and not controlled by the Binding.
