-
-
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]: homekit devices with wait for setup
not persistent across node-red restart/redeploy
#459
Comments
I was able to get the same behavior without a subflow involved or the need for mqtt. This adds 2 service nodes + 4 inject nodes with a startup set to 5 and 6 to setup 2 bulbs. If you deploy this flow they show up under default room, now move them to a different room and and restart node-red or redeploy the flow. The nodes disappear and reappear a few seconds later in the Default Room.
|
wait for setup
not persistent across node-red restart/redeploy
I also tested with service2, same result. I'm not 100% sure but I think on restart, for all node with wait for setup it removes them from the bridge, making homekit forget about them, even if they get setup again later with the same info. (perhaps with a different version, but name/serial is always the same) |
Thanks for example, I will try to look at it soon. |
Were you able to replicate this? |
I think we might be able to close it. If I use a bridge with only services that have If this is by design (I think it might be) we can close this, although perhaps that should be more clearly documented. |
OK so I figured it out and there may be some room for improvement.
So the thing seems to be once a service is published, the other services waiting for setup are 'forgotten' and once they do get there setup payload they appear as a new service for homekit. Seems to be a problem with a large amount of services. The trick is to only use Some improvements that could be made:
|
NRCHKB Plugin Version
1.4.3
Node JS Version
16.13.0
NPM Version
8.1.0
Node-RED Version
2.1.3
Operating System
OmniOS Bloody (updated 2 days ago)
What happened?
I saw that #393 landed a while ago so I wanted to simplify my setup a lot by embedding the homekit node inside a subflow.
This seemed to work at first glance but on redeploy all the devices in homekit end up in the default room again and dissapear from all automation and scenes that had included then.
Because the service node is inside the subflow, I am sending it a setup payload to configure it. My initial assumption was I was sending different setup payloads but on closer inspection this was not the case:
deploy 1
deploy 2
deploy 3
So I'm not really sure if I am doing something wrong or if there is a bug somewhere.
How to reproduce?
Attached is a flow.json, this includes my subflow, and one instance of it.
You might need to edit the IIEEE/groupid of the instance and hook it up to mqtt, in my case I am talking to zigbee2mqtt and also fetch generate the setup payload from the data.
flows.json.txt
Expected behavior:
The node to be persistent across deploys/node-red restarts if I feed it the same setup data.
Additional comments?
Additional comments here, if any.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: