Controller shift - How do you do it ?
-
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
-
This is weird... It should be above 6. Not sure what this 4.38 corresponds to. It looks like you need to keep going... Or try it to see if it migrates. You never know.
-
Another Interesting observation - that recent bootloader upgrade has resulted in the z-wave dongle backup being reported as 4.38 rather that 4.5 when on the previous version ? -, see below extract of yesterdays and todays backups...
16383 Sep 20 19:48 dongle.4.38.dump.0 16383 Sep 19 20:37 dongle.4.5.dump.0Next steps
touch /etc/cmh/dongle.restore.go -- on target VeraSecure scp dongle.4.38.dump.0 root@192.168.1.145:/etc/cmh/dongle.4.38.dump.0 -- on source VeraPlus -
Perhaps not a surprise but the restore failed.
02 09/20/21 20:59:27.962 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 <0x77ab6320> 02 09/20/21 20:59:27.963 ZWave::Start restoring dongle firmware <0x77ab6320> 03 09/20/21 20:59:27.963 JobHandler_LuaUPnP::m_bReloadCriticalOnly_set now 1 <0x77ab6320> 01 09/20/21 20:59:27.977 ZWJob_BackupDongle::FixupBufferVersion don't know version 4.38 <0x77ab6320> 01 09/20/21 20:59:27.977 ZWJob_BackupDongle::ZWJob_BackupDongle restore file invalid <0x77ab6320> 03 09/20/21 20:59:27.983 JobHandler_LuaUPnP::Reload: Dongle Restore Critical 1 m_bCriticalOnly 1 dirty data 1 running 0 <0x77ab6320> 04 09/20/21 20:59:28.319 <Job ID="1" Name="restore" Device="1" Created="2021-09-20 20:59:27" Started="2021-09-20 20:59:28" Completed="2021-09-20 20:59:28" Duration="0.354838000" Runtime="0.0" Status="Failed" LastNote="ERROR: Restore failed. Try again or contact tech support."/> <0x77ab6320>@rafale77 - What do you recommend next on the UZB1 upgrade
I’m guessing i need to get to v6.01 ?
-
yep.. that's what I would do.
-
@rafale77 said in Controller shift - How do you do it ?:
yep.. that's what I would do.
Any idea why the 5.7 (5.07) UZB1 firmware appears as 4.38 on Vera ?
Also what do you recommend we do next? Update the bootloader again or continue on as is just with firmware ?
What confuses me is that this link (https://z-wave.me/support/uzbrazberry-firmwares/) only goes to 5.36, no sight of 6.01?
-
Hold on,, I thought this was familiar
- we back to where we were last year with another UZB1 I hadSo unless you disagree I will follow your previous advice.
@rafale77 said in UZB/RaZberry Firmwares - Update:
I went to read the map myself and here are the steps I would take:
5.7 -> 5.7 40196 BL -> 5.27 ->5.36 ->5.39So yes Bootloader first in general but need to read the version.
-
You caught me there. I was probably smarter then than I am now.
My entire system has been working so well that I stopped tinkering or upgrading it save for only occasional additions or optimization of a scene here or there on openLuup. I lost a lot by not practicing.
-
Well, it looks like I've made it to 5.39, although I'm surprised by the current update options ?
Being in the UK, and only ever using it on the EU frequency, any idea why it's giving me the option to switch to EU ? Where does it think I am set to at the moment ?
-
Maybe I’ve gone to far - v 5.39 appears as v6.09
And now every z-wave backup I try fails..
Any ideas ?
-
You should be able to downgrade back... But yeah that's what I feared... Upgrading too far would make it impossible for the vera to restore...
-
Sadly there is no downgrade option available from v5.39 when I used the ‘all’ token, but I’m beginning to think that the Vera version numbering is related to the SDK
Using another UZB1 stick, and just moving from 5.26 & 5.27 both reported v4.61 on Vera (and both have the same SDK version - 6.71.01)
Observations so far…
UZB1 v5.06 [29304] SDK 6.??.?? = v4.01 on Vera
UZB1 v5.07 [29304] SDK 6.51.09 = v4.38 on VeraUZB1 v5.26 [40196] SDK 6.71.01 = v4.61 on Vera
UZB1 v5.27 [40196] SDK 6.71.01 = v4.61 on VeraUZB1 v5.32 [40196] SDK 6.81.00 = TBC on Vera
UZB1 v5.37 [40196] SDK 6.81.01 = TBC on VeraUZB1 v5.39 [40196] SDK 6.82.01 = v6.09 on Vera
-
The version roadmap - > https://z-wave.me/support/uzbrazberry-firmwares/ has the following ..
UZB1 v5.32 [40196] SDK 6.81.00 = TBC on Vera
UZB1 v5.37 [40196] SDK 6.81.01 = TBC on VeraHowever the actual UZB firmware update options I have available via the zway controller are different - i only have 5.33 and 5.36 - any ideas ?
-
5.33 =5.32 and 5.36=5.37 if I remember correctly. They were just version numbered for Razberry vs UZB.
-
Would you believe it !
The target was to align with the standard v6.01 on the VeraSecure but the UZB1 v5.33 has ended us up on v6.02 !!!!
UZB1 v5.33 [40196] SDK 6.81.00 = v6.02 on Vera
So it seems it’s not possible to get to v6.01 ??
-
Perhaps not unexpected, trying to back up UZB1 5.33 / Vera v6.02 failed..
-
Quick question, if i restore a z-wave backup onto a new controller - I will have two controllers both with the exact same z-wave devices and network registered
I’m curious what are the issues in running both controllers ?
50/67
