One of my Steinel IS 140-2 Z-Wave is not working

Tags: #<Tag:0x00007faf7df5bb38>

Hi,

I have the Aeotec 5th Generation Z-Wave controller on my OpenHAB 2.5.9-1 (On Raspi 3B+)
I have connected 3 Steinel IS 140-2 Z-Wave motion sensors which I want to control using OpenHAB. Two of them work without any problem. But one of them not.
I cannot switch it on/off using HABMin. If I click the switch (or relay) button in HABMin nothing happens. Paper UI says it is online.
I compared the configuration settings of one of the working sensors with the one which is not working - but I cannot see any difference.

This is my Z-Wave network:

ZWave_network

1: Controller
2: 1st Steinel IS 140-2 Z-Wave (working)
3. 2nd Steinel IS 140-2 Z-Wave (not working)
4: 3rd Steinel IS 140-2 Z-Wave (working)

This is where the controller and sensors are located:
(the red one is the one which is not working)

ZWave_network_2

The biggest distance between sensor and controller is between sensor 4 and the z-wave controller 1 and is around 15m.

What I am missing please?

When you enabled DEBUG logging as recommended by the binding documentation, what did the system tell you about this?

Hi Bruce,

thanks for taking care. If I press the button inside HABmin this is what the log gives me:

2020-11-20 19:43:28.639 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Command received zwave:device:b4391616f41:node3:switch_binary --> OFF [OnOffType]
2020-11-20 19:43:28.648 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 3: Creating new message for application command SWITCH_BINARY_SET
2020-11-20 19:43:28.649 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: SECURITY not supported
2020-11-20 19:43:28.653 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: Command Class COMMAND_CLASS_SWITCH_BINARY is NOT required to be secured
2020-11-20 19:43:28.655 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Adding to device queue
2020-11-20 19:43:28.657 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Added 433 to queue - size 1
2020-11-20 19:43:28.665 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 3: Sending REQUEST Message = 01 0A 00 13 03 03 25 01 00 25 96 71
2020-11-20 19:43:28.670 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Polling initialised at 1800 seconds - start in 1500 milliseconds.
2020-11-20 19:43:28.693 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 3: sentData successfully placed on stack.
2020-11-20 19:43:28.696 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: TID 433: Transaction not completed
2020-11-20 19:43:28.743 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 3: SendData Request. CallBack ID = 150, Status = Transmission complete and ACK received(0)
2020-11-20 19:43:28.744 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: resetResendCount initComplete=true isDead=false
2020-11-20 19:43:28.747 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Response processed after 79ms
2020-11-20 19:43:28.748 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: TID 433: Transaction completed
2020-11-20 19:43:28.750 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: notifyTransactionResponse TID:433 DONE
2020-11-20 19:43:28.752 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2020-11-20 19:43:28.814 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Application Command Request (ALIVE:DONE)
2020-11-20 19:43:28.816 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: resetResendCount initComplete=true isDead=false
2020-11-20 19:43:28.817 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: Incoming command class COMMAND_CLASS_SWITCH_BINARY, endpoint 0
2020-11-20 19:43:28.819 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: SECURITY not supported
2020-11-20 19:43:28.820 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 3: Received COMMAND_CLASS_SWITCH_BINARY V1 SWITCH_BINARY_REPORT
2020-11-20 19:43:28.822 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 3: Switch Binary report, value = 0
2020-11-20 19:43:28.823 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2020-11-20 19:43:28.825 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SWITCH_BINARY, value=0
2020-11-20 19:43:28.827 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Updating channel state zwave:device:b4391616f41:node3:switch_binary to OFF [OnOffType]
2020-11-20 19:43:28.829 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Commands processed 1.
2020-11-20 19:43:28.832 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@8511c7.
2020-11-20 19:43:30.170 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Polling…
2020-11-20 19:43:30.172 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Polling zwave:device:b4391616f41:node3:switch_binary
2020-11-20 19:43:30.173 [DEBUG] [converter.ZWaveBinarySwitchConverter] - NODE 3: Generating poll message for COMMAND_CLASS_SWITCH_BINARY, endpoint 0
2020-11-20 19:43:30.175 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 3: Creating new message for application command SWITCH_BINARY_GET
2020-11-20 19:43:30.177 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: SECURITY not supported
2020-11-20 19:43:30.178 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: Command Class COMMAND_CLASS_SWITCH_BINARY is NOT required to be secured
2020-11-20 19:43:30.180 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Polling skipped for zwave:device:b4391616f41:node3:switch_binary on COMMAND_CLASS_BASIC
2020-11-20 19:43:30.182 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Polling zwave:device:b4391616f41:node3:alarm_burglar
2020-11-20 19:43:30.184 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Polling zwave:device:b4391616f41:node3:alarm_system
2020-11-20 19:43:30.186 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Polling zwave:device:b4391616f41:node3:alarm_motion1
2020-11-20 19:43:30.188 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Polling skipped for zwave:device:b4391616f41:node3:alarm_motion1 on COMMAND_CLASS_BASIC
2020-11-20 19:43:30.189 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Polling zwave:device:b4391616f41:node3:sensor_luminance2
2020-11-20 19:43:30.191 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 3: Generating poll message for COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 2
2020-11-20 19:43:30.193 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 3: Creating new message for command SENSOR_MULTILEVEL_GET
2020-11-20 19:43:30.194 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: Encapsulating message, instance / endpoint 2
2020-11-20 19:43:30.196 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 3: Creating new message for command MULTI_CHANNEL_ENCAP endpoint 2
2020-11-20 19:43:30.198 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: SECURITY not supported
2020-11-20 19:43:30.199 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: Command Class COMMAND_CLASS_MULTI_CHANNEL is NOT required to be secured
2020-11-20 19:43:30.201 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Polling skipped for zwave:device:b4391616f41:node3:sensor_luminance2 on COMMAND_CLASS_BASIC
2020-11-20 19:43:30.202 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Polling zwave:device:b4391616f41:node3:switch_binary3
2020-11-20 19:43:30.204 [DEBUG] [converter.ZWaveBinarySwitchConverter] - NODE 3: Generating poll message for COMMAND_CLASS_SWITCH_BINARY, endpoint 3
2020-11-20 19:43:30.206 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 3: Creating new message for application command SWITCH_BINARY_GET
2020-11-20 19:43:30.207 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: Encapsulating message, instance / endpoint 3
2020-11-20 19:43:30.209 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 3: Creating new message for command MULTI_CHANNEL_ENCAP endpoint 3
2020-11-20 19:43:30.211 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: SECURITY not supported
2020-11-20 19:43:30.212 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: Command Class COMMAND_CLASS_MULTI_CHANNEL is NOT required to be secured
2020-11-20 19:43:30.214 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Polling skipped for zwave:device:b4391616f41:node3:switch_binary3 on COMMAND_CLASS_BASIC
2020-11-20 19:43:30.216 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Adding to device queue
2020-11-20 19:43:30.217 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Added 434 to queue - size 1
2020-11-20 19:43:30.223 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 3: Sending REQUEST Message = 01 09 00 13 03 02 25 02 25 97 71
2020-11-20 19:43:30.229 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Adding to device queue
2020-11-20 19:43:30.231 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Added 435 to queue - size 1
2020-11-20 19:43:30.234 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Adding to device queue
2020-11-20 19:43:30.236 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Added 436 to queue - size 2
2020-11-20 19:43:30.252 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 3: sentData successfully placed on stack.
2020-11-20 19:43:30.255 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: TID 434: Transaction not completed
2020-11-20 19:43:30.303 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 3: SendData Request. CallBack ID = 151, Status = Transmission complete and ACK received(0)
2020-11-20 19:43:30.304 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: resetResendCount initComplete=true isDead=false
2020-11-20 19:43:30.307 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: TID 434: Transaction not completed
2020-11-20 19:43:30.375 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Application Command Request (ALIVE:DONE)
2020-11-20 19:43:30.377 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: resetResendCount initComplete=true isDead=false
2020-11-20 19:43:30.378 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: Incoming command class COMMAND_CLASS_SWITCH_BINARY, endpoint 0
2020-11-20 19:43:30.380 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: SECURITY not supported
2020-11-20 19:43:30.381 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 3: Received COMMAND_CLASS_SWITCH_BINARY V1 SWITCH_BINARY_REPORT
2020-11-20 19:43:30.383 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 3: Switch Binary report, value = 0
2020-11-20 19:43:30.384 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2020-11-20 19:43:30.386 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SWITCH_BINARY, value=0
2020-11-20 19:43:30.388 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Updating channel state zwave:device:b4391616f41:node3:switch_binary to OFF [OnOffType]
2020-11-20 19:43:30.390 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Commands processed 1.
2020-11-20 19:43:30.392 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@28f13f.
2020-11-20 19:43:30.394 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@28f13f.
2020-11-20 19:43:30.395 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: notifyTransactionResponse TID:434 DONE
2020-11-20 19:43:30.397 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2020-11-20 19:43:30.408 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 3: Sending REQUEST Message = 01 0D 00 13 03 06 60 0D 01 02 31 04 25 98 02
2020-11-20 19:43:30.434 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 3: sentData successfully placed on stack.
2020-11-20 19:43:30.436 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: TID 435: Transaction not completed
2020-11-20 19:43:30.510 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 3: SendData Request. CallBack ID = 152, Status = Transmission complete and ACK received(0)
2020-11-20 19:43:30.511 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: resetResendCount initComplete=true isDead=false
2020-11-20 19:43:30.514 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: TID 435: Transaction not completed
2020-11-20 19:43:30.590 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Application Command Request (ALIVE:DONE)
2020-11-20 19:43:30.591 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: resetResendCount initComplete=true isDead=false
2020-11-20 19:43:30.593 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2020-11-20 19:43:30.594 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0
2020-11-20 19:43:30.596 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: SECURITY not supported
2020-11-20 19:43:30.597 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 3: Received COMMAND_CLASS_SENSOR_MULTILEVEL V4 SENSOR_MULTILEVEL_REPORT
2020-11-20 19:43:30.599 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 3: Sensor Type = Luminance(3), Scale = 1
2020-11-20 19:43:30.600 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 3: Sensor Value = 3
2020-11-20 19:43:30.602 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2020-11-20 19:43:30.603 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_MULTILEVEL, value=3
2020-11-20 19:43:30.605 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Updating channel state zwave:device:b4391616f41:node3:sensor_luminance to 3 % [QuantityType]
2020-11-20 19:43:30.607 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Commands processed 1.
2020-11-20 19:43:30.608 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1275838.
2020-11-20 19:43:30.610 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1275838.
2020-11-20 19:43:30.611 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: notifyTransactionResponse TID:435 DONE
2020-11-20 19:43:30.613 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2020-11-20 19:43:30.623 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 3: Sending REQUEST Message = 01 0D 00 13 03 06 60 0D 01 03 25 02 25 99 10
2020-11-20 19:43:30.649 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 3: sentData successfully placed on stack.
2020-11-20 19:43:30.652 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: TID 436: Transaction not completed
2020-11-20 19:43:30.720 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 3: SendData Request. CallBack ID = 153, Status = Transmission complete and ACK received(0)
2020-11-20 19:43:30.721 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: resetResendCount initComplete=true isDead=false
2020-11-20 19:43:30.724 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: TID 436: Transaction not completed
2020-11-20 19:43:30.796 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Application Command Request (ALIVE:DONE)
2020-11-20 19:43:30.798 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: resetResendCount initComplete=true isDead=false
2020-11-20 19:43:30.799 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2020-11-20 19:43:30.801 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: Incoming command class COMMAND_CLASS_SWITCH_BINARY, endpoint 3
2020-11-20 19:43:30.802 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: SECURITY not supported
2020-11-20 19:43:30.804 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 3: Received COMMAND_CLASS_SWITCH_BINARY V1 SWITCH_BINARY_REPORT
2020-11-20 19:43:30.805 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 3: Switch Binary report, value = 0
2020-11-20 19:43:30.807 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2020-11-20 19:43:30.808 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got a value event from Z-Wave network, endpoint=3, command class=COMMAND_CLASS_SWITCH_BINARY, value=0
2020-11-20 19:43:30.810 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Updating channel state zwave:device:b4391616f41:node3:switch_binary3 to OFF [OnOffType]
2020-11-20 19:43:30.813 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Commands processed 1.
2020-11-20 19:43:30.814 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1d5e165.
2020-11-20 19:43:30.816 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1d5e165.
2020-11-20 19:43:30.817 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: notifyTransactionResponse TID:436 DONE
2020-11-20 19:43:30.819 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent

Btw: for the other sensors I can see lots of polling messages coming up.
But for the broken sensor not. For the broken one I can only see DEBUG messages if I hit the button inside HABmin.
Don’t know if this ifnormation is useful or not.

I am not a log expert but I know that unfiltered DEBUG logs are needed for troubleshooting. The online log viewer may give some clues until the experts arrive here.

Hi Bruce, thanks again, here is what the viewer shows with the log from above:

I forgot to mention that this sensor I already changed by a brand new one, because I thought it was defective. But the new one is just the same.
The log above comes from the new one - so the device itself should be fine - there is only something wrong with z-wave.

As Bruce mentioned - you need to use unfiltered logs as this otherwise doesn’t show you what’s happening.

1 Like

Hi Chris,

thanks but what does it mean: unfiltered logs?
I set the log level to debug using the karaf console and this command:

log:set debug org.openhab.binding.zwave

is there anything else?

Maybe I’m wrong, but it looks like you’ve filtered your logs using something like grep. This has removed a lot of the content and makes the logs unusable. We need to have the complete logs - not filtered for node 3 or anything else.

Apologies if that’s not what you’ve done here, but every line starts with Node 3, so this is just how it looks to me.

Hi Chris,

OK I understand, you were right I filtered for just Node 3.
I attached another file just filtered for zwave:

ZWave_log.txt (111.2 KB)

What I wonder now, if I look into HABMin for my Steinel IS1402 Z_Wave I don’t see the switch buttons, just empty lines:

This is for all 3 Steinel’s - no buttons anymore :frowning:

And just few minutes later, the buttons are back again:

I really don’t know what happens here, still need your help please!

The log you posted looks fine to me - the commands are going out to the device, and it’s responding just fine.

Here the binding is reading the luminance and switch state - responses are fast and it looks fine to me. Clearly the channels are there and the device is working fine - as far as I can tell anyway.

Hi Chris,

it gets even more strange. Now the node 4 does not work anymore, but node 3 is now working, means switching on/off in HABmin.
Then I powered off my garage so node 3 and node 4 booted up.
Now node 3 is not working anymore but node 4.

It seems that I can only use one of node 3 or node 4 at same time!?!

Here another logfiile, may it helps.

ZWave_log2.txt (108.4 KB)

Btw: This is what my network looks now:

ZWave_network2

The new log you provided doesn’t show any activity with node 4 - only node 3.

I’m not sure what this log shows - as above, there is only any activity with node 3, which if I understand your statement above, is not working :confused: . The log shows it’s working fine - the same as the earlier log you provided, but there is no activity with node 4. I’d suggest to create a log showing activity with both devices - or at least clearly state what the log is meant to show.

Hi Chris,

sorry for the confusion. Here another log.
1st I switched node 3 on then off and again on and off.
The light on the garage did not follow - it keeps off.

Then I switched node 4 on and off and again on and off.
The light on the garage follwos exactly this on and off procedure.

What I also see is, there are two items for each Steinel (see screenshot from one of the prev. messages):

  1. Switch
  2. Relais

For node 3 if I set switch to on then it takes around 5 sec. and then the relais follows.
The light on the garage itself keeps off.
But for node 4 if I set switch to on then immediately the relais turns on as well and the light follows - don’t know if this information is helpful or not.

ZWave_log3.txt (255.9 KB)

I created a simple Basic UI and created a screencast. There you can see that node 3 needs more time to set the relais to on whereas node 4 sets the relais immediately to on if I activate the switch. Again, don’t know if this is an useful information.

Here is the link to the video:

The summary here is that everything looks ok to me…

The log shows it worked fine - both on and off commands respond quite quickly and the channels are updated accordingly -:

This also looks fine -:


I really can’t see anything wrong here - from the logs, and the responses from the devices, it looks like it’s working fine to me… The one interesting point is that the commands are sent to the root node (ie unencapsulated), but the responses come back from EP-3. This tells me that the switch on the root endpoint is likely mapped to endpoint 3 and probably you should just use the EP3 command (which is the one called Relay Switch). (I’ll repeat though - I don’t know the device, and I don’t have one, so I’m only going on what I see in the logs, which requires a little bit of guesswork). I think this is reflected in what the video shows as well - you send a command on the switch, the UI is updating this so it updates immediately. The response comes back on the Relay channel and this is a little later due to delays in the ZWave network.

I’m not familiar with this device so can’t really be sure how it works. There shouldn’t be any difference from the binding perspective, but maybe the device uses these differently. From the binding perspective, they are similar functions - just using different endpoints.

As far as I can see, all commands to both devices respond quickly, and reliably, so I don’t see any issue other than possibly with how the device is configured, or the channels are being used.

I hope this helps :slight_smile:

Hi Chris,

But what does that mean exactly? Should I change something in Paper UI or HABmin?
If yes - what please?

The short answer is that ZWave devices can have multiple endpoints (so kind of logical devices), and they always have a root endpoint (for backward compatibility with devices from before multi channel endpoints were added.

A device will map endpoint functions into the root endpoint - ZWave doesn’t define how this is done. In this case, it appears that the switch in Endpoint0 (root) is mapped to the Relay in endpoint 3.

I would suggest not to use the switch at all - just use the relay channel. It should be exactly the same functionality (as far as I can see) but it avoids this strange cross mapping of commands and responses.

OK,

but if I click on the relais button (instead switch) inside the Basic UI then the light does also not turn on or off. It just keeps off.

This is really strange since this is a brand new device and the prevoius one (which I thought it was broken) has exactly the same behaviour.

The Z-Wave command reach the device but it does not turn on / off the light bulp.
If I move myself to the sensor the light switches on and inside HABmin I can see the switch-channel turning on as well, the relay-channel stays off. This way around it works.
But switching on/off from within HABmin or Basic UI it does not work - but only for this device. This is really strange to me.

Any further ideas are highly welcome…

Sure - I understand that’s what you’re reporting, but that’s a different question. As far as I can see from the logs (and as I’ve shown above) everything is working at the ZWave level. The device is reporting that it has changed state, and you see this in the video you showed.

I can really only point you at the device manual - maybe there is something there. I had a quick look, and it talks about things like twilight mode as being a reason for it not switching on - maybe it’s not configured correctly?

I would suggest to reset the device to factory defaults.

1 Like

Hi Chris,

thanks for your patience.
I several time set the device (and also the previous one, which I thought it was broken) back to factory settings. But the result is always the same.
What I wonder is that today one time this node 3 worked, as you can read in one of my previous posts. But at the same time the node 4 did not work anymore and had the same issues. Then I removed power of both nodes and the behaviour swapped. Means Node 3 was not working anymore and node 4 was working again.
I am not a Z-Wave expert at all, but can it be that the devices block each other somehow?