Skip to content
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 Ring doesnt get recognized everytime #49

Closed
G3rtz opened this issue Nov 24, 2022 · 8 comments
Closed

Nuki Opener Ring doesnt get recognized everytime #49

G3rtz opened this issue Nov 24, 2022 · 8 comments

Comments

@G3rtz
Copy link

G3rtz commented Nov 24, 2022

Hello everyone,
im testing nuki_hub as an alternative to nuki_ng, which always seems to drop connection for a few seconds, so i get 5-10 times the homekit announcement, that my door is now shut / opener is off.

i have it paired as app at the moment, because of the Wife Acceptance Factor. The Bridge is annoying with the messages, but if it doesn't work, would be much worse.

Nuki Hub seems to not register all the events, that are going on.
Here is a screen of the states in HA
image

And here is a MQTT Debug Log
image

So, what am i doing wrong?

@technyon
Copy link
Owner

Can you give some more information? As a far as I can see from the debug output, there were two rings detected ... times don't match up though with the picture above. Which ring wasn't detected?

@G3rtz
Copy link
Author

G3rtz commented Nov 24, 2022

sorry, i wasn't really clear with it. The MQTT Log corresponds to the upper bar (its the "Haustuer Summer ring", not "ring action")
"Nuki Haustuer Summer ring action" is from the Nuki Bridge via nuki-ng. The ring at ~8 AM and 9:15AM are both missing.

@technyon
Copy link
Owner

I'm not really sure what could be the problem. I had to take a guess how the opener signals a ring, since this is completely undocumented. From what I could guess, whenever the opener signals a change to "locked" when the state is already "locked", a ring has been detected. Could you observe in your MQTT logs this is the case? Was the opener in the "locked" state when the ring occured?

@G3rtz
Copy link
Author

G3rtz commented Nov 29, 2022

i dug into yesterdays log, as there were two ring events happening.
image
this is from nuki via nuki bridge and nuki-ng. as you can see, there was a ring event.

image
this is from nuki-hub. there was no event. The binaryState is nondescript also:
image

Despite everything, the lock state seems to have the event, but it seems to not be submitted to Home Assistant:
image

@technyon
Copy link
Owner

It's hard to tell because as I mentioned, the ring detection is undocumented. You can try the attached firmware for debugging, it outputs the previous and new state of the opener on every change via serial. Whenever you see this, a ring is detected (and should be reported via MQTT):

Opener state updated: locked --> locked

Maybe you can figure out if any other state changes should report a ring.

nuki_hub.zip

@iranl
Copy link
Collaborator

iranl commented Feb 18, 2024

This should be fixed since merging #296 and #299

@iranl
Copy link
Collaborator

iranl commented Mar 2, 2024

With the changes in 8.33 a ring that is visible in nukiopener/lock/state should now always signal a Home Assistant ring in the new ring event that is made available through auto discovery.

Can be closed.

@technyon
Copy link
Owner

technyon commented Mar 3, 2024

Closing for now.

@G3rtz Can you recheck if release 8.33 fixes your problems. If not, we'll reopen the issue.

@technyon technyon closed this as completed Mar 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants