Thanks for getting back,
At moment it just shows motion active all the time
Thanks for getting back,
At moment it just shows motion active all the time
Sensor has not reported temp for 7 hours, its been reporting lux and motion ok thoughā¦any ideas how to rectify?
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
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.
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.
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
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.
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]??
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?
and it shows
cmds << zwave.configurationV1.configurationSet(configurationValue: [0,0], parameterNumber: 60, size: 2).format()
for parameter 60
I have mine set to 100 and it seems to report OK to lux changes of 1.
I would think it should be 0,10 to give the default value.
yes thats what i thought, but iāve not touched the code and it showed what i quoted above
To be honest this app doesnāt work too well with my Fibaro Motion Sensor. Perhaps Iām at the wrong firmware level.
I am using this device handler:-
/**
I find this works well for me and it is easy to change the settings when the device is loaded and working.
not sure whats going on with mine as it seems to work ok for a while (30 mins or so) then it just gets āstuckā showing motion continuously.
Yup. Mine shows motion continuosly and vibration continuosly with this device handler.
I your using Cyrilās device type and it works itās definitely the wrong version of firmware you have. This is only for the very latest models
I your using Cyrilās device type and it works itās definitely the wrong version of firmware you have. This is only for the very latest models
Thanks for the reply Stuart. Do you know if there is somewhere I can see the firmware level of the sensor. Iāve had a poke about in the IDE but cannot seem to find it.
It was on the box or came in
Unfortunately thats long gone.