Thanks leoXie. Every product has problems, the difference is where a company is willing to fix them!
So far, after a Matter ping, the device has been stable. I’m happy to give different firmware a try if you can tell me how to install it. I upgraded 1.0 to 1.6 because the Matter integration offered me the firmware. If this is a beta, I’m assuming that it won’t be as simple.
Thanks, that’s very kind of you, I am running two setups for myself, it’s stable for me, but seems there are unforeseen circumstances, let me try to reproduce it and manage to fix it.
Yesterday, I had again a sensor that became unavailable for 16 minutes. It reconnected automatically. The other sensor stayed connected. Other matter devices did not drop from the network.
I am interested in this product but I have some questions before buying.i hope this is the correct thread and someone is willing to answer:
firmware updates are automatically?
If I use custom firmware 4.x, also firmware updates automatically?
What are the benefits of firmware 4.x?
Can I trigger the alarm only with 4.x or also with 1.x?
And the most important part. I have now old aqara smoke detectors. They are grouped. So if one is alerting, all others alerts also. Is this possible with this product? And if yes, how can I connect all smoke detectors? I use all systems in parallel (HA, Alexa, google home and also HomeKit)
I can’t give you all the answers to that Patrick…but I can start you off.
Home Assistant offered me a firmware update (from 1.0 to 1.6) through Matter and I could choose to apply it like any other update.
There’s talk of adding the 4.x firmware’s siren function into the mainline firmware. Currently I’m only testing stuff…for a move to a house that’s just been pulled from under me…but that’s another whinge For linking I’ve got an automation to trigger a test (and send a mobile notificaiont) on other alarms so it’s sort of possible. I’ve also got an automation to notify on problems such as the device going unavailable or low battery. A direct link from one alarm to another would be preferable but I don’t know if Thread/Matter can do this.
Thx a lot. According grouping, I found Amazon recession with mentioned such a feature at 4.1. but not explained more there. So it would be interesting if it really works. But what I found out, a downgrade is not possible from 4.x to 1.x. So I can’t ask you to update to 4.2 and tell we what you see and what are the differences
I've updated my one. It's worth saying that it took a while to upload the firmware - which is the low bandwidth of Thread - but the "Installing..." phase, which has no progress indication, took about 5 minutes. After that it seems to be working fine but even after a "Re-interview Device" through Matter, it isn't offering a siren feature. I have self test and identify still, but no siren. Both these work but there can be a five second or so delay presumably as the device is sleeping a lot of the time.
It's also worth stating that my device has not dropped off the network in the last 24 days.
I'll report any connectivity problems with the new firmware if they happen.
I had mine right next to the border router and it did take a good 5 minutes to come back up. Moved it back to where it's supposed to be after and did the tests there. Was worried it wasn't going to come back up for a while though.
Thanks for the feedback,
I am wondering is there any AC-Powered MoT devices in your setup? how far is the smoke alarms between your OTBR? which OTBR are you using? (HomePod only or multilp OTBRs there?)
Hi leoXie. I don't have the option to mute but I do have a status of whether it is muted or not.
I understand about the siren feature now. It needs changes to the Matter server as well as the firmware. I think I'll wait until those get merged; I'm not in a hurry.
Out of interest, is a self-test quieter than a full alarm?
Hi Gareth,
if you update it to v4.3 and HAOS 2026.5, you should able to see the mute right away, but of course you can use v1.7 if you don't use remote mute for the moment.
Regarding the level of sound, yes, nice catch, that won't scare users at first pattern, but if you keep pressing it, the sound will get louder and louder till reaches its maximum.
I'm already running 2026.5 but as you say, it isn't a function I'm using yet. It will be a nice-to-have feature though.
It might be worth stating on the instructions that a self-test is not as loud as a full alarm. It's nice to be quieter for a test so you don't deafen yourself but unless you know the proper alarm will be louder, you might think it isn't loud enough to wake people through closed doors.
For linking I’ve got an automation to trigger a test (and send a mobile notificaiont) on other alarms so it’s sort of possible. I’ve also got an automation to notify on problems such as the device going unavailable or low battery. A direct link from one alarm to another would be preferable but I don’t know if Thread/Matter can do this.
