SL3P Debug Mode broke (?) Bridge

[SchmuFoo (Jan S.)]

@Juergen

Mabe you discovered a problem in the beta with activating the mqtt API (which requires WiFi) while the SL3P is connected to a bridge (and the internal WiFi is off). I’ll forward this to the firmware team.

Thanks for the insights - Important to know also for the FW Teams: The SL3P was on FW 3.4.10, I received the Beta Confirmation “only” today from the Support (and will install the Beta soon)

@Juergen

Inbetween i’d recommend to not activate the mqtt API (= debug mode) while the Smart Lock is connected to a bridge.

Good to know, Thanks.

Before I will run this setup (Beta [+ MQTT] without the Bridge) I have to find a “maintenance” window to make sure, that I will not run into the “UniFi Problem” some users are reporting apparently

Nuki 3.0 Pro looses connection despite AP is next to it

There is a new beta available: https://developer.nuki.io/t/smart-lock-firmware-3-5-x-beta/17610/22

@Juergen

To recover the bridge you need to set it up and pair it with the Smart Lock again through the Nuki App > Manage Devices > Add Bridge section. You could also activate and set up the HTTP-API through the App and don’t need auto-discovery in this case.

I did the repair already yesterday evening, but still not successfull output in the Auto-Discovery.

But, I wasnt aware that the HTTP-API can also be activated through the App, which I have now found (was not intuitive) and finally I have back HTTP-API Access, Thanks!

P.S. Maybe you can add an small “i” (Info) Icon next to the those product icons: