Fibaro Smoke Sensor FGSD-002

Hey Folks,

unfortunately this one is not supported yet. I just can see the Battery live and can set the wake up. The exact name is: FGSD-002 EU V3.3 from December 2015). Please find below the device information:

07.01.2016 12:21:57
Z-Wave Indigo Device "008 - Routing Slave" Z-Wave Properties:
Indigo Z-Wave Version: 1.0.355
Node ID: 8
Model: Routing Slave
Model ID: 0C021002
Manufacturer: Fibaro System
Manufacturer ID: 010F
Protocol Version: 4.05
Application Version: 3.03
Model Definition Version: 0
Library Type: 3
Class Name: Routing Slave
Class Hierarchy: 04 : 07 : 01
Command Class Base: 00
Command Versions: 20v1 80v1 22v1 84v2 85v1 86v1 71v1 8Ev1 70v1 31v8 72v1 73v1 56v1 98v1 59v1 5Av1 9Cv1 7Av1 5Ev1
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, waking
Neighbors: - none -
Associations: 1:[1] 2:[] 3:[] 4:[] 5:[]
Config Values: - none -

Any possibility to get this supported?

Best regards,
Marcus

I have tried to get it supported since spring 2015.. But it seems like new devices is a low priority at Indigo. Unfortunately. I have a lot of them together with Qubino dimmers which is also not 100% supported in Indigo yet.

I'm interested too. I just bought 2 sensors and can't do anything with them...

I would love to see some support for the smoke sensor.

It never occurred to me that indigo wouldn't support these devices when i bought 2, after all on planet z-wave it doesn't get much bigger than Fibaro!

I must admit to being very disappointed that this has been outstanding for so long (almost a year based on the comments trail)...

btw when is indigo 7 being released? the info i read seemed very sketchy, i understood it would be released in Feb

[matt (support)]

Sorry, but we do not discuss release time estimates or what specific features or new hardware will be supported in upcoming releases. Supporting Fibaro hardware (and Aeotec) are high priority though...

I recently bought a FGSD-002, concurrent with purchasing my Indigo license …

I think the only place this forum has mentioned a Feb release of v7 was a hypothesis from me, but I can't remember where or when.

We are all waiting v7 with bated breath, but once it arrives I'm confident we'll all be delighted with it and forget all our grumblings.

I can't remember whether Matt/Jay publicly announced the beta for v6.1 when that entered beta, or whether we just picked it up from rumours on the forum from those taking part who probably weren't allowed to say anything - either way I've not seen any rumours of it happening yet, so until that happens we are going to have to wait longer.

Peter


Sent from my iPhone using Tapatalk

I am sure Matt and Jay are just concentrating on Indigo 7, rather than supporting products. Supporting products does not increase their revenue, like indigo 7 will. My own fault I know but I have about £1000 of unsupported products. I check most items and it says they are compatible but when you purchase the device it is a slightly newer version and not compatible.

Im totally with the previous contributor, quite frankly I'm getting tired of waiting for Indigo to trickle out updates to allow commonly available devices to work, I'm sure there is a fair degree of truth in the theory that they will make more from Indigo 7 than they will from sorting out compatibility issues!

If it doesn't happen soon i for one won't be staying with indigo, its a trust and confidence issue, and the choice of alternatives is growing rapidly

Based on all the #indigo7sneaks coming out thick and fast, it can't be more than a few weeks away now.


Sent from my iPhone using Tapatalk

I can not get this to work. The temperature reading appears correctly, but when I press the test button, the fire alarm state stays off.
I have exclude and re-include sensor many times, no change

Syncing - started for "076 - Smoke"
Z-Wave Syncing - retrieved module neighbors list: 5, 6, 17, 18, 20, 27, 28, 36, 40, 42, 46, 52, 55, 62
Z-Wave Syncing - assigning return route to "076 - Smoke"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Fibaro System - 010F, Smoke Sensor (FGSD002) - 0C021002
Z-Wave Syncing - retrieved protocol version 4.05, app version 3.03
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01, base 00)
Z-Wave Syncing - retrieved command classes: 20v1 80v1 22v1 84v2 85v1 86v1 71v1 8Ev1 70v1 31v8 72v1 73v1 56v1 98v1 59v1 5Av1 9Cv1 7Av1 5Ev1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, battery, beaming, security, waking
Z-Wave Syncing - retrieved wake interval of 360 minutes
Z-Wave Syncing - device "076 - Smoke" wake interval changed to 60 minutes
Z-Wave Syncing - retrieved group 1 associations: [1]
Z-Wave Syncing - retrieved group 2 associations: [1]
Z-Wave Syncing - retrieved group 3 associations: []
Z-Wave Syncing - retrieved group 4 associations: []
Z-Wave Syncing - retrieved group 5 associations: [1]
Z-Wave Syncing - group 1 association to interface already exists (skipping)
Z-Wave Syncing - group 2 association to interface already exists (skipping)
Z-Wave Syncing - group 5 association to interface already exists (skipping)
Z-Wave Syncing - retrieved parameter 2 "Notification flags" is 3
Z-Wave Syncing - retrieved parameter 10 "Group 2 command type" is 0
Z-Wave Syncing - retrieved parameter 11 "Group 2 command value" is 255
Z-Wave Syncing - retrieved parameter 1 "Smoke sensitivity" is 2 "Medium"
Z-Wave Syncing - retrieved parameter 3 "Visual alerts" is 0 "Disabled"
Z-Wave Syncing - retrieved parameter 4 "Audible alerts" is 0 "Disabled"
Z-Wave Syncing - retrieved parameter 20 "Temperature interval" is 1 * 10 seconds
Z-Wave Syncing - retrieved parameter 21 "Temperature sensitivity" is 10 * 0.1°C
Z-Wave Syncing - retrieved parameter 30 "Temperature threshold" is 55 °C
Z-Wave Syncing - retrieved parameter 31 "Temperature alarm" is 1 "10 Seconds"
Z-Wave Syncing - retrieved battery level of 100%
SQL Logger creating table device_history_649013059 for "076 - Tamper"
Z-Wave Syncing - created device "076 - Tamper"
Z-Wave Syncing - created device "076 - Temperature"
SQL Logger creating table device_history_1272335134 for "076 - Temperature"
SQL Logger adding column "sensorvalue" to table device_history_1272335134 ("076 - Temperature")
Z-Wave Syncing - complete
SQL Logger adding column "sensorvalue_ui" to table device_history_1272335134 ("076 - Temperature")
Z-Wave Error device "076 - Smoke" does not support status request command

And when i press test button

Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 00 4C 09 71 05 00 00 00 FF 01 03 00 38
Z-Wave Debug . . requestAlarmSensorStatus: node 076, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 1, valueExt 3, classSubKeyExt 7100000103
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 4C 06 31 05 01 22 01 05 AE
Z-Wave Debug . . requestVarSensorStatus: node 076, endpoint None, type 1, raw value 2201...
Z-Wave Debug . . requestVarSensorStatus: 26.1 °C (float: 26.100000)
Z-Wave received "076 - Temperature" sensor update to 26.1 °C
Z-Wave received "076 - Temperature" units changed to °C
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 10 00 04 00 4C 0A 71 05 00 00 00 FF 01 00 01 03 25
Z-Wave Debug . . requestAlarmSensorStatus: node 076, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 1, valueExt 0, classSubKeyExt 7100000100

Anyone else got this to work?
It's mentioned in the new supported devices list.

The sensor won't send any alarm frame when the alarm is triggered using "test mode"

Reply from fibaro i found on another forum..
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/67522
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.

To test it you have to try it with test spray or similar to trigger a real smoke alarm.

Asconasny

Thank you very much for the information.