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

Node not available, but are receiving attribute updates from same node? #649

Open
olavt opened this issue Mar 28, 2024 · 2 comments
Open

Comments

@olavt
Copy link

olavt commented Mar 28, 2024

After sending an "open_commissioning_window" commands to matter server for a node (4), I see this in the Python Matter Server log:

2024-03-28 11:38:00 (MainThread) ERROR [matter_server.server.client_handler] [547606914512] Error while handling: read_attribute (node 4): Node 4 is not (yet) available.
2024-03-28 11:38:54 (MainThread) ERROR [matter_server.server.client_handler] [547606914512] Error while handling: read_attribute (node 4): Node 4 is not (yet) available.
2024-03-28 11:38:54 (MainThread) ERROR [matter_server.server.client_handler] [547606914512] Error while handling: read_attribute (node 4): Node 4 is not (yet) available.
2024-03-28 11:38:54 (MainThread) ERROR [matter_server.server.client_handler] [547606914512] Error while handling: read_attribute (node 4): Node 4 is not (yet) available.
2024-03-28 11:44:16 (MainThread) ERROR [matter_server.server.client_handler] [547606914512] Error while handling: open_commissioning_window (node 4): Node 4 is not (yet) available.
2024-03-28 11:44:16 (MainThread) ERROR [matter_server.server.client_handler] [547606914512] Error while handling: read_attribute (node 4): Node 4 is not (yet) available.

At the same time, I'm getting attribute updates from the same node:

[28.03.2024 11:35:12.103 INF] Received response:
{
"event": "attribute_updated",
"data": [
4,
"4/1027/16",
9200
]
}

[28.03.2024 11:39:12.114 INF] Received response:
{
"event": "attribute_updated",
"data": [
4,
"4/1027/16",
9199
]
}

[28.03.2024 11:43:12.113 INF] Received response:
{
"event": "attribute_updated",
"data": [
4,
"4/1027/16",
9200
]
}

Seems like there is a bug somewhere.

@marcelveldt
Copy link
Contributor

Most probably something crashed after the open_commissioning_window ?

@olavt
Copy link
Author

olavt commented Mar 28, 2024

Not sure, but I don't think something crashed. It's more some kind of issue related to inconsistencies in reachability status of the nodes. Either at the Matter SDK level, or somewhere else.

Maybe slightly more details could be added to this log message?

"Error while handling: read_attribute (node 4): Node 4 is not (yet) available."

It would maybe be helpful to understand exactly what attribute that was attempted read to be able to more clearly see what operation it was related to.

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

No branches or pull requests

2 participants