Super basic scene not working

[s3m3nParticipant]

Hello PulseStationers.

I have some basic issues with simple scene. I am using:

1. Z-stick Gen5 (id: zwave-1)
2. Fibaro FGMS-001 Motion Sensor (id: zwave-2, name: Oko 1)
3. Fibaro FGWPF Wall Plug (id: zwave-3, name: Gniazdo 1)

I have very simple scenario, when I walk into the room light should turn on and off again after 1 minute:

And it’s not working. Not sure why. All my services are up and running including database. Z-wave log shows the devices are reporting state changes but scene logic is not switching the wall plug:

2016-01-19 13:00:59.437 Detail, Node002,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x02, 0x03, 0x30, 0x03, 0x00, 0xc0
2016-01-19 13:00:59.438 Detail, 
2016-01-19 13:00:59.438 Info, Node002, Received SensorBinary report: Sensor:192 State=Off
2016-01-19 13:00:59.438 Detail, Node002, Refreshed Value: old value=true, new value=false, type=bool
2016-01-19 13:00:59.438 Detail, Node002, Changes to this value are not verified
2016-01-19 13:00:59.438 Detail, Node002, Notification: ValueChanged
2016-01-19 13:00:59.925 Info, Notification: Value Changed - Add DB Record for device id zwave-2 and value id 48-user-bool-1-0 
2016-01-19 13:00:59.943 Info, mgr,     Manager::WriteConfig completed for driver with home ID of 0xdab82d8e
2016-01-19 13:01:00.902 Detail, Node002,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x02, 0x03, 0x30, 0x03, 0xff, 0x3f
2016-01-19 13:01:00.902 Detail, 
2016-01-19 13:01:00.902 Info, Node002, Received SensorBinary report: Sensor:63 State=On
2016-01-19 13:01:00.902 Detail, Node002, Refreshed Value: old value=false, new value=true, type=bool
2016-01-19 13:01:00.902 Detail, Node002, Changes to this value are not verified
2016-01-19 13:01:00.902 Detail, Node002, Notification: ValueChanged
2016-01-19 13:01:01.122 Info, Notification: Value Changed - Add DB Record for device id zwave-2 and value id 48-user-bool-1-0 
2016-01-19 13:01:01.148 Info, mgr,     Manager::WriteConfig completed for driver with home ID of 0xdab82d8e

Oh and if I use graphical interface switch it works fine…

2016-01-19 13:02:49.701 Info, Node003, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2016-01-19 13:02:49.701 Info, Node003, SwitchBinary::Set - Setting node 3 to On
2016-01-19 13:02:49.701 Detail, Node003, Queuing (Send) SwitchBinaryCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x25, 0x01, 0xff, 0x25, 0x25, 0x3d
2016-01-19 13:02:49.701 Detail, Node003, Queuing (Send) SwitchBinaryCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x25, 0x02, 0x25, 0x26, 0xc0
2016-01-19 13:02:49.701 Detail, 
2016-01-19 13:02:49.701 Info, Node003, Sending (Send) message (Callback ID=0x25, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x25, 0x01, 0xff, 0x25, 0x25, 0x3d
2016-01-19 13:02:49.710 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-01-19 13:02:49.715 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2016-01-19 13:02:49.888 Detail, Node003,   Received: 0x01, 0x07, 0x00, 0x13, 0x25, 0x00, 0x00, 0x12, 0xdc
2016-01-19 13:02:49.888 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x25 received (expected 0x25)
2016-01-19 13:02:49.889 Info, Node003, Request RTT 186 Average Request RTT 133
2016-01-19 13:02:49.889 Detail,   Expected callbackId was received
2016-01-19 13:02:49.889 Detail,   Expected reply was received
2016-01-19 13:02:49.889 Detail,   Message transaction complete
2016-01-19 13:02:49.889 Detail, 
2016-01-19 13:02:49.889 Detail, Node003, Removing current message
2016-01-19 13:02:49.889 Detail, 
2016-01-19 13:02:49.889 Info, Node003, Sending (Send) message (Callback ID=0x26, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x25, 0x02, 0x25, 0x26, 0xc0
2016-01-19 13:02:49.897 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-01-19 13:02:49.897 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2016-01-19 13:02:49.914 Detail, Node003,   Received: 0x01, 0x07, 0x00, 0x13, 0x26, 0x00, 0x00, 0x02, 0xcf
2016-01-19 13:02:49.914 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x26 received (expected 0x26)
2016-01-19 13:02:49.915 Info, Node003, Request RTT 25 Average Request RTT 79
2016-01-19 13:02:49.915 Detail,   Expected callbackId was received
2016-01-19 13:02:49.925 Detail, Node003,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x03, 0x03, 0x25, 0x03, 0xff, 0x2b
2016-01-19 13:02:49.925 Detail, 
2016-01-19 13:02:49.925 Info, Node003, Response RTT 35 Average Response RTT 193
2016-01-19 13:02:49.925 Info, Node003, Received SwitchBinary report from node 3: level=On
2016-01-19 13:02:49.925 Detail, Node003, Refreshed Value: old value=false, new value=true, type=bool
2016-01-19 13:02:49.925 Detail, Node003, Changes to this value are not verified
2016-01-19 13:02:49.925 Detail, Node003,   Expected reply and command class was received
2016-01-19 13:02:49.925 Detail, Node003,   Message transaction complete
2016-01-19 13:02:49.925 Detail, 
2016-01-19 13:02:49.925 Detail, Node003, Removing current message
2016-01-19 13:02:49.925 Detail, Node003, Notification: ValueChanged
2016-01-19 13:02:50.160 Info, Notification: Value Changed - Add DB Record for device id zwave-3 and value id 37-user-bool-1-0 
2016-01-19 13:02:50.178 Info, mgr,     Manager::WriteConfig completed for driver with home ID of 0xdab82d8e
2016-01-19 13:02:50.895 Detail, Node003,   Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x03, 0x06, 0x31, 0x05, 0x04, 0x22, 0x00, 0x23, 0xc3
2016-01-19 13:02:50.895 Detail, 
2016-01-19 13:02:50.895 Info, Node003, Received SensorMultiLevel report from node 3, instance 1, Power: value=3.5W
2016-01-19 13:02:50.895 Detail, Node003, Refreshed Value: old value=0.0, new value=3.5, type=decimal
2016-01-19 13:02:50.895 Detail, Node003, Changes to this value are not verified
2016-01-19 13:02:50.895 Detail, Node003, Notification: ValueChanged
2016-01-19 13:02:51.078 Info, Notification: Value Changed - Add DB Record for device id zwave-3 and value id 49-user-decimal-1-4 
2016-01-19 13:02:51.098 Info, mgr,     Manager::WriteConfig completed for driver with home ID of 0xdab82d8e

Am I missing some stupid thing or there might be different problem? What should I do?

Thanks guys for great work.

[MikaAdmin bbPress]

For your motion sensor, please check the association tab.
Your controller should be associated to the “Basic Group”.

If it’s not the case, try it.

If your controller is not in that group, the openzwave lib will not treat the message as an event.

[s3m3nParticipant]

Thanks for the reply.

I am not sure how can I associate controller to the Basic Group, the only options in the service panel are:

Properties tab is empty.

[s3m3nParticipant]

OK I see, for the sensor there is association tab:

I believe association was done before as you can see at the bottom of popup, but I will do it again. If the association is bad shouldn’t I see empty Z-wave log for device events?

[K.RensAdmin bbPress]

Can you check you are using the latest version of PulseStation and all services?
You can update from within pulsestation.

You should have a new tab next to Properties on the right.

Kind regards,
K.Rens

[s3m3nParticipant]

There is extra tab under sensor menu as above, but not controller.

I have the latest packages:

UPDATE:

Now I realized I have to click on the “open” icons next to the services. Thanks, I will try now.

[Auteur]

Messages