homeassistant

11668 readers

12 users here now

Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io

founded 1 year ago

MODERATORS

GreatAlbatross@feddit.uk

If you are getting the warning in home assistant from Zigbee2MQTT about "Discovered entities with a name that starts with the device name" read this; it's safe to ignore and will go away. (community.home-assistant.io)

submitted 1 year ago by surfrock66@lemmy.world to c/homeassistant@lemmy.world

5 comments fedilink hide all child comments

This was news to me so I thought I'd share:

Everyone, there will be MQTT name changes in the next release of the software. There is nothing to worry about, your names are safe. However the change caused addons like Z2M (and other MQTT integrations) to update their discovery information. As it stands, Z2M will not be able to release a version with this fix until September 2023. 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.

Once Z2M updates, the warnings will go away.

Again, during this whole transition period, your names and the default device names should not change. Please keep us informed if they do change.

you are viewing a single comment's thread
view the rest of the comments

[–] StunningGoggles@sh.itjust.works 4 points 1 year ago (1 children)

What configuration yaml changes? Now I'm worried.

[–] acceptable_pumpkin@lemmy.world 3 points 1 year ago

Here’s what I see in my Settings warning section:

Command Line YAML configuration has moved

This stops working in version 2023.12.0. Please address before upgrading.

Configuring Command Line sensor using YAML has moved.

Consult the documentation to move your YAML configuration to integration key and restart Home Assistant to fix this issue.