ZWave 3.20 & UI4->UI5 upgrade as prerequisites for Vera2->Vera3 upgrade?

Do I need to upgrade the ZWave firmware on my Vera2 running UI5 to 3.20 before backing up to restore to a new Vera3? I couldn’t find an answer to this anywhere in the forums/FAQs/MIOS wiki.

I am in the middle of the upgrade but wanted to ask before taking the backup V2 → restore V3 step. I have upgraded the Vera2 from UI4 to UI5 but am still running the old ZWave 2.78 firmware. I didn’t think the Vera3 supported ZWave 2.78 so I wanted to know if I should upgrade that as well before backing up the V2 and restoring to the V3.

Simple answer. Yes, to UI5, no to Z-Ware firmware. Vera 3 will operate on 2.78.

Thanks for the reply. I bit the bullet and hack upgraded to ZWave 3.20 before backing up the V2 and restoring to the V3. Seems to have worked other than the fact that I can’t link my V3 to my MIOS account either from cp.mios.com or from unit setup…

[quote=“blacey, post:3, topic:172366”]Thanks for the reply. I bit the bullet and hack upgraded to ZWave 3.20 before backing up the V2 and restoring to the V3.
Seems to have worked other than the fact that I can’t link my V3 to my MIOS account either from cp.mios.com or from unit setup…[/quote]

On your Vera 3 have your tried ACCOUNT > Other Users and logging in. It should be displayed here.

When you run the command below does it show up with the correct user details? If it doesn’t I would suggest raising a ticket to MCV.
http://sta1.mios.com/locator_json.php?username=YOUR_USERNAME

Thanks again for your help. If I navigate to Account > Other Users, I am prompted to add the Vera 3 to my account and shows the MIOS login screen. I log in with my credentials successfully but then receive a dialog - unable to retrieve data, if the problem persists…

Using the command you provided, I see that both my old Vera 2 and the new Vera 3:

Vera 2 (decommissioned)

{"serialNumber":"13xxx","FirmwareVersion":"1.5.408","name":"California","ipAddress":"192.168.0.115","users":["myUserName"],"active_server":"fwd2.mios.com","forwardServers":[{"hostName":"fwd2.mios.com","primary":true},{"hostName":"fwd1.mios.com","primary":false}]}]}

Vera 3 (Upgraded and active)

{"serialNumber":"3000zzzz","FirmwareVersion":"1.5.408","name":null,"ipAddress":"192.168.0.69","users":[],"active_server":"fwd2.mios.com","forwardServers":[{"hostName":"fwd2.mios.com","primary":true},{"hostName":"fwd1.mios.com","primary":false}]},

One thing that is interesting is that the Vera 3 IP address is incorrect on the MIOS servers. My DCHP server assigns the address to my Vera using the MAC address so the Vera 3 is currently assigned 192.168.0.115 (the same as what the Vera 2 used) and not 192.168.0.69 - that was the temporary IP assigned until I replaced the Vera 2 MAC address on my DHCP server with the Vera 3 MAC address.

Does it look like the Vera 3 is using the proper MIOS servers? I am perfectly comfortable logging in via ssh and running commands to recover so if there is anything else I can inspect on the Vera 3 and report back here, let me know.

Perhaps this is an indication of what is happening. Note the FAILURE : Received an error response from server : ERROR: invalid FK_AccessPoint/HWKey

Aug 12 08:09:24 MiOS_3000xxxx user.notice cmh-report[16788]: === New call to /usr/bin/Report_AP.sh from init [1] with parent [0] ===
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: RT3662 OpenWrt Backfire or greater detected
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: Current distribution type is: squashfs
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: Returning server for MAIN=sta2.mios.com BCK=sta1.mios.com LAST=sta2.mios.com UseBCK(USE_ST_SRV_BCK=0)
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: Return Server : ST_SRV=sta2.mios.com
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: Returning server for MAIN=ts2.mios.com BCK=ts1.mios.com LAST=ts2.mios.com UseBCK(USE_TS_SRV_BCK=0)
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: Return Server : TS_SRV=ts2.mios.com
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: Returning server for MAIN=cms2.mios.com BCK=cms1.mios.com LAST=cms2.mios.com UseBCK(USE_EVT_SRV_BCK=0)
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: Return Server : EVT_SRV=cms2.mios.com
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: Returning server for MAIN=storage2.mios.com BCK=storage1.mios.com LAST=storage2.mios.com UseBCK(USE_STORAGE_SRV_BCK=0)
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: Return Server : STORAGE_SRV=storage2.mios.com
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: Returning server for MAIN=fwd2.mios.com BCK=fwd1.mios.com LAST=fwd2.mios.com UseBCK(USE_FWD_SRV_BCK=0)
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: Return Server : FWD_SRV=fwd2.mios.com
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: Returning server for MAIN= BCK= LAST=cp.mios.com UseBCK(USE_PORTAL_SRV_BCK=)
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: Return Server : PORTAL_SRV=cp.mios.com
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: Returning working server for MAIN=sta2.mios.com BCK=sta1.mios.com LAST=sta2.mios.com UseBCK(USE_ST_SRV_BCK=0) with do_report=0
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: Testing connection to: sta2.mios.com on Port: 443
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: 1 got response from sta2.mios.com
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: TestSeq=1 - Connection to: sta2.mios.com is 1
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: sta2.mios.com Reached. Proceeding...
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: MAIN Working
Aug 12 08:09:25 MiOS_3000xxxx user.notice cmh-report[16788]: Reporting lan:192.168.81.1 wan:192.168.0.115 mac:xx:xx:xx:xx:xx:x firm-ver:1.5.408 zwave-ver:3.20-l1_r0_h148e0c8_n1_s0_is0_o0_si0_rp1_su0_pr0 to:sta2.mios.com
Aug 12 08:09:26 MiOS_3000xxxx user.notice cmh-report[16788]: st_bck:0 ts_bck:0 fwd_bck:0 store_bck:0 evt_bck:0
Aug 12 08:09:26 MiOS_3000xxxx user.notice cmh-report[16788]: FAILURE : Received an error response from server : ERROR: invalid FK_AccessPoint/HWKey
Aug 12 08:09:26 MiOS_3000xxxx user.notice cmh-report[16788]: Report Response is empty, not overwritting services file

I connected the Vera 3 to my LAN using the WAN port…

  1. I removed the Vera 2 from my MIOS account by powering it up and executing the /cgi-bin/cmh/remove_ra.sh

  2. After looking at this a bit further, it seems the hardware keys on my Vera 3 are from the Vera 2 backup. I confirmed this by modifying the /etc/cmh/PK_Accesspoint file on my Vera 3 to use the Vera 2 serial number. Once I did that, I could run the /usr/bin/Report_AP.sh script without receiving the invalide FK_Accesspoint/HWKey message. Unfortunately, the upgrade instructions did not suggest backing up the Vera 3 prior restoring from the Vera 2 UI5 backup so I don’t have the original Vera 3 hardware keys.

Should I factory reset my Vera 3 and try to upgrade via Vera 2 restore again?

I just filed a trouble-ticket with Micasaverde to help fix the Vera 3/Vera 2 cross-identity problem. Let’s see what they come up with.

I think I know the root cause after looking at the Vera restore scripts. It seems that the restore conditionally executes different steps depending upon the information contained in /etc/mios_backup.info that is generated when you create a backup to prevent overriding prior serial numbers of model-specific settings. However, I actually restored my Vera 2 backup to my Vera 3 twice because the Restore Z-Wave network option wasn’t available during the first restore and I suspect the problem is that the first restore overwrote the Vera 3 /etc/mios_backup.info file with the Vera 2 /etc/mios_backup.info causing the second restore to treat my new Vera 3 as though it was restoring to my old Vera 2 hence overwriting the hardware keys.

It seems that a Vera 3 backup should be available somewhere on the MIOS servers based upon this:

root@MiOS_3000xxxx:/etc# cat mios_backup.info.old 

BACKUP_UnitSerial=3000xxxx
BACKUP_UnitMac=00:00:00:00:00:00

BACKUP_VeraModel=Vera3Pro
BACKUP_VeraPlatform=rt3662_Luup
BACKUP_VeraFirmwareVersion=1.5.286
BACKUP_VeraUI=5
BACKUP_VeraLanguage=en
BACKUP_VeraSkin=mios
BACKUP_VeraBranding=1

BACKUP_UnitModel="Sercomm NA900"
BACKUP_UnitPlatform=rt3662

BACKUP_KernelVersion=2.6
BACKUP_DistributionType=squashfs
BACKUP_DistributionBuildVersion=79
BACKUP_DistributionFullVersion=rt3662-2.6-backfire-10.03.1
BACKUP_DistributionVersion=10.03.1
BACKUP_DistributionCodename=backfire

BACKUP_Date="Sat, 11 Aug 2012 14:57:26 -0700"

This is the /etc/mios_backup.info file that was in place when I performed the second restore.

root@MiOS_3000xxxx:/etc# cat mios_backup.info

BACKUP_UnitSerial=13xxxx
BACKUP_UnitMac=00:00:00:00:00:00

BACKUP_VeraModel=Vera2
BACKUP_VeraPlatform=wl500gP_Luup
BACKUP_VeraFirmwareVersion=1.5.408
BACKUP_VeraUI=5
BACKUP_VeraLanguage=en
BACKUP_VeraSkin=mios
BACKUP_VeraBranding=1

BACKUP_UnitModel="SERCOMM NA401"
BACKUP_UnitPlatform=wl500gP

BACKUP_KernelVersion=2.4
BACKUP_DistributionType=squashfs
BACKUP_DistributionBuildVersion=
BACKUP_DistributionFullVersion=brcm-2.4-backfire-10.03
BACKUP_DistributionVersion=10.03
BACKUP_DistributionCodename=backfire

BACKUP_Date="Sat, 11 Aug 2012 14:43:23 -0700"

Note, I redacted the MAC addresses and unit serial numbers above for obvious reasons :wink:

There is clearly a bug in the restore script - it probably shouldn’t overwrite /etc/mios_backup.info or it should also use /etc/mios_backup.info.old to support a more-than-one restore use case. Anyone performing a Vera 2 → Vera 3 upgrade - DO NOT RESTORE MORE THAN ONCE

Does anyone know how I can access the Vera 3 backup that was created at 14:57 above? I do not have a local copy of the backup so could it be somewhere on the Vera 3 or on the MIOS servers?

Go back three post and modify the post to redact your serial.
As you have now submitted the ticket, you should stop and let MCV review.
They will have a copy of your backups.

Good catch - thanks!

Try this for back up.
Go to System Setting and login.
Goto Backups

Thanks Brientim, no luck on the system backups but I found this little gem in the restore cgi script…

        PK_AccessPoint=$(nvram get vera_serial)
        HW_Key=$(nvram get vera_hw_key)

So the serial number and hardware key are both stored in non-volatile RAM. From the command line, I issued:

cat $(nvram get vera_hw_key) > /etc/cmh/HW_Key

With the PK_Access point serial number and the HW_Key in sync, I then issued:

/usr/bin/Report_Ap.sh

Resulting in success:


MiOS_3000xxxx user.notice cmh-report[6159]: === New call to /usr/bin/Report_AP.sh from -ash [29316] with parent /usr/sbin/dropbear -P /var/run/dropbear.1.pid -p 22 [29267] ===
MiOS_3000xxxx user.notice cmh-report[6159]: RT3662 OpenWrt Backfire or greater detected
MiOS_3000xxxx user.notice cmh-report[6159]: Current distribution type is: squashfs
MiOS_3000xxxx user.notice cmh-report[6159]: Returning server for MAIN=sta2.mios.com BCK=sta1.mios.com LAST=sta2.mios.com UseBCK(USE_ST_SRV_BCK=0)
MiOS_3000xxxx user.notice cmh-report[6159]: Return Server : ST_SRV=sta2.mios.com
MiOS_3000xxxx user.notice cmh-report[6159]: Returning server for MAIN=ts2.mios.com BCK=ts1.mios.com LAST=ts2.mios.com UseBCK(USE_TS_SRV_BCK=0)
MiOS_3000xxxx user.notice cmh-report[6159]: Return Server : TS_SRV=ts2.mios.com
MiOS_3000xxxx user.notice cmh-report[6159]: Returning server for MAIN=cms2.mios.com BCK=cms1.mios.com LAST=cms2.mios.com UseBCK(USE_EVT_SRV_BCK=0)
MiOS_3000xxxx user.notice cmh-report[6159]: Return Server : EVT_SRV=cms2.mios.com
MiOS_3000xxxx user.notice cmh-report[6159]: Returning server for MAIN=storage2.mios.com BCK=storage1.mios.com LAST=storage2.mios.com UseBCK(USE_STORAGE_SRV_BCK=0)
MiOS_3000xxxx user.notice cmh-report[6159]: Return Server : STORAGE_SRV=storage2.mios.com
MiOS_3000xxxx user.notice cmh-report[6159]: Returning server for MAIN=fwd2.mios.com BCK=fwd1.mios.com LAST=fwd2.mios.com UseBCK(USE_FWD_SRV_BCK=0)
MiOS_3000xxxx user.notice cmh-report[6159]: Return Server : FWD_SRV=fwd2.mios.com
MiOS_3000xxxx user.notice cmh-report[6159]: Returning server for MAIN= BCK= LAST=cp.mios.com UseBCK(USE_PORTAL_SRV_BCK=)
MiOS_3000xxxx user.notice cmh-report[6159]: Return Server : PORTAL_SRV=cp.mios.com
MiOS_3000xxxx user.notice cmh-report[6159]: Returning working server for MAIN=sta2.mios.com BCK=sta1.mios.com LAST=sta2.mios.com UseBCK(USE_ST_SRV_BCK=0) with do_report=0
MiOS_3000xxxx user.notice cmh-report[6159]: Testing connection to: sta2.mios.com on Port: 443
MiOS_3000xxxx user.notice cmh-report[6159]: 1 got response from sta2.mios.com
MiOS_3000xxxx user.notice cmh-report[6159]: TestSeq=1 - Connection to: sta2.mios.com is 1
MiOS_3000xxxx user.notice cmh-report[6159]: sta2.mios.com Reached. Proceeding...
MiOS_3000xxxx user.notice cmh-report[6159]: MAIN Working
MiOS_3000xxxx user.notice cmh-report[6159]: Reporting lan:192.168.81.1 wan:192.168.0.115 mac:00:00:00:00:00:00 firm-ver:1.5.408 zwave-ver:3.20-l1_r2_h148e0c8_n1_s1_is0_o0_si0_rp1_su0_pr0 to:sta2.mios.com
MiOS_3000xxxx user.notice cmh-report[6159]: st_bck:0 ts_bck:0 fwd_bck:0 store_bck:0 evt_bck:0
MiOS_3000xxxx user.notice cmh-report[6159]: SUCCESS : Reported AP 192.168.81.1, 192.168.0.115, 00:00:00:00:00:00, 1.5.408 to sta server : sta2.mios.com
MiOS_3000xxxx user.notice mios_services[6348]: BEGIN
MiOS_3000xxxx user.notice mios_services[6348]: local_access undefined
MiOS_3000xxxx user.notice mios_services[6348]: Requesting new servers from server
MiOS_3000xxxx user.notice mios_services[6348]: No changes required for sync users
MiOS_3000xxxx user.notice mios_services[6348]: Updating current ergy key
MiOS_3000xxxx user.notice mios_services[6348]: No update required for ergy conf
MiOS_3000xxxx user.notice mios_services[6348]: MiOS RC: Got Values: (RA_Port|RA_Dissalowed) File: (0|0) Param: (0|0)
MiOS_3000xxxx user.notice mios_services[6348]: No changes required for config_mios_rc
MiOS_3000xxxx user.notice mios-server_sync[6368]: BEGIN
MiOS_3000xxxx user.notice mios_services[6348]: No changes required for branding. Unit allready branded with FK_Branding=1.
MiOS_3000xxxx user.notice mios_services[6348]: auto-upgrade is off
MiOS_3000xxxx user.notice mios_services[6348]: auto-upgrade not pressent in cron
MiOS_3000xxxx user.notice mios_services[6348]: No update required for locator.json
MiOS_3000xxxx user.notice mios-server_sync[6368]: Returning working server for MAIN=sta2.mios.com BCK=sta1.mios.com LAST=sta2.mios.com UseBCK(USE_ST_SRV_BCK=0) with do_report=0
MiOS_3000xxxx user.notice mios_services[6348]: END
MiOS_3000xxxx user.notice mios-server_sync[6368]: Testing connection to: sta2.mios.com on Port: 443
MiOS_3000xxxx user.notice mios-server_sync[6368]: 1 got response from sta2.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: TestSeq=1 - Connection to: sta2.mios.com is 1
MiOS_3000xxxx user.notice mios-server_sync[6368]: sta2.mios.com Reached. Proceeding...
MiOS_3000xxxx user.notice mios-server_sync[6368]: MAIN Working
MiOS_3000xxxx user.notice mios-server_sync[6368]: Successfully retrieved new servers: ST_SRV_MAIN:sta2.mios.com ST_SRV_BCK:sta1.mios.com FWD_SRV_MAIN:fwd2.mios.com FWD_SRV_BCK:fwd1.mios.com STORAGE_SRV_MAIN:storage2.mios.com STORAGE_SRV_BCK:storage1.mios.com EV
MiOS_3000xxxx user.notice mios-server_sync[6368]: Got Server From ProvisionSrv: ST_SRV_MAIN=sta2.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: Got Server From ProvisionSrv: ST_SRV_BCK=sta1.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: Got Server From ProvisionSrv: FWD_SRV_MAIN=fwd2.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: Got Server From ProvisionSrv: FWD_SRV_BCK=fwd1.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: Got Server From ProvisionSrv: STORAGE_SRV_MAIN=storage2.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: Got Server From ProvisionSrv: STORAGE_SRV_BCK=storage1.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: Got Server From ProvisionSrv: EVT_SRV_MAIN=cms2.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: Got Server From ProvisionSrv: EVT_SRV_BCK=cms1.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: Got Server From ProvisionSrv: PROVISION_SRV=provision.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: Got Server From ProvisionSrv: DOWNLOAD_SRV_MAIN=download2.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: Got Server From ProvisionSrv: DOWNLOAD_SRV_BCK=download1.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: Got Server From ProvisionSrv: LOGS_SRV_MAIN=logs2.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: Got Server From ProvisionSrv: LOGS_SRV_BCK=logs1.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: Got Server From ProvisionSrv: TS_SRV_MAIN=ts2.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: Got Server From ProvisionSrv: TS_SRV_BCK=ts1.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: Got Server From ProvisionSrv: PORTAL_SRV=cp.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: NOTICE: Start updating servers in NVRAM and FILE(/etc/cmh/servers.conf)
MiOS_3000xxxx user.notice LOCK[6368]: Try to get lock on NVRAM for mios-service-servers_sync
MiOS_3000xxxx user.notice LOCK[6368]: NVRAM LOCKED
MiOS_3000xxxx user.notice mios-server_sync[6368]: Processing SERVER=ST_SRV_MAIN with values PROVISION=sta2.mios.com, FILE=sta2.mios.com, NVRAM=sta2.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: NVRAM : Old server same as new one
MiOS_3000xxxx user.notice mios-server_sync[6368]: FILE : Old server same as new one
MiOS_3000xxxx user.notice mios-server_sync[6368]: Processing SERVER=ST_SRV_BCK with values PROVISION=sta1.mios.com, FILE=sta1.mios.com, NVRAM=sta1.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: NVRAM : Old server same as new one
MiOS_3000xxxx user.notice mios-server_sync[6368]: FILE : Old server same as new one
MiOS_3000xxxx user.notice mios-server_sync[6368]: Processing SERVER=FWD_SRV_MAIN with values PROVISION=fwd2.mios.com, FILE=fwd2.mios.com, NVRAM=fwd2.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: NVRAM : Old server same as new one
MiOS_3000xxxx user.notice mios-server_sync[6368]: FILE : Old server same as new one
MiOS_3000xxxx user.notice mios-server_sync[6368]: Processing SERVER=FWD_SRV_BCK with values PROVISION=fwd1.mios.com, FILE=fwd1.mios.com, NVRAM=fwd1.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: NVRAM : Old server same as new one
MiOS_3000xxxx user.notice mios-server_sync[6368]: FILE : Old server same as new one
MiOS_3000xxxx user.notice mios-server_sync[6368]: Processing SERVER=STORAGE_SRV_MAIN with values PROVISION=storage2.mios.com, FILE=storage2.mios.com, NVRAM=storage2.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: NVRAM : Old server same as new one
MiOS_3000xxxx user.notice mios-server_sync[6368]: FILE : Old server same as new one
MiOS_3000xxxx user.notice mios-server_sync[6368]: Processing SERVER=STORAGE_SRV_BCK with values PROVISION=storage1.mios.com, FILE=storage1.mios.com, NVRAM=storage1.mios.com
MiOS_3000xxxx user.notice mios-server_sync[6368]: NVRAM : Old server same as new one

And logging into cp.mios.com, the Vera 3 showed up with the correct IP address. I don’t know about /etc/HW_Key2 but I am going to attempt to add the Vera 3 to my account now that the Access Point Serial # and Hardware Keys match and the private IP address is correct on the MiOS servers. I will report back.

Success! My Vera 3 is now linked to my MiOS account on cp.mios.com. I don’t know what other collateral damage the second restore did (i.e. other files that overwrote my Vera 3 files but things are looking better such as /etc/cmh/cmh.conf, /etc/cmh/vera_model, /etc/cmh/platform, etc.). I have a ticket filed with MicasaVerde so hopefully they will scrub the configuration so my Vera 3 knows it is a 3Pro and not a 2.

More good news. Once I recovered the correct hardware key from nvram so I could link the Vera3 to my MiOS account, I was able to download the Vera3 backup on the MiOS servers that was created before I upgraded the Vera3 to 1.5.408 from 1.5.286. This allowed me to restore the correct /etc/cmh configuration files such as HW_Key2, cmh.conf and vera_model so I believe I have recovered nearly completely. I will wait to hear from MiOS at this point but the Vera 3 appears to be working properly at this point.

Breintim, THANKS for all your help. ;D