This is what version I’m on 1.7.649. I added a new device and wanted to run this I went to Settings > Vwave Settings. There used to be a tab for it along with the Options and Advanced tabs.
I’m so confused I just ran this last week. Been adding a few Kwikset 910’s and found doing the heal/repair process after adding them makes them work best.
[quote=“erickpanger, post:1, topic:188286”]This is what version I’m on 1.7.649. I added a new device and wanted to run this I went to Settings > Vwave Settings. There used to be a tab for it along with the Options and Advanced tabs.
I’m so confused I just ran this last week. Been adding a few Kwikset 910’s and found doing the heal/repair process after adding them makes them work best.[/quote]
http://support.getvera.com/customer/portal/articles/2078473
It’s a long read, but your answer is in there :-).
Great what ever they think they fixed does not seem to help me. Added my last 910 last night and now it is just sitting for the last 13 hours “Please wait! Getting secure classes” The heal/repair usually fixed that. It did for the other two I installed.
Hmmmm Starting down the OpenHAB path later today. I have a ASUS Chromebox I’m going to re-purpose. Should be sweet.
OpenHab does not support the secure classes.
No native support yet, since it’s still under development, but @erickpanger indicated they had a VeraLite (in May) which would be more than ample to run the ZWave side of an openHAB deployment (using stable 1.5.xxx releases, and the MiOS Bridge binding).
Hopefully they still have that unit, in addn to whatever they’re currently running (?) UI7 on.
So, is it just me or are there others confused by this as well?
Does the latest Zwave firmware genuinely mean that manual healing is no longer necessary or has Vera just decided to omit the functionality? It’s just all so vague.
I wonder if someone with some knowledge of this could chime in?
I haven’t verified it myself, but the release notes indicate that Vera Ltd. is using newer Z-Wave chip firmware. This newer firmware uses a different routing algorithm than the prior version.
It seems that Vera Ltd is sufficiently satisfied with the newer Z-Wave routing algorithm and is abandoning Mios routing completely, this negates the need for network heal operations, where Vera overrides Sigma Z-Wave routing with its own.
As I said, I have not verified this for myself, so it is possible that there is still a nightly scheduled operation of some kind, but no more manual heals are required.
This should be a good thing.
I really think we need Vera to way in on this. What is the new process for inclusion of a device in a zwave network that can not communicate directly to the controller. Before I would add the device, then do a heal to update neighbors. You can still do this on a per device basis, so I would assume this is the process?
Love the major change without any communications or documentation BTW.
[quote=“swarmier”]I really think we need Vera to way in on this. What is the new process for inclusion of a device in a zwave network that can not communicate directly to the controller. Before I would add the device, then do a heal to update neighbors. You can still do this on a per device basis, so I would assume this is the process?
Love the major change without any communications or documentation BTW.[/quote]
Couldn’t agree more. Such a significant change requires a little more information I think…
Z-Waver is correct. We upgraded to the current Z-Wave firmware from Sigma and they removed the heal function. The controller will automatically run a network heal nightly.
If you are continuing to have connectivity issues please contact Customer Care, support@getvera.com or http://support.getvera.com/customer/portal/emails/new and CC me, marc@getvera.com so we can look into the issue and involve the Development Team if it is a systemic issue.
Hi Marc. If Vera is still running a nightly heal, then what exactly did Sigma remove? Presumably the heal wouldn’t work at all if the actual function was depreciated… And, are you saying that when adding a new node (for example) we must wait for a nightly heal to occur? That can’t be right. Finally, once my network routing is OK, I’d want to disable the nightly heal just as I used to previously. Why is that not permitted anymore.
Still confused…
What about those of us using a Z-Wave USB dongle?
So this morning I check and 11 devices show disconnected. All were fine last night and no changes were made. No way to do a manual heal anymore to try to get that fixed. Needless to say I am not a happy camper. I would really appreciate if GetVera could request Sigma to allow the option to switch the nightly heal off or at least allow a manual heal to resolve this kind of issue. Half my sensors are now offline including smoke detectors. This to me is not acceptable in a production environment,
I used to have more problems (especially with battery devices) and automatic nightly heals. I canceled them before and solved my problems. I haven’t checked but hope its not a forced heel now.
I used to have more problems (especially with battery devices) and automatic nightly heals. I canceled them before and solved my problems. I haven’t checked but hope its not a forced heel now.[/quote]
Brace yourself…
It was also causing me more issues than it fixed which is why I disabled it, so I could control when it ran.
Like I said earlier, if sigma truly removed heals then Vera wouldn’t be able to initiate them at all. This is what makes no sense to me. What was actually changed?
And today all is fine again. Vera happily announces that all devices are working great. I don’t understand why it’s losing devices one night and finding them again the next. They are all indoor devices in an air conditioned house. It’s not even the furthest away devices.
I just had the exact same problem. One day, four devices have errors. The next day, everything works! What’s up with Z-Wave??
Chiming in here - have the same issue work what looks to me like random “can’t connect to device” messages that come and go on a daily basis. Reached out to support days ago, so far no beep from them. Never had that issue before on UI5. More than frustrating ( and somewhat dangerous, since smoke detectors are amongst those “unreachable” devices… )
I have the same issue, but so far I haven’t had an issue actually reaching or using them. It’s only been a neg or notification in the UI (which i don’t use). So I don’t see it as a major issue but there is a bug there.
We are aware of what is going on and are actively working on getting it resolved at the highest levels of Vera.
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules