Well, I voted also for this Feature.
As I saw the Build in WiFi Feature of the Pro, i really assumed that there is also a API. But after I received it, I realized that I need a Bridge to use the API. 
I would also love see the API on the Internal WiFi. 
This was one of main reasons why I bought my first Nuki.My WiFi coverage is 100% on the places where i want to use the Nuki. I’m planning to buy more, but don’t want to have 2 or more Bridges to use the API.
Same here.
Same here ! the nice thing of nuki is the local api, upvote to add that to SL3 Pro !
Same here, too!
Full Ack here, it could be a slimmed down api as well - just status, battery status + lock/unlock… not even http but just simple tcp/telnet if that reduces power consumption
But some way to be able to include it into a smat home with home assistant or something similar…
We would like to start a discussion with you about the specification of a potential MQTT API that could make it as local API into Smart Lock 3.0 Pro. If you have knowledge in that area and would like to participate, please send a request to join this user group: Mqtt (closed group) - Nuki Developers
Only members of this group will have access to the discussion.
This is a mandatory functionality. Without it, we will have too many apps to control all our devices from different manufacturers. Tools like Homeassistant helps to put everything in one place. Should be the same for SL Pro 3.0.
That is exactly what I wanted to post here. What is the purpose to have WiFi on board and call it PRO, when you tight users to relay only on cloud. It is maybe Deluxe, but not PRO.
For me, I would like to make an automation, when the lock is unlocking, it unlocks the grill in front of the door. But with cloud, I get response 10 second fastest and I have to POLL those info.
MQTT or Callbacks (with https) would be obviously appreciated.
+1
Exactly what I need to integrate SL 3.0 PRO into my Home Assistant setup. I wonder what is use to have Wifi on the SL 3.0 PRO if we cannot connect to the SL API through it.
Like many companies Nuki seems to be going down the cloud route more and more leaving home automation enthusiast which prefer local communication behind.
The WiFi on the SL3 can be used to communicate with the cloud API without having to use the bridge. It beats me why they haven’t been able to add some form of local API to the SL3. The only real reason I can come up with is no priority.
I got the offer to upgrade my SL2 to SL3 but I really see no benefit as long as I can’t get rid of the bridge.
I am also looking for API. I just bought a Nuki 3 pro.i didnt think it will not haven an API. Need basic APIs. Commands to lock/unlock, read status.
If you don’t mind depending on cloud you can use the cloud API. Else you will have to buy a separate bridge to be able to use the local bridge API for as long as this feature request is ignored by Nuki.
101% this. I specifically went with the SL3 Pro so that I don’t need another bridge taking up space and now after setting it up I found out that local control from Homeassistant is not even an option currently. That’s really bad.
I hope we’ll see some movement about this as this seems to have been an issue for a long time already now.
Appearantly the number of potential users (% of Nuki customer base) and the complexity of the development requirements play a major role in the decision process .
It’s a typical pattern where the requirements of first time adopters (which are home automation enthousiast with specific needs) are forgotten once the product has gained marketshare I’m afraid.
Waited half a year for this „PRO“ version with integrated wifi and finally got it today, so I wouldn‘t have to use another bridge for the other side of the house. Couldn‘t believe after setting it up that they got rid of the local http API - unbelievable! I use Home Assistant and just require very simple API or webhook functionality like lock/unlock, status and maybe battery state. MQTT would also work just fine. What‘s an absolute no-go for me is to use their cloud API or going back to a bluetooth bridge. Terrible, still in disbelieve and really hope they are making progress on implementing MQTT quickly!
I bought a Nuki Pro for the exact same reason as many people here: local control over WiFi, without the need of a bridge. I’m a big fan of Home Assistant, and want everything to work locally.
The default Nuki integration for Home Assistant only works with a bridge, regardless of what model you have (which defeats the purpose of having WiFi on device). I found a custom integration that can use Nuki Cloud to pull the status of your lock, but obviously that requires a constant internet connection, which is a no-go for me: https://github.com/kvj/hass_nuki_ng
Another option is to use ESPHome to create your own bridge with a cheap ESP32 microcontroller and directly integrate your lock with Home Assistant: https://github.com/uriyacovy/ESPHome_nuki_lock
It’s a bit hard to setup if you haven’t used ESPHome before but once it’s up and running, it’s great. Your lock pairs to the ESP32 board, which in turn relays your lock state to Home Assistant via local network. It’s also a lot cheaper than Nuki’s own bridge.
Personally, I will be returning the Nuki Pro and swap it out for the regular model.
@savjee : thanks for the link to the ESPHome alternative. There is also this alternative that I wanted to try: https://github.com/technyon/nuki_hub
Just ordered an ESP32 wroom dev board for under 10 bucks on amazon. Will probably keep the PRO in hopes they realize an MQTT integration as I‘m not happy to keep adding more and more devices. Use a lot of newer Shelly 1 Plus for different relay use cases. They also have an ESP32 w/ bluetooth. Will look into ESPHome and Tasmota to combine those for relay applications plus see if on same device I could utilize the bluetooth functionality.
Hi @Juergen, is there any outlook or current state of the discussion you can share with the community regarding the potential future MQTT integration?
I think now since the deliveries of the Pro has resumed the requests for it might increase strongly.
Same here, bought the Pro in order to get rid of the bridge. During setup I discovered only then that Home Assistant can’t control the lock anymore since it doesn’t have the API. What a shame.
I don’t want to be the bringer of bad news, but I contacted Nuki support about this and they said “it’s not on our roadmap”.
Just bought the Nuki 3.0 Pro because it integrates directly with WiFi. However, now I discover that it cannot be integrated with Home Assistant because the lock has no local API.
I see that this feature has already been requested. Any ETA on that? I really need this integration. Without it, I will return the Nuki I’m afraid.
Thanks!
Their reply:
Hello Xavier,
thank you for your message!Unfortunately at the moment the requested feature is not on our roadmap. But we are happy to forward your suggestion as a feature request to the responsible colleagues.
We are not able to tell you if and when we will be able to implement the requested feature.If your cancellation period didn’t expire yet, you can arrange everything yourself in the My Account area in the Nuki web shop.
[Return instructions]
That being said, I don’t want to bash on Nuki too hard. It’s the first IoT product that I came across that works without needing an account or connection to the cloud. It’s “local-first”, which I really appreciate! I also love that they publish their BLE specification. That’s very rare.
@Stan81 Good find! Seems like a few people have been building unofficial Nuki bridges.
About Tasmota/MQTT: I personally prefer ESPHome, because I have flashed it to all ESP8266 or ESP32-based devices (including many 1st gen Shelly’s).
I agree with what you say about “adding more and more devices”, so I added the Nuki bridge functionality to my ESP32-based air quality monitor. Works like a charm!