Anyone here with Nuki working with HASS > 0.115.6

Has anyone the Nuk SmartLock integration working with a HASS release 0.116.0 or 0.116.1?

Since upgrading from 0.115.6 I can’t connect to my lock anymore. The log shows timeouts.
My bridge is still working. THe Nuki Android app and Nuki Web still have access. Only HASS is making problems (I restarted hass and the Nuki (Hardware-)bridge multiple times).
I already created a new issue at github, but I would like to know if I am the only one with this issue.

Thanks in advance for your replies.

I’m on 0.116.1 and my Nuki lock is still working with HASS. (The lock firmware was also upgraded a few days ago to 2.8.15).

One error message during the night:

2020-10-09 05:06:22 WARNING (SyncWorker_34) [pynuki] Call failed: <Response [200]>

Otherwise fine.

Thanks for your response.

Which hardware is your HASS running at?
This is a really strange issue. I’ve changed the token of the bridge twice just to be sure and tried accessing the API via Browser. Everything is fine, but HASS always gives me timeouts.

I’ve got a Pi4 with logging going to a Synology NAS.

There was an issue with Nuki timeouts a couple of months ago which made the lock practically unusable (started with HA 0.105, I think, and was fixed a couple of releases later). As far as I understood it (not far), HA was sending/requesting data faster than the Nuki bridge could handle it.

Have you tried removing the Nuki integration entirely and starting again from scratch?

The Nuki is still only configurable via YAML. I removed the entry restarted, reactivated the entry and restarted again.
Same problem.

I even did a quick ioBroker setup just to make sure it’s not a problem with docker or network. No problems in ioBroker with the same token.