New mqtt entities don't show up if they have unique IDs specified

Configuration
1

After one of the recent updates, I found that if I add a new MQTT entity and specify a unique ID, it does not get acknowledged by HA. If I edit the yaml and delete the unique ID, it shows up. If I go back and restore the unique ID it disappears again. This is true for binary sensors and sensors (I haven’t tried others). I also find that if I edit an existing (actively recognized by HA) MQTT entity, that has a unique ID, it disappears when I trigger a reload. To bring it back, I have to delete the unique ID which was working previously.

I searched the releases for breaking changes that relate to this and found none. This seems like a defect to me. Does anyone else see this behavior?

1 Like
2

I’m seeing the exact same thing with a light. In the dashboard where it used to be it says “Entity not available: light.light_name”. At least it’s not just me :slight_smile:

Update: I guess it actually did work, it just made it a different entity id. I went back in, gave it a unique id, then checked and there were two entities, one with an _2 on the end, so I removed that, and I’m all good.