Rule with the Fibaro Smoke Sensor

roher · November 2, 2015, 11:36am

Hello!
@James_Huang, have you tested your configuration since your last post? Did you manage to create a configuration that will correctly react on Smoke Alarm and Excess Temperature Alarm?

I have recently bought three Fibaro Smoke Sensors (Model FGSD-002) and have nearly the same problems.
I have configured my sensor in the following way:

Node1 (the controller) is in Association Group 4 (SENSOR_ALARM notification group according to the doc).
And here is the items configuration:



Contact Smoke_Sensor_Bedroom “Smoke sensor bedroom: [MAP(sensor.map):%s]” (Bedroom, All_Sensors) {zwave=“45:command=sensor_alarm,alarm_type=1”}

Contact Overheat_Sensor_Bedroom “Overheat sensor bedroom: [MAP(sensor.map):%s]” (Bedroom, All_Sensors) {zwave=“45:command=sensor_alarm,alarm_type=4”}

Number Temperature_Bedroom “Temperature Bedroom: [%.1f °C]” (Bedroom, All_Sensors) {zwave=“45:command=sensor_multilevel,sensor_type=1”}

And here’s what I get in result:

Temperature_Bedroom is being read correctly, so it’s ok.
When the temperature falls below 10C (param #30), excess temperature alarm is being triggered (a blue light is lit on, a beep is made), but Overheat_Sensor_Bedroom or Smoke_Sensor_Bedroom don’t become OPEN, and here’s what do I see in the log:
18:50:34.048 [DEBUG] [eController$ZWaveReceiveThread:1528 ] - Receive Message = 01 0F 00 04 00 2D 09 71 05 00 00 00 FF 04 02 00 5D 18:50:34.049 [DEBUG] [b.z.i.protocol.ZWaveController:1210 ] - Receive queue TAKE: Length=0 18:50:34.050 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ] - Assembled message buffer = 01 0F 00 04 00 2D 09 71 05 00 00 00 FF 04 02 00 5D 18:50:34.050 [DEBUG] [b.z.i.protocol.ZWaveController:1211 ] - Process Message = 01 0F 00 04 00 2D 09 71 05 00 00 00 FF 04 02 00 5D 18:50:34.050 [DEBUG] [b.z.i.protocol.ZWaveController:190 ] - Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 2D 09 71 05 00 00 00 FF 04 02 00 18:50:34.051 [DEBUG] [ApplicationCommandMessageClass:38 ] - NODE 45: Application Command Request (ALIVE:DONE) 18:50:34.051 [DEBUG] [ApplicationCommandMessageClass:56 ] - NODE 45: Incoming command class ALARM 18:50:34.051 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:82 ] - NODE 45: Received Alarm Request 18:50:34.051 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:94 ] - NODE 45: Alarm report - Value = 0 18:50:34.051 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:112 ] - NODE 45: Alarm Type = General (0) 18:50:34.051 [DEBUG] [b.z.i.protocol.ZWaveController:682 ] - Notifying event listeners: ZWaveAlarmValueEvent 18:50:34.052 [DEBUG] [.z.internal.ZWaveActiveBinding:433 ] - ZwaveIncomingEvent 18:50:34.052 [DEBUG] [.z.internal.ZWaveActiveBinding:450 ] - NODE 45: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0 18:50:34.052 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:63 ] - Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 2D 02 84 08 18:50:34.052 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:64 ] - Recv message Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 2D 09 71 05 00 00 00 FF 04 02 00 18:50:34.053 [DEBUG] [eController$ZWaveReceiveThread:1452 ] - Receive queue ADD: Length=0 18:50:34.053 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:65 ] - Checking transaction complete: class=ApplicationCommandHandler, expected=SendData, cancelled=false
So, the rule is not triggered, because Alarm Type is General, not Heat as required, and (which is much more important than Alarm Type) it’s value is 0, that means CLOSED, not OPEN.
When I hold the button for 10 seconds (smoke test mode), smoke alarm is being triggered (a red light is flashing, a loud beep is repeating), but again, Smoke_Sensor_Bedroom doesn’t become OPEN, and here’s what do I see in the log:
12:57:39.754 [DEBUG] [eController$ZWaveReceiveThread:1528 ] - Receive Message = 01 10 00 04 00 2D 0A 71 05 00 00 00 FF 01 00 01 02 45 12:57:39.755 [DEBUG] [b.z.i.protocol.ZWaveController:1210 ] - Receive queue TAKE: Length=0 12:57:39.755 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ] - Assembled message buffer = 01 10 00 04 00 2D 0A 71 05 00 00 00 FF 01 00 01 02 45 12:57:39.755 [DEBUG] [b.z.i.protocol.ZWaveController:1211 ] - Process Message = 01 10 00 04 00 2D 0A 71 05 00 00 00 FF 01 00 01 02 45 12:57:39.756 [DEBUG] [b.z.i.protocol.ZWaveController:190 ] - Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 2D 0A 71 05 00 00 0 0 FF 01 00 01 02 12:57:39.756 [DEBUG] [ApplicationCommandMessageClass:38 ] - NODE 45: Application Command Request (ALIVE:DONE) 12:57:39.756 [DEBUG] [ApplicationCommandMessageClass:56 ] - NODE 45: Incoming command class ALARM 12:57:39.756 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:82 ] - NODE 45: Received Alarm Request 12:57:39.757 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:94 ] - NODE 45: Alarm report - Value = 0 12:57:39.757 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:112 ] - NODE 45: Alarm Type = General (0) 12:57:39.757 [DEBUG] [b.z.i.protocol.ZWaveController:682 ] - Notifying event listeners: ZWaveAlarmValueEvent 12:57:39.757 [DEBUG] [eController$ZWaveReceiveThread:1452 ] - Receive queue ADD: Length=0 12:57:39.757 [DEBUG] [.z.internal.ZWaveActiveBinding:433 ] - ZwaveIncomingEvent 12:57:39.758 [DEBUG] [.z.internal.ZWaveActiveBinding:450 ] - NODE 45: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0 12:57:39.758 [DEBUG] [ApplicationCommandMessageClass:85 ] - Transaction not completed: node address inconsistent. 12:57:39.822 [DEBUG] [eController$ZWaveReceiveThread:1528 ] - Receive Message = 01 0D 00 04 08 2D 07 9C 02 2D 01 00 00 00 66 12:57:39.822 [DEBUG] [eController$ZWaveReceiveThread:1452 ] - Receive queue ADD: Length=1 12:57:39.823 [DEBUG] [b.z.i.protocol.ZWaveController:1210 ] - Receive queue TAKE: Length=0 12:57:39.823 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ] - Assembled message buffer = 01 0D 00 04 08 2D 07 9C 02 2D 01 00 00 00 66 12:57:39.823 [DEBUG] [b.z.i.protocol.ZWaveController:1211 ] - Process Message = 01 0D 00 04 08 2D 07 9C 02 2D 01 00 00 00 66 12:57:39.824 [DEBUG] [b.z.i.protocol.ZWaveController:190 ] - Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 08 2D 07 9C 02 2D 01 00 00 00 12:57:39.824 [DEBUG] [ApplicationCommandMessageClass:38 ] - NODE 45: Application Command Request (ALIVE:DONE) 12:57:39.824 [DEBUG] [ApplicationCommandMessageClass:56 ] - NODE 45: Incoming command class SENSOR_ALARM 12:57:39.824 [DEBUG] [c.ZWaveAlarmSensorCommandClass:85 ] - NODE 45: Received Sensor Alarm Request 12:57:39.824 [DEBUG] [c.ZWaveAlarmSensorCommandClass:104 ] - NODE 45: Alarm Report: Source=45, Type=Smoke(1), Value=0 12:57:39.825 [DEBUG] [b.z.i.protocol.ZWaveController:682 ] - Notifying event listeners: ZWaveAlarmSensorValueEvent 12:57:39.825 [DEBUG] [.z.internal.ZWaveActiveBinding:433 ] - ZwaveIncomingEvent 12:57:39.825 [DEBUG] [.z.internal.ZWaveActiveBinding:450 ] - NODE 45: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_ALARM, value = 0 12:57:39.829 [DEBUG] [ApplicationCommandMessageClass:85 ] - Transaction not completed: node address inconsistent. 12:57:39.834 [DEBUG] [eController$ZWaveReceiveThread:1528 ] - Receive Message = 01 0D 00 04 00 2D 07 9C 02 2D 01 00 00 00 6E 12:57:39.835 [DEBUG] [eController$ZWaveReceiveThread:1452 ] - Receive queue ADD: Length=1 12:57:39.835 [DEBUG] [b.z.i.protocol.ZWaveController:1210 ] - Receive queue TAKE: Length=0 12:57:39.835 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ] - Assembled message buffer = 01 0D 00 04 00 2D 07 9C 02 2D 01 00 00 00 6E 12:57:39.836 [DEBUG] [b.z.i.protocol.ZWaveController:1211 ] - Process Message = 01 0D 00 04 00 2D 07 9C 02 2D 01 00 00 00 6E 12:57:39.836 [DEBUG] [b.z.i.protocol.ZWaveController:190 ] - Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 2D 07 9C 02 2D 01 00 00 00 12:57:39.836 [DEBUG] [ApplicationCommandMessageClass:38 ] - NODE 45: Application Command Request (ALIVE:DONE) 12:57:39.836 [DEBUG] [ApplicationCommandMessageClass:56 ] - NODE 45: Incoming command class SENSOR_ALARM 12:57:39.837 [DEBUG] [c.ZWaveAlarmSensorCommandClass:85 ] - NODE 45: Received Sensor Alarm Request 12:57:39.837 [DEBUG] [c.ZWaveAlarmSensorCommandClass:104 ] - NODE 45: Alarm Report: Source=45, Type=Smoke(1), Value=0 12:57:39.837 [DEBUG] [b.z.i.protocol.ZWaveController:682 ] - Notifying event listeners: ZWaveAlarmSensorValueEvent 12:57:39.837 [DEBUG] [.z.internal.ZWaveActiveBinding:433 ] - ZwaveIncomingEvent 12:57:39.838 [DEBUG] [.z.internal.ZWaveActiveBinding:450 ] - NODE 45: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_ALARM, value = 0 12:57:39.838 [DEBUG] [ApplicationCommandMessageClass:85 ] - Transaction not completed: node address inconsistent.
So, again, the rule is not triggered, because the value of the event is 0, that means CLOSED, not OPEN.

Could anybody help me setting up this sensor correctly?
Thanks in advance.

roher · November 2, 2015, 1:18pm

I also assume that changing “SENSOR_ALARM” to “ALARM” in the items configuration will not help, as the value will be still 0 (so, CLOSED).

I’ve also tried to add Node1 into the 2nd Association Group of the sensor (Basic Reports), and I can see that no BASIC event at all is received when Smoke Alarm or Excess Temperature Alarm is being triggered.

roher · November 4, 2015, 10:41am

Can anybody help me?

sihui · November 4, 2015, 4:20pm

Although I don’t have this device I suggest to point the association group “device status” to Node 1, the controller.

roher · November 4, 2015, 5:48pm

Thanks for the answer!
Of course, the association group “device status” is also pointing to Node 1. It was by default, I didn’t change it.
To sum up, the controller is in three groups:
Group 1 - “device status”;
Group 2 - “BASIC alerts”;
Group 4 - “SENSOR_ALARM alerts”.

HFM · November 15, 2015, 7:19pm

@roher I have the same problems. Could you solve it?

roher · November 18, 2015, 12:53pm

No, not yet.

JjS · November 18, 2015, 3:27pm

Did you try to put the sounder into association with the sensor? This way it should go off regardsless of the openHAB, which might be better, especially in extreme cases like fire…

roher · November 18, 2015, 5:34pm

But the sensor already has a built-in siren.

mstormi · November 20, 2015, 10:29am

I am not sure if CLOSED is wrong on alarms. I don’t know the spec on this (@chris: do you ?), but
some binary sensors are ‘normally open’ while others are ‘normally closed’, and in alarm systems, a ‘closed’ contact usually means ‘alarm’.
Either way, you have to interpret the value yourself per-item in openHAB.
Can’t you trigger on ‘CLOSED’ ?

Here’s (condensed) what I get when pushing the button.
Note the 255 on ‘smoke’ and 0 on ‘heat’.

pi@pi /usr/share/openhab/configurations $ egrep -i 'NODE 54.*ALARM'  /var/log/openhab/openhab.log
2015-11-20 10:59:20.209 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass] - NODE 54: Received Alarm Request
2015-11-20 10:59:20.209 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass] - NODE 54: Alarm report - Value = 0
2015-11-20 10:59:20.210 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass] - NODE 54: Alarm Type = General (0)
2015-11-20 10:59:20.214 [DEBUG] [.z.internal.ZWaveActiveBinding] - NODE 54: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
2015-11-20 10:59:40.451 [DEBUG] [ApplicationCommandMessageClass] - NODE 54: Incoming command class SENSOR_ALARM
2015-11-20 10:59:40.452 [DEBUG] [c.ZWaveAlarmSensorCommandClass] - NODE 54: Received Sensor Alarm Request
2015-11-20 10:59:40.527 [DEBUG] [c.ZWaveAlarmSensorCommandClass] - NODE 54: Alarm Report: Source=54, Type=Smoke(1), Value=255
2015-11-20 10:59:40.543 [DEBUG] [.z.internal.ZWaveActiveBinding] - NODE 54: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_ALARM, value = 255
2015-11-20 10:59:40.635 [DEBUG] [ApplicationCommandMessageClass] - NODE 54: Incoming command class SENSOR_ALARM
2015-11-20 10:59:40.636 [DEBUG] [c.ZWaveAlarmSensorCommandClass] - NODE 54: Received Sensor Alarm Request
2015-11-20 10:59:40.637 [DEBUG] [c.ZWaveAlarmSensorCommandClass] - NODE 54: Alarm Report: Source=54, Type=Heat(4), Value=0
2015-11-20 10:59:40.652 [DEBUG] [.z.internal.ZWaveActiveBinding] - NODE 54: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_ALARM, value = 0
2015-11-20 10:59:40.701 [DEBUG] [ApplicationCommandMessageClass] - NODE 54: Incoming command class SENSOR_ALARM
2015-11-20 10:59:40.702 [DEBUG] [c.ZWaveAlarmSensorCommandClass] - NODE 54: Received Sensor Alarm Request
2015-11-20 10:59:40.703 [DEBUG] [c.ZWaveAlarmSensorCommandClass] - NODE 54: Alarm Report: Source=54, Type=Heat(4), Value=0
2015-11-20 10:59:40.706 [DEBUG] [.z.internal.ZWaveActiveBinding] - NODE 54: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_ALARM, value = 0

HFM · November 21, 2015, 4:30pm

@mstormi Ok, I do not get any other reports for alarm than ALARM commands, I mean no sensor_alarm commands.

2015-11-21 17:28:05.534 DEBUG o.o.b.z.i.p.s.ApplicationCommandMessageClass[:38]- NODE 25: Application Command Request (ALIVE:PING)
2015-11-21 17:28:05.534 DEBUG o.o.b.z.i.p.s.ApplicationCommandMessageClass[:56]- NODE 25: Incoming command class ALARM
2015-11-21 17:28:05.534 TRACE o.o.b.z.i.p.s.ApplicationCommandMessageClass[:79]- NODE 25: Found Command Class ALARM, passing to handleApplicationCommandRequest
2015-11-21 17:28:05.534 DEBUG o.o.b.z.i.p.c.ZWaveAlarmCommandClass[:82]- NODE 25: Received Alarm Request
2015-11-21 17:28:05.535 DEBUG o.o.b.z.i.p.c.ZWaveAlarmCommandClass[:94]- NODE 25: Alarm report - Value = 0
2015-11-21 17:28:05.535 DEBUG o.o.b.z.i.p.c.ZWaveAlarmCommandClass[:112]- NODE 25: Alarm Type = General (0)
2015-11-21 17:28:05.535 DEBUG o.o.b.z.i.ZWaveActiveBinding[:450]- NODE 25: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
2015-11-21 17:28:45.788 DEBUG o.o.b.z.i.p.s.ApplicationCommandMessageClass[:38]- NODE 25: Application Command Request (ALIVE:PING)
2015-11-21 17:28:45.788 DEBUG o.o.b.z.i.p.s.ApplicationCommandMessageClass[:56]- NODE 25: Incoming command class ALARM
2015-11-21 17:28:45.788 TRACE o.o.b.z.i.p.s.ApplicationCommandMessageClass[:79]- NODE 25: Found Command Class ALARM, passing to handleApplicationCommandRequest
2015-11-21 17:28:45.788 DEBUG o.o.b.z.i.p.c.ZWaveAlarmCommandClass[:82]- NODE 25: Received Alarm Request
2015-11-21 17:28:45.788 DEBUG o.o.b.z.i.p.c.ZWaveAlarmCommandClass[:94]- NODE 25: Alarm report - Value = 0
2015-11-21 17:28:45.789 DEBUG o.o.b.z.i.p.c.ZWaveAlarmCommandClass[:112]- NODE 25: Alarm Type = General (0)
2015-11-21 17:28:45.789 DEBUG o.o.b.z.i.ZWaveActiveBinding[:450]- NODE 25: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0

So I think I have an error in configuration of the items. Could you please post your configuration? I tried a lot and nothing helpled. Now I am a bit confused.

mstormi · November 23, 2015, 6:17am

roher · November 23, 2015, 11:01am

@mstormi, thanks for the screenshot, but could you please also post Association Groups screen and items configuration strings related to the FGSD-002 device.

mstormi · November 23, 2015, 3:44pm

Controller is in all 5 association groups

Switch EG_Wohnen_Rauchmelder_Rauch "Brandmelderalarm SMOKE"     <fire>          (Rauchmelder)                   { zwave="54:command=sensor_alarm,alarm_type=1" }
Switch EG_Wohnen_Rauchmelder_Hitze "Brandmelderalarm HEAT"     <fire>          (Rauchmelder)                   { zwave="54:command=sensor_alarm,alarm_type=4" }
Number EG_Wohnen_Bat "Wohnen Brandmelder [%s %%]"               <battery>       (EG_Wohnen,Batterien)           { zwave="54:command=battery" }

I also added

Switch EG_Wohnen_Rauchmelder_Basic_Rauch "Brandmelderalarm BASIC SMOKE" <fire>  (Rauchmelder)                   { zwave="54:command=sensor_binary,sensor_type=2,respond_to_basic=true" }
Switch EG_Wohnen_Rauchmelder_Basic_Hitze "Brandmelderalarm BASIC HEAT" <fire>   (Rauchmelder)                   { zwave="54:command=sensor_binary,sensor_type=5,respond_to_basic=true" }

but I haven’t seen FGSD002 use it yet.

sihui · November 23, 2015, 6:42pm

With my Everspring smoke detector I had to use Contact instead of Switch … could be worth a try …

Contact SF812_1_C “Sensoralarm Smoke [%s]” (gTest) { zwave=“2:command=sensor_alarm” }

roher · November 24, 2015, 9:23pm

@mstormi, so as you can see my config is the same as yours. I’ve also added my sensor to all 5 association groups. But I NEVER get:

255 for Smoke SENSOR_ALARM, I always get 0. So, how can I distinguish between “calm” and “alarm” states, as in both of them the sensor reports “0”? It doesn’t matter for me whether 0 (CLOSED) means “calm” and 255 (OPEN) means “alarm”, or vice versa, 0 means “alarm” and 255 means “calm”. But these two states SHOULD BE DIFFERENT, that’s the main problem.
Heat SENSOR_ALARM at all, even when the temperature rises above the configured threshold.

Here are my logs:
First is when the sensor is in “calm” state, I press the button, wait for one beep and green light, and press the button again (the manual states that in this case the sensor will “send device state to associated devices”). As you can see, the sensor answers with one General ALARM report, two(!) sequential Smoke SENSOR_ALARM reports, and one BASIC report:
23:29:13.127 [DEBUG] [ApplicationCommandMessageClass:38 ] - NODE 46: Application Command Request (ALIVE:DONE) 23:29:13.127 [DEBUG] [ApplicationCommandMessageClass:56 ] - NODE 46: Incoming command class ALARM 23:29:13.127 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:82 ] - NODE 46: Received Alarm Request 23:29:13.127 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:94 ] - NODE 46: Alarm report - Value = 0 23:29:13.127 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:112 ] - NODE 46: Alarm Type = General (0) 23:29:13.128 [DEBUG] [.z.internal.ZWaveActiveBinding:450 ] - NODE 46: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0 23:29:13.194 [DEBUG] [ApplicationCommandMessageClass:38 ] - NODE 46: Application Command Request (ALIVE:DONE) 23:29:13.194 [DEBUG] [ApplicationCommandMessageClass:56 ] - NODE 46: Incoming command class SENSOR_ALARM 23:29:13.194 [DEBUG] [c.ZWaveAlarmSensorCommandClass:85 ] - NODE 46: Received Sensor Alarm Request 23:29:13.195 [DEBUG] [c.ZWaveAlarmSensorCommandClass:104 ] - NODE 46: Alarm Report: Source=46, Type=Smoke(1), Value=0 23:29:13.195 [DEBUG] [.z.internal.ZWaveActiveBinding:450 ] - NODE 46: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_ALARM, value = 0 23:29:13.207 [DEBUG] [ApplicationCommandMessageClass:38 ] - NODE 46: Application Command Request (ALIVE:DONE) 23:29:13.207 [DEBUG] [ApplicationCommandMessageClass:56 ] - NODE 46: Incoming command class SENSOR_ALARM 23:29:13.207 [DEBUG] [c.ZWaveAlarmSensorCommandClass:85 ] - NODE 46: Received Sensor Alarm Request 23:29:13.207 [DEBUG] [c.ZWaveAlarmSensorCommandClass:104 ] - NODE 46: Alarm Report: Source=46, Type=Smoke(1), Value=0 23:29:13.208 [DEBUG] [.z.internal.ZWaveActiveBinding:450 ] - NODE 46: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_ALARM, value = 0 23:29:13.311 [DEBUG] [ApplicationCommandMessageClass:38 ] - NODE 46: Application Command Request (ALIVE:DONE) 23:29:13.312 [DEBUG] [ApplicationCommandMessageClass:56 ] - NODE 46: Incoming command class BASIC 23:29:13.312 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:74 ] - NODE 46: Received Basic Request 23:29:13.312 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:78 ] - NODE 46: Basic Set sent to the controller will be processed as Basic Report 23:29:13.312 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:107 ] - NODE 46: Basic report, value = 0x00 23:29:13.313 [DEBUG] [.z.internal.ZWaveActiveBinding:450 ] - NODE 46: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 0 23:29:13.323 [DEBUG] [ApplicationCommandMessageClass:38 ] - NODE 46: Application Command Request (ALIVE:DONE) 23:29:13.324 [DEBUG] [ApplicationCommandMessageClass:56 ] - NODE 46: Incoming command class BASIC 23:29:13.324 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:74 ] - NODE 46: Received Basic Request 23:29:13.324 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:78 ] - NODE 46: Basic Set sent to the controller will be processed as Basic Report 23:29:13.324 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:107 ] - NODE 46: Basic report, value = 0x00 23:29:13.325 [DEBUG] [.z.internal.ZWaveActiveBinding:450 ] - NODE 46: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 0
So, from the log above one would come to a conclusion that the values in “calm” state are 0 (CLOSED).

Next, here what happens when the temperature rises above the threshold (15 C):
00:23:13.738 [DEBUG] [ApplicationCommandMessageClass:38 ] - NODE 46: Application Command Request (ALIVE:DONE) 00:23:13.738 [DEBUG] [ApplicationCommandMessageClass:56 ] - NODE 46: Incoming command class ALARM 00:23:13.738 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:82 ] - NODE 46: Received Alarm Request 00:23:13.738 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:94 ] - NODE 46: Alarm report - Value = 0 00:23:13.739 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:112 ] - NODE 46: Alarm Type = General (0) 00:23:13.739 [DEBUG] [.z.internal.ZWaveActiveBinding:450 ] - NODE 46: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
And that’s all, it is the only thing that I get from the sensor when the temperature threshold is hit. Again, the value is 0 (CLOSED), so the value didn’t change against the “calm” state, and it is General ALARM, not Heat SENSOR_ALARM. When I request sensor’s state at this moment (again, by pressing the button, waiting for one beep and green light, and pressing the button again, I get exaclty the same as in the first log above, absolutely no difference.

Finally, I hide the sensor under several pillows (so that that my wife and neighbours won’t be shocked by the very loud beeper ), and press and hold the button for 5 seconds to trigger smoke alarm test mode. And here is what I get in the logs when the beep starts:
10:10:42.599 [DEBUG] [ApplicationCommandMessageClass:38 ] - NODE 46: Application Command Request (ALIVE:DONE) 10:10:42.599 [DEBUG] [ApplicationCommandMessageClass:56 ] - NODE 46: Incoming command class ALARM 10:10:42.599 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:82 ] - NODE 46: Received Alarm Request 10:10:42.599 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:94 ] - NODE 46: Alarm report - Value = 0 10:10:42.599 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:112 ] - NODE 46: Alarm Type = General (0) 10:10:42.600 [DEBUG] [.z.internal.ZWaveActiveBinding:450 ] - NODE 46: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0 10:10:54.700 [DEBUG] [ApplicationCommandMessageClass:38 ] - NODE 46: Application Command Request (ALIVE:DONE) 10:10:54.700 [DEBUG] [ApplicationCommandMessageClass:56 ] - NODE 46: Incoming command class ALARM 10:10:54.701 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:82 ] - NODE 46: Received Alarm Request 10:10:54.701 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:94 ] - NODE 46: Alarm report - Value = 0 10:10:54.701 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:112 ] - NODE 46: Alarm Type = General (0) 10:10:54.702 [DEBUG] [.z.internal.ZWaveActiveBinding:450 ] - NODE 46: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0 10:10:54.763 [DEBUG] [ApplicationCommandMessageClass:38 ] - NODE 46: Application Command Request (ALIVE:DONE) 10:10:54.764 [DEBUG] [ApplicationCommandMessageClass:56 ] - NODE 46: Incoming command class ALARM 10:10:54.764 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:82 ] - NODE 46: Received Alarm Request 10:10:54.764 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:94 ] - NODE 46: Alarm report - Value = 0 10:10:54.764 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:112 ] - NODE 46: Alarm Type = General (0) 10:10:54.765 [DEBUG] [.z.internal.ZWaveActiveBinding:450 ] - NODE 46: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
Again, the same as with overheating, the value is 0 (CLOSED), so the value didn’t change against the “calm” state, and it is General ALARM, not Smoke SENSOR_ALARM. You may see that it reports General ALARM with value = 0 when the alarm starts (10:10:42), and it reports General ALARM with value = 0 again when the alarm finishes 10 seconds later (10:10:54).

I hope that I have clearly explained what happens with my sensor. As I can see in this thread above, I have the same situation as @GaryWes has. GaryWes, have you resolved your issue?

GaryWes · November 25, 2015, 1:53pm

Hi @roher,

Unfortunately, I still have the same problem I do’nt understand how to operate this sensor…

roher · November 25, 2015, 7:33pm

Hi! I have written an email with the problem description and logs to support@fibaro.com. Hope they will answer something useful. I’ll post here their reply.

roher · November 30, 2015, 3:15pm

Hello!
Here is the Fibaro’s answer:

Dear Sir,
First off all I would like to mention that “test” alarm does not send the alarm frame.
Fibaro smoke detector FGSD-002 according to the Z-wave plus send in the lifeline (1st group) CC Notification (V5) which is also related with Z-wave plus.
First of all make sure that your main controller support Z-wave plus and CC Notification (V5).
For backward compatibility, you can use other groups (5,4,3,2) but in order to fully support our Smoke detector your main controller have to know CC Notification (V5) in order to set it in the lifeline.
Information about association groups you can find for example here: http://www.pepper1.net/zwavedb/device/675
FGSD-002 is tested for various standards also due to the Z-Wave standard.
To avoid doubling frames, set the main controller only in the one group. For example in the lifeline.

So, what I’ve got from it:

Non-Z-wave plus controllers (as mine) don’t support all functions of this sensor.
The sensor won’t send any alarm frame when the alarm is triggered using “test mode”. So, to know what command classes with what values are being sent, we have to trigger a real smoke alarm.

Open questions are the following:

Is non-Z-wave plus controller be able to get overheat alarm from the sensor? I’ve already asked Fibaro about it, waiting for the answer.
How to trigger real smoke alarm? I’ve already tried with a match and a candle (in 5 cm from the sensor), but the sensor doesn’t react on them How much smoke does the sensor need to trigger smoke alarm, does anybody know? Sensivity is set to Normal.

Udo_Hartmann · November 30, 2015, 9:24pm

You could use a Testspray for smoke detectors e.g. http://www.pollin.de/shop/dt/MDI3OTE0OTk-/Haustechnik/Sicherheitstechnik/Ueberwachungssysteme/Rauchmelder_Testspray.html