I noticed that you have node 11 in your item configuration and habmin screen, but in the log it shows it is zwave node 12. Seems that your device is changed to 12 (can happen after re-inclusion?)
hence you will likely need to change your item configuration to node 12?
…zwave="11:command=sensor_alarm …
should be …zwave="12:command=sensor_alarm …
I checked again my FGSD002, and actually get same info in the log from my Openhab when I press test button for 10 seconds.
When I set my items to command class Alarm to match this response, the returned value 0 gets translated to “close”, which means alarm not triggered.
This command class is not mentioned in the FGSD user manual, and no matter how I try, I don’t get the sensor_alarm , alarm type=1 signal in openhab when I press the test button. Gary, what version of firmware is on your FGSD002? I have firmware 3.3 on my FGSD002. I saw on other forums that firmware 3.3 includes some changes and people from Zipato made some update to support it. But I don’t know what exactly those changes are.
I am using Razberry on raspberry pi, when I start the Zway controller program instead of Openhab, the smoke alarm is correctly received. So my guess is that the sensor sends another z-wave command class signal but it is not supported by the Openhab binding yet…
Did you get to any solution @James_Huang? I am currently working on a similar thing. Also, were you able to get battery report from the smoke detector?
Here is my config for the battery and temperature that works,
But the smoke alarm I haven’t tested lately so i didn’t include here. (don’t want to get my wife annoyed with the sound, you know…) Will test the alarm part later.
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.
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.
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”.
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…
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