Replace razberry 1 shield with 7 pro: no devices

[janw]

My main controller is a Razberry 1 shield on a Pi model 2b. As some newer devices communicate poorly (many re-sends), I ordered a Razberry 7pro shield. I replaced the shield. The Expert UI sees the controller. The log file repeats the sequence below at low frequency. But, it sees none of my devices. I tried backup and restore. There are no complains on the procedure, but nothing changes. I could switch back to the old board. It works again as crappy as it did ...

My questions are:

- Is it possible to just replace the board?
- Is some procedure needed to make it see the old devices?
- If all fails, must I unpair all devices, replace the board and re-pair them? Seems a lot of work

Thanks --- Jan

Code: Select all

[2024-11-01 15:51:38.341] [I] [zway] Adding job: Get background noise level
[2024-11-01 15:51:38.347] [D] [zway] SENDING: ( 01 03 00 3B C7 )
[2024-11-01 15:51:38.349] [D] [zway] RECEIVED ACK
[2024-11-01 15:51:38.350] [D] [zway] RECEIVED: ( 01 07 01 3B A2 9F 9F 7F 1F )
[2024-11-01 15:51:38.350] [D] [zway] SENT ACK
[2024-11-01 15:51:38.350] [D] [zway] SETDATA controller.data.statistics.backgroundRSSI.channel1 = 162 (0x000000a2)
[2024-11-01 15:51:38.350] [D] [zway] SETDATA controller.data.statistics.backgroundRSSI.channel2 = 159 (0x0000009f)
[2024-11-01 15:51:38.350] [D] [zway] SETDATA controller.data.statistics.backgroundRSSI.channel3 = 159 (0x0000009f)
[2024-11-01 15:51:38.351] [I] [zway] Job 0x3b (Get background noise level): RSSI Ch#1: -94 dBm, Ch#2: -97 dBm, Ch#3: -97 
dBm
[2024-11-01 15:51:38.351] [D] [zway] Job 0x3b (Get background noise level): success

[lanbrown]

Caveat. I have never tried a restore from the board you're running to that of a Razberry 7.

1) You need to be running at least version 3.23. The latest is 4.1.4 and I would suggest upgrading to at least 3.23 if you're not already running it.
2) You need to perform a backup. You can do this from the Z-Way expert interface as it just does a backup of the Razberry board.
3) You need to make sure to install the latest firmware on the Razberry 7. You need to use the token of all to see all of the firmware available
4) Restore the backup

[janw]

Thanks. I am running 4.1.4. The hardware may be old, the software is nicely up-to-date I did all as you describe, except for updating the Razberry 7 firmware. I'll try that somewhere the coming days and report back.

I understand that in theory, the above should work. If it fails, I just though about setting up the Razberry 7 on another Pi, include it into the network and use the "Start Controller Change" to switch from the old to the new. Could that work?

[lanbrown]

I understand that in theory, the above should work. If it fails, I just though about setting up the Razberry 7 on another Pi, include it into the network and use the "Start Controller Change" to switch from the old to the new. Could that work?

I wouldn't. For starters some devices do not follow the spec and expect the controller to be node 1. This also means your new controller would not be node 1, but the next available node number. You are also expecting that every device follows the specs and will take the new controller as the controller.

There are firmware issues that Silicon Labs fixed in their SDK that Z-Wave.me incorporated into their firmware. The issues are from Silicon Labs and not Z-Wave.me. You need to upgrade the firmware as it will resolve many issues. This is why I put updating the firmware before doing a restore.

[janw]

Thanks. Updating the firmware is not so easy though Network/Controller info tells me it runs 7.28. https://service.z-wave.me/expertui/uzb- ... graph.html tells me Razberry07.19.02.00.gbl should get me to 7.36, after which I can update to 7.42. So, I downloaded Razberry07.19.02.00.gbl, go in the expert UI to Configuration, use Firmware update, select the .gbl file and press Update. This gets me

Z-Wave Expert UI - ERROR
Error during firmware update:
Either manufacturer or firmware id is not present

Search the internet for "Either manufacturer or firmware id is not present" gives no hits

Software version is v4.1.4

It seems the preferred way for updating the firmware is Z-Wave Expert UI. The alternative is ZMESerialUpdater. Any idea what is going on and how can I get around this?

[lanbrown]

You made that much harder than you need too...

Expert UI:

Screen Shot 2024-11-03 at 9.10.29 AM.png (47.62 KiB) Viewed 1922 times

Click firmware update

Screen Shot 2024-11-03 at 9.10.50 AM.png (97.8 KiB) Viewed 1922 times

use the token of all and click go

Screen Shot 2024-11-03 at 9.11.09 AM.png (157.41 KiB) Viewed 1922 times

Update the firmware and it will download what it needs to download.

[Eastpark]

I also upgraded recently, but took a different approach. Adding a new controller to the existing network and after testing I transferred the control to the newly added controller. Followed by removing the old controller.
It only required a second Rasberry Pi.

[seattleneil]

Adding a new controller to the existing network and after testing I transferred the control to the newly added controller. Followed by removing the old controller.

While this approach correctly configures the network ID of the new controller to be the same as the network ID of the old controller, this approach can cause problems since the new controller will have a Z-Wave node ID that is different from the old controller (which has node ID = 1). For example, many Z-Wave devices will only send unsolicited reports to the node with node ID = 1.

The approach described by @lanbrown is the best approach since the new controller will have node ID = 1 (after the backup from the old controller is restored onto the new controller). When you follow the backup/restore approach, from a Z-Wave protocol perspective, the old controller and the new controller are indistinguishable where all of your Z-Wave nodes will be completely unaware that you're using a new controller. If you still have your old controller, please consider doing the backup/restore approach as described by @lanbrown.

Note: As previously mentioned, since the 2 controllers are indistinguishable when you follow the backup/restore approach, make certain you do not have both controllers active at the same time as it will completely destabilize your Z-Wave network.