Switch goes on, but why?

Setup, Configuration and Use Items & Sitemaps
,
1

Hi All,

I have a switch item that goes on (and off) without clear reason.

In the zwave log I find the following :

`2024-10-11 08:01:51.583 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2024-10-11 08:01:51.583 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2024-10-11 08:01:51.632 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 00 1E 07 60 0D 01 01 25 03 FF 5B 
2024-10-11 08:01:51.633 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=30, callback=0, payload=00 1E 07 60 0D 01 01 25 03 FF 
2024-10-11 08:01:51.633 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=30, callback=0, payload=00 1E 07 60 0D 01 01 25 03 FF 
2024-10-11 08:01:51.633 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 9793: [WAIT_REQUEST] priority=Get, requiresResponse=true, callback: 127
2024-10-11 08:01:51.633 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 30: Application Command Request (ALIVE:DONE)
2024-10-11 08:01:51.633 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 30: resetResendCount initComplete=true isDead=false
2024-10-11 08:01:51.633 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 30: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2024-10-11 08:01:51.633 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 30: Incoming command class COMMAND_CLASS_SWITCH_BINARY, endpoint 1
2024-10-11 08:01:51.633 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 30: SECURITY NOT required on COMMAND_CLASS_SWITCH_BINARY
2024-10-11 08:01:51.633 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 30: Received COMMAND_CLASS_SWITCH_BINARY V1 SWITCH_BINARY_REPORT
2024-10-11 08:01:51.634 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 30: Switch Binary report, value = 255
2024-10-11 08:01:51.634 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 30: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2024-10-11 08:01:51.634 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 30: Got a value event from Z-Wave network, endpoint=1, command class=COMMAND_CLASS_SWITCH_BINARY, value=255
2024-10-11 08:01:51.634 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 30: Updating channel state zwave:device:20d35cc2:node30:switch_binary1 to ON [OnOffType]
2024-10-11 08:01:51.634 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 30: Commands processed 1.
2024-10-11 08:01:51.634 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 30: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@d8c7e2c.
2024-10-11 08:01:51.634 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1
2024-10-11 08:01:51.634 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1
2024-10-11 08:01:51.634 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty`

In the eventlog at the same time :

> 2024-10-11 08:01:51.634 [vent.ItemStateChangedEvent] - SchakelaarDampkap changed from OFF to ON

Since there is no “item received command” in the Event-log I suppose it the Thing (a FGS223) goes on and reports it to the controller. Is this assumption correct ?

And more important : how to find out what triggered the change to “ON” ?

2

I’m by no means an expert for zwave, but

2024-10-11 08:01:51.633 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 30: Incoming command class COMMAND_CLASS_SWITCH_BINARY, endpoint 1

it seems that some zwave device sent a command.

3

I noticed the same line, so I have the same tought, but how to find out which one ? Can it be found in the log of z-wave binding ?

Looking deeper in the z-wave log, only NODE 30, has “endpoint 1” in the line. All other z-wave devices have “endpoint 0” in that line.

4

Is the device in any Association groups of any other devices? I have some motion detectors that have a light in the Assoc group (no rule required). Another option is the item linked to the channel used in any rule?

The endpoint 1 just is because the light in question is wired to SW1 of the device. There are two switches available on the FGS223.

5

@apella12, I already checked that. Both are not the case. On top of that, in the meantime, I am assured that the switching on of the item is really random.

I have to be honest; my post was not complete. There are two Z-Wave controllers in the house, not connected to each other in any way. From what I read, they should not interfere with each other. Is this correct ?

I cannot say that this problem started exactly when the second controller was introduced, but I have never seen this before that moment.

Maybe @chris or one of the other Z-Wave guru’s can enlighten us ?

Nevertheless, a Shelly (Wi-Fi) device is ordered to replace the FGS223. If the issue disappears, some causes are definitely ruled out…

6

Yes, they will be independent (I’m assuming they didn’t join the same network).

Not really - if the device is changing state, then either something is sending it a command, or it’s broken. As @apella12 said, the most likely is that it’s controlled via an association from another device, but if you’ve checked that, then I’m not sure.

This isn’t a command being sent to the device - it’s simply the device reporting that it changed state. So this is “after the event” - it doesn’t show WHY it changed state, although if there’s nothing else in the log just prior to this, we can assume the command didn’t come from OH (and as above, the most likely is via an association).

It’s not really (easily) possible. You would need to get a sniffer to listen to what’s happening on the network.

How many devices do you have in the network? Can you correlate the changes with some other event around the house?

7

Less then 20 on the first network, 2 on the second (plus controller).

No, it already happend more then once that the switch goes on, even when nobody (even the four legged pestcontrol device) is at home. In the logs, always the same : the z-wave log reports the change of state, but no other logs report something at the same time. There are only zwave sensors (temp, humidity, brightness,…) and TRV’s in the zwave network and ONE switch (this one - but will be replaced this weekend with a Shelly).

I’ve never configured associations. At this point I can only conlude that the FGS223 is broken (as you mentioned), or there is a device that is using the same frequencies as z-wave in the neighbourhoud.

8

That is super unlikely both because of the zwave distance limits and each network has a unique 4 byte HomeID.

If the Shelly doesn’t solve it, do you have two OH instances (connected via remote OH?) or are both your Zwave networks on one OH? How close are Zsticks to each other?

9

I agree (but I have seen stanger things in my long lasting IT-Infrastructure carreer, that almost could fit in Stranger Things - the series ;-).

I have two OH instatances, One (4.2.1) reads from the other (2.5.12) via the remote OH binding, each with their own z-stick. Like I said, none of the logs show anything else then the switch that changes status to ON.

About 7 meters, walls in between.

Next week when the shelly has replaced the FGS, more news !

1 Like
10

While I also largely agree, there is a problem with zwave in that it uses a very simple error detection system that can easily let corrupt frames through. So, this can mean that frames from different devices, or different networks (less likely) can be received corrupted if a couple of bits flip.

So, I do agree that it’s unlikely for this to occur across different networks since as Bob points out, the home ID is 4 bytes, and bit flips to match this is pretty unlikely. But corrupt frames is definitely a real issue with ZWave. Some newer devices do use a second level of error detection with an extra encapsulation class, but I’m not sure it’s common.

1 Like
11

Update.

To recapitulate :

  • 2 controllers (not connected to each other).
  • First controller, with variuous devices including the haunted switch.
  • Second controller, with only two devices connected.

I replaced the haunted z-wave switch with a Wi-fi Shelly. As expected, the probem was solved.

But, I kept the z-wave switch connected, just to see what/when/why… The swithcs kept switching on (and off) from time to time without any clear reason. Until I did a reset to factory defaults of the secondary controller.