Had similar issues to some of the people above. Support remoted in and sorted them. I don’t have any issues with range. I have one working through 2 internal walls probably 10m distance.
I received the Fibaro sensor this week (FGMS001), I can not get the motion sensor working with my Vera Plus… I’ve tried all the solutions showed on this forum… and it is not working…
Solution on this forum to get the motion sensor working with Vera Plus…
First…
at device_file → D_MotionSensor1.xml
at device_json → D_MotionSensor1.json
at category : 4
at subcategory : 3
Second…
The “Please wait…” usually means that the device went to sleep during the configuration process. Try going to the device’s settings and set Automatically Configure to Yes. They should wake it up and run it through the process. Also note, that when Gen 5/Z-Wave Plus devices are using Network Wide Inclusion that during pairing there is more data being exchanged than normal and distance can slow that down, try moving the device closer for the pairing process, it can help.
Finally… I got in touch with Vera and here what I got from them… I tried it many times, but I can not get my motion sensor working… I joined an image of my sensors… anyone of you got a solution to make it works… Please help me… Tks
Third…
[b][i]he sensor must be exclude and re-included because the sensor for the motion was seen as a generic, also the configuration wasn?t made correctly.
To exclude go on Dashboard ?> Add device ?> scroll down , choose Add Generic Z-wave device ?> next ?> next and retry, then go and do the steps on the device.
To include go on Dashboard ?> Add device ?> scroll down , choose Add Generic Z-wave device ?> next ?> next and you will see the countdown, after that do the steps on the sensor.
The steps on the sensor:
The Fibaro Motion Sensor can be included into the Z-Wave network
by using the B-button.
Insert the battery into the Fibaro Motion Sensor. Enclosure lock is marked with a dot. Make sure the device is located within the direct range of the main controller.
Set the main controller into the learning mode (see main controller?s operating manual).
Quickly, triple click the B-button ? LED diode will glow blue.
Fibaro Motion Sensor will be detected and included in the Z-Wave
network.
Wait for the main controller to configure the sensor.
If necessary, wake up the Motion Sensor by triple clicking the
B-button.
LED diode will glow blue to confirm the sensor woke up, and then
wait for the main controller to configure the sensor.
Guys… how quickly does the LUX sensor report back when changes in LUX occur? I’d like to use the LUX portion to tell me lighting levels and be able to set scenes based on it… dusk/dawn, turn off lights because there is 40 LUX in the room, etc… but I want to make sure the reporting of the LUX level is quick… like 30 seconds.
This is a quick answer bumping into this question. I just paired mine today.
Light sensor response time is from 3 to 6 seconds on a stop watch.
set up is:
sensor is on my desk facing table lamp upward about 2ft. turn on and off table lamp (10watts GE daylight led)gives the result above (3-6 sec sec). 5 trials.
Pretty darn fast on its default state. Some light sensor brands range from 2-3 minutes. Hope this helps.
I think it can also depend on how fast the LUX changes too. If it is a more gradual change, IE the sun rising slowly over a period of time, the sensor doesn’t respond as quickly. If it’s something like a light switching on and quickly changing the LUX value, it responds faster. This is off the top of my head from reading the little booklet months ago though, so prepare the firing squad if I’m wrong lol
How do I get the other sensors (motion & acceleration) to show up?
VeraPlus (firmware 1.7.2349) after a few includes/excludes it only detects it s 3-in-1 (yes its a 5-in-1 Gen5)… the 3 main devices (motion, temp, light) show up properly and work.
I am unable to configure association. Want to associate fibaro sensor with copper dimmer. It shows that it is configured correctly but does not work. anyone with the same problem? (auto configure is on)
If it is the new Zwave Plus sensor they talk encrypted by default and the older non-zwave won’t respond. To fix it you need to tell the Fibaro to send out the direct association commands in unsecure mode.
To set all association groups to unsecure for the Fibaro motion sensor you set parameter 18 to 0
Each device is a little different, so you have to look at the manual for each z-wave + device for using with mixes z-wave and z-wave+ direct association commands.