You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Discovered entities with a name that starts with the device name
Some MQTT entities have an entity name that starts with the device name. This is not expected. To avoid a duplicate name the device name prefix is stripped of the entity name as a work-a-round. Please inform the maintainer of the software application that supplies the affected entities to fix this issue. "
I have Zigbee2MQTT and 2 gateway SLS (slsys.io) in Direct2MQTT Mode (without Z2M). Devices which connected to SLS-MQTT nothave problem with Naming. Only one device connected to Z2M - have problem
Обнаруженные объекты с именем, начинающимся с имени устройства
Это приведет к неисправностям в версии 2024.2.0. Пожалуйста, устраните эту проблему перед обновлением.
Некоторые объекты MQTT имеют имя, начинающееся с имени устройства. Это не предусмотрено. Во избежание задвоения имени префикс имени устройства удаляется из имени объекта. Пожалуйста, сообщите разработчику программного приложения, поставляющего соответствующие объекты, о необходимости устранения этой проблемы.
What happened?
"Discovered entities with a name that starts with the device name
Some MQTT entities have an entity name that starts with the device name. This is not expected. To avoid a duplicate name the device name prefix is stripped of the entity name as a work-a-round. Please inform the maintainer of the software application that supplies the affected entities to fix this issue. "
I think this is the relevant change, will edit it if this isn't right: home-assistant/core#95159
Apologies if this is not a zigbee2mqtt issue I will close it if so, thanks
What did you expect to happen?
No warning
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.32.2
Adapter firmware version
7.3.1.0 build 176
Adapter
skyconnect
Debug log
No response
The text was updated successfully, but these errors were encountered: