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

Devices & Integrations Community Created Device Types
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!

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

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]

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

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.

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

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

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…

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.

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?

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.

21

Thanks for getting back,

At moment it just shows motion active all the time

22

Sensor has not reported temp for 7 hours, its been reporting lux and motion ok though…any ideas how to rectify?

23

Just looking at parameters in above code block

eg Parameter no. 40 has (0,200) listed, what is the ‘0’ for as default value is 200

24

I do. it will be the configuration not being complete .i.e its not joined all the association groups that are needed. sorry but im heading off out so dont have time to document now. will follow up tomorrow with some instructions…uynless of course someone else wants to chime in with some help.

1 Like
25

Parameter 40 is 'Illumination report threshold. 200 is the default setting. i.e. 200 lux. Quote. The parameter determines the change in light intensity level resulting in illumination report being sent to the main controller. Available settings:0-65535. 0=repoerts not sent.

26

If you look at the second page of the PDF manual all the parameters are listed with explainations…http://www.fibaro.com/manuals/en/Motion-Sensor/Motion-Sensor_EN_5.3.14.pdf

27

I’m not finding any significant change in the number of lux reports if I lower that parameter. Maybe it’s me misunderstanding it but I would expect more responsive behaviour to light changes… This hasn’t been the case.

28

yes ive printed off the full manual

but the code in ide is

cmds << zwave.configurationV1.configurationSet(configurationValue: [0,200], parameterNumber: 40, size: 2).format()

why does the value have a [0,200] instead of [200]??

29

Parameter 60 - Temparature Report Threshold. "The parameter determines the change in level of temparature resulting in temp report being sent to the main controller. Available settings: 0-255 (0.1 - 25.5C; 0= reports are not sent) Default setting: 10 (1C)
So, what value have you got for param 60?