Fibaro flood sensor FGFS-101 - no tamper alarm visible?

Posted on
Tue May 11, 2021 3:14 pm
CrazyFin offline
Posts: 381
Joined: Jan 08, 2015
Location: Stockholm, SWEDEN

Fibaro flood sensor FGFS-101 - no tamper alarm visible?

I have mainly used the Fibaro FGFS-111 flood sensor in my home automation system.
I recently purchased a 4th sensor but this time I bought the FGFS-101.

Syncing works fine and I am able to get the water alarm to show up properly but neither the movement alarm or the tamper alarm are shown in the GUI. Status for tamper just stays off but I can see in the debug log that the tamper alarm is indeed there.

I have associated group 4 to the controller as well (default was no association at all) and also made sure config param 74 is set to either 2 or 3 but still no luck.

FGFS-111 works fine with the tamper alarm though.

I can see the following in the debug log when I lift and move the FGFS-101:
Code: Select all
2021-05-11 22:36:10.049   Z-Wave Debug   RCVD requestAlarmSensorStatus: 01 0F 00 04 00 09 09 71 05 00 03 00 FF 07 03 00 78
2021-05-11 22:36:10.049   Z-Wave Debug   . .  requestAlarmSensorStatus: node 009, endpoint None, cmdClass 71, type 0, value 3, classSubKey 710003
2021-05-11 22:36:10.049   Z-Wave Debug   . .  requestAlarmSensorStatus: typeExt 7, valueExt 3, classSubKeyExt 7100030703
2021-05-11 22:36:10.049   Z-Wave Debug   RCVD requestAlarmSensorStatus: 01 0F 00 04 08 09 09 71 05 00 03 00 FF 07 03 00 70
2021-05-11 22:36:10.049   Z-Wave Debug   . .  requestAlarmSensorStatus: node 009, endpoint None, cmdClass 71, type 0, value 3, classSubKey 710003
2021-05-11 22:36:10.049   Z-Wave Debug   . .  requestAlarmSensorStatus: typeExt 7, valueExt 3, classSubKeyExt 7100030703
2021-05-11 22:36:10.050   Z-Wave Debug   RCVD requestAlarmSensorStatus: 01 0F 00 04 00 09 09 71 05 00 03 00 FF 07 03 00 78
2021-05-11 22:36:10.050   Z-Wave Debug   . .  requestAlarmSensorStatus: node 009, endpoint None, cmdClass 71, type 0, value 3, classSubKey 710003
2021-05-11 22:36:10.050   Z-Wave Debug   . .  requestAlarmSensorStatus: typeExt 7, valueExt 3, classSubKeyExt 7100030703
And here are the device details for the FGFS-101:
Code: Select all
Indigo Z-Wave Version: 7.5.0
Node ID: 009
Model: Leak Sensor (FGFS101)
Model ID: 0B011002
Manufacturer: Fibaro System
Manufacturer ID: 010F
Protocol Version: 4.05
Application Version: 3.02
Model Definition Version: 7
Library Type: 3
Class Name: Notification Sensor
Class Hierarchy: 04 : 07 : 01
Command Class Base: 00
Command Versions: 80v1 84v2 85v1 86v1 8Ev1 56v1 98v1 59v1 5Av1 9Cv1 5Ev1 20v1 22v1 71v1 70v1 31v5 72v1 73v1 7Av1
Encryption Status: Supported but not Enabled
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, security, waking
Neighbors: 2, 4, 6, 8, 20, 22, 23, 24, 26, 30, 32, 33, 38, 39, 49, 59, 99, 104, 107, 110, 163, 176, 177, 178, 180, 182, 187, 204, 213, 225
Associations: 1:[1] 2:[1] 3:[1] 4:[1]
Config Values: 2:3 12:50 10:300

Posted on
Wed May 12, 2021 11:15 am
CrazyFin offline
Posts: 381
Joined: Jan 08, 2015
Location: Stockholm, SWEDEN

Re: Fibaro flood sensor FGFS-101 - no tamper alarm visible?

I did some more investigation using the cool plugin Z-Wave Watcher from @howartp. Thanks howartp! :-)

Here is what I see when I trigger the movement sensor by lifting the FGFS-101:
Code: Select all
 Z-Wave Watcher Debug            Raw command received (Node 10): 01 0F 00 04 00 0A 09 71 05 00 03 00 FF 07 03 00 7B
 Z-Wave Watcher Debug            Raw command received (Node 10): 01 0F 00 04 08 0A 09 71 05 00 03 00 FF 07 03 00 73
 Z-Wave Watcher Debug            Raw command received (Node 10): 01 0F 00 04 00 0A 09 71 05 00 03 00 FF 07 03 00 7B
And it looks in fact that the tamper/movement sensor is automatically reset after 15 seconds:
Code: Select all
Z-Wave Watcher Debug            Raw command received (Node 10): 01 0F 00 04 00 0A 09 71 05 00 00 00 FF 07 00 00 7B
Z-Wave Watcher Debug            Raw command received (Node 10): 01 0F 00 04 08 0A 09 71 05 00 00 00 FF 07 00 00 73
Z-Wave Watcher Debug            Raw command received (Node 10): 01 0F 00 04 00 0A 09 71 05 00 00 00 FF 07 00 00 7B
The third last byte changes from 03 to 00 which I believe is to indicate that the tamper alarm is back to "off"?

Posted on
Wed May 12, 2021 11:27 am
CrazyFin offline
Posts: 381
Joined: Jan 08, 2015
Location: Stockholm, SWEDEN

Re: Fibaro flood sensor FGFS-101 - no tamper alarm visible?

So I remembered the possibility to create a work around by using my own triggers with the Match Raw Byte from incoming Z-Wave commands.

I have now one trigger for the tamper when it goes on and another trigger when tamper is set to off again (by incoming command from the device itself).

Posted on
Fri May 14, 2021 1:31 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Fibaro flood sensor FGFS-101 - no tamper alarm visible?

Thanks for the Event Log details on this – we'll get Indigo's device definition modified to trigger tamper state changes for those in the next version.

Image

Posted on
Sat May 15, 2021 3:44 am
CrazyFin offline
Posts: 381
Joined: Jan 08, 2015
Location: Stockholm, SWEDEN

Re: Fibaro flood sensor FGFS-101 - no tamper alarm visible?

Thanks Matt!

I use Prowl to get push notifications on various alarms (doorbell, tampers, water leaks and other important notifications) and I have been struggling with that many of my Prowl push notifications I always get TWO notifications. I realized now when I was looking at these raw commands above that every time I get a tamper alarm (or any other alarm from those kind of sensors) that the Z-Wave messages seems to send 3 commands where two of the commands are identical:

Code: Select all
Z-Wave Watcher Debug            Raw command received (Node 10): 01 0F 00 04 00 0A 09 71 05 00 03 00 FF 07 03 00 7B
Z-Wave Watcher Debug            Raw command received (Node 10): 01 0F 00 04 08 0A 09 71 05 00 03 00 FF 07 03 00 73
Z-Wave Watcher Debug            Raw command received (Node 10): 01 0F 00 04 00 0A 09 71 05 00 03 00 FF 07 03 00 7B
When I first created my tamper trigger I used the first line above but that caused me to get two tamper alerts from Prowl. I then changed the trigger to look for the command in the 2nd line above and now I get only one push notification from Prowl which is correct. I am wondering if the other devices I trigger Prowl notifications in the same way trigger on the "wrong" command that is sent twice?

What is actually the difference between row 1 and 2 above and why is row 1 and 3 identical, i.e. sent twice?

I created a Z-Wave watcher for my other water sensor, FGFS-111 that updates tamper state properly in Indigo and I do indeed see the tamper alarm sent out twice by the device:
Code: Select all
Z-Wave Watcher Debug            Raw command received (Node 58): 01 0D 00 04 00 3A 07 9C 02 3A 00 FF 00 00 90
Z-Wave Watcher Debug            Raw command received (Node 58): 01 0D 00 04 00 3A 07 9C 02 3A 00 FF 00 00 90
So that explains why I get double push notifications on my iPhone from Prowl, it is not Prowl that is sending out the push notification twice, it is just reacting to the fact that some of my devices sends out the tamper alarm twice.

I also noticed that I should NOT have BOTH a Title and a Message on my Prowl notifications since that would also make the same message appear twice on my iPhone. I now send out only a text in the Title and most of my push notifications via Prowl to my iPhone are now single notifications.

Posted on
Thu May 20, 2021 2:47 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Fibaro flood sensor FGFS-101 - no tamper alarm visible?

I'm not sure why the module is sending 3 messages like that (2 of which are duplicates). I've added support to catch the message to the device def'n for the next version. If you then trigger on the device state change I think it should just trigger once.

Image

Posted on
Thu May 27, 2021 10:03 pm
JonathanKing offline
Posts: 36
Joined: Dec 29, 2015

Re: Fibaro flood sensor FGFS-101 - no tamper alarm visible?

Hi Matt,

I just setup a FGFS-101 and the tamper alarm isn't showing up in Indigo 7.5. The Device never changes state, even when the unit itself beeps when I tilt it.

Also, I feel like this must be super simple and I'm just missing it, but the temperature is in Celsius and I don't see how to change it to Fahrenheit. Any tip there?

Thanks!
-jonathan (looking forward to 2021.1 and Alexa support!)

Posted on
Fri May 28, 2021 2:14 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Fibaro flood sensor FGFS-101 - no tamper alarm visible?

Hi Jonathan,

Is the tile/tamper alarm device being created in Indigo but it isn't working? If so that is the same issue CrazyFin above had, which will be fixed in the next release of Indigo (but isn't available in current release).

I don't believe this module has a configuration parameter to change the reported temperature to Fahrenheit, but you can use the Adapters Plugin to create a virtual device that does the conversion.

Image

Posted on
Sat May 29, 2021 12:20 pm
CrazyFin offline
Posts: 381
Joined: Jan 08, 2015
Location: Stockholm, SWEDEN

Re: Fibaro flood sensor FGFS-101 - no tamper alarm visible?

JonathanKing wrote:
Also, I feel like this must be super simple and I'm just missing it, but the temperature is in Celsius and I don't see how to change it to Fahrenheit. Any tip there?


Unfortunately it is NOT possible to change temp unit from Celsius to Fahrenheit on these units.

Posted on
Sat May 29, 2021 12:23 pm
CrazyFin offline
Posts: 381
Joined: Jan 08, 2015
Location: Stockholm, SWEDEN

Re: Fibaro flood sensor FGFS-101 - no tamper alarm visible?

JonathanKing wrote:
I just setup a FGFS-101 and the tamper alarm isn't showing up in Indigo 7.5. The Device never changes state, even when the unit itself beeps when I tilt it.


As Matt wrote above the current release of Indigo does not support the tamper alarm of the FGFS-101. You can do a temporarily workaround like I did above until the device definitions has been included in the next release.

Posted on
Fri Jun 18, 2021 2:47 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Fibaro flood sensor FGFS-101 - no tamper alarm visible?

Indigo 2021.1.0 is now available and should detect the tamper alarm state changes. You may need to first re-sync the device in Indigo.

Image

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 1 guest

cron