Have pushed a new update just now with some pretty major refactoring, couple of minor improvements and a general overhaul so this should make things easier and more stable for people.
More details in the changelog node-red-matter-bridge/CHANGELOG.md at main · sammachin/node-red-matter-bridge · GitHub
5 Likes
Just tested latest version 
It works with Apple Home ! (just checked some virtual lights yet .. but detection in Apple home works seamless)
I'm running latest NR on ubuntu docker
I found an issue in my own home setup last night that wasn't apparent in testing.
The new restart logic means that devices will loose their room assignment and any automations linked to them in your controller. (because the node is removed and re-created)
if this is an important feature for you I suggest not updating yet!
Hi, as mentioned above I'm currently testing with your simple On-OFF Light example and it looks working fine
FYI, I have now seen below logging in my NR (running in docker).. when doing a full deploy
Maybe it helps 
That looks correct to me, if you disable nodes or flows it will now skip them cleanly.
This issue is actually related to a different bit of the code that allows partial restarts of node-red with only the changed nodes but now those devices are removed from the matter bridge and then re-added. Or on a full deploy all nodes are removed and re-added
fixed in 0.11.1 just published.
Also improved the passthrough logic
Just updated to version 0.11.1
Now comes this error:
ReferenceError: willUpdate is not defined
I use socket.
Sorry my bad, missing an import Will get a fix out in 0.11.2 ASAP
0.11.2 published
2 Likes
Alles ok now
2 Likes
My OH asked me to change some of the voice commands, so I thought that if I changed the node name, it would sync google accordingly, but it appears not.
Google Home retained the original names, whilst my nodes had the new names.
I tried rebooting, but the only way I could sync them was to delete the config, and then create a new one, which then synced the new names.
Is there an easier way?
Yeah that’s a bit ecosystem specific so it will update the node name in matter but whether the actual controller picks up that change is variable
It appears that the response name can be changed within Google Home to something completely different.
The node name is 'front garden', yet the voice command responds to 'driveway'.
0.11.3 published with a new feature or two
2 Likes
