[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...).
1 Like
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
