Fibaro FGMS-001 Motion Sensor, doesn't seem to sense!

Thank

//Jens

[matt (support)]

Indigo v6.1.7 is now available and includes support for this model ID.

Now it works again, Thanks Matt

//Jens

Maybe it's a coincidence, but my FGMS-001 doesn't shows any activity at all since at least yestarday.
No LED's is showing anymore, no blinking when motion detected, a test trigger doesn's work, no ACK in Indigo.
I've removed and reinserted the battery again, pressed 3 times the B button, Indigo shows me "it's asleep or unreachable", so can's sync it.
The battery shows about 1,8V.

What do you think? Battery, or the device?

yassi

What do you think? Battery, or the device?

Battery - It should be 3V - I have had these sensors stop working when the battery level is less than 2V

What do you think? Battery, or the device?

Battery - It should be 3V - I have had these sensors stop working when the battery level is less than 2V

Jon, thanks, I will get a new one. It's the first I'm replacing, so.

yassi

Model ID: 08011001

That is a new/different model ID than the previous ones we've seen. I've added it to Indigo so it should work in Indigo 6.1.7 once it is released.

I just got three of these units that show a model ID of 08012001:

Code: Select all

Syncing - retrieved manufacture and model names: Fibaro System - 010F, Routing Slave - 08012001
Syncing - retrieved protocol version 4.05, app version 3.02


Im sure it's not a surprise, but they don't work--they report battery and nothing else

[matt (support)]

I just added those model IDs to the next version for you, so watch the announcements for when v6.1.8 is available (no ETA on it yet).

I just added those model IDs to the next version for you, so watch the announcements for when v6.1.8 is available (no ETA on it yet).

Thanks! I know you probably have no idea, but any guesses as to why they keep changing the model ID, thus breaking compatibility, even though it's the same device?

[matt (support)]

Yeah, each manufacturer seems to follow their own standards on when they use a new ID. Some only upgrade the model ID with major model changes (thank you to those vendors!), and others change with minor changes, and lots of them like to use a different model ID for each region SKU of the product. You would think that vendors would realize that control hubs use the model ID for identification, but apparently not...

I have just purchased some new Gen 5 Fibaro Motion Sensors which arrived today.

The box has a label: FGMS-001, EU V3.2, dated: 11.03.2016 (which is March, not November as we aren't there yet )

The sync gave the following info:

Z-Wave Syncing - started for "155 - Routing Slave"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Fibaro System - 010F, Motion Sensor (FGMS001) - 08011001
Z-Wave Syncing - retrieved protocol version 4.05, app version 3.02
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : -- : -- (04 : 07 : 01, base 00)
Z-Wave Syncing - retrieved command classes: 20v1 80v1 22v1 84v2 85v1 86v1 71v1 8Ev1 70v1 31v8 72v1 73v1 30v1 56v1 98v1 59v1 5Av1 9Cv1 7Av1 5Ev1
Z-Wave Syncing - retrieved wake interval of 60 minutes
Z-Wave Syncing - device "155 - Routing Slave" wake interval changed to 60 minutes
Z-Wave Syncing - retrieved battery level of 100%
Z-Wave Syncing - retrieved group 1 associations: []
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Syncing - retrieved group 3 associations: []
Z-Wave Syncing - retrieved group 4 associations: []
Z-Wave Syncing - retrieved group 5 associations: []
Z-Wave Syncing - added group 1 association to interface
Z-Wave Syncing - added group 2 association to interface
Z-Wave Syncing - added group 3 association to interface
Z-Wave Syncing - retrieved parameter 1 "Motion sensor sensitivity (8: most sensitive, 255: least sensitive)" is 15
Z-Wave Syncing - retrieved parameter 8 "Motion sensor mode (0: always active, 1: day only, 2: night only)" is 0
Z-Wave Syncing - retrieved parameter 6 "Delay after no motion before OFF sent" is 30 seconds
Z-Wave Syncing - retrieved parameter 9 "Night luminance threshold (used to determine day/night if mode 1 or 2 is used above)" is 200
Z-Wave Syncing - retrieved parameter 12 "Group 1 command type" is 0
Z-Wave Syncing - retrieved parameter 20 "Tamper sensor sensitivity (0: inactive, 1: most sensitive, 122: least sensitive)" is 20
Z-Wave Syncing - retrieved parameter 24 "Tamper operating mode" is 0
Z-Wave Syncing - retrieved parameter 40 "Luminance report sensitivity (0: disable reporting, 1 to 65535: lux)" is 200 LUX
Z-Wave Syncing - retrieved parameter 42 "Delay between reporting Luminance changes (0: disable reporting, 1 to 65535: seconds delay)" is 3600 seconds
Z-Wave Syncing - retrieved parameter 60 "Temperature change sensitivity (0: disable reporting, 1: 0.1°C, 2: 0.2°C, 10: 1.0°C, 20: 2.0°C, 50: 5.0°C, ..., 255: 25.5°C)" is 10
Z-Wave Syncing - retrieved parameter 62 "Delay between measuring temperature changes (0: disable measuring, 1 to 65535: seconds delay)" is 900 seconds
Z-Wave Syncing - retrieved parameter 64 "Delay between reporting temperature changes (0: disable reporting, 1 to 65535: seconds delay)" is 0 seconds
Z-Wave Syncing - retrieved parameter 66 "Temperature calibration offset in 0.1 degrees" is 0 * 0.1 degrees
Z-Wave Syncing - retrieved parameter 80 "LED signaling mode (see manual for values)" is 10
Z-Wave Syncing - retrieved parameter 81 "LED brightness (0: auto from ambient, 1 to 100: brightness percentage)" is 50
Z-Wave Syncing - retrieved parameter 82 "Luminance threshold for 1% LED brightness (only if LED brightness value is 0)" is 100 LUX
Z-Wave Syncing - retrieved parameter 83 "Luminance threshold for 100% LED brightness (only if LED brightness value is 0)" is 1000 LUX
Z-Wave Syncing - retrieved parameter 86 "Temperature threshold for triggering blue LED (only if LED signaling mode value is 1, 10, 19)" is 18 degrees
Z-Wave Syncing - retrieved parameter 87 "Temperature threshold for triggering red LED (only if LED signaling mode value is 1, 10, 19)" is 28 degrees
Z-Wave Syncing - retrieved parameter 89 "LED flashes red, white, blue on tamper" is true
Z-Wave Syncing - retrieved battery level of 100%
Z-Wave Syncing - created device "155 - Motion Sensor"
Z-Wave Syncing - created device "155 - Tilt/Tamper"
Z-Wave Syncing - created device "155 - Temperature"
Z-Wave Syncing - created device "155 - Luminance"
Z-Wave Syncing - complete

Dumping the details to the log gives:

Z-Wave Indigo Device "155 - Motion Sensor" Z-Wave Properties:
Indigo Z-Wave Version: 1.0.362
Node ID: 155
Model: Motion Sensor (FGMS001)
Model ID: 08011001
Manufacturer: Fibaro System
Manufacturer ID: 010F
Protocol Version: 4.05
Application Version: 3.02
Model Definition Version: 1
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 30v1 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:[1] 3:[1] 4:[] 5:[]
Config Values: 64:0 1:15 66:0 6:30 81:50 40:200 9:200 42:3600 12:0 80:10 8:0 82:100 83:1000 20:20 86:18 87:28 24:0 89:1 60:10 62:900

I have sync'd it with a standard (non-gen5) Aeon Labs Z-Stick.

It does seem to be sensing motion, lux and temperature readings but not detecting tamper.

I turned on the Z-Wave debug and forced a tamper and got:

Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 00 9B 09 71 05 00 00 00 FF 07 03 00 E9
Z-Wave Debug . . requestAlarmSensorStatus: node 155, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 3, classSubKeyExt 7100000703
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 08 9B 09 71 05 00 00 00 FF 07 03 00 E1
Z-Wave Debug . . requestAlarmSensorStatus: node 155, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 3, classSubKeyExt 7100000703
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 00 9B 09 71 05 00 00 00 FF 07 03 00 E9
Z-Wave Debug . . requestAlarmSensorStatus: node 155, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 3, classSubKeyExt 7100000703

Hope this helps

[matt (support)]

I have just purchased some new Gen 5 Fibaro Motion Sensors which arrived today.

It does seem to be sensing motion, lux and temperature readings but not detecting tamper.

I turned on the Z-Wave debug and forced a tamper and got:

Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 00 9B 09 71 05 00 00 00 FF 07 03 00 E9
Z-Wave Debug . . requestAlarmSensorStatus: node 155, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 3, classSubKeyExt 7100000703
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 08 9B 09 71 05 00 00 00 FF 07 03 00 E1
Z-Wave Debug . . requestAlarmSensorStatus: node 155, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 3, classSubKeyExt 7100000703
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 00 9B 09 71 05 00 00 00 FF 07 03 00 E9
Z-Wave Debug . . requestAlarmSensorStatus: node 155, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 3, classSubKeyExt 7100000703

Dang, they changed what message is sent for tamper alerts. To be honest it is unreal how many different ways this module sends messages based on which firmware version you happen to get. We'll see if we can add more conditional logic...

[matt (support)]

Try Indigo v6.1.8 which I just posted. It will hopefully be able to process the different tamper switch commands.

Try Indigo v6.1.8 which I just posted. It will hopefully be able to process the different tamper switch commands.

Tamper is now working - Thanks

I have been using a Twine vibration sensor for several years with good success. It has finally died, however. I would like to replace it with a z-wave vibration sensor which will work with Indigo. Does the Fibaro work well with Indigo? Are there any other vibration sensors anyone can recommend? My application is the Twine is velcroed to the lid of my emergency power generator at a vacation home. When it starts up for its weekly test, I get an email so I know it is working.