The Smart Lock 3.0 Pro has no included Bridge API, so every integration relying on the Bridge API will not directly work with the Smart Lock 3.0 Pro. So in these cases a Nuki Bridge is needed.
I am not sure where you created which API token though in your example.
(Preparing for the question why it is not included: Mapping the Bridge API functionality to the Smart Lock 3.0 Pro could lead to significant battery issues, as the Bridge normally caches everything possible to avoid constantly waking up the device.)
never the less it would be nice to have the choice if I want to use the bridge API on the lock or not.
I bought the pro because I wanted to use the API to integrate the lock into my FHEM setup…
Battery consumption is not an issue for me, I have 2 battrey packs, so I just change it if one is empty.
This is not such a big deal for me… especially once you fixed the bug that the lock does not automatically reconnect to the wifi when I swap the batteries
Dear Stephan,
I understand reason to not include API to Pro version. I was pretty interested in battery life if I am asking to Pro API (if it would exist) every 5 seconds for lock status.
BUT: why it is not metioned in any marketing papers? Everywhere I just read, that “you dont need bridge when you have PRO”… And result is, that I need it at all.
Hello Mathias,
thank you very much for your reply! Later last night I`ve run successfully api.nuki.io on my SL PRO. Response time is ca 1-2 seconds, so for my use case it is quite OK. And I can say, that i works however I preffered local network solution for case of internet connectivity failure.
But thank you very much for note about MQTT - I am hearing first time about it, but lets say, that it is nice challenge to learn something new :). Have a nice day!