Controller shift - How do you do it ?
-
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.0
Next 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 ?
-
@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 had
So 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.
-
-
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 ?
-
Using the vera backup process you would have to go up or remain on the same version. If you backed up your vera which is on 6.01 into a stick in 6.02, you should be able to restore onto another vera with an SDK 6.02 and above. Have you tried that? Upgrading the vera?
To answer your question if you have both your controller with the same node ID, it will cause a mess to your network. In that case I would add the second controller so it takes a different node ID. (I ran vera and zway together this way for several months).
Here is the type of mess it will cause:
Controller1: turn the light one
Light: Ok the light is on
Controller2: Got it... euh What? who told you to?
Controller1: Are you on yet? Timeout, let me ask again. Retry!This will cause the network to be very busy as nodes do not who to report back to or think they already reported and got an ack...
-
Using the vera backup process you would have to go up or remain on the same version. If you backed up your vera which is on 6.01 into a stick in 6.02, you should be able to restore onto another vera with an SDK 6.02 and above. Have you tried that? Upgrading the vera?
To answer your question if you have both your controller with the same node ID, it will cause a mess to your network. In that case I would add the second controller so it takes a different node ID. (I ran vera and zway together this way for several months).
Here is the type of mess it will cause:
Controller1: turn the light one
Light: Ok the light is on
Controller2: Got it... euh What? who told you to?
Controller1: Are you on yet? Timeout, let me ask again. Retry!This will cause the network to be very busy as nodes do not who to report back to or think they already reported and got an ack...
Thanks @rafale77
@rafale77 said in Controller shift - How do you do it ?:
If you backed up your vera which is on 6.01 into a stick in 6.02, you should be able to restore onto another vera with an SDK 6.02 and above. Have you tried that? Upgrading the vera?
How can I upgrade the onboard zwave firmware on my VeraSecure, which is on v6.01?