-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
[Bug]: Changing the name of a service removes it from Homekit #358
Comments
Interesting, thanks.... however, somehow Philips Hue allows changing the accessory name and it doesn't break the automations. Any ideas? Also, I wonder why the |
It's why I used Accessory word :) |
Thinking about this some more - I suppose this would allow Node Red/Homekit bridge portability between hardware installations? For example, if I need to re-install node red & the HomeKit bridge on a new system and importing my existing config (something I'm considering, since I started my Node Red journey on a Raspberry Pi with Home Assistant, but I'm now realising I don't need Home Assistant, only Node Red). I presume that when this feature is implemented, then Homekit would in future recognise the devices as the same ones, and existing automations would continue to operate? Is this a goal of the project? |
@lougreenwood being native HomeKit as much as possible is our goal. |
|
Consolidating issues, please continue at #231 - it's pretty much the same thing |
Describe the bug
When changing the name of a service (e.g a switch) in Node Red, the corresponding device in Homekit is destroyed and a new one is created.
This means that any automations in Homekit which make use of the device/service which just had it's name changed are now broken.
To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
Changing the name of a service in Node Red should not cause side effects in Homekit
The text was updated successfully, but these errors were encountered: