@aciid st always can handle the v3.2 versions.
So no you don’t need to use this DH, but what this DH does provide you with, is a nicer and more user friendly DH from a visual viewpoint and more importantly has exposed the many different parameters within the sensor for individual configuration which the ST one does not allow.
So this DH is far superior than the ST one.
I’m curious if anyone gets the battery status to update? I have used both this custom DH and the ST DH for the last 3 weeks or so. The only time the battery status changed was when I completely rebooted the device and removed it, then reconnected it to my Hub. Any idea’s or thoughts?
I’ve discovered that this does show up a tamper sensor, rather than acceleration sensor for it’s vibration detection (now that I’m using Core Pistons). However it never triggers when I create a piston for my Fibaro’s tamper sensor, even though it does come through in SmartThings recent activity log. Any thoughts?
@Levahj my battery updates automatically. I don’t see any records in recent activity of its there you mean.
Yup, that is what I mean @KellyDarren. Nothing in the IDE showing recent battery activity. Strange that he only time the battery % even moved was when I rebooted the device. ~ 2 weeks of %100, then immediately showing down to %96 at reboot, and now another 7days with no battery % movement.
Is anyone having issues with the ZW5 stuck on motion? I’ve been experimenting with the stock as well as custom DTH, and the unit seems to get stuck on motion regardless of resets, removal, hub reboots etc.
That usually mean the unit have issue.
Thanks C. I removed, factory reset, and re-added both (new, 3.2) sensors using the stock ST handler and for the last few days at least, they are recording motion and going inactive as expected. The IDE events listing for the device is quite useful to monitor, as is CoRE to push motion detection notifications.
I’m pretty sure now that the issue I was seeing is related to cold temps. (-20C). The Sensor claims (and does measure) temps that low, but the the operating temperature in the specs is listed as 0-40C. Motion seems to stay toggled “active” at low temps. Relying on the Fibaro 3.2 Sensor outside in our climate will not work.
We dropped from around 0C to -25C yesterday and the outside Sensor stopped worked correctly. The inside one is fine.
Hello Levahj. I do miss the configuration capabilities as I have five other Fibaro sensors (not v3.2) that run beautifully on the @CyrilPeponnet DH. I tried the @CSC DH again this weekend and the sensor sends active motion traffic almost every five seconds. I tried to push a new configuration and the “sync/pending” tile in the handler stays stuck on “pending” and I’m not getting the lux updates per my settings. I tried switching back to stock ZW5 handler and none of the custom settings stuck.
I really want to get this solved because I’ve stopped buyer this sensor because I can no longer configure them which is a shame because it is by far the best sensor our there.
Any and all help would be appreciated.
@JBR- when using @CSC’ DH to update the configuration, did you first put the sensor in sync mode by triple clicking the B button behind the sensor (remove the battery case), then quickly clicking the sync button in the app to trigger the actual sync? @CSC’ s DH will still show pending even though changes have been made. Easiest way to know if the new config worked is to also change the color of the LED when you make a change.
Other than that, if the Fibaro is sending active motion every 5 seconds, sounds like the device not working correctly and not sure if any config change would help that. I would reboot the device and see if that fixes it. To do this you need to remove the device from the Z-Wave network. This , per the manual, automatically restores all the default parameters of the device. DIrections below ( go online to Fibaro to download the complete manual if you have not done so already:
Removing (Exclusion) - Z-Wave device learning mode, allowing to
remove the device from existing Z-Wave network.
To remove the device from the Z-Wave network:
@Levahj - well I finally had the time to take sensor down and removed it from ST and factory reset sensor. I then deleted the custom DH from @CSC and recopied the “_F” version of the code from GitHub and recreated the DH in the IDE. The I paired the sensor with the hub and associated it with custom DH…it works like a charm, even with my custom device settings. Feeling bullish, I decided to tackle the temperature F vs C issue, because it was F in the app and C in my SmartTiles. I reworked the temperature code and it reads perfectly across the app and SmarttTiles.
Thanks for the advice and encouragement, I’m back on board with Fibaro.
hello everyone…
i just bought this Fibaro Motion sensor (FGMS-001)
the closest i can get of a version as described on this post[quote=“bobbles, post:21, topic:52360”]
If you go into the ide and then the device it should tell you version of the sensor.
[/quote]
is this.
if i am indeed on ver 2.07, am i out of luck using this DH?
right now, i am only getting this on my smartapp
at this time, id like to use this as a temperature monitor on one our upstairs room or, id like to use it as a “vibration” monitor (as feature as shown on previous posts) for the “LAUNDRY MONITOR” smartapp.
if it helps to further describe my situation, the motion sensor is also detected as an AEON MULTISENSOR.
as always, i thank everyone for your kind help.
Try this one.
https://github.com/CyrilPeponnet/smartthings/blob/master/device-handler/FibaroMotionSensor/FibaroMotionSensor.groovy
Acknowledging that I am a bit lazy, and really “enjoy” updating through the IDE integration, but I was wondering if there is any desire to reorganize the current folder structure to allow this to be visible through the IDE directly rather than copy/paste?
GitHub Integration – Repository Structure
Example:
chancsc/SC_SmartThings/devicetypes/fibargroup/fibarMotion.src/fibarMotion.groovy
I am U.K. user and we do not have github integration, so… 
Oh, but we do.
The good news, is that just updating the folder structure within your repo means those that use it get the benefit without any further investment on your side 
@Bobbles LMAO, it exists but as you know its sooooo sllllllooooowwwwwwwwwwwwwwwww
Just started using your device handler today after the stock handler kept getting stuck on motion. So far I am liking it. Left everything in default so far. I am using the _F version of the code. My readouts look fine even though I see then in Celsius in the device settings in my IDE. The temp readout in the ST app are still reading Celsius but the device is functioning correctly as far as LEDs and ActionTiles shows the correct temp as well.
