Excluding Vera Scenes and Devices configuration about pyvera

[alanfischer]

It should be fairly trivial to add an exclude_scenes configuration option to the vera component in HA. That would get around the ID overlap issue. I might have time this week to get an HA pull request in for that...

[pavoni]

@alanfischer got there before I did. If you take a look at the logic for excluding devices (eg https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/vera.py#L88) then it should be fairly easy to add an extra config variable to do the same for scenes.

[htcheng]

Upon further investigation, it appears that the connection errors I highlighted above were present before the upgrade to HA 0.83+ (I just didn't notice the errors earlier in the log files). The connection errors seem to start in most cases EXACTLY (to the second) 60min after homeassistant is started. I suspect that they might be related to the large number of scenes I have in my setup and the need to subscribe to all of these scenes in the updater.

Other than the log files spitting out errors on the connections, the only symptom I get on Home Assistant is that the state of Vera variables in HA no longer update (temperature of thermostats, dimmer settings, etc), but clicking on lights and changing things within Home Assistant and via Homekit still work via Vera.

The connection errors appear to be related to the large number of scenes that I have in Vera, but the broader issue may be related to how pyvera tracks and subscribes to state changes between Vera and HA as highlighted in this issue.

Apologies for not being more helpful as I haven't coded in a long, long time and I'm only now starting to get back into things and don't know python at all.... I will take a look at how to exclude the Vera scenes as mentioned above as that does look like something even I can do with my limited knowledge...

[htcheng]

UPDATE - The error above occurs when Vera does a LUUP engine reload (duh). I continue to have strange issues post-reload updating state changes and keeping Vera in sync with HA that I'm investigating, but these are related to my other thread on thermostats. I'll keep this open as a feature request for scene exclusion.

[htcheng]

I replaced get_complex_value with refresh_complex_value with my thermostat setpoints (see other thread) and that solved the post-reload state change update issues and it appears to keep Vera in sync with HA now. Set up has been running very reliably now and haven't needed to exclude my vera scenes... yet.

[pavoni]

Stale - so closing.