FGSS-001 Smoke alarm triggered for no reason

Add-ons Bindings
1

Hi All,

I have a FGSS-001 connected to OpenHab 1.8.3 on a Raspberry Pi 2 (using RazBerry daugherboard) which is consistently sending a false smoke alarm for no apparent reason after a network heal.

This happens after both the automatic network heal at 2am and if I manually trigger a network heal from Habmin. There is no sign of smoke present.

2016-06-05 03:45:28.078 [DEBUG] [c.ZWaveAlarmSensorCommandClass:85  ]- NODE 17: Received Sensor Alarm Request
2016-06-05 03:45:28.079 [DEBUG] [c.ZWaveAlarmSensorCommandClass:104 ]- NODE 17: Alarm Report: Source=17, Type=Smoke(1), Value=255
2016-06-05 03:45:33.614 [DEBUG] [c.ZWaveAlarmSensorCommandClass:85  ]- NODE 17: Received Sensor Alarm Request
2016-06-05 03:45:33.615 [DEBUG] [c.ZWaveAlarmSensorCommandClass:104 ]- NODE 17: Alarm Report: Source=17, Type=Smoke(1), Value=0

My initial thought was that it might be related to the z-wave range test, but setting that to 0 has no apparent effect. It has had this behaviour since the first day, so it might be a faulty unit. Any suggestions on what I should try before I attempt to send it back?

Thanks,

Chris

2

I’m not sure why this would happen - it might be worth asking the Fibaro support people. The heal does a couple of things - it requests a neighbour update, and it resets some static routes - neither should cause this to happen (IMHO!).

3

Thanks Chris, I tried excluding the sensor from the network and it continues to alarm, so I’m thinking it’s a faulty unit. I will contact Fibaro and see what they say.