[edi]t this isn't working out in practice so just ignore it
This is my current solution
Wont' that result in the light turning on for 2 sec then turning off?
Sam, do you have any thoughts on why I'm having this problem, as seems that others have managed to get further than this ?
No, the false is only sent back to the single node -by using the 2nd output option
[edi]t this isn't working out in practice so just ignore it
But doesn't that false then toggle the matter lights state resulting in a new "false" being sent out or do you have passthorugh off?
That looks like the same issue Simon was having (mdns failure) which I think was fixed by turning off IPv6 for the newtwork interface in the desktop settings.
as Ben might be stopping support for his nodes in the future
They are not going anywhere in the short/medium term, but it would be nice to not be subsidising it for the long term (I am getting closer to having the costs covered, at ~50% so far...).
Yep! Matter doesn't yet have a doorbell device yet (which announces "There's someone at your front door" etc), so as a workaround I've used AI to create the sentences, downloaded them as mp3 files and served them as static files.
Then used node-red-contrib-cast to cast the mp3's to my Google/Nest speakers.
There is the generic button device type in matter which can then be used to trigger an automation on Alexa or Apple to play an announcement via text to speech on your devices.
Although at the moment I donât think Google supports the generic button device type
Wow, NICE. its working like a charm with google Nest Hubs
one question, possible to add TEMP/HUM (combined) sensos ??
google home now i have in one sensor Termp/Hum/ CO2 in one sensor from SmarNora
wil be realy nice to have this in matter, then i can switch completely from smartnora to matter 
also on thermostat device i have Temp/Hum
and one selector im missing then i can switch over to matter
i can test also (have much devices ) for now im using Light switches and dimmers (23x)
on dimmer, if you dimm to 0 GH says OFF, gives an error (so put the slider to 0) then it gives an error and no action wil be triggered
for the rest all dimmers working fine, (dimming and switch on / off )
but this project is really NICE THANK YOU
Split the temperature & humidity sensor outputs and feed them into the respective matter nodes
Oh my lord! I see that Matter - that supposedly "easy" to use home automation "standard" - not quite standard yet!
The cynic in me is saying that Google and Amazon in particular don't really have much incentive to make things interoperable. Also saw a review recently about the low-cost Ikea Matter devices - great when they work I think was the summary, and probably not really Ikea's fault.
I'll stick to Wi-Fi and Zigbee for a bit longer I think. Home automation gets complex enough without having to fight the protocols.
I use zigbee, Tuya wifi & rtl433 devices but I have them all connected to both Google & Amazon. All devices, apart from the Tuya devices, go through Node-RED and the node-red-matter-bridge (the Tuya devices have to go via SmartLife - and in Node-RED via the tuya-smart-device node).
This has been working well since the last update to these nodes some 10 months ago.
There have been updates to Node-RED, the Pi OS and a change of Pi during this time and it all still works. (fingers crossed now !!!)
But i dont want sepeeate sensors
I have 20 Temp/hum Sensors
If i split them i have 40 devices in GH
Googl can also provide more information on one device like co2 (temp/hum/co2)
I have also devices they can do that
If i split all do seperate device then i wil have more then 100 devices in GH
Thats why im asked to have Temp/hum/co2 possibility in Temp Sensors (Google)
Also my Thermostat provides Humidity, and that will be also nice to have it in Thermostat device and not seperate in GH.
Now i have only one device, if i Split all i have 3 in GH and this x20 ???
The issue is that within the matter spec, Temp, Humidity and Co2 are all separate device clusters,
It is possible to create whats called a composed device in matter where you have multiple clusters all under one device but this is not exposed in the Node-RED Matter Bridge at the moment, Mainly because the UX of creating multiple nodes that are somehow associated with each other as a composed device is complicated!
Where physical devices are shipped and they have a fixed list of device clusters like your combined sensors this is a lot easier as those decisions are made at the manufacturer.
If anyones got any good ideas for how to combine multiple nodes in node-red to create a comboned device then feel free to suggest something or better still send a PR,
I don't have a huge amount of capacity to work on the matter stuff at the moment, maybe that will change in a few months
