Problem with Steinel 140-2

[mr.burns]

Hi,

a few days now I have a Steinel 140-S up and running. My Z-Wave controller is a Z-Wave Aeon Labs USB-Stick GEN5 connected to my Rasppi 3B+ and OpenHAB latest version.
Using HABMin I set following parameters for Steinel 140-2:

Following items I monitored using Grafana and influxdb persistence:

switch_binary
switch_binary3
alarm_motion1
sensor_luminance
sensor_luminance2
alarm_burglar
alarm_system

My problem now is that sometimes in the morning the light is on even light value is above 200.
If I look into the current state of the Steinel 140-2 (in PaperUI–>Controls) the switch_binary
and switch_binary3 are off, same in HABmin. But the light is on!?!.
If I look into the persistence values in Grafana I can see some motion triggers followed by switch_binary3 turning from 0 to 1 and after 180s back to 0 that means the light should still be off.
As I can see from the values the light should be off but it is on!?!

I wonder why the light is on. Can someone explain this?

Thanks…

[Bruce_Osborne]

Follow the instructions for the binding and post unfiltered debug logs. Only the system has the information you seek.

[mr.burns]

Hi Bruce,

thanks, you said ‘Follow the instructions for the binding’.
The instructions are quite long. Is there something special I have to focus on?
And since I am not an expert how to get unfiltered debug logs please?

[Bruce_Osborne]

@mr.burns

Is there something special I have to focus on?

How about “When things don’t go as planned” ?

ZWave - Bindings

[mr.burns]

Hi Bruce,

great thanks. Now I have the Z-Wave logging activated in the Karafg console using:

log:set DEBUG org.openhab.binding.zwave

Now I will wait until the light gets on for some reason and report back.

Thanks so far…

[mr.burns]

Hi,

the log shows sometimes:

2020-05-21 16:54:14.983 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Retry count exceeded. Discarding message: TID 140: [CANCELLED] priority=Get, requiresResponse=true, callback: 211

2020-05-21 16:54:14.986 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveNodeStatusEvent

2020-05-21 16:54:14.989 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Setting OFFLINE

2020-05-21 16:54:14.995 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 7: Node Status event - Node is DEAD

2020-05-21 16:54:14.997 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Node is DEAD.

2020-05-21 16:54:14.999 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveNodeStatusEvent

2020-05-21 16:54:15.002 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Setting OFFLINE

2020-05-21 16:54:15.003 [hingStatusInfoChangedEvent] - ‘zwave:device:16f41b43916:node7’ changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller

2020-05-21 16:54:15.008 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 7: Node Status event - Node is DEAD

2020-05-21 16:54:15.010 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: TID 140: Transaction completed

2020-05-21 16:54:15.013 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: notifyTransactionResponse TID:140 CANCELLED

2020-05-21 16:54:15.021 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent

2020-05-21 16:54:15.034 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 7: Sending REQUEST Message = 01 0D 00 13 07 06 60 0D 01 02 31 04 25 D4 4A

2020-05-21 16:54:15.064 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 7: sentData successfully placed on stack.

2020-05-21 16:54:15.068 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: TID 141: Transaction not completed

2020-05-21 16:54:15.167 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 7: SendData Request. CallBack ID = 212, Status = Transmission complete and ACK received(0)

2020-05-21 16:54:15.170 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveNodeStatusEvent

2020-05-21 16:54:15.171 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Setting ONLINE

2020-05-21 16:54:15.176 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 7: Node Status event - Node is ALIVE

2020-05-21 16:54:15.177 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Node is ALIVE. Init stage is DONE.

2020-05-21 16:54:15.179 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveNodeStatusEvent

2020-05-21 16:54:15.181 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Setting ONLINE

2020-05-21 16:54:15.183 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 7: Node Status event - Node is ALIVE

2020-05-21 16:54:15.187 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: TID 141: Transaction not completed

2020-05-21 16:54:15.190 [hingStatusInfoChangedEvent] - ‘zwave:device:16f41b43916:node7’ changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to ONLINE

2020-05-21 16:54:17.117 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Application Command Request (ALIVE:DONE)

2020-05-21 16:54:17.119 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: resetResendCount initComplete=true isDead=false

2020-05-21 16:54:17.121 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Decapsulating COMMAND_CLASS_MULTI_CHANNEL

2020-05-21 16:54:17.124 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 2

2020-05-21 16:54:17.126 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: SECURITY not supported

So it seams the the Node has connectivity problems. This really wonders becuase this node is only 10 meters away from the AEON Labs USB stick. I have another Steinel IS140-2 which is around 20 meters away but this one has no communication problems.

My questions now:

1:
Can this connection issue cause my initial problem? Means can it switch on the lamp (and keep switched on forever) without any motion detected?

2:
I read somewhere that Z-Wave devices can work in mesh mode. This means not every node is connected directly to the controller (in my case the Aeon stick) but connected via another node - similar like a chain. It is called routing. Can I check somehow how the nodes are currently routed/connected?
Can I change the routing manually between all nodes to get better connectivity?
If yes how?

3:
Is there any way to check the z-wave network using OpenHab, HABmin or any other tool?
I want to see the signal strength of any node to come closer the my issue

Thanks again for any help…

[Bruce_Osborne]

Until an expert arrives, perhaps the log viewer can provide some insights

https://www.cd-jackson.com/index.php/openhab/zwave-log-viewer.

[chris (Chris Jackson)]

@mr.burns

This really wonders becuase this node is only 10 meters away from the AEON Labs USB stick. I have another Steinel IS140-2 which is around 20 meters away but this one has no communication problems.

RF doesn’t know about distance - it knows about signal strength (actually signal to noise ratio). Things that matter to signal strength of a signal at a receive include distance (the obvious one), but also the building you’re in, the environment (eg TV, microwave, WiFi etc), temperature, and the antenna alignment, how the devices are mounted (are they close to concrete or metal)…

I don’t expect you (or anyone actually) to be able to account for all this - it’s not really possible with such consumer electronics. My point is really distance isn’t everything. You could be 1m away, but if that 1m includes a thick wall, it might not work.

@mr.burns

Can this connection issue cause my initial problem? Means can it switch on the lamp (and keep switched on forever) without any motion detected?

Yes, absolutely, this is very likely the issue.

@mr.burns

Can I check somehow how the nodes are currently routed/connected?

The node properties provides the list of neighbours. This isn’t the same as routes, but if every node has a lot of neighbours, then the mesh can be considered good, and routing should work well. If nodes only hae one or two neighbours, then you will likely have problems.

@mr.burns

Can I change the routing manually between all nodes to get better connectivity?

No - this is managed by the controller.

@mr.burns

Is there any way to check the z-wave network using OpenHab, HABmin or any other tool?

No - it’s not possible to see the signal strengths.

[mr.burns]

Hi Bruce,

thanks for the detailed reply.
In PaperUI–>Properties for the Steinel IS140-2 I found following values:

As you can see the zwave_neighbours is empty. In total I have 3 Steinel IS140-2 in my mesh.
But all show zwave_neighbours as empty.
Is there any configuration setting I miss? May I have to switch each node into bridge/mesh mode first?

[chris (Chris Jackson)]

@mr.burns

In total I have 3 Steinel IS140-2 in my mesh.

What other devices do you have in your network?

Neighbours are updated during the heal, but often battery devices may not show up, depending on wakeup times at least.

[mr.burns]

Hi Chris,

I have only 3 devices in my mesh.
All are Steinel IS140-2. All are powered by 230V.

[NCO (E. Gerland)]

Hi @mr.burns
Have you even solved the issue with your Steinel IS140? I have the same issue (although I can Switch the loght (switch_binary3) and get luminance (Sensor_Luminance_2)

[Gerry_Maguire]

I only ever had 1 device from Steinel on my Z-Wave network, an outside light. For whatever reason it caused havoc on my network (caused other devices to drop, flooded the log constantly). Ended up excluding it, it was shit, to be honest.Never again