Page 3 of 9

Re: Problem with Fibaro Motion Sensor

Posted: 09 Jun 2014 01:17
by pofs
edafonseca wrote:I'm not reveiving any report from fibaro Motion sensor.
Check that RaZberry is included in Association Group 3 of Motion Sensor.

Also play with config parameters 40, 42, 60, 62, 64.
By default reports are not sent regularly, only when value changes more than threshold. Default threshold is 1 degree Celsius for temperature, and 200 Lux for illumination.

Re: Problem with Fibaro Motion Sensor

Posted: 09 Jun 2014 11:33
by edafonseca
Thanks for your reply, I think you find the problem.
In Device configuration, Association, there is no values set (neither for group 1, 2 or 3). But I have no selector to set any device in group 3, do you know how can I associate Razberry to this group ?

Re: Problem with Fibaro Motion Sensor

Posted: 09 Jun 2014 11:56
by fredaim
@pofs
effectively when I said not to see illumination it was in Domoticz.
In fact z-wave-server, according to the tests I've done, works better than OpenZWave. But it is better implemented in Domoticz. And I use Domoticz...
I expect future versions of HA UI ...

@edafonseca
You can set the group assignment in expert mode in the last tab of the Blue UI.

Re: Problem with Fibaro Motion Sensor

Posted: 09 Jun 2014 15:07
by edafonseca
Thank you ! It's working great now :)

Re: Problem with Fibaro Motion Sensor

Posted: 09 Jun 2014 15:30
by fredaim
edafonseca wrote:Thank you ! It's working great now :)
good fun ;)

Re: Problem with Fibaro Motion Sensor

Posted: 10 Jun 2014 03:11
by pofs
fredaim wrote:@pofs
effectively when I said not to see illumination it was in Domoticz.
Domoticz has the same flawed implementation as previous versions of Blue UI:

Code: Select all

if ((_device.instanceID==0)&&(haveMultipleInstance))
    continue;
I even think they've copied it from ours JS :)

As I think Motion Sensor has multiple instances, the sensor on default instance might be not present. And sensors on non-default instances probably have only one scale.

Re: Problem with Fibaro Motion Sensor

Posted: 10 Jun 2014 22:05
by PoltoS
pofs wrote:

Code: Select all

if ((_device.instanceID==0)&&(haveMultipleInstance))
    continue;
This was removed few weeks ago (mostly due to Fibaro). So, update to the latest RC code to get it.

Re: Problem with Fibaro Motion Sensor

Posted: 11 Jun 2014 13:56
by blackkane
Hi,
if you have some problems with the sensor settings you can use the "curl" command (I suggest you to read the manual to have more informations about the parameters). For example:
------------------
set 42 param
------------------
curl "http://127.0.0.1:8083/ZWaveAPI/Run/devices\[21\]instances\[0\].commandClasses\[112\].Set(42,180,2)"
------------------
set 80 param (light on/off)
------------------
curl http://127.0.0.1:8083/ZWaveAPI/Run/devices\[21\].instances\[0\].commandClasses\[112\].Set(80,0,1)
Best regards, b.

Re: Problem with Fibaro Motion Sensor

Posted: 19 Jun 2014 13:25
by Confuzer
When I am in the blue expert UI I am unable to set parameter 40, as the UI sets the scroller and input field as "min 32769 max 32769". Same goes for all other interval settings.

So now I almost never get updates, only if motion is detected.

Can I set it another way? Thanks!

Re: Problem with Fibaro Motion Sensor

Posted: 20 Jun 2014 00:43
by PoltoS
In expert tab