My migration from Vera, or what I did on my holidays
-
It is...
But
<quote>
B. Security key. (S0)If you previously succesfully included or shifted the z-way into the vera's network with the security key
<quote>
I didn't
<quote>
then the key will be in your /z-way-server/config/zddx/config*** file at the entry line 57. If not you can always ask vera's support for the way to extract the key as they deleted my post which provided the instructions to do so.
</quote>Hence my asking so I don't have to ask Vera
C
-
Ohh.... Somewhat weird but the vera team wanted to keep that secretive which no other platform really does and found at the end to be quite absurd because to get to the key, they need access to the vera which means that they would have access to controlling all of the devices anyway.
I posted it on this very forum I believe.
Here it is:
https://smarthome.community/topic/28/network-key-location/3?_=1593537609454
It is also possible that your device was not set with security but that the fibaro does support it. Therefore those command classes which require security just won't work and therefore will not respond to an interview. This would be another reason why you would not get to 100% interview. My aeotec dimmer for example shows all kinds of command classes, one set for security, and another for non secure inclusions. So if included securely I can get to 47% interview as the equivalent non secure class would be disabled. If I include insecurely, I get to 75% because the secure class commands are disabled.
-
@CatmanV2 said in My migration from Vera, or what I did on my holidays:
Did I miss something in the install then?
No. You are using a prototype which has not been engineered internally, or externally, for the general public...
...but you’re special, so you can go ahead.
-
@akbooer said in My migration from Vera, or what I did on my holidays:
...but you’re special, so you can go ahead.
Oh I know
OK so secure key copied into the file
Nothing changes. Force interview does nothing
Interview result and manually doing individual interviews gets me up to the 85%
Everything else:
[2020-06-30 20:43:45.377] [I] [zway] Waiting for job reply: Basic Get [2020-06-30 20:43:47.523] [W] [zway] Reply not received before timeout for job (Basic Get)Cheers
C
-
@CatmanV2 said in My migration from Vera, or what I did on my holidays:
[2020-06-30 20:43:45.377] [I] [zway] Waiting for job reply: Basic Get
[2020-06-30 20:43:47.523] [W] [zway] Reply not received before timeout for job (Basic Get)That's why I don't like fibaro... very weird/poor zwave implementation. The basic CC should not matter though so don't worry about it. You are sure you restarted z-way?
-
Positive. What would you recommend replacing it with?
C
-
What I meant that it isn't a problem. Then it means that I was wrong and that the vera did not include it securely.
I would recommend to exclude it and do a secure inclusion to (finally) benefit from the secure class commands on your fibaro device which vera could not support. -
Thanks
C
-
Hah! All sorted
A few more dodgy devices tomorrow ;). Thanks gents
C
-
OK so time for an update. This has kind of drifted off the 'Here's how you do it'
Most of getting Openluup, HA Bridge, AltUI, and getting Z-way up and runningwas pretty trivial (all things considered)
The migration from Vera to Z-way, was not as simple as I'd have hoped. Pretty much 2 days of fettling.
Couple of gotchas:
- My restore to the UZB dongle took a couple of shots. It took quite a long time as well.
- Migration to Z-way per se was pretty simple
- However, Z-way requires a totally different way of thinking. Pretty much every service creates an individual device. If you're not ready for this you can get in a hell of a mess trying to name stuff. I still have a few odd devices that I'm not quite sure what they are. I suspect tamper switches!
- Some devices are not what you think. Sirens. In fact these are shown as switches. Makes total sense when you think about it, but doesn't look great on the interface.
- The rooms were not migrated. So although all my rooms already existed in AltUI / Opeluup (from Vera) new devices all appeared in a ZWay room. In retrospect this could be because I already had rooms named, and they had different UIDs
- Reactor is still fantastic
- There are a couple of devices that aren't supported in Openluup / AltUI. Meh might be worth checking in advance.
Finally a huge thankyou to @akbooer @rafale77 @therealdb Partrick (is he here? If not can someone ping him the other place) and the rest of you that have made this work.
This is so much faster, more sensible, reactive, responsive and everything else. Now I just want to do more
Respect
Chris
-
Oh on that note, does anyone need a Plus for testing? If not I'll eBay it
C
-
rafale77replied to CatmanV2 on Jul 2, 2020, 8:16 PM last edited by rafale77 Jul 2, 2020, 4:19 PM
@CatmanV2 said in My migration from Vera, or what I did on my holidays:
- Some devices are not what you think. Sirens. In fact these are shown as switches. Makes total sense when you think about it, but doesn't look great on the interface.
I have a few of these... If you look at how the vera treats them... they are actually switches with a different icon. You can change the device json file to make them look like a siren.
- The rooms were not migrated. So although all my rooms already existed in AltUI / Opeluup (from Vera) new devices all appeared in a ZWay room. In retrospect this could be because I already had rooms named, and they had different UIDs
The room concept is stored in vera, not in zwave. So the migration does not migrate this. Indeed you do need to redo this part. Thanks for mentioning it.
- There are a couple of devices that aren't supported in Openluup / AltUI. Meh might be worth checking in advance.
This I think is just a matter of getting the z-way bridge to recognize them properly. As @akbooer said, it is really an early development bridge which has not been tested on every device available. @DesT and I made it work for our set of devices but I am sure many more tweaks are needed which is why we asked for some additional information.
This is so much faster, more sensible, reactive, responsive and everything else. Now I just want to do more
This is a bit of opening Pandora's box... like a light switch suddenly flipping on after walking years in darkness. It almost brought me to tears when I thought about all the time I spent and wasted on the vera peeling layers after layers of absurdity, extended by the disappointment of ezlo's own layer, which so far is looking somewhat even worse. Most importantly, the WAF will skyrocket and you will have a lot more time to do other things than fix and troubleshoot this thing to the point of maybe forgetting how it worked to begin with. This where I am after a few months and I leaped to some area of interest very far from dealing with zwave networks and device issues. (I had already long gotten rid of automation/plugin issues thanks to openLuup).. now looking at machine learning, inference models etc...
-
@rafale77 said in My migration from Vera, or what I did on my holidays:
I have a few of these... If you look at how the vera treats them... they are actually switches with a different icon. You can change the device json file to make them look like a siren.
Yes. Thinking about this right now
C
-
yes, I just checked. You can change both. The siren and the light are basically interchangeable. The services they call are the same.
-
Given there is a category, a json and an xml for siren, it seems sensible
C
-
I will embark soon on the same path. I’m just waiting for my home vacation in August. I will leave my Vera on since I still have Nest, I like them and there’s no way to port them. It will just be a Nest gateway, but I’m done with Zwave on it. The last months have been impossible, thanks to more activity outside, as it’s usually for me during Christmas time and Summer.
-
@therealdb said in My migration from Vera, or what I did on my holidays:
I still have Nest, I like them and there’s no way to port them
HA Bridge.....
C
-
Nest closed its APIs, so you cannot request a new key, but previous integrations works. I may have a key or two laying around. We’ll see.
-
@therealdb said in My migration from Vera, or what I did on my holidays:
Nest closed its APIs, so you cannot request a new key, but previous integrations works. I may have a key or two laying around. We’ll see.
Ahhh I see!
C
92/105
