Z-Wave rules with SCENE_ACTIVATION problem

I want to be able to see the thing initialisation. This should happen in the first minute or so, so if you can grab the first minute of the log it should be fine.

If you like, you can open a ticket on my website (if you’re registered) and attach the log there - you can attach large files and it makes it easier for me to keep track than linking out to dropbox or somewhere…

Ok, registered right now. Will create a ticket there in the evening.

Thanks.

Hi again, created a ticket with log inside:
http://www.cd-jackson.com/index.php/tickets/zwave-log-ticket/viewticket/ticketid-146

KFob button press can be found by this line:

2017-07-19 22:35:47.010 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Got a value event from Z-Wave network, endpoint = 0, command class = SCENE_ACTIVATION, value = 11

Please can you provide the XML for your device.

The binding is currently configured to use the CENTRAL_SCENE class which is designed for use by controllers. The device seems to currently use the SCENE_ACTIVATION class which is designed for controlling devices. I expect there’s a configuration parameter to change this in the device.

Hi, attached:
node43.xml (12.6 KB)

Thanks. So the device supports both commands. Looking at the docs, you need to change the configuration to gateway mode (eg parameter 11, set to 8 “Central Scene to Gateway”).

1 Like

Thank you very much, it works now!

I have a Z-Wave.Me Keyfob device. The manual that came with it refers to it as ‘KFOB2’.

It is discovered as a Thing of type ‘kfob’. When set as a scene controller, it sends out SCENE_ACTIVATION messages rather than CENTRAL_SCENE and doesn’t appear to have an option in the configuration to do this (highest config number in the paper manual is ‘6’).

2020-01-25 17:05:30.751 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Application Command Request (ALIVE:DONE)

2020-01-25 17:05:30.753 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: resetResendCount initComplete=true isDead=false

2020-01-25 17:05:30.755 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: Incoming command class COMMAND_CLASS_SCENE_ACTIVATION, endpoint 0

2020-01-25 17:05:30.757 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: SECURITY not supported

2020-01-25 17:05:30.759 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 33: Received COMMAND_CLASS_SCENE_ACTIVATION V0 SCENEACTIVATION_SET

2020-01-25 17:05:30.761 [DEBUG] [ass.ZWaveSceneActivationCommandClass] - NODE 33: Scene activation: Scene 21, Time 255

2020-01-25 17:05:30.762 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Got an event from Z-Wave network: ZWaveCommandClassValueEvent

2020-01-25 17:05:30.765 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SCENE_ACTIVATION, value=21

2020-01-25 17:05:30.767 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Commands processed 1.

2020-01-25 17:05:30.769 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@dc87b9.

I tried to see if I could add SCENE_ACTIVATION to the device endpoint in the database, but of course this throws up an error because of duplicate scene_number channels for endpoint 0.

My device is on firmware 1.4. I suspect the option to send CENTRAL_SCENE (and secure mode too) was added in a later firmware.

@chris
Is it possible for me to create a new device specifically for this firmware version (1.4) that uses SCENE_ACTIVATION rather than CENTRAL_SCENE in the scene_number channel? This would rely on the discovery mechanism being able to choose the correct binding based on the manfacturer ID/device ID/device type AND the firmware number - I see that there is a ‘Firmware Versions’ field in the device database - but I’m not sure if that is what it is used for.

The new definition would be almost a straight copy of the existing one, but I noticed that some of the help text i.e. inclusion/exclusion etc. was wrong and would need amending.

Device XML node_33.xml (12.4 KB)

Are you sure that changing config parameter 13 doesn’t change this? Please try and see what happens - I’m not sure what the difference between send preconfigured scenes and send scenes is.

Please also provide the log when you do this - you’ll need to wake up the device so that it transfers to the device.

If we really need to, then yes, we can add a new version with the different firmware - that can be done, but I want to make sure it’s really needed. Currently it looks like your device does support these extra parameters, but I’d need to see the log to double check.

Parameter #13 is the mode for button #3. i.e. #11=button#1, #12=button #2… etc.).

I tried changing this to ‘5’ (pre configured scenes). I woke the keyfob (which ends up sending out a scene messages as you hold the buttons down to get into wake mode, so ignore them). Log below:

2020-01-25 18:59:59.534 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Configuration update received

2020-01-25 18:59:59.539 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Configuration update set config_13_1 to 5 (BigDecimal)

2020-01-25 18:59:59.540 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 33: Creating new message for application command CONFIGURATION_SET

2020-01-25 18:59:59.543 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: SECURITY not supported

2020-01-25 18:59:59.544 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: Command Class COMMAND_CLASS_CONFIGURATION is NOT required to be secured

2020-01-25 18:59:59.545 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Bump transaction 381 priority from Config to Immediate

2020-01-25 18:59:59.547 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Adding to device queue

2020-01-25 18:59:59.548 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Added 381 to queue - size 1

2020-01-25 18:59:59.550 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 33: Creating new message for application command CONFIGURATIONCMD_GET

2020-01-25 18:59:59.552 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: SECURITY not supported

2020-01-25 18:59:59.553 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: Command Class COMMAND_CLASS_CONFIGURATION is NOT required to be secured

2020-01-25 18:59:59.558 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Bump transaction 382 priority from Config to Immediate

2020-01-25 18:59:59.559 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Adding to device queue

2020-01-25 18:59:59.561 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Added 382 to queue - size 2

2020-01-25 19:00:21.402 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Application Command Request (ALIVE:DONE)

2020-01-25 19:00:21.404 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: resetResendCount initComplete=true isDead=false

2020-01-25 19:00:21.406 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: Incoming command class COMMAND_CLASS_SCENE_ACTIVATION, endpoint 0

2020-01-25 19:00:21.407 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: SECURITY not supported

2020-01-25 19:00:21.408 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 33: Received COMMAND_CLASS_SCENE_ACTIVATION V0 SCENEACTIVATION_SET

2020-01-25 19:00:21.410 [DEBUG] [ass.ZWaveSceneActivationCommandClass] - NODE 33: Scene activation: Scene 33, Time 255

2020-01-25 19:00:21.412 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Got an event from Z-Wave network: ZWaveCommandClassValueEvent

2020-01-25 19:00:21.414 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SCENE_ACTIVATION, value=33

2020-01-25 19:00:21.418 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Commands processed 1.

2020-01-25 19:00:21.420 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1a8ec85.

2020-01-25 19:00:21.472 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Application Command Request (ALIVE:DONE)

2020-01-25 19:00:21.473 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: resetResendCount initComplete=true isDead=false

2020-01-25 19:00:21.476 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: Incoming command class COMMAND_CLASS_SCENE_ACTIVATION, endpoint 0

2020-01-25 19:00:21.477 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: SECURITY not supported

2020-01-25 19:00:21.479 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 33: Received COMMAND_CLASS_SCENE_ACTIVATION V0 SCENEACTIVATION_SET

2020-01-25 19:00:21.481 [DEBUG] [ass.ZWaveSceneActivationCommandClass] - NODE 33: Scene activation: Scene 43, Time 255

2020-01-25 19:00:21.483 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Got an event from Z-Wave network: ZWaveCommandClassValueEvent

2020-01-25 19:00:21.485 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SCENE_ACTIVATION, value=43

2020-01-25 19:00:21.487 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Commands processed 1.

2020-01-25 19:00:21.489 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1f9b12b.

2020-01-25 19:00:21.545 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Application Command Request (ALIVE:DONE)

2020-01-25 19:00:21.547 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: resetResendCount initComplete=true isDead=false

2020-01-25 19:00:21.548 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: Incoming command class COMMAND_CLASS_SCENE_ACTIVATION, endpoint 0

2020-01-25 19:00:21.551 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: SECURITY not supported

2020-01-25 19:00:21.552 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 33: Received COMMAND_CLASS_SCENE_ACTIVATION V0 SCENEACTIVATION_SET

2020-01-25 19:00:21.555 [DEBUG] [ass.ZWaveSceneActivationCommandClass] - NODE 33: Scene activation: Scene 13, Time 255

2020-01-25 19:00:21.556 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Got an event from Z-Wave network: ZWaveCommandClassValueEvent

2020-01-25 19:00:21.559 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SCENE_ACTIVATION, value=13

2020-01-25 19:00:21.561 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Commands processed 1.

2020-01-25 19:00:21.563 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1d62a68.

2020-01-25 19:00:21.591 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Application Command Request (ALIVE:DONE)

2020-01-25 19:00:21.592 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: resetResendCount initComplete=true isDead=false

2020-01-25 19:00:21.593 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: Incoming command class COMMAND_CLASS_SCENE_ACTIVATION, endpoint 0

2020-01-25 19:00:21.594 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: SECURITY not supported

2020-01-25 19:00:21.595 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 33: Received COMMAND_CLASS_SCENE_ACTIVATION V0 SCENEACTIVATION_SET

2020-01-25 19:00:21.597 [DEBUG] [ass.ZWaveSceneActivationCommandClass] - NODE 33: Scene activation: Scene 23, Time 255

2020-01-25 19:00:21.598 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Got an event from Z-Wave network: ZWaveCommandClassValueEvent

2020-01-25 19:00:21.599 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SCENE_ACTIVATION, value=23

2020-01-25 19:00:21.601 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Commands processed 1.

2020-01-25 19:00:21.602 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@8cdf4c.

2020-01-25 19:00:30.850 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 33: Application update request. Node information received. Transaction null

2020-01-25 19:00:30.852 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: resetResendCount initComplete=true isDead=false

2020-01-25 19:00:30.854 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 33: Application update - no transaction.

2020-01-25 19:00:30.872 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Application Command Request (ALIVE:DONE)

2020-01-25 19:00:30.873 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: resetResendCount initComplete=true isDead=false

2020-01-25 19:00:30.875 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: Is awake with 2 messages in the queue

2020-01-25 19:00:30.877 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: Start sleep timer at 1000ms

2020-01-25 19:00:30.879 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Got an event from Z-Wave network: ZWaveNodeStatusEvent

2020-01-25 19:00:30.890 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 33: Node Status event - Node is AWAKE

2020-01-25 19:00:30.892 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Commands processed 1.

2020-01-25 19:00:30.893 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@9ec65c.

2020-01-25 19:00:30.908 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Application Command Request (ALIVE:DONE)

2020-01-25 19:00:30.911 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: resetResendCount initComplete=true isDead=false

2020-01-25 19:00:30.913 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: Incoming command class COMMAND_CLASS_BATTERY, endpoint 0

2020-01-25 19:00:30.915 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: SECURITY not supported

2020-01-25 19:00:30.916 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 33: Received COMMAND_CLASS_BATTERY V1 BATTERY_REPORT

2020-01-25 19:00:30.919 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 33: Battery report value = 73

2020-01-25 19:00:30.921 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Got an event from Z-Wave network: ZWaveCommandClassValueEvent

2020-01-25 19:00:30.923 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_BATTERY, value=73

2020-01-25 19:00:30.924 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Updating channel state zwave:device:1139f694:node33:battery-level to 73 [DecimalType]

2020-01-25 19:00:30.925 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Commands processed 1.

2020-01-25 19:00:30.927 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@bc550d.

2020-01-25 19:00:30.935 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 33: Sending REQUEST Message = 01 0C 00 13 21 05 70 04 0D 01 05 25 50 CC 

2020-01-25 19:00:31.001 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 33: sentData successfully placed on stack.

2020-01-25 19:00:31.003 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: TID 381: Transaction not completed

2020-01-25 19:00:31.076 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 33: SendData Request. CallBack ID = 80, Status = Transmission complete and ACK received(0)

2020-01-25 19:00:31.077 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: resetResendCount initComplete=true isDead=false

2020-01-25 19:00:31.079 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Response processed after 113ms

2020-01-25 19:00:31.080 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: TID 381: Transaction completed

2020-01-25 19:00:31.084 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: notifyTransactionResponse TID:381 DONE

2020-01-25 19:00:31.087 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent

2020-01-25 19:00:31.093 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 33: Sending REQUEST Message = 01 0A 00 13 21 03 70 05 0D 25 51 C8 

2020-01-25 19:00:31.162 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 33: sentData successfully placed on stack.

2020-01-25 19:00:31.169 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: TID 382: Transaction not completed

2020-01-25 19:00:31.194 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 33: SendData Request. CallBack ID = 81, Status = Transmission complete and ACK received(0)

2020-01-25 19:00:31.195 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: resetResendCount initComplete=true isDead=false

2020-01-25 19:00:31.197 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: TID 382: Transaction not completed

2020-01-25 19:00:31.299 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Application Command Request (ALIVE:DONE)

2020-01-25 19:00:31.300 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: resetResendCount initComplete=true isDead=false

2020-01-25 19:00:31.302 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: Incoming command class COMMAND_CLASS_CONFIGURATION, endpoint 0

2020-01-25 19:00:31.303 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: SECURITY not supported

2020-01-25 19:00:31.304 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 33: Received COMMAND_CLASS_CONFIGURATION V1 CONFIGURATIONCMD_REPORT

2020-01-25 19:00:31.305 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 33: Node configuration report, parameter = 13, value = 5, size = 1

2020-01-25 19:00:31.307 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Got an event from Z-Wave network: ZWaveConfigurationParameterEvent

2020-01-25 19:00:31.308 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_CONFIGURATION, value=org.openhab.binding.zwave.internal.protocol.ZWaveConfigurationParameter@18accc8

2020-01-25 19:00:31.310 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Update CONFIGURATION 13/1 to 5

2020-01-25 19:00:31.311 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Commands processed 1.

2020-01-25 19:00:31.312 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@bbbad8.

2020-01-25 19:00:31.313 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@bbbad8.

2020-01-25 19:00:31.315 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: notifyTransactionResponse TID:382 DONE

2020-01-25 19:00:31.316 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent

2020-01-25 19:00:31.379 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: WakeupTimerTask 0 Messages waiting, state DONE

2020-01-25 19:00:31.880 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: WakeupTimerTask 0 Messages waiting, state DONE

2020-01-25 19:00:31.881 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: No more messages, go back to sleep

2020-01-25 19:00:31.885 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 33: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION

2020-01-25 19:00:31.886 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: SECURITY not supported

2020-01-25 19:00:31.888 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: Command Class COMMAND_CLASS_WAKE_UP is NOT required to be secured

2020-01-25 19:00:31.889 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@10985f1

2020-01-25 19:00:31.891 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Bump transaction 383 priority from Immediate to Immediate

2020-01-25 19:00:31.893 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Adding to device queue

2020-01-25 19:00:31.894 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Added 383 to queue - size 1

2020-01-25 19:00:31.900 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 33: Sending REQUEST Message = 01 09 00 13 21 02 84 08 25 52 3D 

2020-01-25 19:00:31.979 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 33: sentData successfully placed on stack.

2020-01-25 19:00:31.982 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: TID 383: Transaction not completed

2020-01-25 19:00:32.023 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 33: SendData Request. CallBack ID = 82, Status = Transmission complete and ACK received(0)

2020-01-25 19:00:32.028 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: resetResendCount initComplete=true isDead=false

2020-01-25 19:00:32.034 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Response processed after 98ms

2020-01-25 19:00:32.035 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: TID 383: Transaction completed

2020-01-25 19:00:32.036 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: notifyTransactionResponse TID:383 DONE

2020-01-25 19:00:32.037 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent

2020-01-25 19:00:32.038 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: Went to sleep COMPLETE

However subsequent presses of button #3 no longer send anything (nothing in the log).

I’m not sure what the pre-configured scenes are either - there is no other mention of them in the manual that I can see, apart from the entry in the config table.