You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered: