I have six FA20RF smoke detectors, initially set them up as one single group. It seemed wise at the time, but the downside is that once the alarm goes off, you have no idea which of the detectors first started beeping. So I want to de-couple them and add them to Domoticz one by one. Via a notification I can then quickly see which alarm has gone off.
So far, so good: first step was to remove all batteries (all 24 of them!) and leave the detectors alone for a while. Then started learning the first detector into Domoticz, works just great.
With the second detector I found out that the group is still intact: one detector triggers the second one.
How can I thoroughly clear the memory of these units? Leaving them without batteries for a week or so has not helped...

If you own the RFXtrx433 use RFXmngr to assign a unique ID to each FA20RF.
Select the Security1 - KD101 smoke detector,
Command = pair KD101
Select a random ID for each FA20RF (different from all zeroes)
Set the FA20RF in learning mode and click Transmit

b_weijenberg wrote:If you own the RFXtrx433 use RFXmngr to assign a unique ID to each FA20RF.
Select the Security1 - KD101 smoke detector,
Command = pair KD101
Select a random ID for each FA20RF (different from all zeroes)
Set the FA20RF in learning mode and click Transmit

Making progress. I found a compatible smoke detector at Conrad and looked at the instruction manual online.
This is the procedure to de-couple a detector:
1. make sure the master is on
2. on the slave, press LEARN until the LED is green
3. now press TEST for about four seconds.

The slave is now de-coupled.

Next problem. I de-coupled all five slaves, and the six all are now independent.
But only the previous master will react properly to the test button: two beeps and then quiet.
The previous slaves react to the test button by continuously beeping. There is no stopping them, taking out the 9V battery is the only way.

I am still struggling with the five slaves. I managed to remove the coupling with the master, but now all five ex-slaves respond to the test button with a permanent beeping, until the batteries are removed.
Meanwhile I have decided to use at least the master, it seems to work OK.
I want to send out a notification when the alarm goes off.
I set a notification, and I do get a mail. Not one, but one for every beep... Is there a way to limit this to one single mail? I prefer to use the standard notification setting if possible, not write a script for it.

manjh wrote:I am still struggling with the five slaves. I managed to remove the coupling with the master, but now all five ex-slaves respond to the test button with a permanent beeping, until the batteries are removed.
Meanwhile I have decided to use at least the master, it seems to work OK.
I want to send out a notification when the alarm goes off.
I set a notification, and I do get a mail. Not one, but one for every beep... Is there a way to limit this to one single mail? I prefer to use the standard notification setting if possible, not write a script for it.

Maybe i don't understand you right.
But as far as i understand you removed the coupling.
When you press the test button on 1 device it will start to sirene but never stops, while it should after a about 5 to 10 seconds.

If i'm right, replace batteries.
Had the same, have 4 of them and did a monthly test.
One alarm did siren but didn't go Off, checked the batteries and the penlites where at a point that the Alarm says batteries are okay but when it sirens the current Volt are to low.

manjh wrote:I am still struggling with the five slaves. I managed to remove the coupling with the master, but now all five ex-slaves respond to the test button with a permanent beeping, until the batteries are removed.
Meanwhile I have decided to use at least the master, it seems to work OK.
I want to send out a notification when the alarm goes off.
I set a notification, and I do get a mail. Not one, but one for every beep... Is there a way to limit this to one single mail? I prefer to use the standard notification setting if possible, not write a script for it.

Maybe i don't understand you right.
But as far as i understand you removed the coupling.
When you press the test button on 1 device it will start to sirene but never stops, while it should after a about 5 to 10 seconds.

If i'm right, replace batteries.
Had the same, have 4 of them and did a monthly test.
One alarm did siren but didn't go Off, checked the batteries and the penlites where at a point that the Alarm says batteries are okay but when it sirens the current Volt are to low.

Ah, that might be it.... considering the age of the detectors. I will try a new set tomorrow.
Is it only the penlites, or also the 9V block?

manjh wrote:I am still struggling with the five slaves. I managed to remove the coupling with the master, but now all five ex-slaves respond to the test button with a permanent beeping, until the batteries are removed.
Meanwhile I have decided to use at least the master, it seems to work OK.
I want to send out a notification when the alarm goes off.
I set a notification, and I do get a mail. Not one, but one for every beep... Is there a way to limit this to one single mail? I prefer to use the standard notification setting if possible, not write a script for it.

Maybe i don't understand you right.
But as far as i understand you removed the coupling.
When you press the test button on 1 device it will start to sirene but never stops, while it should after a about 5 to 10 seconds.

If i'm right, replace batteries.
Had the same, have 4 of them and did a monthly test.
One alarm did siren but didn't go Off, checked the batteries and the penlites where at a point that the Alarm says batteries are okay but when it sirens the current Volt are to low.

Ah, that might be it.... considering the age of the detectors. I will try a new set tomorrow.
Is it only the penlites, or also the 9V block?

Penlites.. but i replaced the 9v block also to be sure to have them al fresh and full.

Siewert308SW wrote:
Maybe i don't understand you right.
But as far as i understand you removed the coupling.
When you press the test button on 1 device it will start to sirene but never stops, while it should after a about 5 to 10 seconds.

If i'm right, replace batteries.
Had the same, have 4 of them and did a monthly test.
One alarm did siren but didn't go Off, checked the batteries and the penlites where at a point that the Alarm says batteries are okay but when it sirens the current Volt are to low.

Ah, that might be it.... considering the age of the detectors. I will try a new set tomorrow.
Is it only the penlites, or also the 9V block?

Penlites.. but i replaced the 9v block also to be sure to have them al fresh and full.

I checked the batteries with a multimeter, and they were all well below specified voltage.
So I took fresh penlites and 9V block, and retried. Same behaviour: when I press "test" it starts an ongoing series of beeps, not the two beeps that is should.
I have also opened one of the sensors, which is quite easy.
Not much on the inside, I was hoping for a "factory reset" but nothing there.
While it was open i used a vacuum cleaner to remove all dust, also from the black closed device that I suspect to be the actual sensor. Did not help.

manjh wrote:
Ah, that might be it.... considering the age of the detectors. I will try a new set tomorrow.
Is it only the penlites, or also the 9V block?

Penlites.. but i replaced the 9v block also to be sure to have them al fresh and full.

I checked the batteries with a multimeter, and they were all well below specified voltage.
So I took fresh penlites and 9V block, and retried. Same behaviour: when I press "test" it starts an ongoing series of beeps, not the two beeps that is should.
I have also opened one of the sensors, which is quite easy.
Not much on the inside, I was hoping for a "factory reset" but nothing there.
While it was open i used a vacuum cleaner to remove all dust, also from the black closed device that I suspect to be the actual sensor. Did not help.

Any more ideas anyone, before I decide to scrap these sensors?

Thats a pitty, but worth a try.
Maybe it's broken but i don't how to check that.
Goodluck.

Siewert308SW wrote:
Penlites.. but i replaced the 9v block also to be sure to have them al fresh and full.

I checked the batteries with a multimeter, and they were all well below specified voltage.
So I took fresh penlites and 9V block, and retried. Same behaviour: when I press "test" it starts an ongoing series of beeps, not the two beeps that is should.
I have also opened one of the sensors, which is quite easy.
Not much on the inside, I was hoping for a "factory reset" but nothing there.
While it was open i used a vacuum cleaner to remove all dust, also from the black closed device that I suspect to be the actual sensor. Did not help.

Any more ideas anyone, before I decide to scrap these sensors?

Thats a pitty, but worth a try.
Maybe it's broken but i don't how to check that.
Goodluck.

That's the weird thing: I have six detectors, one was master, five were slaves. I de-coupled all slaves, and now all of them show the same behaviour. Broken? Could be for one, maybe two, but all five? Too much of a coincidence...

Came across while looking for Domoticz compatible smoke sensors. Don't have specific experience on these devices.
That said i was wondering if it would be possible to pair one of the five slave sensors with one of the other ones so that it will become a master itself. After that decouple the set. Hopefully the ex-master will then work as expected, like your well-behaving original master of the group of six. If that succeeds, do the same with the other slaves.
The challenge will then be the last slave since there will no more devices left to promote it to master.

IAsDoubleYou wrote:Came across while looking for Domoticz compatible smoke sensors. Don't have specific experience on these devices.
That said i was wondering if it would be possible to pair one of the five slave sensors with one of the other ones so that it will become a master itself. After that decouple the set. Hopefully the ex-master will then work as expected, like your well-behaving original master of the group of six. If that succeeds, do the same with the other slaves.
The challenge will then be the last slave since there will no more devices left to promote it to master.

A question from a starter about connecting a smoke detector to the RPI,
I have 3 compatible smoke detectors, but no RFLink or RFxcom but a superheterodyne 3400 wireless receiver, is it then also possible to connect the smoke detectors or not?? I can't see them, but a friend with a RFxcom sees them. Is it just a question of installing some files or must I buy a RFlink (RFxcom is to expensive for me).