my turn to get a false alarm from Fibaro smoke sensor

[goran 9]

Today when I woke up I had several emails telling me that one of my smoke sensors (not the same one with temperature crazyness I reported yesterday) has been in breached mode for about 6 hours. Luckilly there was no actual smoke. And no auccustic or visual alarm. The "Last Breach" value in HC2 confirms the breach, as it has the same timestamp as when the emails started coming (the email monitoring system checks the device's "value", which was changed from 0 to 1 in this case). The event panel however, shows absolutely no sign of any smoke sensor having been breached.

I am so close to throwing this entire system out the window. I am so tired of all the bugs. Most of them I can live with and wait for a future release to fix. But some of them are extremely serious. I guess the usual excuse about "this is a problem with zwave and not HC2" will be used here again. "Wait for the next stable version" is NOT an acceptable answer. The priorities should be to put other features on hold while developing and RELEASING a patch for this. Or rather, it should have been a long long time ago when users started experiencing these problems. When you can't even trust the smoke sensors in your home it's not a joke anymore.

[ Added: 2014-08-23, 09:19 ]

For what it's worth, pressing and holding the B button to manually generate a breach works as expected, I get the alarm noise, the breach value is changed and it will all show up in the event panel.

[Dalle1985 16]

Check the base plate of your smoke sensor. Sounds like you are experiencing the same issue i did. As the hc2doesn't distiguish between a smoke detection and the tamper switch being activated, you can't see the difference. The device itself however does distinguish between the two, so it won't sound the siren, but it will trigger a breach if the tamper switch is activated. For me, it turned out that due to me fixing the base plate to the ceiling with screws, I slightly buckled the base plate, so the switch was only partly depressed. So vibration, temperature expansion or whatever, meant that sometimes it suddenly just tripped the alarm for no apparent reason and I have secondary sirens, so i noticed straight away!

I fixed it by turning the smoke detector slightly compared to the baseplate and that seems to have fixed that issue - haven't had the alarm for a month now!

[goran 9]

Thanks for the reply, it sounds like a logical explanation.

However... Parameter 89 (tamper alarm) is set to "tamper alarm inactive".

[ Added: 2014-08-25, 07:59 ]

Another false breach today, this time on a flood sensor. It stayed breached for about an hour. No entry in the event log but "Last breached" value has been updated. Parameter 74 is set to Tamper alarms disabled.