Jump to content

Fibaro Z-Wave Motion Sensor - FGMS-001


Recommended Posts

Dear community

 

Has anybody used this product

https://www.amazon.com/dp/B01615SUBI

 

With ISY994izw?

I already ordered the Z-Wave for ISY994i (Thanks Michael for allowing me to save money by ordering from Orchestrated Home)

 

My question is, before I order from Amazon, has anybody used that product?

 

Fibaro detects:

1) motion

2) temperature

3) light

4) vibrations due to built-in accelerometer

Link to comment
Share on other sites

Dear Michel

 

Fibaro reports the temperature in Celsius.

Do you know how can I convert it to Farenheit so I can use it in my programs??

 

Thanks

 

Hi rafarataneneces,

 

There is no current way to have the Fibaro show in Fahrenheit, but if your are using the 5.0.x branch of Isy firmware, you can store the value in a variable and use it that way.

Link to comment
Share on other sites

Hi rafarataneneces,

 

There is no current way to have the Fibaro show in Fahrenheit, but if your are using the 5.0.x branch of Isy firmware, you can store the value in a variable and use it that way.

 

Dear Michel

 

When I reboot ISY994i I have to delete the FIbaro Motion Sensor and re-add it again.

 

Also the motion sensor stops working, and I have to delete it, re-add it, test, and when it works, then I am just afraid to see if the next day it's going to work on not.

 

Long story short, it's feeling frustrating.

 

Is Z-Wave still in beta (unstable) condition or am I new to Z-Wave and need to learn more?

 

For example right now it was working great I had to reboot ISY and now I had to factory reset the Z-Wave Dongle.

 

Can I damage the Z-Wave dongle if I factory reset it to many times?

 

Is there a way to force Z-Wave dongle to reassign ZW002 again?

 

All my programs need ZW002 so when it adds ZW003 or ZW004... then I do a factory reset.

 

Pardon my lack of experience but I am so confused why it's so unstable.

 

I am working 3 feet away from the ISY

 

Link to comment
Share on other sites

Dear Michel

 

When I reboot ISY994i I have to delete the FIbaro Motion Sensor and re-add it again.

 

Also the motion sensor stops working, and I have to delete it, re-add it, test, and when it works, then I am just afraid to see if the next day it's going to work on not.

 

 

 

Hi rafarataneneces,

 

You really should not have to keep adding the sensor, what actually happens when you reboot the ISY?  Do you no longer see the device in the Admin Console?

Link to comment
Share on other sites

Hi rafarataneneces,

 

You really should not have to keep adding the sensor, what actually happens when you reboot the ISY?  Do you no longer see the device in the Admin Console?

I see it but then the status doesn't change.

 

So I have to factory reset the dongle and re-add then device.

 

Yesterday I spent the entire day adding/deleting/factory resetting devices

 

So far my experience with Z-Wave has been very unstable.

 

Insteon seems 10 times better and more reliable.

 

But I am interested in multiple sensors I really like the idea.

 

I took a screenshot of what happens so you can see I'll upload it when I'm in my computer

Link to comment
Share on other sites

I see it but then the status doesn't change.

 

So I have to factory reset the dongle and re-add then device.

 

Yesterday I spent the entire day adding/deleting/factory resetting devices

 

So far my experience with Z-Wave has been very unstable.

 

Insteon seems 10 times better and more reliable.

 

But I am interested in multiple sensors I really like the idea.

 

I took a screenshot of what happens so you can see I'll upload it when I'm in my computer

 

Not sure if you are doing this, but one of the things you have to keep in mind with Z-Wave is you should never factory reset a device that is in the network, you must Remove/Exclude it first otherwise you may corrupt your Z-Wave network.

 

From my own experience with the FGMS-001, I can restart the ISY and still get all the status and generally it works fine.  Therefore, I suspect the problem is due to your Z-Wave network.

 

At this point, I would do the following in order:

 

1) Remove/exclude all of your Z-Wave devices

2) Factory reset the Z-Wave dongle

3) Add all of your devices again

4) Update the Z-Wave configuration parameters in your devices

 

Leave the ISY on for at least several hours and see if you are getting status for that whole time.  If you are, then restarting the ISY should not impact this at all.  Its possible when you restart the ISY that the device just hasn't sent status right away and that is why you aren't seeing it.

Link to comment
Share on other sites

Not sure if you are doing this, but one of the things you have to keep in mind with Z-Wave is you should never factory reset a device that is in the network, you must Remove/Exclude it first otherwise you may corrupt your Z-Wave network.

 

From my own experience with the FGMS-001, I can restart the ISY and still get all the status and generally it works fine.  Therefore, I suspect the problem is due to your Z-Wave network.

 

At this point, I would do the following in order:

 

1) Remove/exclude all of your Z-Wave devices

2) Factory reset the Z-Wave dongle

3) Add all of your devices again

4) Update the Z-Wave configuration parameters in your devices

 

Leave the ISY on for at least several hours and see if you are getting status for that whole time.  If you are, then restarting the ISY should not impact this at all.  Its possible when you restart the ISY that the device just hasn't sent status right away and that is why you aren't seeing it.

 

Okay I did what you said but then next day then the sensor doesn't report motion.

 

I am seriously thinking placing the Fibaro Motion Sensor RIGHT NEXT to the ISY994i for the next couple of days just to see what happens, maybe reception is so bad that I would have to either move the ISY994IZw/IR Pro to an open space or just buy an alarm for the heck of it just so it can repeat whatever the ISY broadcasts

Link to comment
Share on other sites

Okay I did what you said but then next day then the sensor doesn't report motion.

 

I am seriously thinking placing the Fibaro Motion Sensor RIGHT NEXT to the ISY994i for the next couple of days just to see what happens, maybe reception is so bad that I would have to either move the ISY994IZw/IR Pro to an open space or just buy an alarm for the heck of it just so it can repeat whatever the ISY broadcasts

 

In researching this a bit further I learned there are two different hardware versions of the Fibaro FGMS-001 motion sensor. The later version is Z-Wave Plus with firmware 3.2 and started shipping sometime earlier this year. There are also multiple versions of firmware for the non-Plus sensor from 2.4 to 2.8.
 
I have the non-Plus version and don't know at the moment which firmware it's using. I'm using ISY 5.0.4 and aren't experiencing any of the problems you are.
 
Could you query your Fibaro sensor from ISY to see if there are some obvious differences between your sensor and mine? To do this first do Tools / Diagnostics / Event Viewer. Then right click on your Fibaro sensor device, Z-Wave / Show Information in Event Viewer / All. Then click the notepad icon in the event viewer and post here. Following below is the output from my Fibaro sensor attached to my test ISY.
 
The sensor's hardware or firmware version you have may not yet be compatible with ISY 5.0.x. As far as I can tell there are at least three other possible causes of the problems you're encountering. One is the radio noise mentioned by larrylix in another thread; the lack of two or more non-battery Z-Wave devices to act as repeaters for your Z-Wave mesh as mentioned by Michel; and/or issues related to ISY alpha firmware 5.0.4.
 
*********************************
 
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ] ----------------------------------------------
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ] ZW010_1 uid=0 type=10.2.73 mid=30954 tid=556 pid=39608 model=0
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ]    -  x30  V1  SENSOR_BINARY
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ]    -  x84  V1  WAKE_UP
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ]    -  x85  V0  ASSOCIATION
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ]    -  x80  V0  BATTERY
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ]    -  x8F  V0  MULTI_CMD
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ]    -  x56  V0  CRC_16_ENCAP
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ]    -  x72  V0  MANUFACTURER_SPECIFIC
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ]    -  x86  V0  VERSION
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ]    -  x70  V0  CONFIGURATION
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ]    -  x8E  V0  MULTI_INSTANCE_ASSOCIATION
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ]    -  x31  V0  SENSOR_MULTILEVEL
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ]    -  x9C  V0  SENSOR_ALARM
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ] 
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ] Node  10 - Fibaro MS ZW-010 Binary has the following neighbors
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ]    -          - Node   1 - [This ISY]
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ]    - Repeater - Node   4 - Aeotec SS6 ZW-004 On-Off
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ]    - Repeater - Node   6 - Aeotec SES ZW-006 On-Off
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ]    - Repeater - Node   8 - Aeotec SStr ZW-008.1 On-Off
Thu 08/18/2016 06:55:58 PM : [ZW-SHOW         ] 
Thu 08/18/2016 06:56:14 PM : [ZW-SHOW         ] Node  10 - Fibaro MS ZW-010 Binary cannot retrieve association groups
Thu 08/18/2016 06:56:14 PM : [ZW-SHOW         ] 
Thu 08/18/2016 06:56:14 PM : [ZW-SHOW         ] ----------------------------------------------
Link to comment
Share on other sites

Here is my information

Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ] ----------------------------------------------
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ] ZW002_1 uid=0 type=2.2.73 mid=42938 tid=556 pid=39592 model=0
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x5E  V2  ZWAVEPLUS_INFO
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x20  V1  BASIC
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x86  V2  VERSION
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x72  V2  MANUFACTURER_SPECIFIC
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x5A  V1  DEVICE_RESET_LOCALLY
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x59  V1  ASSOCIATION_GRP_INFO
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x85  V2  ASSOCIATION
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x73  V1  POWERLEVEL
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x84  V2  WAKE_UP
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x80  V0  BATTERY
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x71  V0  NOTIFICATION
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x56  V0  CRC_16_ENCAP
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x70  V0  CONFIGURATION
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x31  V0  SENSOR_MULTILEVEL
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x8E  V0  MULTI_INSTANCE_ASSOCIATION
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x22  V0  APPLICATION_STATUS
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x30  V0  SENSOR_BINARY
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x9C  V0  SENSOR_ALARM
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x98  V0  SECURITY
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -  x7A  V0  FIRMWARE_UPDATE_MD
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ] 
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ] Node   2 - ZW 002 Notify Sensor has the following neighbors
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ]    -          - Node   1 - [This ISY]
Sat 08/20/2016 03:54:54 AM : [ZW-SHOW         ] 
Sat 08/20/2016 03:55:10 AM : [ZW-SHOW         ] Node   2 - ZW 002 Notify Sensor cannot retrieve association groups
Sat 08/20/2016 03:55:10 AM : [ZW-SHOW         ] 
Sat 08/20/2016 03:55:10 AM : [ZW-SHOW         ] ----------------------------------------------
Sat 08/20/2016 03:55:37 AM : [  31 AD 25 1]      DOF   1
Sat 08/20/2016 03:55:37 AM : [  37 C5 3C 1]       ST   0 (uom=100 prec=0)
Sat 08/20/2016 03:55:37 AM : [  34 CB DC 1]       ST   0 (uom=100 prec=0)
Sat 08/20/2016 03:55:37 AM : [  31 AD 25 1]       ST   0 (uom=100 prec=0)

Link to comment
Share on other sites

Also I want Fibaro Motion Sensor to report "ON" for 2 minutes.

 

After all, even though this report temperature, I bought it so it can report motion.

 

With Insteon Motion Sensor I changed it to two minutes.

 

So it stays ON for 2 minutes.

 

With Fibaro, there is a Z-Wave Parameter

 

MOTION ALARM SETTINGS

6. MOTION ALARM CANCELLATION DELAY

2 - 120

 

BUT when I enable it, the motion sensor literally stops working.

It doesn't report motion no matter how fast or slow or how desperate I try to activate it.

 

I discovered this after hours and hours of testing, this one parameter doesn't work.

Link to comment
Share on other sites

Hi rafarataneneces,

 

Based on the node information, it appears as though your FGMS-001 has older firmware (pre 3.2) because it does not use the Security command class.  This shouldn't necessarily be a problem, but it is different than the unit I am testing with.

 

There are also several parameters you can specify for the motion sensor, including one that prevents from running at night or day (based on the brightness of the room).  You may want to query all the Motion Sensor/PIR parameters to see if they match what you expect.

 

This page has a lot of details of the motion sensor, including differences between the versions (you need to scroll down the page a bit to see v2.9 which is what I suspect you have):

     http://manuals.fibaro.com/motion-sensor/

 

 

Link to comment
Share on other sites

I scrolled down and I found setting 6 should do what I want but it's not working

 

6. Motion alarm cancellation delay

Motion alarm will be cancelled in the main controller and the associated devices after the period of time set in this parameter. Any motion detected during the cancellation delay time countdown will result in the countdown being restarted. In case of small values, below 10 seconds, the value of parameter 2 must be modified (PIR sensor’s “Blind Time”).

Available settings: 1-65535

Default setting: 30 (30 seconds)

Parameter size: 2 [bytes]

 

can you please try in your end?

Link to comment
Share on other sites

ok but can you try to set up motion sensor so if reports ON for two minutes and tell me if it works?

 

thanks!

 

Hi rafarataneneces,

 

My motion sensor reports On then reports Off 30 seconds later.  When I adjust the time (parameter 6) to 2 minutes, it takes a few minutes for the motion sensor to start operating again.  It now waits 2 minutes to turn the sensor Off after last motion was detected.

 

I did notice that if you activate the tamper alarm (by moving the sensor in any way), it seems to disable the motion sensor until all the alarms are reset.  When we add custom support for this sensor, we will try to find out all the specific rules for things like this.

Link to comment
Share on other sites

Well I want a RELIABLE motion sensor Insteon motion sensors have been working GREAT for the last 6 months this one gets 'stuck' in the ON position it has happened twice already.

 

I really like the device I just want it to be reliable because based on its reading I turn on/turn off the thermostat when I enter/leave the house so it's a critical function

 

has this happened to you? (stuck in ON)

Link to comment
Share on other sites

​Untreated to your issue I use the Aeotec MultiSensor 6 (http://aeotec.com/z-wave-sensor) it is z-wave and works great with my ISY.

 

Wow looks great!!

 

Can you set up motion sensor window time to 2 minutes?

 

I will try one more time with Fibaro (I will try today) and if I can't change the motion sensor I think it's time to try another sensor.

 

I can buy that one tomorrow from Amazon!

​Untreated to your issue I use the Aeotec MultiSensor 6 (http://aeotec.com/z-wave-sensor) it is z-wave and works great with my ISY.

 

How's the antenna?

 

It has good reception?

 

My impression with Fibaro is that even though I love how small it is I am afraid the battery won't last too much and the antenna is not too powerful. That is why I was thinking buying more devices so it works.

 

The ONLY way I will be able to see if this is ISY weak antenna or Fibaro weak antenna is if I can test with another Z-Wave device.

 

That motion sensor seems awesome!

Link to comment
Share on other sites

Wow it works!!!

 

Great!

 

 

 

So I think with Fibaro I have to essentially place it NEXT to the ISY lol until I expand my Z-Wave network!

 

I agree that in setting up Z-Wave, getting the network right always seems to be the biggest challenge (positioning devices etc.)

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...