That’s normal. With DEBUG turned off, there won’t be much in the log.
Always best to use code fences when posting debug logs. Much easier to read. 
2019-05-06 20:19:51.740 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 04 15 05 5B 03 68 00 01 BF 00 6C
2019-05-06 20:19:51.775 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=21, callback=4, payload=04 15 05 5B 03 68 00 01 BF 00
2019-05-06 20:19:51.779 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=21, callback=4, payload=04 15 05 5B 03 68 00 01 BF 00
2019-05-06 20:19:51.782 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-05-06 20:19:51.785 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 21: Application Command Request (ALIVE:STATIC_VALUES)
2019-05-06 20:19:51.789 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 21: Incoming command class COMMAND_CLASS_CENTRAL_SCENE, endpoint 0
2019-05-06 20:19:51.791 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 21: SECURITY not supported
2019-05-06 20:19:51.795 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 21: Received COMMAND_CLASS_CENTRAL_SCENE V2 CENTRAL_SCENE_NOTIFICATION
2019-05-06 20:19:51.798 [DEBUG] [dclass.ZWaveCentralSceneCommandClass] - NODE 21: Received scene 1 at key 0 [Single Press]
2019-05-06 20:19:51.802 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2019-05-06 20:19:51.804 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_CENTRAL_SCENE, value=1.0
2019-05-06 20:19:51.809 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Updating channel state zwave:device:a7a53341:node21:scene_number to 1.0 [DecimalType]
2019-05-06 20:19:51.812 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 21: Commands processed 1.
2019-05-06 20:19:51.817 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 21: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@19cf5cd.
2019-05-06 20:19:51.821 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-05-06 20:19:51.825 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-05-06 20:19:51.827 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-05-06 20:19:51.831 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
This looks fine. If you have an item linked to the scene_number channel, you should be able to deal with it in a rule like this.
rule "wallmote rule"
when
Item Wallmote_Scene received update
then
var double sceneNumber = (Wallmote1_Scene.state as Number).doubleValue
switch (sceneNumber) {
case 1.0 : { // Button 1 short press
// Do something
}
case 1.1 : { // Button 1 long press
// Do something
}
case 1.2 : { // Button 1 hold
// Do something
}
// Repeat for buttons 2, 3, & 4
}
end