Controller shift - How do you do it ?
-
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
-
@catmanv2 said in Controller shift - How do you do it ?:
So you're trying to shift from a Vera Plus to a Vera Secure running different zwave versions?
Yep, although I’m assuming it wouldn’t much different to someone upgrading from a vera3 or Vera lite to the newer plus or secures as they were different zwave versions..
Why are things never as straightforward as you want them to be
-
Sorry, just came back and am trying to catch up with all the posts... It looks like you manage to trigger the restore. The vera firmware is a bit idiotic in the sense that it will choose the target of the network restore as the one you have set in the UI when the vera UI starts (LuaUPnP). I don't think it works when downgrading from one stack version to a lower stack version but it does when going up. You should actually see a converted database file show up in the etc folder when it has to do a conversion. I have not tried upgrading from major versions however as my upgrades were always within stack version 6.x.
-
-
Hahaha... yeah it does take some time to figure out. Try to get it to the same level as the vera so that it doesn't need to do a conversion.
-
Sounds like a plan,
By any chance - do you know if there is an easier (idiots) step by step guide that can take me from v4 to v6 - rather than that spaghetti mess of a web of connections..
-
Yeah the only way I know of is for me to figure out the spaghetti for you…
-
Thanks @rafale77
I’m always conscious something’s going to fail when I do any firmware upgrade, and while I have two UZB1 sticks (one v4 the other v5) I was wondering if I could upgrade the v5 first and then copy the data over/clone from the v4 one ?
To do the latter part, I came across this zwave cloner tool in another forum, have you seen it before ?
-
Here's where I am on the v5 UZB1 stick
-
Looks like you should be going to 5.26 and then 5.27. These are already 6.xx stack versions though.
-
Thanks - I upgraded that UZB1 stick as requested and it now reports it's on the latest version (does that sound right to you ?)
-
Always upgrade bootloader before the firmware. I at times ended in a dead end and ended up having to use the linux tool to upgrades. The Z-way-server firmware upgrader doesn't always offer the "beta" versions which can be a necessary step to another official version. You can see more by inserting an "all" token but I prefer the lower level linux tool...
Note that you may need to go up all the way to do the backup/copy. You just need to get close enough in the SDK version.
-
Thanks,
Ok I did the bootloader update and then the 5.06 to 5.07 upgrade.
I just had the new bootloader originally, but using the 'all' token it added a few more,
I assume I update the bootloader again ? (even though it is dated after the other upgrades).
-
Before you keep on upgrading, I would recommend to try the vera migration. 29304 is the bootloader I am currently on. So I am not sure what the new bootloader does. It doesn't look like I went down this upgrade path...
-
OK, putting the UZB1 back into the VeraPlus, it’s moved from 4.01 to 4.38 - do we think that’s enough, when the VeraSecure is reporting 6.01
Zwave Cloner
34/67
