Fibaro Motion Sensor - New device-handler with all settings and auto sync feature

[CyrilPeponnet]

Hi community,

This is my very own Fibaro Motion Sensor device-handler with ALL parameters customizable and an autosync feature when the device wake up.

Feel free to comment

https://github.com/CyrilPeponnet/smartthings/tree/master/device-handler/FibaroMotionSensor

Note that there is a ST bug on iOS with preferences:

[REPORTED] Input number in device-handler weird behavior

Just to let you know guys that I have open a bug request to ST support for the following issue: When using a number input type with a default value like this: input(name:"testNumber", type:"number", title: "type number not working fine", defaultValue: "10") First time you open the preference panel and press Done it will store the default value shown in the field. Second time when you load the preference pane the text field is empy. IF you press done here, this will erase the previous value. Here are the log related to updated() callback 4c5f1ad3-4da2-4635-80ee-6bab200ec11c 2:58:24 PM PDT: debug testEnum is:Red 4c5f1ad3-4da2-4635-80ee-6bab200ec11c 2:58:24 PM PDT: debug testNumber is:null 4c5f1ad3-4da2-4635-80ee-6bab200ec11c 2:58:24 PM PDT: debug Done button has been pressed <…

[MichaelS]

Nicely done…will need to try this out…

[Mbhforum]

Looks good but does battery reporting work? This was one thing I never got working.

[CyrilPeponnet]

What do you mean ? it does work for me.

[Mbhforum]

The device type I was using has said my battery is 100% since I installed the device. I am wondering if this is the case with this device type.

[CyrilPeponnet]

Mines too but they were also reporting 100% on my previous system. Battery status is not yet complete here. I will improve it in a few days. (I was focusing on preferences so for now it only report battery upon association :p).

[CyrilPeponnet]

I just updated the code now it handler request battery status every 48h on wakeup. I also change how current properties are stored using state instead of event attribute (as it sounds to work fine now).

[Mbhforum]

Great! Keep us posted and if it’s working for you, I’ll give it a try in a few days.

[CyrilPeponnet]

Looks good to me, battery report give me:

New Zwave Event: zw device: 26, command: 8003, payload: 64

0x64 is 100. Specific value of 0xFF means low battery. (other values give the battery level).

[CyrilPeponnet]

I have fixed another potential issue. Be sure to use the latest from master.

[Mbhforum]

I am trying it out now. So far, Battery hasn’t changed yet from 100% in the preferences, but not sure how long it will take. Also, how do you change the temperature from C to F?

[CyrilPeponnet]

Good catch, I fixed it. I’d never been able to understand F

[Mbhforum]

Thanks, in the US, it’s all we understand So the only thing not working for me is the battery reporting. It still says 100%. How did you get yours to work?

[CyrilPeponnet]

I’m in the US and I still don’t understand it (not my origin country).

Battery report 100% for me too but I think it’s because it’s still 100%. The Zwave command return 0x64 which is 100 in decimal. My previous setup using Domoticz was reporting the same thing (openZwave based). So I think it’s working…

[slagle]

Pretty awesome device type man!

[CyrilPeponnet]

Note that this also a good HUB state indicator… if the sync state stay on pending for more than few hours it means that zwave commands are not beeing passed to your device and you may have to reboot the hub (powercycle, the reboot from the web page did not worked). I was scratching my head on this one trying to understand why my zwave cmd are not been taken by the device for several HOURS…

[Mbhforum]

Overall this device type is performing well and I like the updated GUI options. My battery still says 100% even though I’ve had this sensor running for a few months so I can’t see how that is proper. Also, I believe I’ve found another bug as in my buttons it says the sensor is “Moving” when it’s not. See below.

[CyrilPeponnet]

From my Readme:

Vibration is always on

This is the default behavior for tampering alerts, you should change the paramter 24 to value 4 vibration. This will report the vibration level.

[slagle]

So… I think you should submit this device type to be officially supported… just saying

[CyrilPeponnet]

Yeah but my groovy is pythonic style and some options are still missing like the way put the sensor to association group 1 and 2 for direct triggering devices (not a big deal but if I do that I have an issue with tamper alarm in vibration mode).