Most Homematic sensors doubled after restart

[liflitz]

The problem

Most Homematic sensors doubled after restarting when installing core_2024.7.0 and core_2024.7.1. The new sensors are named like the old ones with the addition of "_2" at the end. I manually deleted the old sensors and renamed the new ones to the names of the old sensors (deleting the _2 from the entity ids). After the next restart following a core update the same sensor doubling happened again.

What version of Home Assistant Core has the issue?

2024.7.1

What was the last working version of Home Assistant Core?

2024.6.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

HomematicIP Cloud

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.core
Quelle: core.py:552
Erstmals aufgetreten: 18:09:55 (1 Vorkommnisse)
Zuletzt protokolliert: 18:09:55

Something is blocking Home Assistant from wrapping up the start up phase. We're going to continue anyway. Please report the following info at https://github.com/home-assistant/core/issues: hassio.sensor, reolink.sensor, application_credentials, tag, homematicip_cloud.weather, person, matter.cover, dwd_pollenflug, shelly.update, matter.fan, compensation.sensor, samsungtv.remote, file_upload, influxdb, reolink.update, fan, gdacs.sensor, dhcp, reolink.select, wake_word, valve, nina, tomorrowio.sensor, sun, accuweather, matter.event, cloud.stt, mobile_app.binary_sensor, shelly.light, cloud.binary_sensor, cast.media_player, samsungtv, google_assistant, energy, number, usb, compensation, xbox.sensor, bluetooth, lovelace, reolink.switch, scene, python_script, homematicip_cloud.climate, template.binary_sensor, hassio, homematicip_cloud.button, switch, broadlink, camera, androidtv_remote, androidtv_remote.media_player, counter, thethingsnetwork.binary_sensor, shelly.cover, dlna_dmr, synology_dsm.switch, logger, mobile_app.device_tracker, matter.climate, ipp.sensor, homematicip_cloud.cover, homematicip_cloud.switch, media_player, ipp, energy.sensor, reolink.siren, map, hacs, homematicip_cloud, xbox.remote, repairs, mqtt.sensor, thethingsnetwork, siren, device_automation, template.sensor, image_upload, system_log, template, timer, homematicip_cloud.sensor, esphome, frontend, assist_pipeline, androidtv_remote.remote, thread, synology_dsm.camera, forecast_solar.sensor, binary_sensor, diagnostics, group, config, utility_meter, default_config, zone, hacs.sensor, samsungtv.media_player, ecowitt.sensor, shelly.valve, matter.light, tomorrowio, trace, reolink.camera, modbus.sensor, synology_dsm, nina.binary_sensor, http, notify, xbox.binary_sensor, mobile_app.notify, media_source, button, google_translate.tts, homematicip_cloud.lock, shelly.climate, shelly.event, synology_dsm.sensor, my, ecowitt, input_boolean, lock, network, analytics, hassio.binary_sensor, nmap_tracker.device_tracker, stream, shelly, utility_meter.sensor, synology_dsm.update, gdacs, system_health, webhook, tomorrowio.weather, esphome.sensor, schedule, matter.lock, input_text, blueprint, hassio.update, mqtt.binary_sensor, synology_dsm.binary_sensor, conversation, cloud.tts, persistent_notification, matter.binary_sensor, hardkernel, mobile_app.sensor, accuweather.sensor, homematicip_cloud.alarm_control_panel, shelly.number, alarm_control_panel, homeassistant, homeassistant.scene, broadlink.remote, shelly.sensor, input_number, ssdp, device_tracker, homeassistant_alerts, forecast_solar, hardware, modbus, script, matter.switch, downloader, event, homematicip_cloud.light, homematicip_cloud.binary_sensor, select, nmap_tracker, xbox, shelly.button, thethingsnetwork.device_tracker, dwd_pollenflug.sensor, geo_location, cast, mobile_app, input_select, dlna_dmr.media_player, automation, light, search, history, cover, intent, gdacs.geo_location, reolink.binary_sensor, broadlink.switch, websocket_api, thermal_comfort.sensor, command_line.sensor, shelly.binary_sensor, matter, remote, mqtt, ecowitt.binary_sensor, onboarding, climate, matter.number, matter.sensor, weather, update, synology_dsm.button, thermal_comfort, api, input_button, reolink.button, sun.sensor, logbook, esphome.update, zeroconf, usgs_earthquakes_feed.geo_location, accuweather.weather, reolink.light, reolink.number, command_line, reolink, broadlink.sensor, sensor, ffmpeg, cloud, tts, recorder, input_datetime, xbox.media_player, auth, stt, shelly.switch, thethingsnetwork.sensor, backup The system is waiting for tasks: {<Task pending name='Task-2273' coro=<AbstractConfig.async_initialize.<locals>.sync_google() running at /usr/src/homeassistant/homeassistant/components/google_assistant/helpers.py:114> wait_for=<_GatheringFuture pending cb=[Task.task_wakeup()]> cb=[set.remove()]>}

Additional information

No response

[home-assistant[bot]]

Hey there @hahn-th, mind taking a look at this issue as it has been labeled with an integration (homematicip_cloud) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `homematicip_cloud` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign homematicip_cloud` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

homematicip_cloud documentation homematicip_cloud source _{^{(message by IssueLinks)}}

[shennig84]

Can confirm this issue. First time i have seen this behavior was in B7.

[schmidtdon]

Same problem here. !

[hoernle53]

Same problem

[akrea]

same issue! second time this week I had to comb through all entities. Costs a lot of time every single time.

[fcoppey]

same problem... happened also two times... I don't know what triggers it, what it the update from 2024.7.0 to 2024.7.1?

[hahn-th]

When upgrading from 2024.6 or earlier to 2024.7, the function which generates the unique id of an entity has changed. The unique id is the internal identification of the entity. For HomeAssisant you got new devices with this change and you got your binary_sensor....._2 entities. You deleted the old ones and renamed the _2 entities into names without _2. Because of lots of sideeffects with the unique id generation in 2024.7.0 i switched back to the unique-id-generation-algorithm 2024.6.x and earlier. Now HomeAssistant thinks again you got new entities, because the unique-id differs to the unique-id out of 2024.7. But it is the same unique it as it was in 2024.6.

I hope i could explain whats the point 😄

[liflitz]

What do you recommend us to now? After the next core update, will we get sensor duplications again? If yes, how should be best react to it?

[hahn-th]

No more unique-id changes (without migration). So no new (duplicated) sensors.

"leaning by burning"

[liflitz]

Indeed no more sensor duplication going to 7.2 - thanks!!

[hahn-th]

@home-assistant close