I messed up my upgrade and now my controller is secondary

Discussions about Z-Way software and Z-Wave technology in general
Post Reply
the wife
Posts: 23
Joined: 27 Oct 2015 21:02

I messed up my upgrade and now my controller is secondary

Post by the wife »

I've had my system for a number of years now. It consists of an early model raspberry pi + zwave.me daughter board (first gen probably).
The last upgrade I did was in January of this year, to Bullseye and whatever the latest z-way firmware was at the time.

Everything was working well, until yesterday when a power cut corrupted the SD card. Unfortunately I had not taken a backup of the SD card, although I did have backups of /opt/z-way-server, /etc/zbw and /etc/init.d/zbw_connect

I started with a fresh SD card which I installed Bookworm on. I then made the mistake of installing a completely fresh z-way, before copying the above backups and then upgrading. I realised the mistake when I accessed find.zwave.me and was presented with a different user number after admin/

So, I copied the backups across and re-issued wget -qO - https://storage.z-wave.me/RaspbianInstall | sudo bash hoping it would fix things. It did not.

I'm back to the original user number, but my controller is now 'secondary in the network' and I am unable to include/exclude devices.

I've accepted that I've lost all my configured / included devices and would just like to put things back to a state where I can start again.

Has anyone had anything similar or does anyone have any advice as to how to do this please?
the wife
Posts: 23
Joined: 27 Oct 2015 21:02

Re: I messed up my upgrade and now my controller is secondary

Post by the wife »

Looking at the z-way-server.log I found this. Could this be signs of hardware failure?

[2023-12-12 23:30:53.819] [D] [zway] Job 0x07 (Get controller info and supported function classes): success
[2023-12-12 23:30:53.838] [zway] Adding job: Set Serial API timeouts
[2023-12-12 23:30:53.839] [zway] Adding job: Set RF power level
[2023-12-12 23:30:53.839] [zway] Adding job: WatchDog Start
[2023-12-12 23:30:53.840] [D] [zway] SETDATA controller.data.frequency = "unknown"
[2023-12-12 23:30:53.840] [E] [zway] Error returned from zway_fc_zme_freq_change(zway, 0xFF, NULL, NULL, NULL): Function class not supported by the hardware (-4)
[2023-12-12 23:30:53.840] [zway] Adding job: Get home id and controller node id
[2023-12-12 23:30:53.840] [zway] Removing job: Get controller info and supported function classes
[2023-12-12 23:30:53.841] [D] [zway] SENDING: ( 01 03 00 D2 2E )
[2023-12-12 23:30:53.841] [E] [zway] RECEIVED UNKNOWN PACKET TYPE: 0x04
[2023-12-12 23:30:53.843] [E] [zway] RECEIVED UNKNOWN PACKET TYPE: 0x00
[2023-12-12 23:30:53.844] [E] [zway] RECEIVED UNKNOWN PACKET TYPE: 0x26
[2023-12-12 23:30:53.844] [E] [zway] RECEIVED UNKNOWN PACKET TYPE: 0x1c
[2023-12-12 23:30:53.845] [E] [zway] RECEIVED UNKNOWN PACKET TYPE: 0x8f
[2023-12-12 23:30:53.845] [W] [zway] Received SOF, while awaiting ACK
[2023-12-12 23:30:53.846] [D] [zway] RECEIVED: ( 01 06 03 80 03 3F 06 43 )
[2023-12-12 23:30:53.847] [D] [zway] Wrong checksum
[2023-12-12 23:30:53.847] [D] [zway] SENT NAK
[2023-12-12 23:30:53.848] [E] [zway] RECEIVED UNKNOWN PACKET TYPE: 0x03
[2023-12-12 23:30:53.849] [W] [zway] Received SOF, while awaiting ACK
[2023-12-12 23:30:54.253] [zway] Job 0xd2 (WatchDog Start): No ACK received before timeout
[2023-12-12 23:30:54.254] [D] [zway] SENDING: ( 01 03 00 D2 2E )
[2023-12-12 23:30:54.463] [zway] Job 0xd2 (WatchDog Start): No ACK received before timeout
[2023-12-12 23:30:54.463] [D] [zway] SENDING: ( 01 03 00 D2 2E )
[2023-12-12 23:30:54.670] [zway] Job 0xd2 (WatchDog Start): No ACK received before timeout
[2023-12-12 23:30:54.672] [W] [zway] Job 0xd2 (WatchDog Start) dropped: too many resends
[2023-12-12 23:30:54.673] [D] [zway] Job 0xd2 (WatchDog Start): fail
[2023-12-12 23:30:54.673] [zway] Removing job: WatchDog Start
[2023-12-12 23:30:54.674] [D] [zway] SENDING: ( 01 05 00 06 0A 0A FC )
[2023-12-12 23:30:54.882] [zway] Job 0x06 (Set Serial API timeouts): No ACK received before timeout
[2023-12-12 23:30:54.883] [D] [zway] SENDING: ( 01 05 00 06 0A 0A FC )
[2023-12-12 23:30:55.091] [I] [zway] Job 0x06 (Set Serial API timeouts): No ACK received before timeout
[2023-12-12 23:30:55.092] [D] [zway] SENDING: ( 01 05 00 06 0A 0A FC )
[2023-12-12 23:30:55.299] [I] [zway] Job 0x06 (Set Serial API timeouts): No ACK received before timeout
[2023-12-12 23:30:55.299] [W] [zway] Job 0x06 (Set Serial API timeouts) dropped: too many resends
[2023-12-12 23:30:55.300] [D] [zway] Job 0x06 (Set Serial API timeouts): fail
[2023-12-12 23:30:55.300] [I] [zway] Removing job: Set Serial API timeouts
[2023-12-12 23:30:55.300] [D] [zway] SENDING: ( 01 04 00 17 00 EC )
[2023-12-12 23:30:55.505] [I] [zway] Job 0x17 (Set RF power level): No ACK received before timeout
[2023-12-12 23:30:55.506] [D] [zway] SENDING: ( 01 04 00 17 00 EC )
[2023-12-12 23:30:55.710] [I] [zway] Job 0x17 (Set RF power level): No ACK received before timeout
[2023-12-12 23:30:55.711] [D] [zway] SENDING: ( 01 04 00 17 00 EC )
[2023-12-12 23:30:55.916] [I] [zway] Job 0x17 (Set RF power level): No ACK received before timeout
[2023-12-12 23:30:55.916] [W] [zway] Job 0x17 (Set RF power level) dropped: too many resends
[2023-12-12 23:30:55.916] [D] [zway] Job 0x17 (Set RF power level): fail
[2023-12-12 23:30:55.916] [I] [zway] Removing job: Set RF power level
[2023-12-12 23:30:55.917] [D] [zway] SENDING: ( 01 03 00 20 DC )
[2023-12-12 23:30:56.122] [I] [zway] Job 0x20 (Get home id and controller node id): No ACK received before timeout
[2023-12-12 23:30:56.122] [D] [zway] SENDING: ( 01 03 00 20 DC )
[2023-12-12 23:30:56.327] [I] [zway] Job 0x20 (Get home id and controller node id): No ACK received before timeout
[2023-12-12 23:30:56.328] [D] [zway] SENDING: ( 01 03 00 20 DC )
[2023-12-12 23:30:56.532] [I] [zway] Job 0x20 (Get home id and controller node id): No ACK received before timeout
[2023-12-12 23:30:56.533] [W] [zway] Job 0x20 (Get home id and controller node id) dropped: too many resends
[2023-12-12 23:30:56.533] [D] [zway] Job 0x20 (Get home id and controller node id): fail
[2023-12-12 23:30:56.533] [C] [zway] Get HomeId failed.
[2023-12-12 23:30:56.533] [I] [zway] Removing job: Get home id and controller node id
[2023-12-12 23:30:56.544] [D] [zway] Worker thread exit point
[2023-12-12 23:30:56.551] [D] [zway] Worker thread successfully finished
the wife
Posts: 23
Joined: 27 Oct 2015 21:02

Re: I messed up my upgrade and now my controller is secondary

Post by the wife »

Panic over for now!

I plugged the raspberry pi into a different power supply and all the errors I had been seeing in the log file disappeared. The smarthome web interface showed that the controller was back up as primary. And the best bit was that all my devices were still included - phew. So, I just had to copy back my previous z-way-server directories etc and do another upgrade.

All working ok. Just need to source a new power supply, add some UPS protection and get some backup SD cards. Lessons learned.
Post Reply