What happens to people who don’t ignore the repair? Catastrophic failure? Messed up system? Need to repair all devices and start over?
Thanks for the reassurance.
I too was horrified at the alerts, I have several hundred sensors provided by Z2Mqtt and redoing everything that relies upon them would be days of work.
1 Like
Hardly. MQTT is used by less than half of HA installs (that report stats anyway).
As it’s been a while, can I recommend you read the code of conduct that you’re supposed to abide by:
Examples of unacceptable behavior include:
…
- Trolling, insulting or derogatory comments, and personal or political attacks
7 Likes
That is answered in the topic post. In very large text, with an accompanying image.
Final Lastly, Your devices will continue to work after the April update, even if the upstream developer doesn’t make the necessary changes. You just might have a duplicate name shown in the UI.
6 Likes
Just stop it, please. You’re not saying anything that hasn’t been said — except for the insults.
Perhaps treat others with a bit more respect. These are highly talented and skilled adults; not children.
Given your entitled attitude, are you contributing to this project in any meaningful way (community, financial or development support, or custom integration developer)?
This project is stable. Stable shouldn’t be confused with stagnant. Unless it’s stagnant, big changes will happen from time to time. This, however, really isn’t such a big deal.
HA is a hobbyist system and I’d prefer it to stay that way.
8 Likes
thank you for the reply. ok that is as i thought. i do not really like to update the firmware. beside that i also seem to have a third party sensor. i think my best option is to go back to an older version. or never update again.
How many do you have ? If you copy the topic and discovery message in mqtt explorer (text, not an image) , I can write a script for you.
and
3 Likes
This is a train wreck that signals an utter lack of proper management of the project. And yes, you do want people using it to feel entitled to better behavior by the team managing releases.
4 Likes
that is very kind of you. i did not knew mqttexplorer. that is a great tip already. I try to explain my ‘problem’. i am an occasional user. which means i dive into something, get it working, then forget about it because i am already working with the next thing. so each time i need to change something i need to read all info again. my mqtt server is on a NAS. which also requires an update. at the moment i get mixed signals : one is that i do not need to care, everything keeps working even if i do not change a thing. and the other is that i need to update things, the firmware, settings. for the tasmota that is not a big issue since i have just a few. i just do not see where/what to change. the bigger concern is the tuya energy monitor. i think i need to reserve time to get into everything again.
thanks again for the kind offer. i will do more reading first.
1 Like
Sorry guys but I don’t understand how to fix this error…
I have home assistant as well as zigbee2mqtt and mosquitto running in docker.
After the update to 2023.08 I have a ton of entity listed in 2 warnings.
I have to fix this in HA or in Zigbee2mqtt? Could you help me?
my entities are named like so:
# type of device (philips hue) and a short description of where is located (ex television back light in bedroom, etc.)
light.hue_luce_televisione_camera
light.hue_monitor_scrivania_destro_studio
light.hue_luce_letto_camera
light.hue_luce_televisione_soggiorno
I don’t have set a friendly name for each entity the name I set is already descriptive to me.
Also, if I need to add one of this in a card on the dashboard I can set a short name there…
Please read the intital post. It covers what you do in bold font.
1 Like
sorry I read it but I don’t completely understand… I also used translator to help me but without success… could you explain it in simple words? thanks
Ignore the warning messages.
4 Likes
Just that?
but if I don’t want? how can I do to fix this “naming thing”?
Yes. Just that. It’s not a thing for end users to fix… If you’re not writing your own integrations or building a bunch of MQTT devices manually. There’s nothing for you to do - hit ignore.
1 Like
The dev branch of Zigbee2MQTT already contains the proposed fix for that and make the warnings go away.
Thank you all! 
…at the beginning I thought I had to manually rename all entities, fortunately it is not so 
So i Understand that i have to nothing so far. And that I don’t have Fear about nothing works after April 2024.
BUT since the update some Automations with my Aqara Switches doesnt work. If i Triger a light wether it is ligt or switch it will work fine. If I trigger a Cover if it is a real cover or a Switch triggering a Garage Door unit it will not work…
If i trigger the same things with a Philips Hue dial everything is fine…
Am i right here ? I have openend an Issue the developer of the aqara Blueprint too…but i don"t know if a blueprint can be broken by an update
Then your problem is unrelated to this and you should start a new topic. This existing topic may be relevant and you should read it first though.
Also, for all the users not happy with how this was handled, Nabu-Casa hired a Product Manager a week ago to handle and anticipate customer issues like this in the future.
Things should go smoother when this person is more involved in the product release loop and the team finds their flow going forward.
In the meantime on this issue, just push ignore…
8 Likes