Has anybody issues with the FGSD002 smoke sensors?
A while ago, I had an issue with a sensor in the bathroom. Battery was empty, I replaced it, but value remained on 10%. After checking with Fibaro, they claim that the reason was that the sensor is in the bathroom. OK, they’re right that it’s not suited for bathrooms (humidity).
But today, i’m having the same issue with a simular sensor in my living room.
Battery empty, I replaced it (with 2 different battery), values are coming in, but I can’t see any battery entries in my logs.
Temperature is updating (for both), but not much more?
Just pushed the button on 5 simular device, but nothing came in the logs?
Gives me not much confidence that alerts will be seen by OH… 
Just did some extra tests, when the smoke sensor trigger a fire alert, OH notice this.
020-09-30 17:20:54.457 [vent.ItemStateChangedEvent] - Brand_Badkamer_Rook changed from OFF to ON
2020-09-30 17:21:15.630 [vent.ItemStateChangedEvent] - Brand_Badkamer_Rook changed from ON to OFF
With some extra debug, I see the tamper and so coming in, but nothing about battery state?
2020-09-30 17:36:02.483 [vent.ItemStateChangedEvent] - Brand_Badkamer_Pruts changed from OFF to ON
2020-09-30 17:36:02.628 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:alarm_tamper to ON [OnOffType]
2020-09-30 17:36:02.726 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:alarm_tamper to ON [OnOffType]
2020-09-30 17:36:11.148 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:sensor_temperature to 27.4 °C [QuantityType]
2020-09-30 17:36:11.152 [vent.ItemStateChangedEvent] - Brand_Badkamer_Temperatuur changed from 26.3 to 27.4
2020-09-30 17:36:42.938 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:alarm_tamper to OFF [OnOffType]
2020-09-30 17:36:42.940 [vent.ItemStateChangedEvent] - Brand_Badkamer_Pruts changed from ON to OFF
2020-09-30 17:36:43.096 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:alarm_tamper to OFF [OnOffType]
2020-09-30 17:36:43.186 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:alarm_tamper to OFF [OnOffType]
2020-09-30 17:36:46.572 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:alarm_tamper to ON [OnOffType]
2020-09-30 17:36:46.576 [vent.ItemStateChangedEvent] - Brand_Badkamer_Pruts changed from OFF to ON
2020-09-30 17:36:46.736 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:alarm_tamper to ON [OnOffType]
2020-09-30 17:36:46.843 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:alarm_tamper to ON [OnOffType]
2020-09-30 17:37:10.874 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:sensor_temperature to 28.5 °C [QuantityType]
2020-09-30 17:37:10.875 [vent.ItemStateChangedEvent] - Brand_Badkamer_Temperatuur changed from 27.4 to 28.5
2020-09-30 17:37:28.195 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:alarm_tamper to OFF [OnOffType]
2020-09-30 17:37:28.197 [vent.ItemStateChangedEvent] - Brand_Badkamer_Pruts changed from ON to OFF
2020-09-30 17:37:28.350 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:alarm_tamper to OFF [OnOffType]
2020-09-30 17:37:28.440 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:alarm_tamper to OFF [OnOffType]
2020-09-30 17:37:30.224 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:alarm_tamper to ON [OnOffType]
2020-09-30 17:37:30.226 [vent.ItemStateChangedEvent] - Brand_Badkamer_Pruts changed from OFF to ON
2020-09-30 17:37:30.379 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:alarm_tamper to ON [OnOffType]
2020-09-30 17:37:30.469 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:alarm_tamper to ON [OnOffType]
2020-09-30 17:37:34.091 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:30038385:node63' has been updated.
2020-09-30 17:37:37.573 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:30038385:node63' has been updated.
2020-09-30 17:37:39.575 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:30038385:node63' has been updated.
2020-09-30 17:38:08.731 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:alarm_smoke to OFF [OnOffType]
2020-09-30 17:38:20.516 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:sensor_temperature to 29.5 °C [QuantityType]
2020-09-30 17:38:30.269 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:30038385:node63' has been updated.
2020-09-30 17:38:40.181 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:alarm_smoke to OFF [OnOffType]
2020-09-30 17:42:38.788 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:sensor_temperature to 28.5 °C [QuantityType]
2020-09-30 17:42:38.791 [vent.ItemStateChangedEvent] - Brand_Badkamer_Temperatuur changed from 29.5 to 28.5
2020-09-30 17:44:28.265 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:sensor_temperature to 27.5 °C [QuantityType]
2020-09-30 17:44:28.268 [vent.ItemStateChangedEvent] - Brand_Badkamer_Temperatuur changed from 28.5 to 27.5
2020-09-30 17:47:17.487 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:sensor_temperature to 26.5 °C [QuantityType]
2020-09-30 17:47:17.490 [vent.ItemStateChangedEvent] - Brand_Badkamer_Temperatuur changed from 27.5 to 26.5
2020-09-30 17:51:56.324 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 63: Updating channel state zwave:device:30038385:node63:sensor_temperature to 25.5 °C [QuantityType]
Fibaro Zwave battery devices:
I have 12 of their Leak sensors, 9 contact sensors and 8 eye of Sauron motion sensors. I have had so many problems with their battery sensors doing this. I find I have to add them one at a time, and wake them up manually 30-40 times each to get every channel to initialize properly. They work for a few months then go into this dumb state again. I had the same problem when I was using homeseer with the sensors, I was having lots of other problems with homeseer, and attributed these problems with homeseer. I have other Zooz and Monoprice battery sensors that do not have this problem. I don’t know if it’s a problem with the zwave chip or tech that Fibaro use.
I have not found a way to make these reliable, The motion and contact sensors are annoying as they are not critical and used mostly to adjust comfort and lighting but I hate not being able to trust the leak sensors. I can’t justify replacing them all right now cost wise. But I might buy 1 or 2 and test, at least in the most critical areas.
a side note as well with the Fibaro leak sensors. I configured the association groups to send basic OFF command to my well directly bypassing OpenHab. This is also not reliable, I can manually set the sensor in water and it’s a 50/50 shot they fire the association group command. Since they do work for awhile with super fresh batteries, I wonder if their battery percentage is WAY off, and just stop working because they don’t have enough power, even tho the battery says 70%
anyways long post, and mini rant, but you arn’t alone, and I can verify you arn’t crazy (and if you are, I am as well) I havn’t found a solution, and now that I’ve commented I’ll see other responses and maybe somebody else did solve this.
1 Like
Just recieved feedback from Fibaro: "Since you use things that are unknown (=openHAB) to us, we can’t support you. "
Nice to know that they have a great support department in the Benelux. Why do these firms profile themselves as ‘open’ and ‘flexibel’, when they don’t want to support open things? Or stands the ‘open’ only for the sales department?
Open means you open your wallet to spend your money 
1 Like
I’ve done an exclude, a hardware reset of the node, and an include.
The device was picked up directly as new node. Then I had to wake it up about 20 times before it was recognized as the FGSD002 Smoke Detector.
And now, suddenly, the battery went from 10% towards 100%?
I’ve done this also for the node that went ‘bad’ a while ago, and same behavor. It workes again. So the assumption of Fibaro support that the node was broken isn’t not correct?
Not sure if it was the refresh of the zwave node binding, or the hardware reset. But for the moment, it seems to be normal (till the next battery replacment?).
1 Like
The waking up 20 times permitting discovery to complete on this battery operated device probably was the solution.
This has been my experience with my battery Fibaro devices, in 3-4 months I’ll be right back here again.
That is short battery life. Z-Wave devices usually claim up to 2 years with CR123A batteries. I replaced a cheap Chinese sensor due to life that short Two others have gone over a year.
this is a problem I have with ONLY my Fibaro battery devices. They will say ~70% on battery, but go dumb, and nothing I can do except hard reset them. punt from zwave and re-add brings them back. All my other z-wave battery devices work fine. See my response above.
