forum

I have a primary z-way server using a razberry pi 5th generation card, running the latest version of z-way.

Last night I ran reorganization and when it had completed, I realized it had deleted from the network several devices which were functioning. One of the switches is associated to a switch that was not deleted and it can still toggle the other switch.

This is not the first time I have seen this behavior. The devices that end up being deleted this time were all mains powered. Some where older GE switches, and others were wave-plus. Not all of devices were switches. All three Stelpro thermostats were removed.

If I go into expert->network->control, and select start_inclusion? If I press a switch, it will be re-added to the network, with whatever Node ID is was previously had. Z-way though will have lost the name of device and any automations that used the devices are broken.

First: Reorganization should not silently delete devices. This breaks automations silently and does not provide an opportunity to replace a failed node. If z-way believes that a node needs to be deleted? It should add the node to the list that "Removed Failed Node" uses.

If I look at what the Reorganization output is under expert is for a device that was deleted?
00:10:11 Starting neighbours update 221
00:41:07 Neighbours update done 221

The information from the log file is confusing as well:

[2022-01-09 01:25:49.563] [D] [zway] SETDATA devices.211.data.neighbours = byte[22]
[2022-01-09 01:25:49.563] [D] [zway] ( 04 06 07 27 2A 32 49 4A 4C 4F 50 51 7F 82 84 87 A6 AE AF DD E4 E5 )
[2022-01-09 01:25:49.563] [zway] Job 0x80 (Get routing table line to node 211): List of neighbours for node 211: [ 04 06 07 27 2a 32 49 4a 4c 4f 50 51 7f 82 84 87 a6 ae af dd e4 e5 ]
[2022-01-09 01:25:49.564] [D] [zway] Job 0x80 (Get routing table line to node 211): success
[2022-01-09 01:25:49.564] [zway] Removing job: Get routing table line to node 211
[2022-01-09 01:25:49.565] [D] [zway] SENDING: ( 01 06 00 80 DD 00 00 A4 )
[2022-01-09 01:25:49.566] [D] [zway] RECEIVED ACK
[2022-01-09 01:25:49.571] [D] [zway] RECEIVED: ( 01 20 01 80 6C C1 89 04 C3 7A 3A FA 24 41 C9 83 39 01 21 44 5B 02 C1 00 00 00 00 00 00 C0 04 00 18 31 )
[2022-01-09 01:25:49.571] [D] [zway] SENT ACK
[2022-01-09 01:25:49.571] [D] [zway] SETDATA devices.221.data.neighbours = byte[64]
[2022-01-09 01:25:49.571] [D] [zway] ( 03 04 06 07 09 0F 10 11 14 18 1B 21 22 27 28 2A 2C 2D 2E 2F 32 34 35 36 3A 3C 3D 3E 3F 40 43 46 49 4F 51 54 57 58 59 5A 60 61 64 65 66 69 71 76 7B 7F 81 82 84 85 87 8A 91 97 98 CF D0 D3 E4 E5 )
[2022-01-09 01:25:49.571] [zway] Job 0x80 (Get routing table line to node 221): List of neighbours for node 221: [ 03 04 06 07 09 0f 10 11 14 18 1b 21 22 27 28 2a 2c 2d 2e 2f 32 34 35 36 3a 3c 3d 3e 3f 40 43 46 49 4f 51 54 57 58 59 5a 60 61 64 65 66 69 71 76 7b 7f 81 82 84 85 87 8a 91 97 98 cf d0 d3 e4 e5 ]
[2022-01-09 01:25:49.571] [D] [zway] Job 0x80 (Get routing table line to node 221): success
[2022-01-09 01:25:49.571] [zway] Removing job: Get routing table line to node 221
[2022-01-09 01:25:49.573] [D] [zway] SENDING: ( 01 06 00 80 E1 00 00 98 )
[2022-01-09 01:25:49.574] [D] [zway] RECEIVED ACK
[2022-01-09 01:25:49.579] [D] [zway] RECEIVED: ( 01 20 01 80 7C 81 09 00 82 50 4A F8 34 42 C9 83 39 01 21 44 5B 02 C1 00 00 00 00 00 00 00 00 00 18 2B )
[2022-01-09 01:25:49.579] [D] [zway] SENT ACK


[2022-01-09 01:25:51.917] [zway] Node 221 was removed


[2022-01-09 01:25:51.926] [core] Deleting device switchBinary ZWayVDev_zway_221-0-37

Please show the few lines before
[2022-01-09 01:25:51.917] [zway] Node 221 was removed

It is known that in some cases 5th gen SiLabs (Sigma Designs) SDK freaked out and reported nodes deletion to the upper (Z-Way) level. This should be solved by firmware upgrade via Z-Way. This is not normal of course, it is a bug.

This doesn't solve the problem, but it's a quick and easy way to help recover from "surprises".

Add a daily cron job that takes creates a tar file of Z-Way's config data:
59 23 * * * /bin/tar cf /opt/z-way-server_`/bin/date +%a`.tar /opt/z-way-server/config/zddx /opt/z-way-server/automation/storage

The cron job should provide a 7-day rolling backup. If the backups are written to a removable USB drive, then recovering from an SD card failure can be relatively straightforward.

PoltoS wrote: ↑

10 Jan 2022 02:26

Please show the few lines before
[2022-01-09 01:25:51.917] [zway] Node 221 was removed

It is known that in some cases 5th gen SiLabs (Sigma Designs) SDK freaked out and reported nodes deletion to the upper (Z-Way) level. This should be solved by firmware upgrade via Z-Way. This is not normal of course, it is a bug.

Are you saying the RaZberry-500 should be upgraded, or are you saying that the devices which Z-way deleted should have their firmware upgraded?

The Razberry is running 5.39 ( SDK 6.82.01 ) and Z-way v3.2.2.

I can't look at the logs because they have already rolled over. I have seen this happen before, so I am sure it will happen again.

If it will, please provide logs