Event with Fibaro Mension Sensor

[leroymthBijdrager]

Hello,
I’m trying to catch an event when motion is detected with my Fibaro Mention Sensor.
At my opinion all configuration is good between receiver and devices.

My Fibaro statis is “complete”. Associations on Basic Report, Tamper Alarm, Device Status are connected to my receiver.

My scene is very simple.

`If Device Event == Event Device : Fibaro 1 Value : On
do AddLog “Je bouge”

And so when there is a motion….nothing in scene logs….even after one or two minutes….

Someone can help me?

[MikaSleutelbeheerder]

Consult the log file (zwave, core and scene) to see if there are messages coming.
Normally, the first one you have to check is the zwave you’ll find something with “send event”.
Then the core service will catch the message with something with “SCENEVENT” and finally, the scene service will also trigger the scene associate to the event…

So just check the log for the moment to see if something happen…

[leroymthBijdrager]

Hi Mika,

First, thx for your answer and I would like to thank you regarding PulseStation (I was on Synozwave and you did a great work here !).

Unfortunatelly, for my problem, there is no trace of log “send event” or “send” in the /volume1/web/PulseStation/services/zwave/OZW.log…I did a tail -f during I moved in front of the sensor and I have such logs :

`2016-01-21 19:12:34.947 Detail, Node012, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x0c, 0x03, 0x30, 0x03, 0x00, 0xce
2016-01-21 19:12:34.947 Detail,
2016-01-21 19:12:34.947 Info, Node012, Received SensorBinary report: Sensor:206 State=Off
2016-01-21 19:12:34.947 Detail, Node012, Refreshed Value: old value=true, new value=false, type=bool
2016-01-21 19:12:34.947 Detail, Node012, Changes to this value are not verified
2016-01-21 19:12:34.948 Detail, Node012, Notification: ValueChanged
2016-01-21 19:12:35.183 Info, Notification: Value Changed – Add DB Record for device id zwave-12 and value id 48-user-bool-1-0
2016-01-21 19:12:35.198 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0x0184e172
2016-01-21 19:12:35.496 Detail, Node012, Received: 0x01, 0x0d, 0x00, 0x04, 0x00, 0x0c, 0x07, 0x60, 0x0d, 0x01, 0x01, 0x20, 0x01, 0x00, 0xb1
2016-01-21 19:12:35.497 Detail,
2016-01-21 19:12:35.497 Info, Node012, ApplicationCommandHandler – Unhandled Command Class 0x60
2016-01-21 19:13:02.701 Info, Node012, Value::Set – COMMAND_CLASS_CONFIGURATION – LED signaling mode – 80 – 1 – Long blink Yellow.
2016-01-21 19:13:02.701 Info, Node012, Configuration::Set – Parameter=80, Value=7 Size=1
2016-01-21 19:13:02.701 Detail,
2016-01-21 19:13:02.701 Detail, Node012, Queuing (WakeUp) ConfigurationCmd_Set (Node=12): 0x01, 0x0c, 0x00, 0x13, 0x0c, 0x05, 0x70, 0x04, 0x50, 0x01, 0x07, 0x25, 0xc8, 0x26
2016-01-21 19:13:02.701 Detail,
2016-01-21 19:13:02.701 Detail, Node012, Queuing (WakeUp) ConfigurationCmd_Get (Node=12): 0x01, 0x0a, 0x00, 0x13, 0x0c, 0x03, 0x70, 0x05, 0x50, 0x25, 0xc9, 0x20
2016-01-21 19:13:32.756 Detail, Node012, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x0c, 0x03, 0x30, 0x03, 0xff, 0x31
2016-01-21 19:13:32.757 Detail,
2016-01-21 19:13:32.757 Info, Node012, Received SensorBinary report: Sensor:49 State=On
2016-01-21 19:13:32.757 Detail, Node012, Refreshed Value: old value=false, new value=true, type=bool
2016-01-21 19:13:32.757 Detail, Node012, Changes to this value are not verified
2016-01-21 19:13:32.757 Detail, Node012, Notification: ValueChanged
2016-01-21 19:13:32.967 Info, Notification: Value Changed – Add DB Record for device id zwave-12 and value id 48-user-bool-1-0
2016-01-21 19:13:32.982 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0x0184e172
2016-01-21 19:13:33.296 Detail, Node012, Received: 0x01, 0x0d, 0x00, 0x04, 0x00, 0x0c, 0x07, 0x60, 0x0d, 0x01, 0x01, 0x20, 0x01, 0xff, 0x4e
2016-01-21 19:13:33.296 Detail,’

So I’m still not able to raise an event as soon as there is a move….

An idea?

[K.RensSleutelbeheerder]

We are aware of this issue and are investigating it.
Sorry for this!

Kind regards,
K.Rens

[leroymthBijdrager]

Hi K.Rens,

Some news about this issue?

I did not find any workaround unfortunattelly to catch an event in my logs (even with a customized code in PHP…).

Regards.

[K.RensSleutelbeheerder]

Hi,

In all cases where users complained, this was fixed by correcting the associations in the associations tab.
Basic report and device status should both only be associated to zwave-1

Kind regards,
K.Rens

[leroymthBijdrager]

Hi,
My device is correctly associated with the key zwave1. Just remind, I would like to catch the event when there is a motion.

Here an extract when something move in front of the sensor.

2016-03-30 16:23:48.060 Detail, Node012,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x0c, 0x03, 0x30, 0x03, 0xff, 0x31
2016-03-30 16:23:48.060 Detail,
2016-03-30 16:23:48.060 Info, Node012, Received SensorBinary report: Sensor:49 State=On
2016-03-30 16:23:48.060 Detail, Node012, Refreshed Value: old value=false, new value=true, type=bool
2016-03-30 16:23:48.061 Detail, Node012, Changes to this value are not verified
2016-03-30 16:23:48.061 Detail, Node012, Notification: ValueChanged
2016-03-30 16:23:48.333 Info, Notification: Value Changed - Add DB Record for device id zwave-12 and value id 48-user-bool-1-0
2016-03-30 16:23:48.397 Info, mgr,     Manager::WriteConfig completed for driver with home ID of 0x0184e172
2016-03-30 16:23:48.787 Detail, Node012,   Received: 0x01, 0x0d, 0x00, 0x04, 0x00, 0x0c, 0x07, 0x60, 0x0d, 0x01, 0x01, 0x20, 0x01, 0xff, 0x4e
2016-03-30 16:23:48.787 Detail,
2016-03-30 16:23:48.787 Info, Node012, ApplicationCommandHandler - Unhandled Command Class 0x60

I’m not able to use SCENEVENT as Mika talked about before into the post.

Any idea or correction?

[MikaSleutelbeheerder]

The zwave1 device should be include in 2 groups.
That’s what koen try to say.

By default, the zwave1 (controller) is part of one group (dont remember what). But it should also be part of the group “Basic Report” (something like that)

[leroymthBijdrager]

Hi Mika, K.Rens,

If you want I can send you screenshot by emails or share my configuration but what I have currently in “associations” tab of my Fibaro zwave device (zwave-12) is :
– Basic Report (COMMAND_CLASS_ASSOCIATION) => zwave-1 (Aeotec USB Z-Stick S2 Z-Wave)
– Tamper Alarm (COMMAND_CLASS_ASSOCIATION) => zwave-1 (Aeotec USB Z-Stick S2 Z-Wave
– Device Status (COMMAND_CLASS_ASSOCIATION) => zwave-1 (Aeotec USB Z-Stick S2 Z-Wave)
So for me all associations are made….
Thx.

[vryfBijdrager]

Hi,
I have exactly the same issue,
Something new ?
Thx.

[leroymthBijdrager]

Hi,
Is there someone for whom it runs correctly? If we could have an example….
Thx

[Miss LauraModerator]

Associations inside z-wave service for the motion device:
http://screencast.com/t/OfhGjhQuyj0Y

It’s working fine for me.

Inside blocky you can just use
IF Device event (util) = Even Device [your z-wave motion sensor] On (z-wave block)

Have fun,
Laura

[leroymthBijdrager]

Hi Laura,
Thx for your sharing, I have normally same configuration than you but it doesn’t work.
In your Scene.log what do you have?
Mika was talking about “SCENEVENT” inside logs as soon as you have an event.
Regards

[Miss LauraModerator]

It’s something like:
EVENT_xxx
where xxx is replaced with the actual event.

I’m not certain it was recorded in the scenes log, I think it’s rather the core log.
The scene log just outputs if something is executed (triggered via core).

Have fun,
Laura

[leroymthBijdrager]

Nothing in the core.log too….however I’m in front of my Fibaro and I’m moving :).

2016-06-01 16:08:23.547  Message Finished, remove it from the stack (0|HUB|HUB|AUTORESTART)
2016-06-01 16:08:23.681  Message Finished, remove it from the stack (0|HUB|HUB|AUTORESTART)
2016-06-01 16:08:31.576  Forwarding message : 0|HUB|HUB|AUTORESTART
2016-06-01 16:08:31.710  Forwarding message : 0|HUB|HUB|AUTORESTART
2016-06-01 16:08:34.050  Message Finished, remove it from the stack (0|HUB|HUB|AUTORESTART)
2016-06-01 16:08:34.210  Message Finished, remove it from the stack (0|HUB|HUB|AUTORESTART)
2016-06-01 16:08:41.054  Forwarding message : 0|HUB|HUB|AUTORESTART
2016-06-01 16:08:41.214  Forwarding message : 0|HUB|HUB|AUTORESTART
2016-06-01 16:08:43.569  Message Finished, remove it from the stack (0|HUB|HUB|AUTORESTART)
2016-06-01 16:08:43.761  Message Finished, remove it from the stack (0|HUB|HUB|AUTORESTART)

[Auteur]

Berichten