I might be stupid, but can someone give me a step by step description on how to assign/associate a wall light controller to a ceiling light switch (receiver). I have everything correctly added to vera/UI5 and both the controller and switch appare in the dashboard.
It baffles me that there is noe clear guide in the vera help files to do this very basic procedure.
[quote=“inv, post:1, topic:171472”]I might be stupid, but can someone give me a step by step description on how to assign/associate a wall light controller to a ceiling light switch (receiver). I have everything correctly added to vera/UI5 and both the controller and switch appare in the dashboard.
It baffles me that there is noe clear guide in the vera help files to do this very basic procedure.[/quote]
docs for adding a scene are here. This is how Vera will turn devices on and off via a controller. Can you give more specifics on what you have and what you really want to do? Direct association as you described is not really a function of vera per se but of the controller/switch. The procedure varies from brand to brand. This section of the online documentation discusses associations.
Thanks for the reply. I dont know how to be more specific, other than that i have a wall switch that I want to turn a light on with. The components are the latest zwave.me products (Z-Wave.Me). They all seem to work from UI5. I tried creating a scene (Which works) and then adding a trigger with the wall controller set as device and type to “a scene is activated”. This does not work. Can anyone confirm that this is the correct procedure?
I am not familiar with that controller or how Vera ‘sees’ it. When you click on the wrench icon for the controller is there a scenes tab? If so you can assign the scene to turn on the light and a scene to turn off the light… I tried to download the documentation for that controller and got an error on the website.
I attached an image of what I see in UI5 under the scenes tab for the controller. From the vendor I was told that the zave.me products (which are based on duwi) support scene assigning in veralite.
PS: I do have multiple scenes set up. Seems like they are not visible?
[quote=“inv, post:5, topic:171472”]I attached an image of what I see in UI5 under the scenes tab for the controller. From the vendor I was told that the zave.me products (which are based on duwi) support scene assigning in veralite.
PS: I do have multiple scenes set up. Seems like they are not visible?[/quote]
Unfortunately I do not know those controllers well at all. Under normal circumstances you would get what I am showing (this is a leviton controller). In the end the scenes tab is just a short cut way to associate a scene, which you can do manually.
Well, that’s for a 4-button scene/zone controller for which the scene tab is enabled. It’s not enabled for all scene controllers. As @aschwalb mentioned, the scene tab is a ‘shortcut’ to associate a scene. It auto-generates the trigger. You should still be able to use the method of manually setting up a trigger in a scene, select the scene controller and select [tt]A scene is activated[/tt] as the event, etc.
Although it seems like more of a hack for products that are sold as compatible it does actually work. Strange thing is that a quick click on the button doesnt work, need to hold it (not a full hold) for the scene to trigger.
I guess after this I cannot recommend duwi/zme controllers. Do you know leviton sells controllers for the EU marked?
What part are you referring to as a hack? Most of what is in the documentation seems correct. The only thing I can see what you call a hack is setting the parameters of the scene controller.
Without putting the device in ‘scene mode’ (i.e. parameters 13 and 14) you should be able to create association groups 1 and 2 from Vera to have the 06443 control other devices directly, according to the manual (which also mentions parameters 13 and 14). But you probably won’t get status updates for those devices and have to rely on polling for Vera to update.
Thanks for your help. This has clearified a lot for me. Stuff that for the rest of the iphone using world seems like a hack, is normal operation in Vera And I guess that is OK, as there arnt many companies solving this problem any better.
Nevertheless they should spend some time implementing templates for different vendors/controller so this stuff does not seem like magic. Maybe they could identify devices by their ID or users could enter manufacturer details themselves. I know there are a lot of devices out there, but it should be managable and would improve the product tenfolds.
they should spend some more time focusing on removing bugs. I edited a scene just now and it got duplicated instead of persisting the settings. Basic stuff, that reveals a none optimized product development process. Less features…more quality.
just my 50 cents
Best Home Automation shopping experience. Shop at Ezlo!