2023.9: New climate entity dialogs, lots of tile features, and template sensors from the UI!

[w00zy]

The AC in ventilation mode is not showing anything

[Mariusthvdb (Marius)]

That’s just it: it’s in my dev Ui dashboard where I try all core card options …

No yaml for that

But check this now:
Closing

Opening:

Fingers crossed for closed:

Arrgg

[petro]

Yes there is… there’s yaml for everything. Just click the “show code editor” button.

[Mariusthvdb (Marius)]

Ofc . I know … just that it wasn’t me this time…

type: tile
entity: cover.screen_keuken
features:
  - type: cover-open-close
  - type: cover-position

We need a copy button in that editor…

[coolhand]

Same tabbed-card problem

[tom_l]

That needs to be taken up with the third party card developer, have you opened an issue with them?

[yousaf465]

@petro

Wled has a bunch of different light enti

Only one WLED and only one light.wled2 entity.

[SlavikS]

Same for me. Had to go back to previous version too.

[coolhand]

Looks like someone did, thanks:

https://github.com/kinghat/tabbed-card/issues/115

[Gav_in]

Someone has… so no need for more on it here (hopefully)

Bug after 2023.9 update

Edit: x2… sorry Tom

[spacegaier (Philip Allgaier)]

That is somewhat “expected”. I will prepare a PR with a fix proposal to get the discussion started.

Ensure custom colors work with cover tile features

[Mariusthvdb (Marius)]

Thanks Philip, thats exactly what is happening indeed, great you picked its up!

[tjhart85 (TJH)]

Ugh, that ESPHOME breaking change is going to hurt over the next few months as I upgrade from 8266 to esp32’s, if I can’t just easily swap them out!

[nickrout]

Not sure that it will be that dramatic. Just delete the old device and let the system discover the new one.

[tjhart85 (TJH)]

Hm … Maybe I’m misunderstanding the severity, won’t this result in all the entities potentially having incorrect ids and needing their entities to be re-assigned to areas?

Does the below sound accurate:

Right now, all I’d need to do is update the esphome config, flash it and replace the device and that’s it.

Once I upgrade, I’ll have to do all of that, delete the device from HA but keep track of the entity_id’s, restart (or reload … whichever is needed), add the ‘new’ device and then check the entity_id’s and correct them if necessary, re-assign the area for the device (or individual entities, whichever applies for this specific device since a dozen or so of my devices have multiple sensors in different rooms, so the areas of the individual entities don’t always match the area of the device itself).

I get that this may be a spacebar heating situation, but it doesn’t make it suck any less, lol. I’ve largely been unaffected by breaking changes for the last few years, so I guess I was bound to have something affect me again eventually :-\

[nickrout]

If you are using the same config on the new device, I think the entity_ids should be the same. (I based my comment on that assumption, but as I often say to others, assumption is the mother of failure.)

[tjhart85 (TJH)]

Oh well, I’ll see what happens, I’ll already be limited in how fast I can deploy these replacements just by how fast I can physically get them swapped out and configured … adding an extra couple steps into the mix won’t inconvenience me too much, but it seems like a lot of extra work I’ve got to do just because some others can’t set their IPs properly (but, to be fair, it’s only a lot of extra work in the quite rare instance where you’re replacing an ESPHOME device with another virtually identical one).

[tom_l]

@nickrout

If you are using the same config on the new device, I think the entity_ids should be the same.

They will be. I always delete my existing ESPHome devices from HA before replacing the ESP board. Never had an issue. You will lose any customisations made via the UI. Fortunately there is little need for this nowadays.

[Mariusthvdb (Marius)]

Too bad the Overkiz entities (Rssi/number) that were borked for some time and had finally returned after Pr in 2023.9, now are gone again in 2023.9.1…

Some Somfy/Overkiz entities unavailable or replaced after update to 2023.6.1

Hope this will finally point to why they were borked in the first place

[kineticscreen]

I’m not sure if this is true of all climate entities, or just an interaction between the Daikin integration and the new More Info display, but it rounds decimal values to a whole number.

See that the Daikin is actually set to 15.5º, but the new interface shows this as 16º.

It also means you can no longer set it to half degree values as you used to.
Are people finding this with other integrations too?