Vera automatically adds itself to any association groups created. Is there a way to prevent this, and remove it from the associations.
When I view the associations Vera does not show itself listed, but I know that it is. I have viewed the associations with another z-wave controller to confirm that it does this. This auto created association causes extremely slow response times for 3-way switches that use the associations to pair with a light switch (or what ever it’s associated with).
For people who have items like the Linear 3 way switch this can quickly be demonstrated by unplugging the vera, turning off a light, then trying to turn the light back on. There will be a delay of several minutes while the switch tries to notify everything in it’s associated group but can’t (since the vera is now in-accessible).
Please help
There no way to do what you want through the GUI. I don’t think it can be done with Vera at all, but there might be some hidden script somewhere.
Vera relies on that association in order to receive state changes when the switch is manually activated. The association is an important aspect of how Vera works.
I have used the WD500Z/WS15Z and the WT00Z and they respond very quickly, if not instantly.
The slowness that you describe can be resolved by improving the resilience of your Z-Wave mesh, thereby improving routes, by adding intermediate nodes. If the network is already sufficiently dense then a heal or routing configuration changes may be the answer.
The switches respond instantaneously as long as Vera is on (and working). The issue arises when Vera is off or frozen.
I’m not sure how the association in this case helps Vera. When I turn on the light via the 3 way switch the light in the gui isn’t updated until the next poll. The association in this case does nothing for Vera, and it’s not how other controllers (at least controllers from z-way) work.
[quote=“Erasmuz, post:3, topic:188246”]The switches respond instantaneously as long as Vera is on (and working). The issue arises when Vera is off or frozen.[/quote]I understand your situation a little better now.
What you describe indicates that Vera is a routing node between the switches. When you turn Vera off, and the route becomes broken, the switch has to retry other routes(possibly all failing) before finally getting the command through(possibly via direct broadcast). The point is that the association has nothing to do with the delay, the delay is a routing “issue”.
Sadly, routing is not the issue. The issue is that Vera adds itself to any association group created. I have tested this in the past by including a secondary controller which let me query devices for associations, and removing them with the secondary controller. This fixed the issue.
I would do this procedure again, but now Vera is giving security scheme errors when I try to add my secondary controller, and would just like to prevent Vera from doing this in the future, or at least be able to easily remove it from the list of associations via Vera.
I was planning on posting pictures to show the associations, but again, Vera is giving me errors so I am unable to add my secondary controller to view the associations.