Reading this thread, I got the impression that the error can be ignored.
THIS IS NOT TRUE, and this change for me is a security risk!
I use a Nuki lock with the Nuki Hub integration via MQTT, and ths change has caused for me - without any warning - that the lock is always displayed as locked, and it cannot be operated anymore.
If something like that is not a breaking change, what else?!?!
Something else is going on, I suggest you open a new thread for support.
I confirm Nuki’s problem with the new version 2023.08.
It remains in the same state as before the update. Any change in the Nuki application is not reflected in Home Assistant.
Impossible to lock the door from Home Assistant for example.
2023-08-04 10:41:18.390 DEBUG (MainThread) [homeassistant.components.mqtt.client] Transmitting message on nuki/36BF957C/lockAction: '2', mid: 15, qos: 0
I don’t use Z2M.
I rushed back to version 2023.7.3 and now everything works again.
As the Nuki entities are the ones given in the cryptic error message the other thread is about, I assume the same reason. I don’t use any other MQTT stuff.
And that message has nothing to do with the device not working. That warning message is simply telling you to notify Nuki of the API changes that HA made in 2023.8.
If you want, you can post your discovery topic here and it’s contents and we can figure out why your lock no longer works.
The fact remains, the naming change has nothing to do with this issue. Other MQTT changes were made last month.
After a complete restart (both complete HA server and NukiHub) it seems to work again even with 2023.8.0. Strange enough, after the restart I did not get the cryptic MQTT-warning again which I got the first time I upgraded to 2023.8.0.