Ugly hack to make it works with Nuki v2 #16
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So, the problem was that we need to subscribes to "indication" in order to receive a response from the Nuki.
I also needed to add some time.sleep(2) after every char_write_handle and more sleep after the characteristics discovery. Don't know if this is only a problem with my raspberry pi 0, but anyway it is working (a bit slow) now with my Nuki v2.
Yes, it is ugly and inefficient, but it works (at least for me) ;)
I cannot test it with a Nuki v1 (I don't have it) but i guess it should still works.
If someone can test it, let me know.
I'll try to make it better if I'll find the time!