Okay so let's write this down to think it though.

The latest smoke detector to howl pointlessly into the night sends out 11.3V DC onto the signal pin when triggered but running off batteries. I suspect that's 12V nominal, and it probably delivers 12V when operating on AC power.

Most importantly, it's not like... 500mv. Or AC. Or complicated. It's simple DC.

When acting as a non-reporting _satellite_ node, it triggers when _receiving_ 4V DC on the signal pin (4.0 exactly), and that voltage is polarity sensitive. -4V doesn't trigger the alarm.

(1/n)

#electronics #SmokeDetectors #why

Checking for DC on the signal line, I get functionally nothing. 20ma DC at most, and even that's something I'm picking up out of noise floor shift rather than direct measurement.

My _thought_ was that if the signal line was somehow floating in whole number volts (for whatever reason) than maybe somehow the right RF noise could kick it over.

The problem with _that_ is that I can now _also_ confirm that non-detecting units go off _exactly as long_ as a detecting device keeps saying it's detecting by putting voltage on the signal line. If that voltage goes away, so do the satellite alarms - and immediately.

And that's not what happens. We have to manually intervene and shut the alarms off ourselves.

(2/n)

#electronics #SmokeDetectors #why

The reason I paid meaningfully more than baseline for this particular set is that they report exactly which detector went off and why. That way, if it were the signal line somehow triggering the alarms, none of them would claim to be the originating unit; they'd all report it came from the signal backbone.

But they don't. There's always a unit claiming to be the active detector and it's always smoke (and there is *never* actually smoke), and none of them shut up until we shut off that unit, which sometimes seems to require removing it from power.

So today's afternoon check was basically just another way of confirming what we already knew, and I guess I've done that now, but...

(3/n)

#electronics #SmokeDetectors #why

All _that_ does is get us right back to where we started, which is, "we have alarm after alarm after alarm of different makes, methods (ionisation, photodetector), and models which just in this house are determined to go off randomly, usually but not always at night, for absolutely no detectable fucking reason, and then pass self-test just fine afterwards."

And no, regular cleaning - even weekly cleaning - does not help. I do _all the things_. None of it stops the problem.

(4/?)

#electronics #SmokeDetectors #why

If you're new to this adventure, I have heard this exact same story from _many other people_ at this point - though nobody I've talked to has said they've literally taken metres to the signal wires to verify that way.

Regardless, I know it is not just us.

What I've been told from others who deal with this is to RMA individual units that trigger randomly one at a time until you end up with a set that doesn't. And I guess that's what I'm gonna do, but

holy shit, team

holy shit

(5/6)

#electronics #SmokeDetectors #why

this is the opposite of fire safety

this is the opposite of how anything like this should ever work, I mean

what if all the RMAs are getting you are a set that won't go off even when they should?

but whelp

guess i'm gonna find out

'cause this sure ain't workin'.

(6/6 fin)

#electronics #SmokeDetectors #why

Well, the good news is that _unlike_ the makers of the previous smoke detectors we've had who refused to honour their warranties, BRK/FirstAlert gave absolutely no pushback on this. They don't even want the original unit mailed back, they told me I could just toss it out.

(Since it's optical, I can recycle it cleanly.)

#SmokeDetectors

@moira It sounds like your alarms are actually alarming, as if they sensed fire, at night.

There's this info about marginal battery power and colder temps leading to low battery chirping at night.

https://www.kidde.com/support/smoke-alarms/nighttime-alarm-chirps

Could something like that be involved?

I also have had problems with false alarms from a variety of units, models, technologies, and brands. I'd love to have a better solution than the one you outlined.

1/

Why Do Smoke Alarms Always Chirp in the Middle of the Night?

@moira I have stopped buying networked devices that need every device individually silenced and devices that take wired rather than battery power. These are both aimed at making it simpler to find the source of the false alarm and silence it.

I know that having alarms that don't trigger every alarm when one senses fire is slightly more dangerous, but the usability trade-off is terrible.

2/

@david42 Yes, as per thread, one specific unit always reports having detected actual smoke. Not chirping, full alarm, due to smoke detection. Also, I check batteries, and it is _not_ a battery issue regardless.

(Curiously, they never report having detected carbon monoxide.)

Also the reporting unit is not difficult to find as it announces itself, and when between announcements, flashes a reasonably visible red LED. You do have to get close enough to see it, but the offender is reasonably clear.

As for here, networked is a code requirement and we also get an insurance discount for networked alarms.