-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nuki Opener options: ledEnabled, buttonEnabled, soundLevel not working #206
Comments
Hi, Those nodes represent what is referred to as "Configuration" in the API. If you update them from one device (e. g. Smartphone), other devices (e. g. NUKI Hub) don't know that these values have changed. There's no mechanism (unlike for the lockstate) to notify other devices that there was a configuration change. NUKI Hub polls the configuration in intervals, you can configure the interval under "Advanced NUKI Configuration", "Query interval configuration". So if you set the interval for example to 30 minutes, in the worst case it can take 30 minutes for NUKI Hubs to update those nodes if you've updated the configuration via the smartphone. I'm not sure about buttonEnabled. The API documentation only specifies it as a boolean value, on or off, I'd need to further investigate this (see https://developer.nuki.io/page/nuki-opener-api-1/7/). This could also be a copy/paste error, because the documentation has been copied from the smartlock docs, and some things haven't been updated properly. Making the doorbell suppression configurable via MQTT is actually a good idea, I'll look into it. |
Thank you very much for the explanation. Really appreciated!! 🙌 I didn't know the synchronization APP <-> MQTT was based on a polling process. Reduced the "Query interval configuration" to 5 minutes and I'm able to see the changes done in the app (the sound level) reflected in MQTT/HA and viceversa (enable LED through MQTT/APP and eventually it is reflected in the app too). It will be really appreciated if new functions available in the app (configuration of button, doorbell supression, opening delay...) will be available in the future. If tested will be needed, I can help on that :-) |
Recent user of this nuki_hub development (a great one, indeed!) and really excited with my new Opener, this, and its HA integration without Nuki Bridge!
Raised this case because although I can see the
nukiopener/configuration/buttonEnabled
,nukiopener/configuration/ledEnabled
andnukiopener/configuration/soundLevel
topics they don't seem to work:So, I'm just wondering: Are those topics expected to be working (thus I'm facing a bug) or maybe they are still work in progress and it is the expected behaviour?
I've seen this api web https://api.nuki.io/#/Smartlock/SmartlockOpenerAdvancedConfigResource_post_post
and those parameters (and others, like enable/disable the doorbell supression, the electricStrikeDelay) seem to be suitable to be modified somehow. But not sure if this development uses that Nuki Web API or another method to communicate with the Opener.
Thank you in advance
The text was updated successfully, but these errors were encountered: