No updates on iOS's Home app after flow change

[TroLoos]

Hi, it seems like after several (2-3 times) changes to any flow containing a HomeKit device, iOS's Home app stops receiving updates coming from the bridge. Status changes are reflected in NodeRed GUI, but they do not show up on my phone anymore. Should I be more patient and wait for it to update itself?

Right now only re-adding a bridge on iOS helps instantly. But I have to re-assign all the devices to their respective rooms from scratch...

I was looking into eventually moving all my devices from Homebridge to NodeRed. But with this kind of issue it is rather not possible.

[Shaquu]

Hi, thanks for using our plugin. First of all, have you tried following this #118

Another thing. It would be good if you provide some informations:

• node-red version
• node-red-contrib-homekit-bridged version

[TroLoos]

Sure, my node-red version is 1.0.2, and node-red-contrib-homekit-bridged version is 0.8.0.

It seems like what I described may be connected to the bug you mentioned. But there's no cure at the table right now. I can always re-add all the accesorries to my Home.app but it is a pain in the ass to be hones, having a lot of them it's quite some work...

[radokristof]

Restarting the node-red service does not help on this? This is a known bug.

[industrialinternet]

I have I think, a related issue with NR 1.0.2, and node-red-contrib-homekit-bridged 0.8.0. No MSG output from node after first deploy from a NR re-start The node.status works though from Homekit (HK) but HK accessory doesn't update from COS of node input.

[Shaquu]

In next week I am back home and I will investigate.

[lukaskorl]

Hi, I'm experiencing the same issue as @industrialinternet described. homekit-service node does not update HK accessory on input. And no message is sent when change is triggered via Home App. Haven't found a reliable way to reproduce it. Most likely it happens after restarting and redeploying NR.

Tested with NR v1.0.2 with node-red-contrib-homekit-bridged 0.8.0. I've also tried pulling node-red-contrib-homekit-bridged from dev branch (currently at 1.0.0-dev.1) but the problem persists. Let me know how I can help.

[markus-fischbacher]

Hi there, I'm facing the same problem. External changes sent to the HK accessory (in my case done by MQTT) is reflected on the default HK output. Changes within the Home App are not sent to the default HK output. After a NR restart it's working again. Doing some wiring and deployment is breaking the system. Unfortunately I've not been able to reproduce it right now.

[Shaquu]

For now I can only recommend to wait for another release which might fix some problems with reliability. Or you can try dev version if you want to test it earlier.

[radokristof]

I think I also have this issue. I don't know what changed. Some accessories are working, some are not. I think nothing got updated related to Node-RED/npm, maybe an iOS update caused this? I'm not sure. I have multiple bridges, but some devices works right on both bridges, some are not. Restarting Node-RED only helps for a few hours I think, without even touching Node-RED it has this issue. @Shaquu do you any idea what can cause this?

Sometimes it just shows 'Updating...', sometimes it reflects the actual state, but toggling the accessory from HomeKit takes for ever... Also when in Updating state, getting the current state also takes forever...

Updating to dev version means that I need to re-add the bridges right?

[mriksman]

I'm new to this contrib. Is it normal that if I add ANY new service I have to RESTART Node-RED?? I would have thought once you add a Node, configure the Service, and then click Deploy, it would appear in Home. Same with deleting a Node.

[Shaquu]

@mriksman we at the stage where we have a big and we wait for some more checks to make a new release. So it’s not normal but can appear.

[crxporter]

@Shaquu I believe these things should be fixed up with 1.0+ releases.

[sanderdatema]

I wonder if this problem is still there or if it has returned... When restarting the flows, the iOS app doesn't get any updates. As soon as I trigger the light on the app, updates will be processed after that and all is well. But it's a bit silly to have to touch all lights after every restart.

[crxporter]

@sanderdatema this doesn't seem like my experience at all. When I restart nodered everything comes back quickly and without problems - but reset to the default state. The default state issue is separate, that will come with persistence.

Most of my stuff is zwave lights over mqtt. The mqtt state messages are retained so when I restart nodered it receives the state message of everything. I've never had to click through my lights, cameras, or other things to get things to refresh after deploy or restart.

Which version of everything are you on? Node version: Nodered version: Homekit plugin version:

[sanderdatema]

Which version of everything are you on? Node version: 10.12.1 Nodered version: 1.2.2 Homekit plugin version: 1.2.0

And I use the latest nrchkb/node-red-homekit docker container.

[Shaquu]

@sanderdatema As docker got involved. What is your OS running docker?

[sanderdatema]

@Shaquu Ubuntu 20.04.1 LTS (kernel 5.4.0-52-generic)

[Shaquu]

@sanderdatema Cool. Can you share you flow? It might be your flow not updating state after restart. Have in mind that currently our plugin is not preserving last state.

[Shaquu]

@sanderdatema if you still have problem then feel free to open Discussion