-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
Vera state tracking broken since ~0.85 #23415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
I am running the latest version and it works for a day or so and stops updating. |
I'm also seeing the same issues. |
Hopefully it can be fixed relatively soon. I use the Vera for a few things, one of which is a scene switch that doesn't appear to be supported by OpenZwave, and therefore home assistant. |
I think there is better tracking here: |
I've given up and ditched HA altogether - luckily the latest version of Vera is stable now and I can live without all the neat stuff in HA now that the core Vera platform is stable. |
While Vera may be somewhat stable, it's a decade behind so many other
platforms. Without PLEG (or possibly reactor, I've never used it), the Vera
platform would be nearly useless. I have automations that would be
impossible to do with Vera in one step. Going back would not be possible
for me. Many use the Vera for the hardware interface and HA for the rest.
Probably the best use of Vera....
…On Mon, Jul 29, 2019, 5:52 PM dJOS1475 ***@***.***> wrote:
I've given up and ditched HA altogether - luckily the latest version of
Vera is stable now and I can live without all the neat stuff in HA now that
the core Vera platform is stable.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#23415>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABGBF5SV2REBQB5P7ZSLRYDQB5RBTANCNFSM4HIRPA7Q>
.
|
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
I believe this issue has been resolved, but I'm not totally certain. I have almost completely moved away from Vera being a part of my HA setup... |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Uh oh!
There was an error while loading. Please reload this page.
Home Assistant release with the issue:
Last working Home Assistant release (if known):
0.84
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Component/platform:
Vera
https://www.home-assistant.io/components/vera/
Description of problem:
my Hass.io had been working great as the front end to my Vera Plus (managing Zwave devices) but from about v0.85 hassio no longer updates device states from my Vera Plus.
I can trigger things on but then the slider switch goes right back to the off position and never updates - which also means I cant turn them off. If something is turned on physically it also never updates in hassio (everything is working fine in Vera).
I’m running 100% lovelace and have been since around v0.74 without issues till 2019.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
From the logs:
The text was updated successfully, but these errors were encountered: