Controller shift - How do you do it ?
-
It's not a very hard thing to do but I unfortunately gave away most of my veras and only have a couple of bricked ones left so I can't test this.
There was another way which was to manipulate the zwave serial port inside your backup user-data.json which is what I had to do but it takes decompressing your backup and the user-data.json.lzo and the compress it back and then restore that backup.
The silliness of the backup restore process is that it is very rigid and doesn't allow you to restore to a different serial port than what your original backup file. What I gave you should work though... manually grab the last dongle file from one unit, move it to the other one and with your UI already showing the new target serial port, start a dongle restore.As I previously said, I also highly recommend you stay with the usb stick. It likely has greater range and upgradeability.
-
parkercreplied to rafale77 on Mar 3, 2021, 7:17 PM last edited by parkerc Mar 3, 2021, 2:18 PM
@rafale77 said in Controller shift - How do you do it ?:
I also highly recommend you stay with the usb stick. It likely has greater range and upgradeability.
I’d actually seriously consider that, but the upgrading route for the z-way UZB1 dongle, seems so unnecessarily complicated .
One of the reasons for getting the new Vera was because a Fibaro RGBW Module was appearing as many multiple nodes, and Vera support had a look and seemed to suggest it was due to the z-wave version I was running.
parkerc said in Controller shift - How do you do it ?:
My UZB1 usb stick is on 4.05 L:1 - Role: Suc SIS: YES PRI: YES
The new Vera is on 6.01 L:1 - Role: Master SIS: NO PRI: YES -
upgrading firmware on a UZB is actually quite easy...
what is the brand of your stick?
Updating firmware on Silicon Labs Z-wave UZB USB sticks
There may be occasions when it becomes necessary to update the firmware of Silicon Labs Z-wave UZB controller USB sticks. Firmware updates may be needed when new SDKs are released or a change in UZB functionality is required. UZB firmware can be updated using Silicon Labs Windows based Z-Wave...
-
@rafale77 said in Controller shift - How do you do it ?:
what is the brand of your stick?
Z-wave.me - ZMEEUZB
-
Ahhhhh then this is what you need:
https://z-wave.me/zmeserialupdater-manual/
and it is indeed a little more complicated due to the need of following this crazy map:
-
Yep, that’s it
and I think you even helped me a while back, as that ‘crazy map’ was doing me head in.Trying to follow it drove me crazy !
-
I can help you read through it and break down the commands to upgrade if you want me to. What is your current firmware version?
-
parkercreplied to rafale77 on Sep 19, 2021, 2:39 PM last edited by parkerc Sep 19, 2021, 10:40 AM
@rafale77 said in Controller shift - How do you do it ?:
What you need to do now that you changed the zwave serial port back to the vera onboard chip, is to manually grab the latest dongle backup file from the old vera (it's in /etc/cmh-ludl) and move it to the new vera in the same location. Use SFTP to do this.
Then SSH into the new vera and run
touch /etc/cmh-ludl/dongle.restorethen reload luup. It should normally restore your previous zwave network configuration into the new vera zwave chip
Hi @rafale77
Picking this up again as i have managed to find a bit of time - and looking on my Vera I can’t see that a
dongle.restore.shfile, plus the dongle files seem to be in/etc/cmhrather than/etc/cmh-ludlsee below..root@MiOS_55100454:/# find -name dongle*.* ./etc/cmh/dongle.4.5.dump.0 ./etc/cmh/dongle.4.5.dump.1 ./etc/cmh/dongle.4.5.dump.2 ./etc/cmh/dongle.4.5.dump.3 ./etc/cmh/dongle.4.5.dump.4 ./etc/cmh/dongle.4.5.dump.5 ./ezmi/cmh/dongle.4.5.dump.0 ./ezmi/cmh/dongle.4.5.dump.1 ./ezmi/cmh/dongle.4.5.dump.2 ./ezmi/cmh/dongle.4.5.dump.3 ./ezmi/cmh/dongle.4.5.dump.4 ./ezmi/cmh/dongle.4.5.dump.5 root@MiOS_55100454:/#Any ideas where the dongle.restore file might be or if it’s called something different ?
-
Have looked here too, which has helped a bit.. https://smarthome.community/topic/199/problem-migration-z-wave-nw-from-vera-to-uzb1-dongle?_=1632067117298
The issue seems to be the
dongle.restorefile requirementsIf it helps, i found this within the ./mios/www/cgi-bin/cmh/restore.sh file
if [ "$FORM_dongle" == "1" ]; then # LuaUPnP will restore the Z-Wave backup file if it finds the 'dongle.restore.go' file. # To prevent LuaUPnP from restoring a dongle backup until the next boot, # we'll save the file as 'dongle.restore', and the 'Start_cmh.sh' script will rename it to 'dongle.restore.go'. log "Create $MIOS_CONF_PATH/dongle.restore" touch "$MIOS_CONF_PATH/dongle.restore" 2>>$log_file fiAnd then looking in
./usr/bin/Start_cmh.shthe reference there is..# to prevent LuaUPnP from restoring a dongle backup until the next boot, # the web ui saves .restore and LU looks for .go mv /etc/cmh/dongle.restore /etc/cmh/dongle.restore.go || /bin/trueSadly not much further forward…
-
I don't want to be stupid, but have you actually made a backup? Unless it's automatic and storing locally.....
C
-
Yep, I have made a local back up. (Inc z-wave network) and have it stored locally
Both Veras are on the network, I first went into the veraplus with the usb zwave dongle and did the full backup, saved it locally and then logged into the VeraSecure and did the restore.
Everything but the zwave devices was restored and based on what @rafale77 had said before my issue is that it’s trying to restore back to an /dev/ttyACM0 dongle, rather than the onboard one /dev/ttyS0
I somehow need to get the zwave records onto the right tty..
-
So from memory, if you just create the dongle.restore.go file in /etc/cmh and reboot.....
But that is from memory
touch /etc/cmh/dongle.restore.goOh and obviously make sure your backup file is uploaded!
C
The Ex-Vera abuser know as CatmanV2.....
-
parkercreplied to CatmanV2 on Sep 19, 2021, 6:17 PM last edited by parkerc Sep 19, 2021, 2:19 PM
@catmanv2 said in Controller shift - How do you do it ?:
So from memory, if you just create the dongle.restore.go file in /etc/cmh and reboot.....
Hi @CatmanV2
That’s the bit I’m not sure about , so do I just create a blank file , with nothing in it and call it a
dongle.restore.go?Also, just to confirm do I copy over the dongle back up file
dongle.4.5.dump.0into /etc/cmh tooOnce both are in there (making sure the a-wave settings are set to the correct onboard zwave chip etc.) I can just do a reboot or luup.reload ?
-
I believe that's exactly it. Although if you create dongle.restore.go you'll need to reboot, not just luup.reload.
Clearly you might want to keep dongle.4.5.dump.0 as a copy somewhere, but I guess it depends on the current state of the Vera you are restoring to
C
-
Ok, i gave that a go, but sadly no luck..
FYI - The Veraplus (with external a-wave dongle), dongle dump files are already on the VeraSecure in the /etc/cmh folder - I assume they must have come over during the restore this morning.
On the VeraSecure I ssh’d on to it and run that file creation command -
touch /etc/cmh/dongle.restore.goSo, all file are in
/etc/cmh/now..-rw-r--r-- 1 root root 16383 Sep 19 10:16 /etc/cmh/dongle.4.5.dump.0 -rw-r--r-- 1 root root 16383 Sep 2 03:00 /etc/cmh/dongle.4.5.dump.1 -rw-r--r-- 1 root root 16383 May 29 03:00 /etc/cmh/dongle.4.5.dump.2 -rw-r--r-- 1 root root 16383 Mar 15 2021 /etc/cmh/dongle.4.5.dump.3 -rw-r--r-- 1 root root 16383 Mar 11 2021 /etc/cmh/dongle.4.5.dump.4 -rw-r--r-- 1 root root 16383 Feb 27 2021 /etc/cmh/dongle.4.5.dump.5 -rw-r--r-- 1 root root 0 Sep 19 19:48 /etc/cmh/dongle.restore.goI did the full reboot, a few luup.reloads too, but still the same now zwave devices are shown or being picked up.
Any ideas ?
-
Ok, found something in the Luaupnp logs, which suggests an invalid restore file ?? - interesting..
02 09/19/21 19:54:21.868 ZWave::Start reset 0 use45:1 minor:1 model:37 port:/dev/ttyS0 nodes:1 using_prefer: 1 prefer 0.0 ports:/dev/ttyS0 - /dev/ttyS0 <0x77212320> 02 09/19/21 19:54:21.868 ZWave::Start restoring dongle firmware <0x77212320> 03 09/19/21 19:54:21.869 JobHandler_LuaUPnP::m_bReloadCriticalOnly_set now 1 <0x77212320> 01 09/19/21 19:54:21.882 ZWJob_BackupDongle::FixupBufferVersion not a valid 4.5 backup: 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff (<0x1b>[34;1m################<0x1b>[0m) <0x77212320> 01 09/19/21 19:54:21.883 ZWJob_BackupDongle::ZWJob_BackupDongle restore file invalid <0x77212320> 03 09/19/21 19:54:21.889 JobHandler_LuaUPnP::Reload: Dongle Restore Critical 1 m_bCriticalOnly 1 dirty data 1 running 0 <0x77212320> 04 09/19/21 19:54:22.257 <Job ID="1" Name="restore" Device="1" Created="2021-09-19 19:54:21" Started="2021-09-19 19:54:22" Completed="2021-09-19 19:54:22" Duration="0.386898000" Runtime="0.0" Status="Failed" LastNote="ERROR: Restore failed. Try again or contact tech support."/> <0x77212320> 02 09/19/21 19:54:22.258 JobHandler::PurgeCompletedJobs purge job#1 :restore dev:1 (0xbb88a0) P:5 S:2 Id: 1 restore status 2 <0x7603c520> 06 09/19/21 19:54:22.259 Device_Variable::m_szValue_set device: 2 service: urn:micasaverde-com:serviceId:ZigbeeNetwork1 variable: ComPort was: /dev/ttyXRUSB1 now: /dev/ttyXRUSB1 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x77212320> -
OK that made me delete my answer but at least we know how to fire the restore!
Where did your dump file come from, and how did you get it there?
C
-
It must have got there via the original restore process.
Ok, I’ve now copied over an earlier dongle dump direct from the VeraPlus, and made that the zero/0 one.
scp dongle.4.5.dump.4 root@192.168.1.145:/etc/cmh/dongle.4.5.dump.0Let’s try again
-
Hummmmm, same error..
Does it matter that this is a 4.5 dump file, and the Vera secure is on zwave version 6.1 ?
02 09/19/21 20:42:35.508 ZWave::Start reset 0 use45:1 minor:1 model:37 port:/dev/ttyS0 nodes:1 using_prefer: 1 prefer 0.0 ports:/dev/ttyS0 - /dev/ttyS0 <0x77e96320> 02 09/19/21 20:42:35.521 ZWave::Start restoring dongle firmware <0x77e96320> 03 09/19/21 20:42:35.522 JobHandler_LuaUPnP::m_bReloadCriticalOnly_set now 1 <0x77e96320> 01 09/19/21 20:42:35.549 ZWJob_BackupDongle::FixupBufferVersion not a valid 4.5 backup: 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff (<0x1b>[34;1m################<0x1b>[0m) <0x77e96320> 01 09/19/21 20:42:35.550 ZWJob_BackupDongle::ZWJob_BackupDongle restore file invalid <0x77e96320> 03 09/19/21 20:42:35.551 JobHandler_LuaUPnP::Reload: Dongle Restore Critical 1 m_bCriticalOnly 1 dirty data 1 running 0 <0x77e96320> 04 09/19/21 20:42:35.735 <Job ID="1" Name="restore" Device="1" Created="2021-09-19 20:42:35" Started="2021-09-19 20:42:35" Completed="2021-09-19 20:42:35" Duration="0.212538000" Runtime="0.0" Status="Failed" LastNote="ERROR: Restore failed. Try again or contact tech support."/> <0x77e96320> -
So you're trying to shift from a Vera Plus to a Vera Secure running different zwave versions?
I honestly have no idea if that's going to work or not. Unless you have 100s of devices I'd probably start from scratch at this point, or wait for one of the experts!
C
The Ex-Vera abuser know as CatmanV2.....
