-
Notifications
You must be signed in to change notification settings - Fork 46
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
Logging updates to improve debugging: adding cluster path information #103
Comments
ivmarkov
added a commit
to ivmarkov/rs-matter
that referenced
this issue
Oct 2, 2023
ivmarkov
added a commit
to ivmarkov/rs-matter
that referenced
this issue
Oct 6, 2023
ivmarkov
added a commit
to ivmarkov/rs-matter
that referenced
this issue
Jan 2, 2024
ivmarkov
added a commit
to ivmarkov/rs-matter
that referenced
this issue
Jan 8, 2024
ivmarkov
added a commit
to ivmarkov/rs-matter
that referenced
this issue
Jan 13, 2024
ivmarkov
added a commit
to ivmarkov/rs-matter
that referenced
this issue
Jan 18, 2024
ivmarkov
added a commit
to ivmarkov/rs-matter
that referenced
this issue
Feb 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When an interaction arrives at the device, the TLV contents are logged, but it's not easy to get the cluster path or attribute being read. The general commissioning cluster handlers have some code for invoke commands, but it'd make it easier to debug from log captures if the log line included information about the cluster being queried in a ReadRequest or other requests, like in #102
The text was updated successfully, but these errors were encountered: