-
-
Notifications
You must be signed in to change notification settings - Fork 597
-
-
Notifications
You must be signed in to change notification settings - Fork 597
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
Yale Lock Inclusion Issue: Inconsistent ACK Responses During Interview Process #7129
Open
2 of 3 tasks
Labels
bug
Something isn't working
Comments
The Zwave JS version is 11.14.3 |
sorry I was on vacation. |
This might just be a connectivity issue. Please read and follow https://zwave-js.github.io/node-zwave-js/#/troubleshooting/first-steps?id=first-steps to exclude the most common factors first. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
Deploy method
Manually built (git clone - npm run build - npm install
Z-Wave JS UI version
1.0.0
ZwaveJS version
11.14
Describe the bug
I've been testing the inclusion process of Yale locks using Zniffer and encountered an issue that might be worth investigating further. During the interview process, the lock occasionally sends a manufacturer_specific_report frame.
On some occasions, the Gateway (GW) fails to acknowledge (ACK) this specific report sent by the lock.
As a result of the missing ACK, the lock emits an error sound, indicating a failure at the lock level.
Despite the error sound, the interview process continues and is completed successfully at the protocol level. I am attaching the Zniffer log files link for your reference.
https://drive.google.com/drive/folders/1tZD1bMb0FQXkUAivFdlSBH8HjhqGKyMJ?usp=drive_link
To Reproduce
The behaviour is repeating itself automatically. Out of 10 times the behaviour is repeated 8 times itself.
Expected behavior
Inclusion Success Announcement from the device instead of Failure announcement even after successful addition.
Additional context
@robertsLando Could you please help us out with a potential fix for the same.
The text was updated successfully, but these errors were encountered: