Thanks, it looks there are some changes but still some issues, I’m going to send you a private message.
Messages we still have are in the Home Assistant log, I personally have no repair issue.
It would be great if an official update of the Nuki firmware is shared before the Home Assistant 6 months grace period ends (which should be in 2024.2) - so by January end I’d say.
The changes are already in the current beta version.
I’m still in discussion with the previous poster but it seems that it is necessary to manually delete the MQTT entity in Home Assistant and then reconnect via the MQTT settings in the Nuki app in order to get rid of the log messages. Just edit the MQTT configuration and hit “Save” without changing anything after you have deleted the .MQTT entity in Home Assistant.
According to the GitHub link I shared earlier it doesn’t seem like there is a grace period anymore.
This repair issue is mostly misunderstood as a breaking change, while it is not breaking at all. The original intent was to inform and to get people to report issues upstream to third-party software that integrate with Home Assistant over MQTT. It is currently handled gracefully and in a backward-compatible manner for the end-user.
If there is still some information somewhere regarding a grace period, please let me know.
First of all, thanks a lot @marc for your quick answer on this.
Right, my understanding is that this would not trigger a “repair notification” anymore.
However, if I understood well, this would still result in a super-long entity name that includes “device_name”_“entity_name”. If I go to my last homeassistant.log, I still see the warning about this there:
MQTT entity name starts with the device name in your config {'availability_topic': 'nuki/<redacted>/connected', 'payload_available': 'true', 'payload_not_available': 'false', 'device': {'identifiers': ['[<redacted>]'], 'manufacturer': 'Nuki', 'name': 'SmartLock', 'model': 'Smart Lock 3.0 Pro', 'connections': []}, 'name': 'SmartLock Battery charging', 'unique_id': '<redacted>_battery_charging', 'device_class': <BinarySensorDeviceClass.BATTERY_CHARGING: 'battery_charging'>, 'entity_category': <EntityCategory.DIAGNOSTIC: 'diagnostic'>, 'state_topic': 'nuki/<redacted>/batteryCharging', 'payload_off': 'false', 'payload_on': 'true', 'enabled_by_default': True, 'availability_mode': 'latest', 'encoding': 'utf-8', 'force_update': False, 'qos': 0}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Battery charging'
If I understand well the warning above, Home Assistant is still handling the problem by stripping off the device name from the entity name, but I’m not clear what will happen in 2024.2 - if they’ll keep stripping this or we would end up with a super-long entity name.
Ideally, and to be on the safe side, this should be resolved in the Nuki integration by January - this way we certainly avoid any possible issue.
Thanks!
Have you tried to remove the entity and reconnect as I’ve suggested above?
The log messages should then not be there anymore.
But you would need the current 3.8.2 beta.
Nope, I’ve not tried yet as I was hoping not to use beta releases on my production instance… after all, it’s the main entrance to my home 
I might decide to do that if I don’t see an official release by January, though.
Thanks again!
@marc I’ve tested 3.8.2 beta with latest HA 2024.1.2 and Z2M, after deleting MQTT integration from Nuki as well from HA and setting up everything again - it work like a charm !
great work guys
4 Likes
Seems that we can not update ha. Or we will loose the function of nuki. 
Except if I understood wrong, it will work but with very ugly names.
The only solution to avoid this is to use the latest beta version.
No it works with well formed names.
Without updating the lock.
I am relay surprised.
@Thomas_Schindele have you already done the HA core update 2024.2.0 - and it still works with the old Nucki firmware?
But you don’t have well formed names. See in the third screenshot "door apartment door apartment "
1 Like
It seems that version 3.9.0 has been released and I can confirm that, after removing the MQTT configuration from the Nuki app (and the corresponding entry from Home Assistant) and adding it back, I have well formed names again (friendly name, etc).
1 Like
You are right. But I can deal with that. 
Taping save directly in the Nuki app without deleting nor modifying anything also do the job.
1 Like
No problem on your end. The firmware is still rolling out in stages.
1 Like