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.

Sign up for GitHub

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

Jump to bottom

Parse and Report NAK Details #95

Closed
krkeegan opened this issue Jan 7, 2019 · 1 comment
Closed

Parse and Report NAK Details #95

krkeegan opened this issue Jan 7, 2019 · 1 comment

Comments

@krkeegan
Copy link
Collaborator

krkeegan commented Jan 7, 2019

When we receive a NAK, we should try and parse the cmd2 value and provide the user with a bit more information. This is supposedly what the cmd2 value means:

0xFF = Sender’s device ID not in responder’s database
0xFE = Load sense detects no load (confirm this one)
0xFD = Checksum is incorrect
0xFC = Pre NAK in case database search takes too long
0xFB = illegal value in command

http://cache.insteon.com/developer/i2CSdev-022012-en.pdf

See #94 for a real world example of the issue.
@krkeegan krkeegan mentioned this issue Jan 11, 2019
Merged
@TD22057
Copy link
Owner

TD22057 commented Jan 20, 2019

Fixed in PR #98

@TD22057 TD22057 closed this as completed Jan 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@TD22057 @krkeegan