Fibaro Smoke detector

My Fibaro Smoke Sensors (002) are pairing as Z-wave sensor. I can change it in IDE, but I´m not able to configure the devices. If I change a parameter it always says false on configuration in IDE, I have tried to force it to wake up and waited days. I have returned one unit and got two new today, but it was just the same on the new units.

Hi,

I have two questions regarding these Fibaro sensors. Perhaps someone that owns one or has used one could help?

  1. Is it possible to inter-connect multiple sensors using ST as a hub? So if one detects fire, they all sound.

  2. Is it possible to use these as a generic alarm, e.g. With motion sensors, to sound in the event of intrusion?

Thanks.

Hi,

I have this smoke sensor model 002 in combination with an UK hub v2, but for me it just pairs as a Fibaro flood sensor. I have tried to remove it and re-pair a lot of times, but same result every time. When it is paired as a flood sensor, it does however show correct temperature and battery level.

If I go to the IDE and change the device type to Fibaro smoke sensor, nothing works: it does not update the temperature and the battery level does not show at all - even when waiting for weeks.

Anyone got a suggestion for how to get it to work?

BR
/Anders

Hi,
Just installed a Fibaro 002 Smoke Detector in my house and added to SmartThings. Tested with some smoke and set up alerts, voice notification and lights. Everything seems to work fine, but I have a question which I am hoping someone in the community can answer. I have trawled Google and read the Fibaro documentation but can not find anything on how to silence the Alarm in the event of a false alarm.

I see on the SmartThings Dashboard that you can dismiss and note the alert as a False Alarm… but the siren in the unit keeps sounding for quite a while longer. Pressing the “B” button doesn’t appear to work either to silence it. And there is no Tile to silence from the “Things” screen either.

Any ideas?

Thanks

1 Like

Can someone confirm whether or not the FGSS-001 is compatible with an ST V2 hub please? Thanks.

Confirmation received from support that the FGSS-001 is not supported. I also went looking for the small print on the compatibility list and it’s there for all to be seen (when you click the information button) thus proving I need to open my eyes!

Damn!

2 Likes

I encountered the same type behavior with my smoke sensor also, did you manage to get it fix?

Hi,

Unfortunately, I have not been able to fix it yet.

Sincere regards,
Anders Gaarsdal Holst, MD, PhD

Mobile: +45 3075 3460
Email: anders@kanten.dk

http://ICDPedia.dk - Søg efter diagnosekoder

Any indication as to why it isnt supported? Best i could tell the only difference is the FGSS-001 has a hard wiring option - which for me is a must.

No idea. Just not supported.

I’ve been looking at other oiptions, smoke detectors with a relay option that can trigger a binary sensor.

Have you found anything that isn’t butt ugly? The Fibaro’s are so small they look great!

Where are you? US/UK?

I’m in the UK

Have you had any success finding a good replacement? At the moment the only thing I would actually want to screw to my ceiling is the Nest Protects. I should be able to get a mains feed to them reasonable easily

Hi,

Are you able to confirm that you can set preferences for the 002 detector ok in ST?

thanks

I can confirm that it does not update preferences and I found the problem too.
It checks that the device MSR (manufacturerId-productTypeId) is correct before sending configuration commands.

if (!isConfigured() && getDataValue("MSR")?.startsWith("010F-0C02"))

I checked the log and it seems getDataValue(“MSR”) returns null for some reason.

Log:

19:19.37: debug After zwaveEvent(cmd) >> Parsed 'zw device: 07, command: 9881, payload: 00 84 07 ' to [['descriptionText':Smoke Sensor (Kitchen) woke up, 'isStateChange':false, 'displayed':false, 'linkText':'Smoke Sensor (Kitchen)'], physicalgraph.device.HubMultiAction@42f7eddf]
19:19.37: debug Device has been configured sending >> wakeUpNoMoreInformation()
19:19.37: info checking this MSR : null before sending configuration to device
19:19.37: info Executing zwaveEvent 84 (WakeUpV1): 07 (WakeUpNotification) with cmd: WakeUpNotification()
19:19.37: debug command: 98 (Security) 81(SecurityMessageEncapsulation) encapsulatedCommand: WakeUpNotification()
19:19.37: debug parse() >> zwave.parse(description)
19:19.37: debug parse() >> description: zw device: 07, command: 9881, payload: 00 84 07

Also I noticed that some default values in device handler do not match Fibaro Smoke Sensor manual (http://manuals.fibaro.com/content/manuals/en/FGSD-002/FGSD-002-EN-A-v1.01.pdf)
I edited the default values to match manual, removed the MSR check and it updated configuration without any problems.

I have Fibaro Smoke Sensor FGSD-002 ZW5 v3.3 and I’m using the device handler that is available in IDE

Hi. I just got a Smartthings Hub v2 and a Fibaro Smoke fgsd-002 (I’m new to this).
I have some issues regarding updating the preferences. It shows
secured: true
configured: false
And the sensor is not reporting back correct as I try to change the preferences.

-I get the same “info checking this MSR : null before sending configuration to device”. Can you share your device handler data or give some more detail to which values you changed, and to what?

-I have also a strange issue; If I remove the battery from the smoke sensor, there is no updated information in Smartthings about this. It behaves as if everything is fine and that the sensor is just not detecting smoke. Makes me a bit worried. Does your sensor behave this way?

-And the “Opened enclosure detection” does not work for me. Does that work after you got to change the preferences?

Thanks, sorry for all the questions :slight_smile:

Hi poisike,
Would it be possible to send a copy of you altered handler?

Hi there,
still not confident my FGSD-002 working properly.
I can manually get it to report using the IDE simulator and Configure option.
However, when left to itself, it doesn’t seem to be waking up and doesn’t report temperature. So no confidence it would report a fire!
I’ve seen mention of a wake up interval but there doesn’t seem to be a way to configure this.
I’ve set temperature reporting interval to 5 and hysteresis to 1.
Any ideas?

Here are logs:
Logs
db8c3711-4b8a-48eb-9feb-9da376118151 09:54:25: debug After zwaveEvent(cmd) >> Parsed 'zw device: 11, command: 9881, payload: 00 31 05 01 22 00 EA ’ to [‘name’:‘temperature’, ‘value’:‘23.4’, ‘unit’:‘C’, ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Fibaro Smoke Sensor’, ‘descriptionText’:Fibaro Smoke Sensor temperature is 23.4°C]
db8c3711-4b8a-48eb-9feb-9da376118151 09:54:25: info Executing zwaveEvent 31 (SensorMultilevelV5): 05 (SensorMultilevelReport) with cmd: SensorMultilevelReport(precision: 1, scale: 0, scaledSensorValue: 23.4, sensorType: 1, sensorValue: [0, 234], size: 2)
db8c3711-4b8a-48eb-9feb-9da376118151 09:54:25: debug command: 98 (Security) 81(SecurityMessageEncapsulation) encapsulatedCommand: SensorMultilevelReport(precision: 1, scale: 0, scaledSensorValue: 23.4, sensorType: 1, sensorValue: [0, 234], size: 2)
db8c3711-4b8a-48eb-9feb-9da376118151 09:54:25: debug parse() >> zwave.parse(description)
db8c3711-4b8a-48eb-9feb-9da376118151 09:54:25: debug parse() >> description: zw device: 11, command: 9881, payload: 00 31 05 01 22 00 EA
db8c3711-4b8a-48eb-9feb-9da376118151 09:54:15: info Sending secured command: SensorMultilevelGet(reserved110: 0, reserved212: 0, scale: 0, sensorType: 1)
db8c3711-4b8a-48eb-9feb-9da376118151 09:54:15: info Sending secured command: ConfigurationSet(configurationValue: [0, 30], defaultValue: false, parameterNumber: 20, reserved11: 0, scaledConfigurationValue: 30, size: 2)
db8c3711-4b8a-48eb-9feb-9da376118151 09:54:15: info Sending secured command: ConfigurationSet(configurationValue: [0, 90], defaultValue: false, parameterNumber: 32, reserved11: 0, scaledConfigurationValue: 90, size: 2)
db8c3711-4b8a-48eb-9feb-9da376118151 09:54:15: info Sending secured command: ConfigurationSet(configurationValue: [0, 180], defaultValue: false, parameterNumber: 31, reserved11: 0, scaledConfigurationValue: 180, size: 2)
db8c3711-4b8a-48eb-9feb-9da376118151 09:54:15: info Sending secured command: ConfigurationSet(configurationValue: [7], defaultValue: false, parameterNumber: 2, reserved11: 0, scaledConfigurationValue: 7, size: 1)
db8c3711-4b8a-48eb-9feb-9da376118151 09:54:15: info Sending secured command: ConfigurationSet(configurationValue: [7], defaultValue: false, parameterNumber: 3, reserved11: 0, scaledConfigurationValue: 7, size: 1)
db8c3711-4b8a-48eb-9feb-9da376118151 09:54:15: info Sending secured command: WakeUpIntervalSet(nodeid: 1, seconds: 21600)
db8c3711-4b8a-48eb-9feb-9da376118151 09:54:15: info inside commands: [WakeUpIntervalSet(nodeid: 1, seconds: 21600), ConfigurationSet(configurationValue: [2], defaultValue: false, parameterNumber: 1, reserved11: 0, scaledConfigurationValue: 2, size: 1), ConfigurationSet(configurationValue: [7], defaultValue: false, parameterNumber: 2, reserved11: 0, scaledConfigurationValue: 7, size: 1), ConfigurationSet(configurationValue: [7], defaultValue: false, parameterNumber: 3, reserved11: 0, scaledConfigurationValue: 7, size: 1), ConfigurationSet(configurationValue: [0, 30], defaultValue: false, parameterNumber: 20, reserved11: 0, scaledConfigurationValue: 30, size: 2), ConfigurationSet(configurationValue: [1], defaultValue: false, parameterNumber: 21, reserved11: 0, scaledConfigurationValue: 1, size: 1), ConfigurationSet(configurationValue: [0, 180], defaultValue: false, parameterNumber: 31, reserved11: 0, scaledConfigurationValue: 180, size: 2), ConfigurationSet(configurationValue: [0, 90], defaultValue: false, parameterNumber: 32, reserved11: 0, scaledConfigurationValue: 90, size: 2), BatteryGet(), SensorMultilevelGet(reserved110: 0, reserved212: 0, scale: 0, sensorType: 1)]
db8c3711-4b8a-48eb-9feb-9da376118151 09:54:15: info Sending secured command: ConfigurationSet(configurationValue: [2], defaultValue: false, parameterNumber: 1, reserved11: 0, scaledConfigurationValue: 2, size: 1)
db8c3711-4b8a-48eb-9feb-9da376118151 09:54:04: debug Updated with settings: [smokeSensorSensitivity:Medium, zwaveNotificationStatus:all notifications, visualIndicatorNotificationStatus:all notifications, temperatureReportInterval:5 minutes, temperatureReportHysteresis:1, lackOfZwaveRangeIndicationInterval:15 minutes]

FIXED FIBARO SMOKE SENSOR DEVICE HANDLER

As the original device handler seems not to be working properly, and haven’t give a chance to update the sensor:

  1. I used “poisike” tip and removed the check for MSR datavalue:
    if (!isConfigured() && getDataValue(“MSR”)?.startsWith(“010F-0C02”))

so the configration is being send properly now. Tip: remember to click the button on the sensor after you update the configratuion in UI.

  1. updated the default values based on the spec from here, as not all them was proper:
    http://manuals.fibaro.com/smoke-sensor/

  2. added configuration for wakeup interval. Minimum is 70 mins based on the spec.

The device handler can be downloaded form here:

Feel free to testm, share and let me know if it works for you.

1 Like