Home Assistant Update 2024.2.0. Detected entities with a name starting with the device name

[edudele]

Description

Need update or modify mqtt-hassio.cfg

[mwrben]

This relates to a change in the latest version of HA 2023.8. The change causes addons like Z2M (and other MQTT integrations) to update their discovery information. During that time a warning will be in your logs indicating that there is an issue. You can safely ignore this warning. As of this writing, there may also be an accompanied repair. You can also safely ignore this repair. If I understand it correctly, developers need to take the change into account by February 2024 Details of this is at https://community.home-assistant.io/t/psa-mqtt-name-changes-in-2023-8/598099

[john30]

great, phantastic move of HA. the device name is added as prefix in order to assure that is unique, if they remove it now, it will no longer be unique - brilliant. I'll search HA issue tracker if another developer sees it the same way

[john30]

please check if the warning is gone and the entities remain as previously when changing line 137 of mqtt-hassio.cfg from this: "name":"%prefixn %circuit", to this: "name":"%circuit",

if that yields in the desired result, users of HA before 2023.8 would have to use the old version and everyone else the new version.

[edudele]

After the change the warning seems to disappear but this one still appears:

Logger: homeassistant.components.mqtt.mixins Source: components/mqtt/mixins.py:294 Integration: MQTT (documentation, issues) First occurred: 10:19:20 (5 occurrences) Last logged: 10:19:20

MQTT entity name starts with the device name in your config {'unique_id': 'ebusd_global_running', 'device': {'identifiers': ['ebusd'], 'manufacturer': 'ebusd.eu', 'name': 'ebusd', 'sw_version': '23.2', 'suggested_area': 'Heating', 'connections': []}, 'state_topic': 'ebusd/global/running', 'name': 'ebusd running', 'device_class': <BinarySensorDeviceClass.RUNNING: 'running'>, 'payload_on': 'true', 'payload_off': 'false', 'qos': 0, 'payload_available': 'online', 'encoding': 'utf-8', 'availability_mode': 'latest', 'force_update': False, 'payload_not_available': 'offline', 'enabled_by_default': True}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'running' MQTT entity name starts with the device name in your config {'unique_id': 'ebusd_global_signal', 'device': {'identifiers': ['ebusd'], 'manufacturer': 'ebusd.eu', 'name': 'ebusd', 'sw_version': '23.2', 'suggested_area': 'Heating', 'connections': []}, 'state_topic': 'ebusd/global/signal', 'name': 'ebusd signal', 'device_class': <BinarySensorDeviceClass.CONNECTIVITY: 'connectivity'>, 'payload_on': 'true', 'payload_off': 'false', 'qos': 0, 'payload_available': 'online', 'encoding': 'utf-8', 'availability_mode': 'latest', 'force_update': False, 'payload_not_available': 'offline', 'enabled_by_default': True}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'signal' MQTT entity name starts with the device name in your config {'unique_id': 'ebusd_global_uptime', 'device': {'identifiers': ['ebusd'], 'manufacturer': 'ebusd.eu', 'name': 'ebusd', 'sw_version': '23.2', 'suggested_area': 'Heating', 'connections': []}, 'state_topic': 'ebusd/global/uptime', 'name': 'ebusd uptime', 'state_class': <SensorStateClass.TOTAL_INCREASING: 'total_increasing'>, 'unit_of_measurement': 's', 'qos': 0, 'payload_available': 'online', 'encoding': 'utf-8', 'availability_mode': 'latest', 'force_update': False, 'payload_not_available': 'offline', 'enabled_by_default': True}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'uptime' MQTT entity name starts with the device name in your config {'unique_id': 'ebusd_global_updatecheck', 'device': {'identifiers': ['ebusd'], 'manufacturer': 'ebusd.eu', 'name': 'ebusd', 'sw_version': '23.2', 'suggested_area': 'Heating', 'connections': []}, 'state_topic': 'ebusd/global/updatecheck', 'name': 'ebusd updatecheck', 'value_template': Template<template=({% set my_new = value_json|truncate(255)|regex_replace(find=',.*| available|revision v|version v|OK',replace='') %}{% if my_new == '' %}{% set my_new = '23.2' %}{% endif %}{{ {'installed_version':'23.2','latest_version':my_new,'entity_picture':'https://ebusd.eu/logo-32x32.png','release_url':'https://github.com/john30/ebusd/releases/latest'} | tojson }}) renders=0>, 'qos': 0, 'payload_available': 'online', 'encoding': 'utf-8', 'availability_mode': 'latest', 'retain': False, 'payload_not_available': 'offline', 'enabled_by_default': True}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'updatecheck' MQTT entity name starts with the device name in your config {'unique_id': 'ebusd_global_scan', 'device': {'identifiers': ['ebusd'], 'manufacturer': 'ebusd.eu', 'name': 'ebusd', 'sw_version': '23.2', 'suggested_area': 'Heating', 'connections': []}, 'state_topic': 'ebusd/global/scan', 'name': 'ebusd scan', 'qos': 0, 'payload_available': 'online', 'encoding': 'utf-8', 'availability_mode': 'latest', 'force_update': False, 'payload_not_available': 'offline', 'enabled_by_default': True}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'scan'

[edudele]

The warning problem disappears, but a bigger problem comes, we are left without history.

But the unique_id are renamed, losing all the history of Home Assistant, InfluxDB, etc... Original: number.ebusd_basv0_hwctempdesired_tempv With Change: number.basv0_ebusd_basv0_hwctempdesired_tempv

Make it clear that the creation of the ID is generated by HA based on the device name adding the name prefix.

We can't keep the unique_id as it was and comply with the new requirements?

[Danit2]

You must change the line 312 to "name":"%name %fieldname",

Then it works and only some global error rest. This i try to remove also.

[Danit2]

For the global errors you must change the line 341 to "name":"%name"

That have fix all the errors for me.

[edudele]

For the global errors you must change the line 341 to "name":"%name"

That have fix all the errors for me.

With those changes that you comment, does it change the ids of the entities? ​

[Danit2]

No, for me not. The entity id is the same and the history is stil there.

[estegewr]

The change was rolled back in HA release 2023.8.4. Therefore, no warning occurs anymore even with the original mqtt configuration.

[edudele]

Close Remove repair issue for MQTT discovered items #98768

[Danit2]

No, the Changes is not rolled back. Only the repair messgae is gone.

but the developers of programs still need to have this problem fixed by version 2024.2.

Quote: "The goal of getting MQTT naming up to par with the rest of the Home Assistant integrations remains."

so, i would be interested to know if my changes have fixed the bug or not? @edudele?

If so, can I do a PR to implement this.

Thanks.

[edudele]

I think the change is valid. the ids are kept and the warning was fixed.