Certain z-wave device disappears from z-way after a few days

[gongtao0607]

My setup:

• RaZberry (z-way) as primary controller (SUC/SIS)
• OpenZWave (using UZB) as secondary controller (/inclusion controller)
• 60+ devices (mains/sleeping/flirs)

The issue: While the network is mostly running fine, certain device keep disappearing from z-way after a few days included in the network (at least from Web UI), namely Monoprice Motion Sensor. I have 4 and all of them behave the same. (They even disappear in the sequence of adding them).

More details:

• These devices are sleeping wakeup to z-way. (The setup is correct as I can see last wakeup is updated in the device->status, and queued commands are accepted by the devices)
• These devices do not have association with z-way (instead, they are associated to OpenZWave and zwave switches)
• After they disappear from z-way, they still behave normally to other associations (OpenZWave and other switches still gets motion reports)
• However, then I lose ability to change the configuration of them (as they wakeup to only z-way).

Please let me know what specific details I need to provide and I'll be glad to do so (it may take me some days to to test).

[PoltoS]

Please show the Z-Way log with the period where one of them disappear

[PoltoS]

Can we close it?

[gongtao0607]

Hi Poltorak,

I just caught it happen again minutes ago. How can I send you the log (~100MB just for today).

[gongtao0607]

I cut it down to 43MB for 3 hours window

[gongtao0607]

The second device in series just disappeared too. Here's a section of the log (Node 132):

[2021-01-17 17:06:03.579] [I] [zway] Adding job: Get background noise level
[2021-01-17 17:06:03.579] [D] [zway] SENDING: ( 01 03 00 3B C7 )
[2021-01-17 17:06:03.582] [D] [zway] RECEIVED ACK
[2021-01-17 17:06:03.582] [D] [zway] RECEIVED: ( 01 05 01 3B AD A2 CF )
[2021-01-17 17:06:03.582] [D] [zway] SENT ACK
[2021-01-17 17:06:03.582] [D] [zway] SETDATA controller.data.statistics.backgroundRSSI.channel1 = 173 (0x000000ad)
[2021-01-17 17:06:03.582] [D] [zway] SETDATA controller.data.statistics.backgroundRSSI.channel2 = 162 (0x000000a2)
[2021-01-17 17:06:03.582] [D] [zway] SETDATA controller.data.statistics.backgroundRSSI.channel3 = 127 (0x0000007f)
[2021-01-17 17:06:03.583] [I] [zway] Job 0x3b (Get background noise level): RSSI Ch#1: -94 dBm, Ch#2: -94 dBm, Ch#3: invalid
[2021-01-17 17:06:03.583] [D] [zway] Job 0x3b (Get background noise level): success
[2021-01-17 17:06:03.583] [I] [zway] Removing job: Get background noise level
[2021-01-17 17:06:23.951] [D] [zway] Job 0x3b: deleted from queue
[2021-01-17 17:06:28.316] [D] [zway] RECEIVED: ( 01 06 00 49 20 84 00 14 )
[2021-01-17 17:06:28.316] [D] [zway] SENT ACK
[2021-01-17 17:06:28.316] [I] [zway] Node 132 was removed
[2021-01-17 17:06:28.316] [I] [zway] Job 0x13 (Wakeup Sleep): Cancelling job: Wakeup Sleep
[2021-01-17 17:06:28.316] [W] [zway] Can not find device 132 the job is assigned to
[2021-01-17 17:06:28.316] [I] [zway] Removing job: Wakeup Sleep
[2021-01-17 17:06:28.318] [I] [zway] Adding job: Get routing table line
[2021-01-17 17:06:28.318] [I] [zway] Adding job: Get routing table line
[2021-01-17 17:06:28.318] [I] [zway] Adding job: Get routing table line

(Please let me know if I can send you the full log somewhere, this one is only 445KB)

Is it possible that the secondary controller is excluding it? (This doesn't make sense as no learn button from any device was ever touched during the period.)

[gongtao0607]

What's behind this? (Sorry I don't know how to decode):

[2021-01-17 17:06:28.316] [D] [zway] RECEIVED: ( 01 06 00 49 20 84 00 14 )

[gongtao0607]

The 3nd one have just disappeared too (node 134).

[2021-01-17 21:21:40.338] [I] [zway] Job 0x3b (Get background noise level): RSSI Ch#1: -89 dBm, Ch#2: -89 dBm, Ch#3: invalid
[2021-01-17 21:21:40.338] [D] [zway] Job 0x3b (Get background noise level): success
[2021-01-17 21:21:40.338] [I] [zway] Removing job: Get background noise level
[2021-01-17 21:21:47.322] [D] [zway] RECEIVED: ( 01 06 00 49 20 86 00 16 )
[2021-01-17 21:21:47.322] [D] [zway] SENT ACK
[2021-01-17 21:21:47.322] [I] [zway] Node 134 was removed
[2021-01-17 21:21:47.323] [I] [zway] Job 0x13 (Wakeup Sleep): Cancelling job: Wakeup Sleep
[2021-01-17 21:21:47.323] [W] [zway] Can not find device 134 the job is assigned to
[2021-01-17 21:21:47.323] [I] [zway] Removing job: Wakeup Sleep
......

[PoltoS]

[2021-01-17 21:21:47.322] [D] [zway] RECEIVED: ( 01 06 00 49 20 86 00 16 )

This informs Z-Way some inclusion controller has deleted node 134.

Please check it with sniffer - who is doing that? Looks your secondary controller is sending it. This is not a Z-Way issue, we just follow the protocol here.

[gongtao0607]

Could you provide more info from these bytes? (i.e., is second byte 06 the sender? 49 the command class? I couldn't find the mapping) Thanks!

[PoltoS]

01 SOF 06 size of the packet 00 REQ 49 ApplicationNodeUpdate 20 Node removed 86 NodeId 00 don't remember (or unused) 16 CRC

If you have a zniffer, you can catch it

[gongtao0607]

Really thanks for the info. Is there a way to find the sender in log (I guess no) or in z-way zniffer? (I don't know what triggers it. I literally did nothing in the period it happens. It's kind of hard to run zniffer for weeks to capture a single packet :( but I can try if that's the only way to find out)

[PoltoS]

The Serial API does not provide that info. Only Zniffer can reveal the truth.

[gongtao0607]

Thanks, I was a bit lucky that the last one just disappeared too and I happened to have zniffer running and my Windows didn't go to sleep :D. Just like our hypothesis, it is the secondary controller sent out a message

[Home id] 02 41 04 13 01 01 0D 85 00 00 00 00 00 00 23

So it's node 2 (which is the secondary controller) send message to node 1 (zway) with command class 0x0D and param 0x85 (133, which is the device that is removed). Although I couldn't find any information about CC 0x0D (I guess it's sigma proprietary), pretty sure this is telling node 1 to remove it.

Really appreciate your time helping out with this issue irrelated to z-way!