core: ONLY 2023.9.0 Overkiz breaks some unique_id [fixed on 2023.9.1]

Note

Issue concerns only 2023.9.0 Fixed on 2023.9.1 (see https://github.com/home-assistant/core/pull/99950#discussion_r1320342578)

We advice skipping 2023.9.0 if not already updated.

It reopens #97705 as the fix consists on reverting a dependency bump that fixes that issue.

The problem

Having my Overkiz devices set up before 2023.9 with official core integration and changes their entity_id from about sensor.io_2429113_2_temperature, which got some protocol ID plus its type, to sensor.radiateur_bureau_temperature, to simply the device name plus its type (🇫🇷 radiateur bureau --> 🇬🇧 office heater).

So now that I am on 2023.9.0b0, my changed entities are not working anymore, as the integration duplicated entities that their entity_id is now sensor.radiateur_bureau_io_2429113_2_temperature, device name + protocol ID + type then.

Indeed, why this integration entity names & ids contain protocol ID in the first place ? (protocol is IO) I always thought this should not be the case, and only device name + type

Screenchot: image

Note: the climate entity is not affected.

Caused by #95238 ?

What version of Home Assistant Core has the issue?

core-2023.9.0b0

What was the last working version of Home Assistant Core?

core-2023.8.4

What type of installation are you running?

Home Assistant Container

Integration causing the issue

overkiz

Link to integration documentation on our website

https://www.home-assistant.io/integrations/overkiz/

Diagnostics information

overkiz-392925a41b4580113109bbeef69971ea-Radiateur-2e3b6b6300c5797400657d53181e0436.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

About this issue

  • Original URL
  • State: closed
  • Created 10 months ago
  • Comments: 18 (14 by maintainers)

Most upvoted comments

As 2023.9.0 went live with this breaking change, there is no reason to fix that anymore … (see https://github.com/home-assistant/core/pull/99741#pullrequestreview-1613582253)

So, I think we are good to revert the revert #99742 and let it go like that.

Otherwise, 2023.9.0 is making a BC for users updating and then a second BC in 2023.9.1 ! People updating directly to 2023.9.1+ won’t have the issue, but then what ? Should we prevent certain people from updating ? Letting this BC permits to only make one BC in 2023.9.0

I don’t think there is a log in the release note but it should ! (https://github.com/home-assistant/home-assistant.io/pull/28811)