Thank you xcguy, i will try these 
I had my parameter 40 set down to 1 as my LUX readings seem to stay in the single digits inside the house with just sunlight in the room, unless i have really bright lights on then it goes into triple digits. Then my parameter 42 I left at 0 so will now make same adjustment to 180 and see how that works. thanks again.
Just my two cents, but setting p.40 to 1 I think will eat your battery up fast. At 50, it is still sensitive enough to report tiny changes down to zero (including the single digits), but doesnât repeatedly report a single digit in change. Check your logs to confirm.
ok I will set to 50. i thought that if set at 50 it would not report if it went say from 10 to 4 where my setting is to consider anything under 5 LUX as dark, and thats based on what i see the sensor report when i consider a dark enough room to need light.
thanks
Folks, I am trying to configure 2 Fibaro motion sensors to work with my new SmartThings hub (v2).
I have copied the latest code from CyrilPeponnet and published it to my devices, that seemed to go ok. I have the devices connected to my hub and visible in my Android phone, the sensor is reporting motion and sending alerts to my phone.
I am unable to access the configuration menu. Not sure if this is relevant or not, but I am only able to view motion, temperature, acceleration, battery, lux and configure options. I do not have sync status, activity or smart apps tiles.
I hope this isnât gibberish and someone can point me in the right direction to correct this.
Hi @fmttm,
Can you send a screenshot of the sensor status screen from your ST app? Sounds like it might be using the default motion sensor device type and not the custom device from CyrilPeponnet
Hello @adeparker,
I have attached a screen shot for reference although I no longer have an issue with the motion sensors. When I woke up this morning they were working with no LED indicators flashing, which is exactly how I want them to work. Now I will work on connecting the Sonos speaker that will interact with the motion sensors and smartthings hub.
Thanks for the reply.
After you have created the device type, you have to assign the device type to the actual device under âMy Devicesâ in the IDE. Make sure you complete that step or the device will continue to use the default SmartThings device type.
Thanks Eric, I made sure I did that yesterday. I think I was just being a little impatient with the devices yesterday with being new to this system. Appreciate the advice!
Good to hear you got them working @fmttm. Theyâre a great little device and definitely worth the added time to set them up
This is a great addition! Appreciate the efforts in making these fully customisable.
Just got my fibaro sensor and had some issues getting it set up correctly as well.
Got it working finally by restarting hub before connecting, resetting sensor to factory, putting sensor right next to hub, pairing with the standard device type, leaving it a bit, then making all the changes (name, device type to this one) on the IDE. All suggestions I picked up from various threads - not sure which helped - but the combination worked for me 
Nice work there @Yanwoo
I am now working on connecting the Sonos Play 1 speaker and having it play a mp3 file hosted on Amazon AWS. Easier than it sounds so farâŠ
I have the smartapp configured in IDE, with the parameter for DOG BARKING set to the URI for the file located in the Amazon AWS. I have the smartapp configured to use the DOG BARKING action using the Sonos speaker I have configured. I see the sensor detect the motion, I see the log event indicate the event occurred at the same time it played the sound file, but I get nothing out of the Sonos speakerâŠsigh.
Anyone have any idea where I am going wrong or what additional information you need to assist me.
FYI, I have browsed to the file hosted on Amazon and can play it, so I know its accessible.
Cheers and Happy New Year!
FMTTM
Not sure how often the author of the device frequents the forums but I sent an pm to him about this and thought I would also get forum member observations and options. This is purely detective work on my part by matching the errors in live logging and the event list.
I am getting random Err 116: Got CRC-16 that appear to be related to the Fibaro Motion Sensor using this device type. I noticed that @duncan called this out in another thread: Pre-release of Fibaro Motion Sensor
So I wanted to follow up on this with more detailed
information from my logs. Just had to wait for it happen with live
logging open and event list from the hub which I have included below.
The CRC event happened at 8:13:59. What is interesting is that the
event time in live logging is out of time sequence. Let me know what
you think. Thanks!
Live Logging Results:
0030de7e-7268-4f76-b8c7-8d679ab8925d 8:14:12 AM: debug === Parsed 'zw device: 1E, command: 5601, payload: 31 05 03 0A 00 02 27 D3 â to [[âdisplayedâ:true, ânameâ:âilluminanceâ, âvalueâ:â2â, âunitâ:âluxâ, âisStateChangeâ:false, âlinkTextâ:âFoyer Motion Sensorâ, âdescriptionTextâ:Foyer Motion Sensor illuminance is 2 lux]]
0030de7e-7268-4f76-b8c7-8d679ab8925d 8:14:12 AM: debug %%%% Multi Sensor Report
0030de7e-7268-4f76-b8c7-8d679ab8925d 8:14:12 AM: debug ==> New Zwave Event: zw device: 1E, command: 5601, payload: 31 05 03 0A 00 02 27 D3 , Battery: 1452000690060
f8947a7a-cf77-458e-a8a6-ecf03d45e72b 8:14:00 AM: info Master Bedroom Night Light Scene is False
f8947a7a-cf77-458e-a8a6-ecf03d45e72b 8:14:00 AM: info Master Bedroom Night Light Scene: Master Bedroom Motion Sensor motion active
99f2a1cd-3899-4250-8233-ad8ae7fdf258 8:13:59 AM: debug === Parsed 'zw device: 20, command: 5601, payload: 31 05 03 0A 00 02 27 D3 â to [[âdisplayedâ:true, ânameâ:âilluminanceâ, âvalueâ:â2â, âunitâ:âluxâ, âisStateChangeâ:true, âlinkTextâ:âMaster Bedroom Motion Sensorâ, âdescriptionTextâ:Master Bedroom Motion Sensor illuminance is 2 lux]]
99f2a1cd-3899-4250-8233-ad8ae7fdf258 8:13:59 AM: debug %%%% Multi Sensor Report
99f2a1cd-3899-4250-8233-ad8ae7fdf258 8:13:59 AM: debug ==> New Zwave Event: zw device: 20, command: 5601, payload: 31 05 03 0A 00 02 27 D3 , Battery: 1452055368366
99f2a1cd-3899-4250-8233-ad8ae7fdf258 8:14:00 AM: debug === Parsed 'zw device: 20, command: 2001, payload: FF â to [[ânameâ:âmotionâ, âvalueâ:âactiveâ, âdescriptionTextâ:Master Bedroom Motion Sensor detected motion , âisStateChangeâ:false, âdisplayedâ:false, âlinkTextâ:âMaster Bedroom Motion Sensorâ]]
99f2a1cd-3899-4250-8233-ad8ae7fdf258 8:14:00 AM: debug %%%% Basic Set Cmd
99f2a1cd-3899-4250-8233-ad8ae7fdf258 8:14:00 AM: debug ==> New Zwave Event: zw device: 20, command: 2001, payload: FF , Battery: 1452055368366
d020bf5b-3225-4226-8f28-9320cdc513b1 8:13:56 AM: debug === Parsed 'zw device: 11, command: 5601, payload: 31 05 03 0A 00 49 DE 7C â to [[âdisplayedâ:true, ânameâ:âilluminanceâ, âvalueâ:â73â, âunitâ:âluxâ, âisStateChangeâ:true, âlinkTextâ:âFamily Room Motion Sensorâ, âdescriptionTextâ:Family Room Motion Sensor illuminance is 73 lux]]
d020bf5b-3225-4226-8f28-9320cdc513b1 8:13:56 AM: debug %%%% Multi Sensor Report
d020bf5b-3225-4226-8f28-9320cdc513b1 8:13:56 AM: debug ==> New Zwave Event: zw device: 11, command: 5601, payload: 31 05 03 0A 00 49 DE 7C , Battery: 1452078515054
d020bf5b-3225-4226-8f28-9320cdc513b1 8:13:51 AM: debug === Parsed 'zw device: 11, command: 5601, payload: 31 05 03 0A 00 48 CE 5D â to [[âdisplayedâ:true, ânameâ:âilluminanceâ, âvalueâ:â72â, âunitâ:âluxâ, âisStateChangeâ:false, âlinkTextâ:âFamily Room Motion Sensorâ, âdescriptionTextâ:Family Room Motion Sensor illuminance is 72 lux]]
d020bf5b-3225-4226-8f28-9320cdc513b1 8:13:51 AM: debug %%%% Multi Sensor Report
d020bf5b-3225-4226-8f28-9320cdc513b1 8:13:51 AM: debug ==> New Zwave Event: zw device: 11, command: 5601, payload: 31 05 03 0A 00 48 CE 5D , Battery: 1452078515054
60707b02-933e-4443-ba73-4aea6dee4177 8:13:50 AM: debug === Parsed 'zw device: 10, command: 5601, payload: 31 05 03 0A 00 0B B6 FA â to [[âdisplayedâ:true, ânameâ:âilluminanceâ, âvalueâ:â11â, âunitâ:âluxâ, âisStateChangeâ:true, âlinkTextâ:âKitchen Motion Sensorâ, âdescriptionTextâ:Kitchen Motion Sensor illuminance is 11 lux]]
60707b02-933e-4443-ba73-4aea6dee4177 8:13:50 AM: debug %%%% Multi Sensor Report
60707b02-933e-4443-ba73-4aea6dee4177 8:13:50 AM: debug ==> New Zwave Event: zw device: 10, command: 5601, payload: 31 05 03 0A 00 0B B6 FA , Battery: 1452161764563
Hub CRC-16 Event:
Err 116: Got CRC-16 encapsulated command with bad checksum
Name Value
archivable true
date 2016-01-07 8:13:59.902 AM EST (2016-01-07T13:13:59.902Z)
description Err 116: Got CRC-16 encapsulated command with bad checksum
displayed false
eventSource HUB
hubId f24a0d06-09b7-4899-9d27-1a1c30d0e734
id 83d5abd3-b540-11e5-9d04-22000b490252
isStateChange false
isVirtualHub false
linkText La Maison Hub
locationId d76e4022-f4c8-4cd4-8141-6156c6089945
rawDescription Err 116: Got CRC-16 encapsulated command with bad checksum
translatable false
unixTime 1452172439902
value Err 116: Got CRC-16 encapsulated command with bad checksum
viewed false
Err 116 comes from the hub and shouldnât have anything to do with the device type. It just means there was a corrupted Z-Wave packet. Probably you have too much noise and/or weak signal from the sensor or on one jump in the route.
1 Like
Ok. So yesterday just for fun I relocated my hub to see if I could generate the errors again with the hub in the new location so a weak signal might not be the cause. Noise is a possible cause because I do see a lot of lux readings, sometime several in a minute. I have parameter 40 set to 50 and parameter 42 set to 180. I donât mind turning the lux readings down a bit as so long as it is in a reasonable amount of time. Any suggestions what those parameter values should be set at to get reasonable readings from the sensor? Thanks!
Iâm not able to set up a push notification for this fibaro when it senses vibration/acceleration, like i can with the Smartthings multi sensor, using Notify Me When.
Iâve placed the fibaro above my doorbell and want it on its highest vibration sensitivity and to trigger push notifications.
Iâve changed parameters 22 to 01
and parameters 24 to 4
any ideas? is this possible?
on a side note changing parameters 80,81,89 to 0 as suggested by a previous poster helped to finally lose the LED lights!
Hello , I new here , I have fibaro motion sensor and same issue with lux , can you please explain me how to fix that issue step by step? how to update motion sensor?
Does anyone else find that these devices donât detect motion quite as quickly as the Smartthings motion detector?
Any tips on values to change to help with this?
I have:
Option 1 set to 8
Option 2 set to 15
Option 3 set to 2 pulses
Option 4 set to 12 seconds
I have also noticed that this is not as fast as the SmartThings motion detector. Unfortunately my SmartThings one died after a week of using so I just got myself a fibaro one. I will let you know if I figure out what settings make it work best
Is there a device handler for the Fibaro Door Sensor as well? Default ST one only presents open/close indication and battery level.