Help with NodOn Soft Remote needed

I recently acquired a Z-Wave NodOn Soft Remote. I’m having some problems getting it to work with Home Assistant. I have followed the advice in this thread.

I can get the remote paired and it shows up as node 26. I have verified that I am able to change configuration options of the device from home Assistant by changing the behavior of the LED light when clicking buttons (option 8: LED management).

Changing configuration option 3 Scene Type to Scene Activation, which is needed for operation with Home Assistant does not seem to be working, or I am misunderstanding something. Following excerpts for OZW_Log.txt:

When pushing a button on the remote:

2019-08-19 22:21:32.863 Detail, Node026,   Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x1a, 0x02, 0x84, 0x07, 0x68
2019-08-19 22:21:32.864 Detail, 
2019-08-19 22:21:32.864 Info, Node026, Received Wakeup Notification from node 26
2019-08-19 22:21:32.864 Info, Node026,   Node 26 has been marked as awake
2019-08-19 22:21:32.864 Detail, Node026, Queuing (WakeUp) WakeUpCmd_NoMoreInformation (Node=26): 0x01, 0x09, 0x00, 0x13, 0x1a, 0x02, 0x84, 0x08, 0x25, 0x10, 0x44
2019-08-19 22:21:32.864 Detail, Node026, Notification: Notification - Node Awake
2019-08-19 22:21:32.871 Detail, 
2019-08-19 22:21:32.871 Info, Node026, Sending (WakeUp) message (Callback ID=0x10, Expected Reply=0x13) - WakeUpCmd_NoMoreInformation (Node=26): 0x01, 0x09, 0x00, 0x13, 0x1a, 0x02, 0x84, 0x08, 0x25, 0x10, 0x44
2019-08-19 22:21:32.877 Detail, Node026,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-08-19 22:21:32.878 Detail, Node026,   ZW_SEND_DATA delivered to Z-Wave stack
2019-08-19 22:21:32.892 Detail, Node026,   Received: 0x01, 0x07, 0x00, 0x13, 0x10, 0x00, 0x00, 0x02, 0xf9
2019-08-19 22:21:32.892 Detail, Node026,   ZW_SEND_DATA Request with callback ID 0x10 received (expected 0x10)
2019-08-19 22:21:32.892 Info, Node026, Request RTT 20 Average Request RTT 26
2019-08-19 22:21:32.893 Info, Node026,   Node 26 has been marked as asleep
2019-08-19 22:21:32.893 Detail,   Expected callbackId was received
2019-08-19 22:21:32.893 Detail,   Expected reply was received
2019-08-19 22:21:32.893 Detail,   Message transaction complete
2019-08-19 22:21:32.893 Detail, 
2019-08-19 22:21:32.893 Detail, Node026, Removing current message
2019-08-19 22:21:32.893 Detail, Node026, Notification: Notification - Node Asleep

When trying to change configuration option to Scene Activation:

2019-08-19 22:23:51.645 Info, Node026, Configuration::Set - Parameter=3, Value=1 Size=1
2019-08-19 22:23:51.645 Detail, 
2019-08-19 22:23:51.646 Detail, Node026, Queuing (WakeUp) ConfigurationCmd_Set (Node=26): 0x01, 0x0c, 0x00, 0x13, 0x1a, 0x05, 0x70, 0x04, 0x03, 0x01, 0x01, 0x25, 0x11, 0xbc
2019-08-19 22:23:51.646 Detail, 
2019-08-19 22:23:51.646 Detail, Node026, Queuing (WakeUp) ConfigurationCmd_Get (Node=26): 0x01, 0x0a, 0x00, 0x13, 0x1a, 0x03, 0x70, 0x05, 0x03, 0x25, 0x12, 0xbe

Subsequently pushing a button on the remote to wake it up:

2019-08-19 22:24:32.984 Detail, Node026,   Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x1a, 0x02, 0x84, 0x07, 0x68
2019-08-19 22:24:32.984 Detail, 
2019-08-19 22:24:32.985 Info, Node026, Received Wakeup Notification from node 26
2019-08-19 22:24:32.985 Info, Node026,   Node 26 has been marked as awake
2019-08-19 22:24:32.985 Detail, Node026, Queuing (WakeUp) ConfigurationCmd_Set (Node=26): 0x01, 0x0c, 0x00, 0x13, 0x1a, 0x05, 0x70, 0x04, 0x03, 0x01, 0x01, 0x25, 0x11, 0xbc
2019-08-19 22:24:32.985 Detail, Node026, Queuing (WakeUp) ConfigurationCmd_Get (Node=26): 0x01, 0x0a, 0x00, 0x13, 0x1a, 0x03, 0x70, 0x05, 0x03, 0x25, 0x12, 0xbe
2019-08-19 22:24:32.985 Detail, Node026, Queuing (WakeUp) WakeUpCmd_NoMoreInformation (Node=26): 0x01, 0x09, 0x00, 0x13, 0x1a, 0x02, 0x84, 0x08, 0x25, 0x14, 0x40
2019-08-19 22:24:32.985 Detail, Node026, Notification: Notification - Node Awake
2019-08-19 22:24:32.992 Detail, 
2019-08-19 22:24:32.993 Info, Node026, Sending (WakeUp) message (Callback ID=0x11, Expected Reply=0x13) - ConfigurationCmd_Set (Node=26): 0x01, 0x0c, 0x00, 0x13, 0x1a, 0x05, 0x70, 0x04, 0x03, 0x01, 0x01, 0x25, 0x11, 0xbc
2019-08-19 22:24:32.999 Detail, Node026,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-08-19 22:24:32.999 Detail, Node026,   ZW_SEND_DATA delivered to Z-Wave stack
2019-08-19 22:24:33.014 Detail, Node026,   Received: 0x01, 0x07, 0x00, 0x13, 0x11, 0x00, 0x00, 0x01, 0xfb
2019-08-19 22:24:33.014 Detail, Node026,   ZW_SEND_DATA Request with callback ID 0x11 received (expected 0x11)
2019-08-19 22:24:33.014 Info, Node026, Request RTT 22 Average Request RTT 24
2019-08-19 22:24:33.014 Detail,   Expected callbackId was received
2019-08-19 22:24:33.014 Detail,   Expected reply was received
2019-08-19 22:24:33.015 Detail,   Message transaction complete
2019-08-19 22:24:33.015 Detail, 
2019-08-19 22:24:33.015 Detail, Node026, Removing current message
2019-08-19 22:24:33.015 Detail, 
2019-08-19 22:24:33.015 Info, Node026, Sending (WakeUp) message (Callback ID=0x12, Expected Reply=0x04) - ConfigurationCmd_Get (Node=26): 0x01, 0x0a, 0x00, 0x13, 0x1a, 0x03, 0x70, 0x05, 0x03, 0x25, 0x12, 0xbe
2019-08-19 22:24:33.021 Detail, Node026,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-08-19 22:24:33.021 Detail, Node026,   ZW_SEND_DATA delivered to Z-Wave stack
2019-08-19 22:24:33.036 Detail, Node026,   Received: 0x01, 0x07, 0x00, 0x13, 0x12, 0x00, 0x00, 0x02, 0xfb
2019-08-19 22:24:33.036 Detail, Node026,   ZW_SEND_DATA Request with callback ID 0x12 received (expected 0x12)
2019-08-19 22:24:33.036 Info, Node026, Request RTT 20 Average Request RTT 22
2019-08-19 22:24:33.036 Detail,   Expected callbackId was received
2019-08-19 22:24:33.048 Detail, Node026,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x1a, 0x05, 0x70, 0x06, 0x03, 0x01, 0x01, 0x9a
2019-08-19 22:24:33.048 Detail, 
2019-08-19 22:24:33.048 Info, Node026, Response RTT 33 Average Response RTT 96
2019-08-19 22:24:33.048 Detail, Node026, Refreshed Value: old value=1, new value=1, type=list
2019-08-19 22:24:33.048 Detail, Node026, Changes to this value are not verified
2019-08-19 22:24:33.048 Info, Node026, Received Configuration report: Parameter=3, Value=1
2019-08-19 22:24:33.049 Detail, Node026,   Expected reply and command class was received
2019-08-19 22:24:33.049 Detail, Node026,   Message transaction complete
2019-08-19 22:24:33.049 Detail, 
2019-08-19 22:24:33.049 Detail, Node026, Removing current message
2019-08-19 22:24:33.049 Detail, Node026, Notification: ValueChanged
2019-08-19 22:24:33.089 Detail, 
2019-08-19 22:24:33.089 Info, Node026, Sending (WakeUp) message (Callback ID=0x14, Expected Reply=0x13) - WakeUpCmd_NoMoreInformation (Node=26): 0x01, 0x09, 0x00, 0x13, 0x1a, 0x02, 0x84, 0x08, 0x25, 0x14, 0x40
2019-08-19 22:24:33.105 Detail, Node026,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-08-19 22:24:33.105 Detail, Node026,   ZW_SEND_DATA delivered to Z-Wave stack
2019-08-19 22:24:33.115 Detail, Node026,   Received: 0x01, 0x07, 0x00, 0x13, 0x14, 0x00, 0x00, 0x02, 0xfd
2019-08-19 22:24:33.115 Detail, Node026,   ZW_SEND_DATA Request with callback ID 0x14 received (expected 0x14)
2019-08-19 22:24:33.115 Info, Node026, Request RTT 25 Average Request RTT 23
2019-08-19 22:24:33.115 Info, Node026,   Node 26 has been marked as asleep
2019-08-19 22:24:33.115 Detail,   Expected callbackId was received
2019-08-19 22:24:33.115 Detail,   Expected reply was received
2019-08-19 22:24:33.115 Detail,   Message transaction complete
2019-08-19 22:24:33.115 Detail, 
2019-08-19 22:24:33.115 Detail, Node026, Removing current message
2019-08-19 22:24:33.116 Detail, Node026, Notification: Notification - Node Asleep

Any subsequent button press looks like the first one.

This does not seem to get the remote into Scene Activation mode, or at least I can’t see anything related to scenes being activated in any logs. I also have AppDaemon logging events in Home Assistant without any luck.

Can anyone with a better understanding of Z-Wave or the NodOn remotes give me any pointers what to look for?

For anyone else with the same problem in the future: Don’t change the LED settings. Doing that breaks the scene type setting.

I reset the remote, re-paired and changed just the scene type and now scene activation works as expected.