The wonderful thing about standards, is there are so many to choose from (obigitory XKCD reference: https://xkcd.com/927/)!
UK building regulations Document B references BS 5839-6:2004 (no reference as the BS standards cost money), but state:
1.14 Where more than one alarm is installed they should be linked so that the detection of smoke or heat by one unit operates the alarm signal in all of them. The manufacturers’ instructions about the maximum number of units that can be linked should be observed.
My understanding was that there is no means of getting a FGSD-002 to sound an alarm remotely (must read Chris’s Z-Wave doc and the XML to check), so although the sensing element of each device may well meet EN14604 specifications, they can’t work as a system of multiple interlinked devices.
This first came up with someone wishing to use the detector as a siren (e.g. for intruders or doorbell), but the same problem is referenced in several places including Vesternet:
Not Interlinked - cannot be triggered by other Z-Wave devices, cannot act as a group.
As my two devices are still in the box I can’t confirm the issue however, this would seem to be a pretty fundamental design error.
The sensor sends an Alarm Broadcast SMOKE ALARM to all Z-Wave devices in range. Why would another identical sensor be designed not to act on this broadcast, when even a Fibaro light dimmer can (FGD-212 parameter 42 sets flashing lights)?
My guess is the wake-up interval of Z-Wave battery devices is too long to reliably give fast alarm broadcast (always on), and long battery life (always off). Fibaro’s insistence that firmware updates are only available via their own Home Centre controller means a change is not going to improve my kit.
And, no, even though my OpenHAB controller is on a UPS, I don’t want to rely on it being active and connected to the Internet to send an alert email. Autonomous resilient systems capable of independent action, but linked for extra benefit are better IMHO.
Interestingly, the manual does mention parameters for control frames (10 - 2nd Association Group
SMOKE ALARM), and alarm broadcast (13 - Alarm broadcast, mentions several Association Groups) suggesting there are settings to experiment with.
Has anyone actually tested >1 FGSD-002 paired with OpenHAB to test Alarm Broadcast between devices please?
Do you know if there a way to generate an Alarm Broadcast SMOKE ALARM from a script? (interesting for testing, though likely to kill battery life if used regularly).
I have enough issues trying to get a FGK-101 to report a tamper alarm (reports as a ‘alarm_smoke’ channel), but haven’t yet upgraded from Release 2.2 to snapshot 2.4 and enabled secure inclusion to give decent quality feedback to Chris’s Device Database.