Schedule values don't match

[ando2040]

Great integration! The new API must be more functional than the old reverse-engineered effort, judging by the increased number of entities.

In particular, it's great to see control over schedules. This is bothering me because I'd expected to be able to leave my units on "auto" all year round, but the temperature sensors are so inaccurate (Perfera FTX-M), this won't be possible! I believe this is because only an idiot would place a thermostat two metres off the ground next to a heat source, without robust logic to correct for those things - yet it appears that was the Daikin engineering decision! I discovered too late that they don't offer an external sensor connectable to Perfera...

So, I will now use my own external sensor to switch the schedule between 'none' and '0'.

Before I do this, is there any way to remap the values? In the Onecta app I have 1, 2, 3

But as mentioned, in the HA states it is different, and I'm not sure if this is hardcoded or definable?

options:
  - "0"
  - "1"
  - "2"
  - none
icon: mdi:calendar-clock

Note: I've changed the icon myself. I would assume 0 corresponds to 1 in Onecta though I confess I haven't yet tested. It's always annoyed me I can't rename them on the Onecta side...

[jwillemsen]

Please attach your integration diagnostics so that I can see what Daikin provides

[ando2040]

That is the kind of low-code idea I came here for - thanks! Will give it a try.

[ando2040]

Odd, I made a change trying to add a dictionary, and the integration wouldn't reload (first reboot since installed).

I backed out the dictionary change, and same thing: message is as below

I deleted the integration (keeping credentials) and re-added it, now it's back. It did go through re-auth on the Daikin site for temporary application. This is probably incidental but I don't know the cause.

I've rebooted again with this code in configuration.yaml but it breaks that entity - I think it must no longer correspond to the API. I even tried the other way around (ie. Winter : "0"), which interestingly had no effect at all.

So I'll try with a helper and template automation when I have the time.

homeassistant:
  customize:
    select.master_bedroom_a_climatecontrol_schedule:
      options:
        0: "Winter"
        1: "Summer"
        2: "Custom"
        none: "Off"

Results in State attributes as follows (but the entities card has literally nothing in it, it's just a border):

options:
  "0": Winter
  "1": Summer
  "2": Custom
  none: "Off"
friendly_name: Master bedroom A ClimateControl Schedule

Whereas previously (entities card works but has these unfriendly values):

options:
  - "0"
  - "1"
  - "2"
  - none
friendly_name: Master bedroom A ClimateControl Schedule

[jwillemsen]

I renamed none to off on master. I will first wait on Daikin to hear back on the id/name issue.

[jwillemsen]

No response from Daikin on the id/name issue at this moment

[jwillemsen]

I have added the schedule name to the list of data we would like to see Daikin export, see #46