-
Notifications
You must be signed in to change notification settings - Fork 173
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
How to set accessory/device name in Homekit? (CON-1325) #1074
Comments
I add only two light on the bridge, and add label like this:
and
But it still show: "Matter Accessory, 2" and "Matter Accessory, 3", iOS 17.6.1 |
Hi @dzungpv Please check #1046 (comment). |
@jadhavrohit924 your comment is not helping me at all. I found out that it is fairly easy to change the label of the root node, but I still can't figure out how to change the label of the endpoint.
|
@herculesp17 If you read the node label from chip-tool, you'll get a string that you have set for your node. Ecosystems don’t show the node label in the UI. This is not an issue with the SDK. |
@jadhavrohit924 thanks for the hint. I just ask myself if someone want to cert their device and have multiple lights for example as different endpoints they can't name it differently. That is inconvenient. So it seems that is an issue with the matter integration of the Ecosystems. |
I read all the issue but not found a way to set display name of the accessory / node in the Homekit.
basic_information does nothing and the bridged_device_basic_information I could not make it work.
I create a thermostat, a fan and two lights. I try with multiple endpoint in a node and It can add to Homekit, but I could not found a way to set name for light, it show Light and Light2.
I try bridge but could not add more than 2 devices, it show
Seem like bridge is the only way but I could not make it work
I follow some hint here but not working #201 (comment)
#356 (comment)
I don' know why a basic feature like set the name off a device/node/accessory does not include in the simple way
The text was updated successfully, but these errors were encountered: