[DEPRECATED] Fibaro Motion Detector v3.2 (Alpha Release)


(Stuart Buchanan) #1

As the newer capabilities are now in the European server Shard. Stop using my handler. Use the official handler below


Fibaro motion sensor grrrrr
Fibaro Motion Sensor USA ver 3.2 not compatible
Fibaro multi sensor fgms-001
Pre-release of Fibaro Motion Sensor
Which Fibaro Motion Sensor device-handler to use?
Which Fibaro Motion Sensor device-handler to use?
Fibaro Z-Wave Motion Sensor
Fibaro Motion Sensor won't install
Fibaro FGMS-001 Smartthings detects this a door/window sensor and just shows as open?
Fibaro Motion Sensor - New device-handler with all settings and auto sync feature
Does the new version of Fibaro motion sensor work with ST now?
Fibaro Motion Sensor Uses
(Adrian Parker) #2

Any news from @CyrilPeponnet regarding an update to his excellent custom code? Been using it on the old firmware devices with great success


(Stuart Buchanan) #3

Your assuming of course that @CyrilPeponnet has a new v3.2 device or indeed needs one in the near future! But the code difference is documented in the code above if you want to amend his device type.


(Cyril Peponnet) #4

I don’t have the time right now and I don’t have a 3.2 version. Pull Requests are welcome if you can make it works for both firmware release.


(Brian) #5

Just an update on this.

I have 2 sensors using this device type both have been re-added after being excluded. Both correctly identified the device type and are reporting Motion, Temp and Vibration. One is correctly reporting Lux the other is not…May be a sensor issue…nope works now

Will give another update in 24hrs

My hat goes off to @Fuzzyligic who has done all the hard work and made this available.


#6

Finally got my IDE working again. Tested this on my new motion sensor, all good so far


(Jaideep Punwani) #7

Thank you very much for the device handler. Great job!
I have two of the new v3.2s and couldn’t get them to work before using this device handler.
All sensors, motion, temp, lux & vibration seem to be working. I say seem to, because the vibration notification got stuck to on when I moved one of the sensors. Had to shake it again to remove the blue background in the app. Almost like a toggle switch.


(Patrick) #8

I’m not having any luck with the new device handler. I have six of these new English 3.2 sensors sitting on my computer desk.

Steps Taken:

  • Removed All Fibro Motion Devices from my IDE
  • Deleted old device handler
  • Installed device handler above.
  • Re-paired my devices through the app
  • Switched the device type to the new handler in the IDE

Results:

  • App reports constant motion and vibration.
  • All other tiles are blank

Any help is appreciated. I will happily be a tester if that would help.


(Stuart Buchanan) #9

ok so describing what steps you have completed the device configuration would not have been completed correctly on the device and the correct association groups would not have been joined.
You need to install the handler on the device from device handler page so you can see the simulator, then you need to tile click the button on the device and click SetSTDefaults to attempt configuration wait 5 mins Once done click uninstall and do the same to the next one.

Weird if warning though until at fix the delay and delaybetween functions the configuration has got a lot harder for zwave devices. You may have to try multiple times. You can click listSTDefaults to list the config. What you need to check is that the node Id of 1 Is a member of the association groups listed.


(Patrick) #10

Fuzzy, thanks for the reply and help. Unfortunately I still can’t get it to work. I will post my trials and results below:

  • Install the Device Handler
  • Connect the device to the hub
  • Open the Device handler and set up the Simulator
    • (in debugger) set Location to Home,
    • Choose a device to test with: (device)
      • selected "Z-Wave Sensor (The newly connected Fibaro)
      • clicked install
        *At this point with the new device handler simulating the following options are available"
      • resetParams2STDefaults, listCurrentParams, updateZwaveParam, test, configure
      • I triple clicked the setup button on the device and then cycled through all the options waiting 5 minutes each time.
    • Ultimately I would get the β€œlog.debug” command in the Log window, but very little else.

Do you have any other advice?

Thanks!


(Stuart Buchanan) #11

so when you clicked ListCurrentParams whilst the device was showing the Blue LED, it should have reported its configuration to the live logging window with multiple debug entries. if you post the result of that i can see if its in the association groups


(Patrick) #12

Below is the log read bottom to top for pressing a the simulator buttons while in (device blue setup mode)

  • debug Listing of current parameter settings of Z-Wave Sensor
    *[Pressed listCurrentParams]

  • debug Parse returned [[isStateChange:false, displayed:false, linkText:Z-Wave Sensor]]

  • debug Catchall reached for cmd: VersionReport(applicationSubVersion: 2, applicationVersion: 3, zWaveLibraryType: 3, zWaveProtocolSubVersion: 5, zWaveProtocolVersion: 4)}

  • debug Parse returned [[isStateChange:false, displayed:false, linkText:Z-Wave Sensor]]

  • debug Catchall reached for cmd: VersionReport(applicationSubVersion: 2, applicationVersion: 3, zWaveLibraryType: 3, zWaveProtocolSubVersion: 5, zWaveProtocolVersion: 4)}

  • debug Parse returned [[isStateChange:false, displayed:false, linkText:Z-Wave Sensor]]

  • debug Catchall reached for cmd: VersionReport(applicationSubVersion: 2, applicationVersion: 3, zWaveLibraryType: 3, zWaveProtocolSubVersion: 5, zWaveProtocolVersion: 4)}

  • debug Parse returned [[name:battery, value:100, unit:%, displayed:false, isStateChange:true, linkText:Z-Wave Sensor, descriptionText:Z-Wave Sensor battery is 100%]]

  • debug BatteryReport(batteryLevel: 100)

  • debug Configuring Device For SmartThings Use
    [Pressed configure]

  • debug Listing of current parameter settings of Z-Wave Sensor
    [Pressed listCurrentParams]

  • debug Resetting Sensor Parameters to SmartThings Compatible Defaults
    *[Pressed resetParams2StDefaults]


(Patrick) #13

This is the log from a different sensor following the same steps…

The tiles for this one show

  • Constant Motion

  • 100% battery

  • No Lux

  • No Temp

  • Vibration seems to be working

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:35:21 PM: debug Parse returned [[isStateChange:false, displayed:false, linkText:Fibaro Motion Sensor v3.2]]

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:35:21 PM: debug Catchall reached for cmd: BasicSet(value: 255)}

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:35:21 PM: debug Parse returned [[isStateChange:false, displayed:false, linkText:Fibaro Motion Sensor v3.2]]

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:35:21 PM: debug Catchall reached for cmd: SensorBinaryReport(sensorValue: 255)}

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:35:18 PM: debug Configuring Device For SmartThings Use

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:33:07 PM: debug Parse returned [[isStateChange:false, displayed:false, linkText:Fibaro Motion Sensor v3.2]]

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:33:07 PM: debug Catchall reached for cmd: SensorAlarmReport(seconds: 0, sensorState: 0, sensorType: 0, sourceNodeId: 17)}

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:33:06 PM: debug Parse returned [[name:acceleration, value:inactive, descriptionText:Fibaro Motion Sensor v3.2 Vibration No Longer Detected, isStateChange:true, displayed:true, linkText:Fibaro Motion Sensor v3.2]]

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:33:06 PM: debug Vibration No Longer Detected

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:33:06 PM: debug Hit notifcation Section with command : NotificationReport(event: 0, eventParameter: [3], eventParametersLength: 1, notificationStatus: 255, notificationType: 7, reserved61: 0, sequence: false, v1AlarmLevel: 0, v1AlarmType: 0, zensorNetSourceNodeId: 0)

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:33:06 PM: debug Parse returned [[isStateChange:false, displayed:false, linkText:Fibaro Motion Sensor v3.2]]

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:33:06 PM: debug Catchall reached for cmd: BasicSet(value: 0)}

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:33:06 PM: debug Parse returned [[isStateChange:false, displayed:false, linkText:Fibaro Motion Sensor v3.2]]

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:33:06 PM: debug Catchall reached for cmd: SensorBinaryReport(sensorValue: 0)}

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:33:05 PM: debug Parse returned [[isStateChange:false, displayed:false, linkText:Fibaro Motion Sensor v3.2]]

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:33:05 PM: debug Catchall reached for cmd: SensorBinaryReport(sensorValue: 0)}

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:47 PM: debug Fibaro Motion Sensor v3.2 parameter β€˜66’ with a byte size of β€˜2’ is set to β€˜[0, 0]’

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:46 PM: debug Parse returned [[name:battery, value:100, unit:%, displayed:false, isStateChange:false, linkText:Fibaro Motion Sensor v3.2, descriptionText:Fibaro Motion Sensor v3.2 battery is 100%]]

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:46 PM: debug BatteryReport(batteryLevel: 100)

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:39 PM: debug Fibaro Motion Sensor v3.2 parameter β€˜60’ with a byte size of β€˜2’ is set to β€˜[0, 5]’

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:40 PM: debug Fibaro Motion Sensor v3.2 parameter β€˜24’ with a byte size of β€˜1’ is set to β€˜[0]’

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:33 PM: debug Fibaro Motion Sensor v3.2 parameter β€˜42’ with a byte size of β€˜2’ is set to β€˜[14, 16]’

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:33 PM: debug Fibaro Motion Sensor v3.2 parameter β€˜28’ with a byte size of β€˜1’ is set to β€˜[0]’

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:33 PM: debug Fibaro Motion Sensor v3.2 parameter β€˜40’ with a byte size of β€˜2’ is set to β€˜[0, 200]’

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:29 PM: debug Fibaro Motion Sensor v3.2 parameter β€˜20’ with a byte size of β€˜1’ is set to β€˜[20]’

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:28 PM: debug Fibaro Motion Sensor v3.2 parameter β€˜87’ with a byte size of β€˜2’ is set to β€˜[0, 28]’

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:28 PM: debug Fibaro Motion Sensor v3.2 parameter β€˜87’ with a byte size of β€˜2’ is set to β€˜[0, 28]’

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:28 PM: debug Fibaro Motion Sensor v3.2 parameter β€˜86’ with a byte size of β€˜2’ is set to β€˜[0, 18]’

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:28 PM: debug Fibaro Motion Sensor v3.2 parameter β€˜89’ with a byte size of β€˜1’ is set to β€˜[1]’

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:28 PM: debug Fibaro Motion Sensor v3.2 parameter β€˜86’ with a byte size of β€˜2’ is set to β€˜[0, 18]’

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:27 PM: debug Fibaro Motion Sensor v3.2 parameter β€˜82’ with a byte size of β€˜2’ is set to β€˜[0, 100]’

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:27 PM: debug Fibaro Motion Sensor v3.2 parameter β€˜87’ with a byte size of β€˜2’ is set to β€˜[0, 28]’

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:27 PM: debug Fibaro Motion Sensor v3.2 parameter β€˜86’ with a byte size of β€˜2’ is set to β€˜[0, 18]’

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:27 PM: debug Fibaro Motion Sensor v3.2 parameter β€˜86’ with a byte size of β€˜2’ is set to β€˜[0, 18]’

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:26 PM: debug Parse returned [8002, 8408, [descriptionText:Fibaro Motion Sensor v3.2 woke up, isStateChange:false, displayed:false, linkText:Fibaro Motion Sensor v3.2]]

  • a8686f13-e522-4e1b-84ce-cd98add032e3 9:32:08 PM: debug Listing of current parameter settings of Fibaro Motion Sensor v3.2


(Stuart Buchanan) #14

From those logs i cannot see the association groups. But as long as you confirm these logs were attempted whilst the sensors led was lit blue after triple clicking the button. It does appear that you are afflicted with the delay between issue. I added some zwave devices last week and it took over 20 attempts on each one to configure because of the same issue.

What i suggest is triple clicking ad immediately when the led is blue hit resetParams2STDefaults. Don’t do anything else until the blue led stops. Then do the same again another 2 times. Then triple click again and hit listSTDefaults. I does look to just be a configuration issue because of the DelayBeyween issue… Or you can wait until the food is live. If not had confirmation it’s live yet.


(kylan) #15

Hey. Thank you very much for this. i have 5 of the newer sensors and this works pretty much perfect for all but one but i think its just the sensor location. id like to be able to adjust the settings to make it more sensitive like i can with this handler i use for my older sensors Fibaro Motion Sensor - New device-handler with all settings and auto sync feature

am i missing something or is there a way to adjust all the settings like the other handler yet?

Thanks in advance


(Stuart Buchanan) #16

Just look at the code block resetParams2STDefaults just change your parameters there, they are all listed with the default values. Then install on the device from the device handler page so it shows the simulator, the triple click the sensors button and hit the resetParams2STDefaults button in the simulator to send the Config parameters to the device


(Gareth) #17

I’ve noticed that I have been able to update the device parameters much more consistently since the update on Thursday. I’m not sure if this is coincidence or not…be interested to know if other people are noticing the difference. Thanks for the advice @Fuzzyligic, I thought I was doing something wrong with the updating of parameters but seems to work fine now…


(Stuart Buchanan) #18

yes the Delay and DelayBetween functions that this Device Handler and many more Zwave Device Handlers rely upon has now been resolved. I did some testing and it definitely now seems to be that case.


(Jon) #19

Just getting my head round all this…

think I’ve followed the thread and information in it, but, one question I have is why does nothing happen when i click on configure button on iphone app?


(Stuart Buchanan) #20

Nothing will happen on the phone by pressing it you attempt the configuration of the device (should only be doen when the device has been triple clicked and is lit up blue), if you log into the IDE you will see a statement about configuring etc… but thats it. whats the issue you are having? if motion/temp/lux & Tamper are working the configuration is already complete.