FA21RF smoke detector not beeing detected

leader21

Hey guys!
Having a FA21RF smoke detector that is not being detected by alarm1 or alarm2 protocol
Has somebody an idea of how to improve the alarm protocols?

debug [pimatic-homeduino]: received: [ 800, 1400, 2736, 9552 ] 002010101020202010201010102020202020202020202010203
debug [pimatic-homeduino]: data: "RF receive 800 2736 1400 9552 0 0 0 0 001020202010101020102020201010101010101010101020103"

mwittig

@leader21 said in FA21RF smoke detector not beeing detected:

Has somebody an idea of how to improve the alarm protocols

Looks much different from the existing protocols.

header pulses 00 vs. 30 with alarm1 and alarm2
footer pulses 03 vs. 04 with alarm1 and alarm2
one pulse less compared to alarm1
pulse lengths differ

Apart from this the encoding seems to be the same as I managed to get a tweaked datagram processed by the test suite. So, it looks like we need an “alarm3” variant.
Is it a new device you have bought recently? What happens if you push the learn button?

leader21

yes,i bought it on monday in a bunch of 3 packages from amazon, 2 pcs. for 20 Euro, a very good deal!
The protocols of the detectors were mixed up.There are 3 with alarm2 protocol and 2 with alarm1 protocol - and the one that does not match any of those what i was talking of above.

pairing with the other detectors works.
when pressing the learn button nothing happens on the debug messages. it’s just for initiating the learn mode for master / slave

All product numbers and PCB part no. are the same on all 6 devices
PN is FA21RF - 001CPR, PO 4500176689
They were all built in 2016

leader21

Got it to work

@mwittig we don’t need another protocol!

i got it to work the following way - first i tried to pair the device with a master detecor like i said above, which worked.

then i reset the device (take batteries out, press test button to get all power out of the device, put batteries in, press learn button - led is green, press and hold test button until the id shows up in the debug messages).

with the reset, the device got a new id and shows up as alarm1 now.
i also reset all other devices and they got new id’s too. so i guess this is a way to get a detector to work that does not match the protocol.
just do a reset.

the reset procedure is not found in the manual, i needed to search a bit.
maybe this helps other users too…