As a long-time user of Nuki locks, I’ve noticed an issue with HTTP responses when interacting with my locks. Whenever I send a request to open or close a lock, I always receive a 204 HTTP code, even if the lock encounters a motor block. This makes it impossible to log errors in my system. I wonder if there’s a way to return a dedicated HTTP response code for lock errors, such as motor blocks. A general error code would be a huge improvement and would help me troubleshoot issues more effectively.
Another issue I’ve encountered is with the firmware updates for my Nuki devices. Currently, firmware updates can only be done via Bluetooth, even when a bridge is installed. This is inconvenient because Bluetooth requires me to be within range of the product. I’d love to see an option for remote firmware updates over WiFi, which would make maintaining my devices much easier.
I’ve also had some trouble with my dimmer switches. Whenever I try to change the dimmer percentage to something other than 99%, it immediately reverts back to 99%. I’ve looked at the logs, but I’m not experienced enough to detect if the issue is shown there. If anyone has any insights or solutions, I’d greatly appreciate it!
Despite these challenges, I’m really impressed with the Nuki ecosystem and the support from the community. It’s great to see so many users sharing their experiences and tips. I’m hopeful that these issues will be resolved soon, and I’m excited to continue exploring the full potential of my smart home setup.