Here’s what I wrote:
So this one app will be able to service many devices. It also puts the configuration capability high up on the shelf. Away from the people not meaning to change something, but they’re curious and start pushing buttons cuz the blinky light thingy doesn’t work anymore (battery dead or something).
Keep up the discussion/argument though. I’d like to hear from more users before the official release.
I can see this from both sides, first thought is that these belong with the device. Second thought was within a smart app.
Reason being, it may allow for group application, or at lease storage of the parameters.
Most devices don’t have anywhere near the parameters of this device, so going into each device tile for say 10 of these, to then configure 5 to 10 parameters…, That becomes an exercise to be sure
.
One smart app, one pile of preferences per device type, then select the device, wake it up (if required), apply the global settings…
When you think of configuring a pile of devices, the smart app approach makes more sense.
You can always remove the app when done anyway.
Todd, just a thought, some central database somewhere where all these parameters could be stored and maintained by the community?, the smart app pulling from this repository?
Certainly more work up front, but self sustaining in the long run.
This is great and made me order a Fibaro motion sensor. I am using Tasker and Sharptools plugin making it possible to do lots of stuff! I am hoping that one will be able to set the led color and intensity either in the device preferences since that would simplify doing things with tasker and sharptools, or possibly in another app as wackware is talking about.
If it was to be set in another smart app that is for more delicate settings, if I set status away in smartthings with tasker and sharptools when disconnecting from my home wifi the other preferences smart app should be able to trigger on that and set the led color to red and change brightness of led for example? Ie I dont need the settings in the device preferences but it would be nice since I then could query the states with sharptools?
Also, when will the device be released officialy to ST? Should I wait or use the pre-release?
The pre-release code from @wackware works VERY well (as is typical with his code! 
). I wouldn’t wait!
Recvd. the second one today and temporarily putting it in covered front porch and see how it goes regarding the motion thing. Hope it doesn’t bombard me like the aeons even with passing clouds, change in sunlight etc. even though the literature warns about these.
I will suggest and totally agree with @brianlees that @wackware’s code works superb and there is no need to wait. And these are difficult to get and are awesome and can’t stress enough how cute these are. 
Update: no false alarm as of now but it is cloudy outside and not much variance in passing cloud or sunlight. Temperature is stabilizing towards the correct temp. Was showing the inside temp. for a while where I installed it by the hub. It is going down towards the actual outside temp. gradually.
@brianlees @smart Works great! Installed during the weekend and really happy with it getting push notifications via @joshua_lyon Sharptools plugin for tasker and creating my own notifications on android. Looking forward to possibility to adjust led brightness and color (want it to blink red when away and green when at home) thanks for the great work @wackware .
For those with lux issues try re-pairing and don’t further setup. Pull the battery from the sensor and see if it shows. Following this approach has worked for several of my Fibaro devices. Once everything shows as expected I set them up with desired actions.
Using the default parameters, LUX will only report changes of 200 LUX or more. Pulling the battery won’t change this.
@Mike_Maxwell is absolutely correct and helped me understand the whole thing. Will go by his suggestion tmrw. Couldn’t do it in the last two days due to emergency roofing which set me back 20K and now I don’t have the dough to get anymore device. 
Look for the thread “interpreting lux values” from me. So depressed and shocked at this point that I don’t have the energy to look and post it here. Just wanted to help If I can.
Could someone please post the FCC id off the device? I’m unable to find a reference to it in the fcc application list.
Thanks!
Hi Everyone…
Loving the active community here. It’s been hugely helpful.
I’m hitting a snag on Fibaro and trying to figure if the device is fubar or not. At this point, I’ve:
In each case (four times now, waiting 1/2 hour just in case), it detects motion correctly only. The Vibration is on constantly and it reports the (wrong) temperature once when first pairs and never again. Tried holding it to warm up and putting in fridge for 5 minutes. No temperature change. Motion always detected. No lux / no battery, just dashes each time. Nothing in the activity monitor for either of those and live logging shows no bits for that.
Any tips for what I might be doing wrong? After each time, I would remove the Thing from the graph.api account, kill the app and reboot the phone, reset the Fibaro (hold for 6 seconds to amber, press once, wait til pulses red, then off), remove the battery for a minute, and put the battery back in and repeat the pairing. Also repasted the code once to be safe.
Appreciate any help. As I’m only 3 days in and not yet scripting, can’t return the favor yet, but I will.
I found rebooting the hub before pairing did the trick.
Cool, will try that. Thanks!
You may also want to turn on “Live Messaging” from the IDE to see any other clues. This is how I saw “Z-Wave UART error” that a reboot seemed to fix.
One final one… Another user suggests not to configure immediately after pairing, let it age so to speak before changing name, etc.
I have 5 of these now, my steps:
-Pair near hub
-re-name/set to group in ide
-wake up/apply custom parameters
-set in final location
-add to activities
Not had an issue with any of them, and the above process end to end is like 5 minutes.
Battery initially reports on pairing, I don’t expect to see another until it drops significantly.
Temps reported seem reasonable, I’ve not compared to a reference.
LUX appears very accurate, I compared one level last night with a standalone meter, will provide more updates later today.
As others have noted motion response is delayed slightly over ST V2 motion, however this default sensitivity ignores the cat.
If your install doesn’t go similar to mine, or similar to other pairings in your environment then something’s up with the device.
Really appreciate the suggestions. Spent a 1/2 hour on it (which probably means something is wrong… spread out over this evening to let it age each time). I tried the steps @beckwith suggested, both creating the device in the IDE and creating it in the app, two times each, both after rebooting Hub and resetting device, removing the battery. Also followed @Mike_Maxwell’s steps twice for good measure .
Pasting the log from when it was discovered and paired on the network. Anything leap out/missing?
Sorry to be a pest, but definitely thankful for the pointers.
37d8845d-33a1-495d-91aa-f55a310afddf 12:17:14 AM: debug Parse returned [[isStateChange:false, displayed:false, linkText:Fibaro Motion Sensor]]
37d8845d-33a1-495d-91aa-f55a310afddf 12:16:53 AM: debug Parse returned [[value:active, name:motion, descriptionText:Fibaro Motion Sensor detected motion, isStateChange:true, displayed:true, linkText:Fibaro Motion Sensor]]
37d8845d-33a1-495d-91aa-f55a310afddf 12:16:53 AM: debug Parse returned [[isStateChange:false, displayed:false, linkText:Fibaro Motion Sensor]]
37d8845d-33a1-495d-91aa-f55a310afddf 12:16:53 AM: debug Catchall reached for cmd: Crc16Encap(checksum: 203, command: 3, commandClass: 48, data: [255, 209])}
37d8845d-33a1-495d-91aa-f55a310afddf 12:16:44 AM: debug Parse returned [[value:83.8, unit:F, name:temperature, isStateChange:true, displayed:true, linkText:Fibaro Motion Sensor, descriptionText:Fibaro Motion Sensor temperature is 83.8°F]]
37d8845d-33a1-495d-91aa-f55a310afddf 12:16:44 AM: debug Parse returned [[isStateChange:false, displayed:false, linkText:Fibaro Motion Sensor]]
37d8845d-33a1-495d-91aa-f55a310afddf 12:16:44 AM: debug Catchall reached for cmd: Crc16Encap(checksum: 230, command: 3, commandClass: 128, data: [100, 29])}
37d8845d-33a1-495d-91aa-f55a310afddf 12:16:12 AM: debug Fibaro Motion Sensor parameter ‘60’ with a byte size of ‘1’ is set to '[5]'
37d8845d-33a1-495d-91aa-f55a310afddf 12:16:11 AM: debug Fibaro Motion Sensor parameter ‘24’ with a byte size of ‘1’ is set to '[4]'
37d8845d-33a1-495d-91aa-f55a310afddf 12:16:10 AM: debug Parse returned [[descriptionText:Fibaro Motion Sensor MSR: 010F-0800-2001, isStateChange:false, displayed:false, linkText:Fibaro Motion Sensor]]
37d8845d-33a1-495d-91aa-f55a310afddf 12:16:10 AM: debug Configuring Device For SmartThings Use
37d8845d-33a1-495d-91aa-f55a310afddf 12:16:10 AM: debug msr: 010F-0800-2001
09ed6f25-b9ca-4575-98d5-a7b203e0564e 12:16:10 AM: trace NON-HUE EVENT Fibaro Motion Sensor updated
09ed6f25-b9ca-4575-98d5-a7b203e0564e 12:16:10 AM: info LOCATION HANDLER: Fibaro Motion Sensor updated
37d8845d-33a1-495d-91aa-f55a310afddf 12:16:09 AM: debug Parse returned [8404001C2001, 7204]
37d8845d-33a1-495d-91aa-f55a310afddf 12:16:09 AM: warn Exception ‘java.lang.StringIndexOutOfBoundsException: String index out of range: 3’ encountered parsing 'cmd: upda, payload: ted’
37d8845d-33a1-495d-91aa-f55a310afddf 12:16:09 AM: debug Configuring Device For SmartThings Use
09ed6f25-b9ca-4575-98d5-a7b203e0564e 12:16:08 AM: trace NON-HUE EVENT Thing added
09ed6f25-b9ca-4575-98d5-a7b203e0564e 12:16:08 AM: info LOCATION HANDLER: Thing added
09ed6f25-b9ca-4575-98d5-a7b203e0564e 12:16:08 AM: trace NON-HUE EVENT zwStatus:ready:Z-Wave device inclusion finished
09ed6f25-b9ca-4575-98d5-a7b203e0564e 12:16:08 AM: info LOCATION HANDLER: zwStatus:ready:Z-Wave device inclusion finished
09ed6f25-b9ca-4575-98d5-a7b203e0564e 12:16:08 AM: trace NON-HUE EVENT desc: 0 0 0x2001 0 0 0 10 0x30 0x84 0x85 0x80 0x8F 0x56 0x72 0x86 0x70 0x8E 0x31 0x9C 0xEF 0x30 0x31 0x9C
09ed6f25-b9ca-4575-98d5-a7b203e0564e 12:16:08 AM: info LOCATION HANDLER: desc: 0 0 0x2001 0 0 0 10 0x30 0x84 0x85 0x80 0x8F 0x56 0x72 0x86 0x70 0x8E 0x31 0x9C 0xEF 0x30 0x31 0x9C
09ed6f25-b9ca-4575-98d5-a7b203e0564e 12:16:06 AM: trace NON-HUE EVENT zwStatus:device inclusion:Z-Wave device inclusion started
09ed6f25-b9ca-4575-98d5-a7b203e0564e 12:16:06 AM: info LOCATION HANDLER: zwStatus:device inclusion:Z-Wave device inclusion started
09ed6f25-b9ca-4575-98d5-a7b203e0564e 12:16:04 AM: trace NON-HUE EVENT zwStatus:include search:Z-Wave include search started
09ed6f25-b9ca-4575-98d5-a7b203e0564e 12:16:04 AM: info LOCATION HANDLER: zwStatus:include search:Z-Wave include search started
Was able to add two of these to the network and waiting on 3 more. Will post an update when I try adding them.
It appears that there is something going on. The ID is changing back and forth and the NON-HUE is not something I’ve seen. Please forward this to support.
Do you have a Hue Bridge and Hue devices?
TIA
I do and have them connected re the Hue. Sent over to support… will post what I hear back. Thanks!
@brianless I have both the first gen and second gen smart things motion sensor and found the 1st generation to have less range than the second generation. The second generation has about the same range from my testing as the ecolink motion sensor. Speaking of which has anyone noticed the increase in price for the ecolink motion sensor, it was like $35 on amazon and now can only find it for $55 at that price i rather get the smartthings motion.