Fibaro Double switch FGS-223 S2 no switch_binary2 report

OMR · August 14, 2017, 10:49pm

Just included a FGS-223 v3.2 to use as a controller in OH2.
I’m running snapshot 2.2.0 Build #1008 with development binding from 20170808

I am able to receive all central scene events when pressing S1 & S2, and also get status from both binary_switch1 & 2 when changing state from Habmin. However, when pressing S1 or S2 on the node, events are only reported as binary_switch (no indication if it is ch1 or ch2.)

Lifeline association is openHab Controller, and in order to get any switch_binary report from S2 I also associated ON/OFF(S2) with openHab Controller. No other associations.

I have captured debug logs when pressing S1 and S2 and there is clearly different messages received, but it looks like they are all parsed to report the same event.

My .item file :

Switch WallSwitchStuaSW           (div, switches)        { channel = "zwave:device:f180343d:node52:switch_binary" }
Switch WallSwitchStuaSW1          (div, switches)        { channel = "zwave:device:f180343d:node52:switch_binary1" }
Switch WallSwitchStuaSW2          (div, switches)        { channel = "zwave:device:f180343d:node52:switch_binary2" }

S1 pressed:

2017-08-15 00:18:25.065 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 00 34 07 56 01 25 03 00 67 A8 7B 
2017-08-15 00:18:25.066 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Response SENT 6
2017-08-15 00:18:25.066 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=52, callback=0, payload=00 34 07 56 01 25 03 00 67 A8 
2017-08-15 00:18:25.066 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=52, callback=0, payload=00 34 07 56 01 25 03 00 67 A8 
2017-08-15 00:18:25.066 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=52, callback=0, payload=00 34 07 56 01 25 03 00 67 A8 
2017-08-15 00:18:25.066 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2017-08-15 00:18:25.066 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 52: Application Command Request (ALIVE:DONE)
2017-08-15 00:18:25.066 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 52: resetResendCount initComplete=true isDead=false
2017-08-15 00:18:25.066 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 52: Decapsulating COMMAND_CLASS_CRC_16_ENCAP
2017-08-15 00:18:25.066 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 52: Incoming command class COMMAND_CLASS_SWITCH_BINARY, endpoint 0
2017-08-15 00:18:25.066 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 52: SECURITY NOT required on COMMAND_CLASS_SWITCH_BINARY
2017-08-15 00:18:25.066 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 52: Received COMMAND_CLASS_SWITCH_BINARY V1 SWITCH_BINARY_REPORT
2017-08-15 00:18:25.066 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 52: Switch Binary report, value = 0
2017-08-15 00:18:25.066 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2017-08-15 00:18:25.067 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 52: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-08-15 00:18:25.067 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 52: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SWITCH_BINARY, value = 0
2017-08-15 00:18:25.067 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 52: Updating channel state zwave:device:f180343d:node52:switch_binary to OFF [OnOffType]
2017-08-15 00:18:25.070 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 52: Commands processed 1.
2017-08-15 00:18:25.070 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 52: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@74b7abf7.
2017-08-15 00:18:25.070 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2017-08-15 00:18:25.070 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2017-08-15 00:18:25.070 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2017-08-15 00:18:25.070 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start
2017-08-15 00:18:25.070 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 49: listening == false, frequentlyListening == false, awake == false
2017-08-15 00:18:25.070 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 49: Node not awake!

S2 pressed: (note 2 messages received)

2017-08-15 00:13:48.265 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 08 34 03 20 01 FF 13 
2017-08-15 00:13:48.265 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Response SENT 6
2017-08-15 00:13:48.265 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=52, callback=8, payload=08 34 03 20 01 FF 
2017-08-15 00:13:48.265 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=52, callback=8, payload=08 34 03 20 01 FF 
2017-08-15 00:13:48.265 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=52, callback=8, payload=08 34 03 20 01 FF 
2017-08-15 00:13:48.265 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2017-08-15 00:13:48.265 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 52: Application Command Request (ALIVE:DONE)
2017-08-15 00:13:48.265 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 52: resetResendCount initComplete=true isDead=false
2017-08-15 00:13:48.265 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 52: Incoming command class COMMAND_CLASS_BASIC, endpoint 0
2017-08-15 00:13:48.265 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 52: SECURITY NOT required on COMMAND_CLASS_BASIC
2017-08-15 00:13:48.266 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 52: Received COMMAND_CLASS_BASIC V1 BASIC_SET
2017-08-15 00:13:48.266 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 52: Basic report, value = 255
2017-08-15 00:13:48.266 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2017-08-15 00:13:48.266 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 52: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-08-15 00:13:48.266 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 52: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_BASIC, value = 255
2017-08-15 00:13:48.266 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 52: Updating channel state zwave:device:f180343d:node52:switch_binary to ON [OnOffType]
2017-08-15 00:13:48.270 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 52: Commands processed 1.
2017-08-15 00:13:48.270 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 52: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@3025de2a.
2017-08-15 00:13:48.270 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2017-08-15 00:13:48.270 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2017-08-15 00:13:48.270 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2017-08-15 00:13:48.270 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start
2017-08-15 00:13:48.270 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 49: listening == false, frequentlyListening == false, awake == false
2017-08-15 00:13:48.270 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 49: Node not awake!
--
2017-08-15 00:13:48.282 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 34 03 20 01 FF 1B 
2017-08-15 00:13:48.282 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Response SENT 6
2017-08-15 00:13:48.282 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=52, callback=0, payload=00 34 03 20 01 FF 
2017-08-15 00:13:48.282 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=52, callback=0, payload=00 34 03 20 01 FF 
2017-08-15 00:13:48.282 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=52, callback=0, payload=00 34 03 20 01 FF 
2017-08-15 00:13:48.282 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2017-08-15 00:13:48.282 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 52: Application Command Request (ALIVE:DONE)
2017-08-15 00:13:48.283 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 52: resetResendCount initComplete=true isDead=false
2017-08-15 00:13:48.283 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 52: Incoming command class COMMAND_CLASS_BASIC, endpoint 0
2017-08-15 00:13:48.283 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 52: SECURITY NOT required on COMMAND_CLASS_BASIC
2017-08-15 00:13:48.283 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 52: Received COMMAND_CLASS_BASIC V1 BASIC_SET
2017-08-15 00:13:48.283 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 52: Basic report, value = 255
2017-08-15 00:13:48.283 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2017-08-15 00:13:48.283 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 52: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-08-15 00:13:48.283 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 52: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_BASIC, value = 255
2017-08-15 00:13:48.283 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 52: Updating channel state zwave:device:f180343d:node52:switch_binary to ON [OnOffType]
2017-08-15 00:13:48.287 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 52: Commands processed 1.
2017-08-15 00:13:48.287 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 52: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@5f44b70b.
2017-08-15 00:13:48.287 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2017-08-15 00:13:48.287 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2017-08-15 00:13:48.287 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2017-08-15 00:13:48.287 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start
2017-08-15 00:13:48.287 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 49: listening == false, frequentlyListening == false, awake == false
2017-08-15 00:13:48.287 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 49: Node not awake!

I’m quite happy with the central_scene working, except for the occasional missing release event after a long press, but I have seen this missing from many devices. Could be a critical timing in the protocol maybe? (I have also noticed that sending Z-wave commands too soon after receiving a central_scene event in a rule makes is unstable. Have to wait ~150ms. Could be related.)

Anyway, getting binary_switch1 & 2 state updates from S1 & S2 presses would make it perfect.

Cheers

chris · August 15, 2017, 11:26am

I would guess that this is related to multi-channel associations, but I’m not sure. I’ll check if I have one of these devices or not (I have a couple of unopened Fibaro devices - if I have one I’ll see if I can test this).

Newan · August 18, 2017, 6:50pm

i have an FGS212 this showed me also switch, swicht one and switch two. i have no directly connected light or something. i will only the notice as an switch (on /off) in openhab2 to change lighning an scenes?

is this possible or wrong device?
which setting are musst be set in Habmin?

thanks

OMR · August 18, 2017, 10:59pm

Totally possible. I also have nothing connected to the relay outputs and use it only as a scene controller.
Due to the fact that I don’t really care what the output states are, I only use the central scene parameter.

.item file:

Number WallSwitchStua (div, remotes) { channel = "zwave:device:f180343d:node52:scene_number" }

rule:

rule "WallSwitchLivingRoom" 
when
        Item WallSwitchStua received update
then 
    var swState = WallSwitchStua.state 
    var name = "WallSwitchStua" 
	logInfo(name, "Rule: Got: " + swState)
	
    if (nodOnDebounceTimer != null) {
        logInfo(name, "debounce active")
    	return
    }
	
    if(nodOnDebounceTimer == null) {
      logInfo(name, "debouncing start")
      nodOnDebounceTimer = createTimer(now.plusSeconds(debounceSeconds), [|
       	logInfo("WallSwitchStua", "debouncing done")
        nodOnDebounceTimer = null
        ]
    )}

	Thread::sleep(150)
    
    switch swState {
	    case 1.0: {logInfo(name, "Rule: Button1 SingleClick " + swState)}	    																		    	    
	    case 1.1: {logInfo(name, "Rule: Button1 Release " + swState)}
	    case 1.2: {logInfo(name, "Rule: Button1 Hold-down " + swState)}
	    case 1.3: {logInfo(name, "Rule: Button1 DoubleClick " + swState)}	    
	    case 2.0: {logInfo(name, "Rule: Button2 SingleClick " + swState)}	    
	    case 2.1: {logInfo(name, "Rule: Button2 Release " + swState)}
	    case 2.2: {logInfo(name, "Rule: Button2 Hold-down " + swState)}
	    case 2.3: {logInfo(name, "Rule: Button2 DoubleClick " + swState)}	    
	    default:  {logInfo(name, "Rule: Say what? " + swState)}
    }

end

Hope that you will get it working!

norbert_jordan · September 7, 2017, 2:45pm

Any progress here? also suffering with FGS223 and FGS222 regarding updates to the GUI when manual button switch is pressed…so running out of sync.

Thanks, Norbert

sihui · September 8, 2017, 5:09pm

Ahiel · October 22, 2017, 11:55am

What kind of USB Zwave stick are you using?

sihui · October 22, 2017, 3:23pm

Me? https://www.z-wave.me/index.php?id=28

Marco_Goncalves · March 14, 2018, 1:01am

Any solution without using scenes? I have the same problem.

I am using ZWave Binding 2.3.0.201803101457 and I only get update changed when pressing S1 or S2 on binary_switch. The binary_switch1 & 2 I get no updates.

DubZ · May 1, 2018, 3:40pm

@chris dont want to spam you. but this is still not solved. I have exactly the same problem (like also discussed in Problems with states/events)

I switch my controller from uzb1 to aeotec gen5. I tried a lot zwave bindings from standard 2.2.0 to different 2.3.0 snapshots. I dont get the states from all my fibaro switchs. always, when I change something in my zwave configruation (a new binding snapshot, a new controller, including a new device, …) some fibaro switchs are working with state on switch_binary1 and 2 and some not. after changing something again, its randomly again some other fibaro where it is working and where not.

I spent a lot of time now in that and I’m nearly to discontinue with openhab because I dont want to buy new zwave devices to get this problem solved… ;(

sihui · May 1, 2018, 9:09pm

I’m following your different posts since a while but your problem is very strange. And it is hard to give you any advice because you are trying to many things at the same time: switching from Win to Linux, switching from one Zwave stick to another, switching between different zwave bindings …
The Fibaros are working fine, I have several of those and they do report their states fine and instantly.
You need to stick to one configuration (hardware and software), then switch the binding to debug, then feed the debug log through the log viewer.

Good luck.

DubZ · May 2, 2018, 7:51am

Hi sihui,

I will do this as last step the next days when I have time. but we are talking here from basic functionallity where I expect that this will work without doing of troubleshooting and debugging. I’m not the only person which response about state report issues with at least the fibaro double switch. more I’m reading and troubleshooting, more threads I find which exactly discussing this issue.

dont get me wrong, but we are talking here from basics, no scripting, configuring, parameterizing, … I feel good with openhab, its a really great community and a great tool but its similar like my decission iobroker vs openhab - why I chose openhab. First I started with iobroker and zwave wasnt working on windows OS (as far as I know there is a new release for some days now so it is working on windows again). so I switched to openhab because I dont want to struggle with so simple basic things.

question too you: do you have the FGS-223 double switch? Or other fibaro modules.

so… I stop my offense now and come back with a better troubleshoot with log file again.

sihui · May 2, 2018, 8:22am

As I already said before: yes, several of those

Here is part of the events.log when switching one of my FGS223 via the physical switch, also the GUI is reflecting the actual state without any issues

2018-05-02 10:15:23.948 [vent.ItemStateChangedEvent] - FibFGS223_1_Sw_2 changed from OFF to ON
2018-05-02 10:15:25.594 [vent.ItemStateChangedEvent] - FibFGS223_1_Sw_1 changed from OFF to ON
2018-05-02 10:15:25.655 [vent.ItemStateChangedEvent] - FibFGS223_1_Scenes changed from 2.0 to 1.0
2018-05-02 10:15:26.681 [vent.ItemStateChangedEvent] - FibFGS223_1_watt2 changed from 0 to 2.6
2018-05-02 10:15:26.688 [GroupItemStateChangedEvent] - gEnergyW changed from 3.2 to 5.8 through FibFGS223_1_watt2
2018-05-02 10:15:27.695 [vent.ItemStateChangedEvent] - FibFGS223_1_watt1 changed from 0 to 7.7
2018-05-02 10:15:27.702 [GroupItemStateChangedEvent] - gEnergyW changed from 5.8 to 13.5 through FibFGS223_1_watt1
2018-05-02 10:15:27.733 [vent.ItemStateChangedEvent] - FibFGS223_1_Sw_2 changed from ON to OFF
2018-05-02 10:15:27.797 [vent.ItemStateChangedEvent] - FibFGS223_1_Scenes changed from 1.0 to 2.1
2018-05-02 10:15:28.680 [vent.ItemStateChangedEvent] - FibFGS223_1_watt2 changed from 2.6 to 0
2018-05-02 10:15:28.685 [GroupItemStateChangedEvent] - gEnergyW changed from 13.5 to 10.9 through FibFGS223_1_watt2
2018-05-02 10:15:29.545 [vent.ItemStateChangedEvent] - FibFGS223_1_Sw_1 changed from ON to OFF
2018-05-02 10:15:29.602 [vent.ItemStateChangedEvent] - FibFGS223_1_Scenes changed from 2.1 to 1.0
2018-05-02 10:15:29.765 [GroupItemStateChangedEvent] - gEnergyW changed from 10.9 to 3.2 through FibFGS223_1_watt1
2018-05-02 10:15:29.767 [vent.ItemStateChangedEvent] - FibFGS223_1_watt1 changed from 7.7 to 0

Make sure you are using channels switch_binary1 and switch_binary2

DubZ · May 2, 2018, 7:09pm

after reading through the different threads they exists I found the association groups. When setting the association group the the openhab controller, some fibaro devices started to work correctly, some still not.

one example:
I press the switch from Node 7 and the light goes from off to on. the event got successfully reported back to openhab! but when I press the light from on to off, habpanel still shows the light on. I switched the log level to debug and when I understand it correct, the problem is that the fibaro device reports a scene number 99 and a status ON instead of OFF…

2018-05-02 21:03:42.608 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: sendTransaction org.openhab.binding.zwave.internal.protocol.ZWaveSerialPayload@4926ff86
2018-05-02 21:03:42.609 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Adding to controller queue
2018-05-02 21:03:42.609 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Added to queue - size 1
2018-05-02 21:03:42.609 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start
2018-05-02 21:03:42.610 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:42.610 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Node not awake!
2018-05-02 21:03:42.610 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:42.611 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Node not awake!
2018-05-02 21:03:42.611 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 11: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:42.611 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Node not awake!
2018-05-02 21:03:42.612 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:42.612 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Node not awake!
2018-05-02 21:03:42.613 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction from controllerQueue
2018-05-02 21:03:42.613 [DEBUG] [nal.protocol.ZWaveTransactionManager] - getTransactionToSend 6
2018-05-02 21:03:42.614 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 00 62 03 9A 
2018-05-02 21:03:42.614 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 04 00 62 03 9A 
2018-05-02 21:03:42.615 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2018-05-02 21:03:42.615 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1609: Transaction Start type IsFailedNodeID 
2018-05-02 21:03:42.616 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 1609: [WAIT_RESPONSE] requiresResponse=true callback: 0
2018-05-02 21:03:42.616 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2018-05-02 21:03:42.616 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: expected cmd class: null
2018-05-02 21:03:42.616 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-05-02 21:03:42.616 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: expected cmd: null
2018-05-02 21:03:42.617 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-05-02 21:03:42.617 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage Transactions outstanding: 1
2018-05-02 21:03:42.617 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Start transaction timer to Wed May 02 21:03:44 CEST 2018 - 2000ms
2018-05-02 21:03:42.617 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 62 01 99 
2018-05-02 21:03:42.618 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage lastTransaction: TID 1609: [WAIT_RESPONSE] requiresResponse=true callback: 0
2018-05-02 21:03:42.618 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 1<>127 : Message: class=IsFailedNodeID[98], type=Response[1], dest=255, callback=0, payload=01 
2018-05-02 21:03:42.618 [DEBUG] [nal.protocol.ZWaveTransactionManager] - STOP transaction timer
2018-05-02 21:03:42.618 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=IsFailedNodeID[98], type=Response[1], dest=255, callback=0, payload=01 
2018-05-02 21:03:42.618 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Start transaction timer to Wed May 02 21:03:44 CEST 2018 - 1999ms
2018-05-02 21:03:42.619 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (1): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-05-02 21:03:42.619 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 1609: [WAIT_RESPONSE] requiresResponse=true callback: 0
2018-05-02 21:03:42.620 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2018-05-02 21:03:42.620 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=IsFailedNodeID[98], type=Response[1], dest=255, callback=0, payload=01 
2018-05-02 21:03:42.620 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 1609: [WAIT_RESPONSE] requiresResponse=true callback: 0
2018-05-02 21:03:42.621 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2018-05-02 21:03:42.624 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 1609: [WAIT_RESPONSE] requiresResponse=true callback: 0
2018-05-02 21:03:42.625 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=IsFailedNodeID[98], type=Response[1], dest=255, callback=0, payload=01 
2018-05-02 21:03:42.626 [DEBUG] [rialmessage.IsFailedNodeMessageClass] - NODE 3: Is currently marked as failed by the controller!
2018-05-02 21:03:42.626 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1609: Transaction COMPLETED
2018-05-02 21:03:42.626 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1609: TransactionAdvance ST: DONE
2018-05-02 21:03:42.627 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1609: TransactionAdvance WT: null {}
2018-05-02 21:03:42.627 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1609: TransactionAdvance RX: Message: class=IsFailedNodeID[98], type=Response[1], dest=255, callback=0, payload=01 
2018-05-02 21:03:42.628 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1609: TransactionAdvance TO: DONE
2018-05-02 21:03:42.628 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Response processed after 13ms
2018-05-02 21:03:42.628 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: TID 1609: Transaction completed
2018-05-02 21:03:42.628 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: notifyTransactionResponse TID:1609 DONE
2018-05-02 21:03:42.629 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2018-05-02 21:03:42.629 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-05-02 21:03:42.630 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start
2018-05-02 21:03:42.630 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:42.630 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Node not awake!
2018-05-02 21:03:42.631 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:42.631 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Node not awake!
2018-05-02 21:03:42.631 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 11: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:42.632 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Node not awake!
2018-05-02 21:03:42.632 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:42.632 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Node not awake!
2018-05-02 21:03:42.633 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction from controllerQueue
2018-05-02 21:03:42.633 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage nothing
2018-05-02 21:03:42.633 [DEBUG] [nal.protocol.ZWaveTransactionManager] - STOP transaction timer
2018-05-02 21:03:42.634 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 1609: Transaction event listener: DONE: DONE -> 
2018-05-02 21:03:42.636 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: -- To notify -- COMPLETE
2018-05-02 21:03:42.637 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ********* Transaction Response Complete -- 1609 --
2018-05-02 21:03:42.637 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 3: Node Init response (0) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@47d38011
2018-05-02 21:03:42.638 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 3: Node Init transaction completed with response COMPLETE
2018-05-02 21:03:43.328 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 08 07 07 60 0D 01 01 20 01 63 D1 
2018-05-02 21:03:43.329 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=7, callback=8, payload=08 07 07 60 0D 01 01 20 01 63 
2018-05-02 21:03:43.330 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[4], type=Request[0], dest=7, callback=8, payload=08 07 07 60 0D 01 01 20 01 63 
2018-05-02 21:03:43.330 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=7, callback=8, payload=08 07 07 60 0D 01 01 20 01 63 
2018-05-02 21:03:43.331 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-05-02 21:03:43.331 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Application Command Request (ALIVE:DONE)
2018-05-02 21:03:43.331 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: resetResendCount initComplete=true isDead=false
2018-05-02 21:03:43.331 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2018-05-02 21:03:43.332 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Incoming command class COMMAND_CLASS_BASIC, endpoint 1
2018-05-02 21:03:43.332 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: SECURITY NOT required on COMMAND_CLASS_BASIC
2018-05-02 21:03:43.332 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 7: Received COMMAND_CLASS_BASIC V0 BASIC_SET
2018-05-02 21:03:43.332 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 7: Basic report, value = 99
2018-05-02 21:03:43.333 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2018-05-02 21:03:43.333 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-05-02 21:03:43.333 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got a value event from Z-Wave network, endpoint = 1, command class = COMMAND_CLASS_BASIC, value = 99
2018-05-02 21:03:43.334 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Updating channel state zwave:device:1aa147bc:node7:switch_binary1 to ON [OnOffType]
2018-05-02 21:03:43.335 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Commands processed 1.
2018-05-02 21:03:43.335 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@7810ed5.
2018-05-02 21:03:43.336 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-05-02 21:03:43.336 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-05-02 21:03:43.337 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-05-02 21:03:43.337 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start
2018-05-02 21:03:43.338 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:43.338 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Node not awake!
2018-05-02 21:03:43.338 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:43.339 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Node not awake!
2018-05-02 21:03:43.339 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 11: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:43.340 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Node not awake!
2018-05-02 21:03:43.340 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:43.341 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Node not awake!
2018-05-02 21:03:43.341 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction from controllerQueue
2018-05-02 21:03:43.341 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage nothing
2018-05-02 21:03:43.343 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 00 07 07 60 0D 01 01 20 01 63 D9 
2018-05-02 21:03:43.345 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=7, callback=0, payload=00 07 07 60 0D 01 01 20 01 63 
2018-05-02 21:03:43.346 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[4], type=Request[0], dest=7, callback=0, payload=00 07 07 60 0D 01 01 20 01 63 
2018-05-02 21:03:43.347 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=7, callback=0, payload=00 07 07 60 0D 01 01 20 01 63 
2018-05-02 21:03:43.347 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-05-02 21:03:43.348 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Application Command Request (ALIVE:DONE)
2018-05-02 21:03:43.348 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: resetResendCount initComplete=true isDead=false
2018-05-02 21:03:43.348 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2018-05-02 21:03:43.349 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Incoming command class COMMAND_CLASS_BASIC, endpoint 1
2018-05-02 21:03:43.349 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: SECURITY NOT required on COMMAND_CLASS_BASIC
2018-05-02 21:03:43.349 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 7: Received COMMAND_CLASS_BASIC V0 BASIC_SET
2018-05-02 21:03:43.350 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 7: Basic report, value = 99
2018-05-02 21:03:43.350 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2018-05-02 21:03:43.350 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-05-02 21:03:43.351 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got a value event from Z-Wave network, endpoint = 1, command class = COMMAND_CLASS_BASIC, value = 99
2018-05-02 21:03:43.351 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Updating channel state zwave:device:1aa147bc:node7:switch_binary1 to ON [OnOffType]
2018-05-02 21:03:43.352 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Commands processed 1.
2018-05-02 21:03:43.352 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@3dc2e39b.
2018-05-02 21:03:43.353 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-05-02 21:03:43.353 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-05-02 21:03:43.353 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-05-02 21:03:43.354 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start
2018-05-02 21:03:43.354 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:43.355 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Node not awake!
2018-05-02 21:03:43.355 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:43.356 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Node not awake!
2018-05-02 21:03:43.356 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 11: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:43.357 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Node not awake!
2018-05-02 21:03:43.357 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:43.357 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Node not awake!
2018-05-02 21:03:43.358 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction from controllerQueue
2018-05-02 21:03:43.358 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage nothing
2018-05-02 21:03:43.484 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 04 0A 32 02 21 44 00 00 01 2D 00 00 9C 
2018-05-02 21:03:43.485 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 0A 32 02 21 44 00 00 01 2D 00 00 
2018-05-02 21:03:43.485 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 0A 32 02 21 44 00 00 01 2D 00 00 
2018-05-02 21:03:43.486 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 0A 32 02 21 44 00 00 01 2D 00 00 
2018-05-02 21:03:43.486 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-05-02 21:03:43.487 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Application Command Request (ALIVE:DONE)
2018-05-02 21:03:43.487 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: resetResendCount initComplete=true isDead=false
2018-05-02 21:03:43.487 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Incoming command class COMMAND_CLASS_METER, endpoint 0
2018-05-02 21:03:43.487 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY NOT required on COMMAND_CLASS_METER
2018-05-02 21:03:43.488 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 4: Received COMMAND_CLASS_METER V3 METER_REPORT
2018-05-02 21:03:43.489 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 4: Meter: Type=Electric(1), Scale=kWh(0), Value=3.01
2018-05-02 21:03:43.489 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMeterValueEvent
2018-05-02 21:03:43.490 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveMeterValueEvent
2018-05-02 21:03:43.490 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_METER, value = 3.01
2018-05-02 21:03:43.491 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Updating channel state zwave:device:1aa147bc:node4:meter_kwh to 3.01 [DecimalType]
2018-05-02 21:03:43.491 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Commands processed 1.
2018-05-02 21:03:43.491 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@55090d5f.
2018-05-02 21:03:43.492 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-05-02 21:03:43.492 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-05-02 21:03:43.492 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-05-02 21:03:43.492 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start
2018-05-02 21:03:43.493 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:43.493 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Node not awake!
2018-05-02 21:03:43.494 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:43.494 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Node not awake!
2018-05-02 21:03:43.494 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 11: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:43.495 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Node not awake!
2018-05-02 21:03:43.495 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: listening == false, frequentlyListening == false, awake == false
2018-05-02 21:03:43.495 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Node not awake!
2018-05-02 21:03:43.496 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction from controllerQueue
2018-05-02 21:03:43.496 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage nothing

update: this switch is a momentary switch… the others are toggle. so setup was on toggle instead of momentary (my fault). I will test more and keep you informed.

havaak · November 30, 2018, 2:17pm

I have been pulling my hair out (which is very difficult ) why my newly bought FGS-223 did not report the right scenes, only to discover the switch was setup as toggle which is plain wrong as I have momentary switches. Did not notice this however because even with this setting the load was switched.
So when setting up scenes on the FGS-223:

check lifeline to controller
option 28/29: 15
when you have a momentary switch, then make sure the setup resembles this!