(Problem) Migration Z-Wave NW from Vera to UZB1 dongle
-
At this point it isn't worth the headache and time to potentially solve this. The "all" access token which used to work on v3.06 to be able to access via the gui the firmware downgrade option doesn't work anymore. I initially thought it was related to upgrading to v3.10 of SmartHome so I rolled back, but still it didn't work. Looks like they shut that one down.
-
I think I figured out part of my problem... in looking closer at the controller information in SmartHome app, it looks like I got an EU version instead of a US version of the dongle so it was on the wrong frequencies. I am sending it back to Amazon and re-ordered the chip off of your recommended eBay seller.
-
hmm interesting and weird... You know you can recode the dongle to US frequency right? I am just not sure if the embedded antenna was calibrated properly for it. The difference is in the number of channels and how they are optimized for their specific frequencies. The US use only two channels while 3 are used in other regions.
-
I was having issues where using OZWD I would try and add a node (inclusion) and it wouldn't register the device even if was almost on top of it.. so that eventually led me there.
I looked on the sticker on the dongle which claims it is the US version (ZMEUUZB1).
In Z-way app, it shows EU and only options that appear to be for the ZMEEUZB version (EU) dongle for changing frequency.
I tried changing frequency via shell script to US, which says it does, but Z-way still showed EU even after that.
-
I received the new USB dongle from e-bay seller. Shows US frequency in Zwave SW (5.27 release) and connected into OZWD in Home Assistant fine. Was able to successfully pair a Fibaro Dongle with it (which I couldn't get anything to pair with old dongle). So I think we have a winner
-
My wild guess is that there is a problem with the SDK version between the vera and the uzb. When I did this, my uzb was running version 6.81.05, the same version I was running on the vera, so I had no problems at all. The latest uzb firmware runs on 6.82.01. The vera also officially only supported 6.81.01 so I was already being very adventurous.
My advice would be to check what SDK your vera is running and then downgrade your uzb to a firmware version supporting this same SDK so that the zwave serial API program on the vera doesn't need to do an SDK translation. There are so many people who did this, including on the HA forum that if it isn't working anymore, probably something changed on the vera which I am not aware of. -
I might try the whole thing again. I just did a restore because at some point after I thought that none of it worked all my devices names were reset and all sitting in 'No Room'. Of course this was after I had switched the port back to the default Vera device. So something was happening maybe just at a snail's pace? Also how do I check the Vera's SDK version?
-
Sorry for not responding sooner, I was busy with work today. The SDK version of the vera should be shown in the advanced page under the z-wave submenu. You should see something like 6.1 or 6.01. which is the version of the serial API corresponding to 6.71. The point is to downgrade the firmware of the uzb to a version old enough that the vera can support. Not much more you can do on the vera.
-
Just to update: I decided to bite the bullet and just manually move everything over from Vera to Z-way. Still a couple of outstanding devices to transition. It went mostly smooth. I have a couple of devices that aren't responding as they did with the Vera network. Shouldn't be an issue of coverage.
-
wow... so it did recognize the UZB just fine and can read the network ID from it. It is purely about triggering the recovery from your backup to the Uzb dongle then. I am a bit surprised that it didn't work.
So the "/etc/cmh/dongle.restore" file never got replaced?... I wonder if the script has changed. Unfortunately I wiped my vera from anything mios so I can't test with this firmware. The nuclear option would be to edit the user-data.json from a backup and recover from it.... You are sure you have all your dongle files in the etc/cmh folder right?extract from my own old posting:
Just for documentation purpose, I also found how to restore only the onboard zwave dongle:
-move your desired dongle file (example: “dongle.6.1.dump.0”) to /etc/cmh,
-rename it “dongle.restore”,
-run Stop_cmh.sh
-run Start_cmh.sh
-run Reboot@rafale77 said in (Problem) Migration Z-Wave NW from Vera to UZB1 dongle:
wow... so it did recognize the UZB just fine and can read the network ID from it. It is purely about triggering the recovery from your backup to the Uzb dongle then. I am a bit surprised that it didn't work.
So the "/etc/cmh/dongle.restore" file never got replaced?... I wonder if the script has changed. Unfortunately I wiped my vera from anything mios so I can't test with this firmware. The nuclear option would be to edit the user-data.json from a backup and recover from it.... You are sure you have all your dongle files in the etc/cmh folder right?extract from my own old posting:
Just for documentation purpose, I also found how to restore only the onboard zwave dongle:
-move your desired dongle file (example: “dongle.6.1.dump.0”) to /etc/cmh,
-rename it “dongle.restore”,
-run Stop_cmh.sh
-run Start_cmh.sh
-run RebootRunning into the same issue with dongle.restore not getting replaced. Version shows 6.2 in Zwave settings on vera and firmware is 1.7.599 (V7.0.8 June 2015). Would you recommend renaming the dongle file and trying the above or trying a different vera firmware?
-
You can try to rename it to dongle.restore.go but the number of reports that this no longer works makes me very suspiscious. I don't know if it is another of the ezlo kamikaze moves to make migrations harder or if there is some new incompatibilities from the uzb firmwares.
It could be that you will have to downgrade the uzb firmware to make the zwave SDK compatible as the vera restore tool may be balking out at translating to unknown SDKs. -
Something worked!! Believe I set fw on 1.7.1040 then factory reset. Copied over the dongle renamed to dongle.restore.go and then tried your steps with a manual reboot. Devices didn't appear in vera but the dongle lit up blue for a second so something was going on. As I resigned myself to setting up from scratch I found 32 devices copied over to UZB in zway. Huge thanks - light at the end of the tunnel. Any way of telling which device is which, an id maybe the same on vera and zway?
-
Awesome news! The altid on the vera are technically the lower level zwave node IDs so they should match the altid (if I remember correctly as my memory of the vera is fading). The z-way bridge on openLuup however will add a pre-fix (2 digits) to the node ID and suffix (1 digit) corresponding respectively to the parents controller index and child device index.
-
Ok, so. Reloading the luup engine doesn't remove the dongle.restore or turn in into dongle.restore.go, but rebooting the vera seems to. I checked the logs and I see this:
ZWJob_BackupDongle::FindFileToRestore found 12 files using /etc/cmh/dongle.6.1.dump.0 timestamp 1630736238 / 2021-09-04 16:17:18 version 6.1 md5 30586bc3340164f7dccfb39ca218dda1 <0x77f00320>
01 09/06/21 11:53:40.943 ZWJob_BackupDongle::FixupBufferVersion don't know how to validate since there's no zensys in the firmware <0x77f00320>
01 09/06/21 11:53:40.943 ZWJob_BackupDongle::FixupBufferVersion don't know how to convert from 6.1 to 3.95 <0x77f00320>
01 09/06/21 11:53:40.944 ZWJob_BackupDongle::ZWJob_BackupDongle restore file invalid <0x77f00320>
10 09/06/21 11:53:40.944 FileUtils::DelFile /etc/cmh/dongle.restore.go <0x77f00320>So I assume from that it doesn't recognise the file as valid so it just deletes it. I assume the 6.1 to 3.95 complaint is the version (the Vera version on the Z-Wave Settings page was 6.1, and the Aeotec stick version on that page is Version: 3.95 L:1).
No idea if any of that is useful for troubleshooting?
