-
Notifications
You must be signed in to change notification settings - Fork 88
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
Web Interface - Entity Name Issue #792
Comments
I reset my system and Matter Server web interface no longer displays the user-assigned name. All entries now display the Brand / Model information so they are consistent. I'm assuming the odd display behavior shown above may have been some database corruption fixed in later versions, so I'm going to close this issue. |
It's simple, we show node label if the device has that but unfortunately all devices loose that on restart so it's pretty much useless |
Thanks for the info - I appreciate knowing what is going on. Too bad the label gets lost on restart. When I saw the node label, I thought 'this is great, now when a device goes offline, its easier to figure out which device was impacted. But not such a big deal anymore - I recently changed my Router/OTBR setup - it was a mix of Google Nest Router/OTBRs and Apple TVs, I now only use Apple TVs and got rid of the Nest stuff - now devices rarely go offline! In any case, this was an old issue, which was why I closed it out (I try to regularly review any issues I raised to see if they are resolved and should be closed). |
See image below.
For the Python Matter Server Web interface, for some devices, such as node 88, the Web interface shows the name that I assigned to the device (after trimming the room name), while others, such as Node 89 don't. I have no idea why.
Diagnostic data for node 88 and 89 are attached. Nodes 88 and 89.zip
Preferably the un-trimmed name (i.e., without trimming off the room name if it is at the start of the assigned name) should be used (or a link to the device page in the integration).
The text was updated successfully, but these errors were encountered: