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

Merge Dev #1

Merged
merged 32 commits into from
Mar 26, 2024
Merged

Merge Dev #1

merged 32 commits into from
Mar 26, 2024

Conversation

AzonInc
Copy link
Owner

@AzonInc AzonInc commented Mar 26, 2024

No description provided.

uriyacovy and others added 30 commits December 15, 2022 10:18
Update example-project-main.yaml
Update example-project-dev.yaml
Sometimes, when sending 2 subsequent lock actions (one right after the other),
the Nuki lock reports the second as successful without really doing it.
Moreover, multiple fast-paced commands can trigger a loop of
`requestKeyTurnerState failed with error error (99)`.
This makes the lock orders of magnitude faster and more reliable.
Bluetooth advertisements are received earlier and commands can be sent faster.
Only wait a long cooldown when the lock is turning the key.
Increase speed and reliability by orders of magnitude
@AzonInc AzonInc merged commit 73f1662 into main Mar 26, 2024
2 checks passed
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

Successfully merging this pull request may close these issues.

3 participants