Thanks for the update. Just did a test and the temp is not converting to fahrenheit, so it does show the correct “temperature” however it shows it in Celsius. Which at least makes it reasonable and working (showing Blue if cold, showing Red if hot).
I also just wanted to again thank you for the work on this whole thing. It really makes this expensive motion sensor very valuable in my ST setup. So 2 very big thumbs up to you Chan!!!
Okay this is odd. I just checked the device and it is now showing it in Fahrenheit (and correctly).
So again, when I did the configure (the 3 B button step + sync) it inititally showed the temps in Celsius (but again the correct value, so say 22 degrees for the room it is in). But now, an hour later, it shows it in Fahrenheit at 72 degrees.
Odd, but hey, it works!!!
Thank you - that fixed the temperature reporting issue for me (Farenheit user)! 
Looking forward to playing around with the device parameters later this week (Fibaro manual: http://manuals.fibaro.com/content/manuals/en/FGMS-001/FGMS-001-EN-T-v2.0.pdf).
Thanks for sharing your parameters. I too had the constant motion start/stop logging with the DH, but not in the stock ZW5 handler. Did your parameters fix this motion sensitivity/false readings?
Not quite understand with your problem, can you explain it a bit more, so can I check the issue
Update:
The FibaroMotionSensor_F.groovy DH allows me to see the correct temperature reported when viewing the Fibaro motion sensor “Right Now” screen, but I’m getting false alarms on a custom Smart Home Monitor that I setup (text message when temperature drops below 50 degrees). I end up getting a message “Extreme temperature of 23 has been detected in the Motion Sensor - Utility Room” (it’s obviously using the 23 degrees Celcius to trigger the alert). …as such, my custom rule to notify when temperature exceeds 110 degrees (max operating range of my networking gear) will also not work (it would only trigger on 110 degrees Celcius).
FYI: I have three devices using the same temperature monitoring rules in SmartThings (two Fibaro moisture detectors + the Fibaro motion sensor in my utility room). …I realize I could temporarily resolve this issue by using separate custom rules for the moisture sensors vs. the motion sensor, but that doesn’t scale well.
I’ve noticed that the sensor doesn’t seems to be sensitive enough when it comes to motion, by the time it detects its too long , any ideas which settings to change?
Check the parameter
Fibaro manual: http://manuals.fibaro.com/content/manuals/en/FGMS-001/FGMS-001-EN-T-v2.0.pdf3
Hi,
I just received my 3.2 EU version of the sensor (I have 3 other older sensors working on another device handler) and I’m struggling with getting it to sync. It detects motion, tamper and temperature all ok but I want to change some settings to match my other devices.
I’ve tried triple clicking the button, going into the settings for the device in the app whilst the light is blue and confirming the settings. I tried triple clicking, going into the settings in the IDE for the device whilst the light is blue and confirming the settings. I’ve tried deleting and re-adding the device to smartthings.
This is what is displayed in the IDE logs when I triple click, change some settings (either in app or IDE) then click the pending tile in the app. I see that it says the Configuration Set has been run. Does this mean it is working ok and just ignore the Sync tile?
1027af18-7073-46b2-bd49-547deeef3446 22:30:59: debug productTypeId: 2049
1027af18-7073-46b2-bd49-547deeef3446 22:30:59: debug productId: 4097
1027af18-7073-46b2-bd49-547deeef3446 22:30:59: debug manufacturerName: Fibargroup
1027af18-7073-46b2-bd49-547deeef3446 22:30:59: debug manufacturerId: 271
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: info [ConfigurationSet(configurationValue: [10], defaultValue: false, parameterNumber: 1, reserved11: 0, scaledConfigurationValue: 10, size: 1), ConfigurationSet(configurationValue: [15], defaultValue: false, parameterNumber: 2, reserved11: 0, scaledConfigurationValue: 15, size: 1), ConfigurationSet(configurationValue: [1], defaultValue: false, parameterNumber: 3, reserved11: 0, scaledConfigurationValue: 1, size: 1), ConfigurationSet(configurationValue: [2], defaultValue: false, parameterNumber: 4, reserved11: 0, scaledConfigurationValue: 2, size: 1), ConfigurationSet(configurationValue: [0, 30], defaultValue: false, parameterNumber: 6, reserved11: 0, scaledConfigurationValue: 30, size: 2), ConfigurationSet(configurationValue: [0], defaultValue: false, parameterNumber: 8, reserved11: 0, scaledConfigurationValue: 0, size: 1), ConfigurationSet(configurationValue: [0, 200], defaultValue: false, parameterNumber: 9, reserved11: 0, scaledConfigurationValue: 200, size: 2), ConfigurationSet(configurationValue: [0], defaultValue: false, parameterNumber: 12, reserved11: 0, scaledConfigurationValue: 0, size: 1), ConfigurationSet(configurationValue: [255], defaultValue: false, parameterNumber: 14, reserved11: 0, scaledConfigurationValue: 255, size: 1), ConfigurationSet(configurationValue: [0], defaultValue: false, parameterNumber: 16, reserved11: 0, scaledConfigurationValue: 0, size: 1), ConfigurationSet(configurationValue: [15], defaultValue: false, parameterNumber: 20, reserved11: 0, scaledConfigurationValue: 15, size: 1), ConfigurationSet(configurationValue: [0, 30], defaultValue: false, parameterNumber: 22, reserved11: 0, scaledConfigurationValue: 30, size: 2), ConfigurationSet(configurationValue: [4], defaultValue: false, parameterNumber: 24, reserved11: 0, scaledConfigurationValue: 4, size: 1), ConfigurationSet(configurationValue: [0], defaultValue: false, parameterNumber: 26, reserved11: 0, scaledConfigurationValue: 0, size: 1), ConfigurationSet(configurationValue: [0, 0], defaultValue: false, parameterNumber: 40, reserved…[TRUNCATED]
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 89 will be updated to 1
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 87 will be updated to 25
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 83 will be updated to 1000
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 82 will be updated to 100
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 81 will be updated to 50
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 86 will be updated to 15
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 64 will be updated to 0
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 62 will be updated to 900
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 80 will be updated to 10
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 66 will be updated to 0
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 60 will be updated to 5
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 42 will be updated to 1800
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 26 will be updated to 0
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 40 will be updated to 0
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 24 will be updated to 4
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 14 will be updated to 255
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 16 will be updated to 0
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 12 will be updated to 0
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 9 will be updated to 200
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Parameter 4 will be updated to 2
1027af18-7073-46b2-bd49-547deeef3446 22:30:53: debug Executing 'configure’
1027af18-7073-46b2-bd49-547deeef3446 22:30:50: debug productTypeId: 2049
1027af18-7073-46b2-bd49-547deeef3446 22:30:50: debug productId: 4097
1027af18-7073-46b2-bd49-547deeef3446 22:30:50: debug manufacturerName: Fibargroup
1027af18-7073-46b2-bd49-547deeef3446 22:30:50: debug manufacturerId: 271
Yes, one way to confirm the sync is to change the color of sensor when detect motion, you can then verify the sync.
Ok I think its working. I turned off the police flashing lights on the tamper alarm and it seems to have stuck.
The only difference between my old sensors and the new one is the temperature readings. My old sensors only record every 0.5 degrees of change and send an update to the controller every 15 mins. I.E. the temp will only ever be 20.0 or 20.5, etc. The new one seems to be ignoring parameter 60. It has recently recorded the temperature as 22.4 and 22.3. The default is 1 degree so not sure why it is doing increments as little as 0.1. It’s still only sending the results to the controller once every 15 mins so I don’t think it’s a huge deal and hopefully won’t sap the battery too much more than the others.
I also updated line 477 of the code to: isUpdateNeeded = “NO” purely to get rid of the “Pending” on the tile. I know it’s not a proper fix but it was driving me crazy. 
Sorry I know this is a very basic question. How do I install this. I have created the device handler (I understand that bit) but how do I actually add the device. I assume there is more than just the device handler I need to add.
Ok so you have your device handler.
Have you actually connected your device yet?
If not you need to go into the Marketplace, things and then connect new things.
On the Fibaro press the button 3 times to get it to associate with the hub.
When it’s associated you can go into the ide and change the DTH to the one you have downloaded, if not already allocated to it.
I really appreciate the response. I tried ST a while ago but gave up as the forum was so unresponsive to my basic questions.
So I connected the device and simple changed the drop-down “TYPE” to the one DTH created "FIBARO MOTION SENSOR SC"
Thanks again for the help.
Its seems Lux is reading very strangely - Sitting in a room in daylight it report 3 Lux then shine a torch on it and i’m getting reading over a 1000 which is what I would expect. Perhaps I have a setting wrong. Any advice on this please?
@JBR i keep getting this with one of my sensors and I have to take it off the wall and re-synch. Have you come up with a solution yet
These are my current settings, I’ll see if they make a difference
It kept sticking or just outright failing to trigger so I reset the motion sensor and now just using the stock DH. It’s not as customized as I would like, but at least it works. Not sure why Fibaro changed their bios in the new 3.2 version of this great motion sensor but it seems to me they wanted to keep the sensor customization for their own platform. It’s still a better sensor than anything else out there.
Great code, thanks for creating @CSC. I’m using with my version 3.2 fibaro to change parameters. All is well.
Any plans to update/fix the pending tile?
It’s actually working, just not updated on UI, so I will leave it for now
Do you mean once the fibaro is updated, the tile changes from “pending” to “synced”? Mine is stuck on pending even though I know the parameter changes have been accepted.
