Nuki smartlock continues to fail after upgrade to 112

The upgrade from 110 to 111 pretty much disabled Nuki smartlocks (long discussion on Github here). Consesus seems to be that it is a HA problem (though who knows?).

We were all hoping it would go away with 112, but apparently not:

nuki1

nuki2

Anyone got any ideas?

1 Like

Come on - really?

nuki3

1 Like

I too have this problem since upgrading to 111.

I have the same problem.

With HA 0.110, nuki integration works fine. All after 0.111 —> nuki fails permanently.

So, unless this issue is not resolved, a lot of people cannot update HA.

As nuki works without any problems under 0.110 with the former as well as the actual nuki firmware (so all of the bug is on the HA side), it is very hard to understand, why this issue still exists after more than 15 days after it has been mentioned for the first time. It‘s odd…

HA 0.112.4 and nuki smart lock 2.7.30. Error messages start appearing after 48 hours. Which is a bit odd when you think about it - what happens after 48 hours? I was away when the errors started, so it can’t be anything to do with the use of the lock.

The Github thread on this subject now has 53 comments.

Whether it has 53 or 500, unless the developer of the integration can resolve there isnt much we can do. I see there hasn’t been any response from him in a few days on the github issue, so either he is busy in RL, away on leave or just given up. its a waiting game

the question is where the issue is located - currently I’m tending to think of more a HA problem bcs its working with older HA versions.

I would love to have some collaboration here - I’m a bit puzzled to debug and isolate either towards the component or HA. Any advise how I can do so?

The latest posts on Github here seem to be narrowing down the problem very effectively.