-
Notifications
You must be signed in to change notification settings - Fork 25
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
[Feature]: Allow label to be prepended to names for uniqueness #436
Comments
I should add that I can't change the actual names of the devices, as these are used in the HA UI, so generating unique names with a label prefix would allow for that. |
Matter in general allows just 32 characters for device names. When adding the label as a prefix, you'll have cut the names quite quickly. In general, i dont really get the use case. Let's simplify:
Do they all use the same amazon account? |
Yes different Amazon accounts, but because the add-on can only have one hub on port 5540 to support all of them, I was hoping to use un-utterable naming to get all devices for all holiday lets and our home. (They are all on the same WiFi network and HA instance) |
'un-utterable' because then they can't be called up by accident, and the guests have no knowledge of their existence, only the ones they can use ie. 'lounge lights' group etc. |
Could IPv6 be used to create 2 port 5540's on the same network somehow? (I haven't read up on IPv6 much) |
(There is a guest network but it's all isolated so guests can't see each others connections, so I use a private network for the Alexa's, and Matter bulbs etc). |
Alternatively, if the name length is limited, could we have a way to rename the devices exposed? OR, even better, a checkbox to automatically give them all un-utterable generated names? (Like 'Potting Shed bathroom lights' becomes for example P0tt1ng 5hed b@thr00m l1ght5 ) |
I've never tested it, but i've heard that it could actually work to create a bridge on port 5540, pair it with Alexa and then change the port. This seems somehow to allow Alexa to connect to non-5540 ports. I'll give it a try this weekend, but if you cannot wait, you could give it a try, too. In general I'd suggest using different bridges for your use case - if the port change is actually working. Otherwise you could rename the devices in the Alexa app itself. |
Just tried it and it didn't work for me (port changes).
The problem is that I have a lot of devices and holiday lets, so that means a lot of admin renaming everything. |
Requested feature
When using a label to filter devices to expose, it would be nice to have a checkbox to prepend the label name to the device. This makes them unique in Alexa, so they don't clash, and also eases admin in the Alexa app where I want to make these device names 'un-utterable' to Alexa, and put them in rooms/groups with utterable names (for different holiday lets for example, so the guest can't turn the lights in the other holiday let on/off by accident! This is important as we can only have a single Alexa hub on 5540, so it might contain lights for different properties, and admin can be a headache, hence the un-utterable names initially. Hope that makes sense!
Documentation & Issues
The text was updated successfully, but these errors were encountered: