anyone have a way to directly trigger a scene rather than associate with a device and then set up triggers based on that device?
I think there have been other threads concerning this topic, and up to now there was no solution.
But I really want to be able to do that to! Would be nice if we could figure it out or at least enter it as a feature request for vera.
I would like to be able to do it to !
If you find a solution please let me know 
I have set the following FGD-211 dimmer Parameters to “1”;- 7,14,16,19,41and Parameter 15 to “0” then created two scenes for S1 on and S2 off. But triggering these scenes with #2_Scene Controller “a scene is activated” and “which scene” = 20 does NOT work?
Any ideas anyone?
Guess you have the latest version of the dimmer described here in this documentation:
http://materialy.fibaro.com/instrukcje/instructions_EN/dimmer/dimmer%20FGD211%20v19%20-%20v111%20ENG.pdf
It is pretty new and i’m not sure the Vera recognizes it correctly yet.
Does it show up as a scene controller for you?
Anyone else having this new version?
I have a similar problem with a Vitrium Satellite 4 button controller. The buttons appear in Vera but there is no instant status support so you can’t use them directly as scene triggers 
However, I also have a fibaro 1 gang relay in my setup and the firmware on this appears to be much the same as the 2 gang one. At any rate there is a phantom second switch. Now, I can assoicate the vitrium buttons with the phantom switch and fortunately the Fibraro gear does support instant status. So now, pressing the vitrium buttons will turn the phantom switch on and I can trigger a scene called ‘Vitrium Button Event’ from the fibaro s2.
This scene runs the following LUA code, then turns off the s2 switch.
– This scene polls the vitrium buttons so that their states are valid
– Any triggers associated with the buttons will then fire
luup.call_action(“urn:micasaverde-com:serviceId:HaDevice1”,“Poll”,{},31)
luup.call_action(“urn:micasaverde-com:serviceId:HaDevice1”,“Poll”,{},32)
luup.call_action(“urn:micasaverde-com:serviceId:HaDevice1”,“Poll”,{},33)
luup.call_action(“urn:micasaverde-com:serviceId:HaDevice1”,“Poll”,{},34)
which forces Vera to poll the Vitrium buttons. Forunately this is reasonably quick.
The polling causes the button states to update in Vera and now, if any events are linked to the buttons, they trigger immediately.
If you have a similar, spare device, this is the way to go - associate group id 2 on the fibaro dimmer with somthing else and then pick up the switching of that something to trigger your event.
Of course, what we really want is to be able to associate the dimmer’s group id 2 directly with a virtual switch in Vera. See here: http://forum.micasaverde.com/index.php/topic,13344.0.html
[quote=“hek, post:5, topic:171322”]Guess you have the latest version of the dimmer described here in this documentation:
http://materialy.fibaro.com/instrukcje/instructions_EN/dimmer/dimmer%20FGD211%20v19%20-%20v111%20ENG.pdf
It is pretty new and i’m not sure the Vera recognizes it correctly yet.
Does it show up as a scene controller for you?
Anyone else having this new version?[/quote]
What do you mean by a “scene controller” Hek? do you mean does it appear in the scene trigger drop dons menu ?
Does the device have a scene “tab” like my minimote have?
Guess not?
I only have the older version of the dimmer module…
I have a support ticket on this but unfortunately support is quite bad. I put in the ticket on the 14th and first response came yesterday (21st) simply asking for more information. No response since full v1.11 manual and explanation was sent.
FYI, this works correctly in Z-Way/Z-Cloud free controller of Z-Wave.Me. I’m currently trying to run it alongside Vera using firmware 2.78 so that I can overcome some of the limitations of Vera.
[quote=“hek, post:8, topic:171322”]Does the device have a scene “tab” like my minimote have?
Guess not?
I only have the older version of the dimmer module…[/quote]
No the FGD211 does not have a “scene” tab.
In fact if I select the FGD211 dimmer as the device in the trigger section - I can only get “A device is turned on or off?”
The only way I can get “A Scene is activated” as a trigger is by selecting “#2_Scene Controller” as the device?
I wonder if I have to re-include the dimmer, having set parameter 41 to get this functionality?
When you re-include the device all setting will be cleared in the module
So is this a Fibaro problem, in that they have not identified their dimmer as a scene controller device?
or is the problem due to Vera not offering the correct drop down menu choice as a trigger?
It’s a Vera issue since they don’t offer the dimmer as a scene trigger like Z-Way/Z-Cloud does with ease. Also note that I have to set parameter 7 to 0 for dimmer to send scene changes to Z-Cloud.
As you can see from the screenshots above - I too have set parameter 7 to 0.
Are you saying that this needs a firmware fix in vera to sort out?
[quote=“jjmixman, post:6, topic:171322”]I have a similar problem with a Vitrium Satellite 4 button controller. The buttons appear in Vera but there is no instant status support so you can’t use them directly as scene triggers
However, I also have a fibaro 1 gang relay in my setup and the firmware on this appears to be much the same as the 2 gang one. At any rate there is a phantom second switch. Now, I can assoicate the vitrium buttons with the phantom switch and fortunately the Fibraro gear does support instant status. So now, pressing the vitrium buttons will turn the phantom switch on and I can trigger a scene called ‘Vitrium Button Event’ from the fibaro s2.
This scene runs the following LUA code, then turns off the s2 switch.
– This scene polls the vitrium buttons so that their states are valid
– Any triggers associated with the buttons will then fire
luup.call_action(“urn:micasaverde-com:serviceId:HaDevice1”,“Poll”,{},31)
luup.call_action(“urn:micasaverde-com:serviceId:HaDevice1”,“Poll”,{},32)
luup.call_action(“urn:micasaverde-com:serviceId:HaDevice1”,“Poll”,{},33)
luup.call_action(“urn:micasaverde-com:serviceId:HaDevice1”,“Poll”,{},34)
which forces Vera to poll the Vitrium buttons. Forunately this is reasonably quick.
The polling causes the button states to update in Vera and now, if any events are linked to the buttons, they trigger immediately.
If you have a similar, spare device, this is the way to go - associate group id 2 on the fibaro dimmer with somthing else and then pick up the switching of that something to trigger your event.
Of course, what we really want is to be able to associate the dimmer’s group id 2 directly with a virtual switch in Vera. See here: http://forum.micasaverde.com/index.php/topic,13344.0.html[/quote]
I tried this, but when I associate Group2 (S2 input of FGD211 dimmer) to the device e2 (S2 input of FGS211) then the main FGS211 light turns on - and not the second input?
You need to employ multi channel assoication to associate with the e2 object. Make the assoication with the main (parent) module of the relay and then put a ‘2’ in the multi-channel association textbox.
Thankyou jjmixman, I have used your instructions above to associate the S2 input of my FGD211 to the S2 input of a FGS211.
At least the Fibaro switch can trigger a scene - even if the dimmer can’t.
This will do until micasverde and Fibaro sort out their differences - which doesnt seem anytime soon
I got this reply from ticketing.mios.com;-
[i]Hi John,
We added this issue as a feature request, but currently we can only set the device to be entirely as a scene controller, meaning you will loose dimming capabilities and will only be able to use it as a scene controller.
The feature offered by Fibaro is not according to the z-wave standard as far as I know and it may be a bit tricky to be implemented, but I’ll consult with my colleagues from development and let you know as soon as I have any updates.
In the meantime please let me know if you want to use the device as a scene controller and I’ll change it for you.
Thank you!
–
Kind Regards,
Daniel Stephen
Mi Casa Verde Inc.
Technical Support Team - ticketing@my.mios.com[/i]
[quote=“Rompabear, post:17, topic:171322”]Thankyou jjmixman, I have used your instructions above to associate the S2 input of my FGD211 to the S2 input of a FGS211.
At least the Fibaro switch can trigger a scene - even if the dimmer can’t.
This will do until micasverde and Fibaro sort out their differences - which doesnt seem anytime soon
I got this reply from ticketing.mios.com;-
[i]Hi John,
We added this issue as a feature request, but currently we can only set the device to be entirely as a scene controller, meaning you will loose dimming capabilities and will only be able to use it as a scene controller.
The feature offered by Fibaro is not according to the z-wave standard as far as I know and it may be a bit tricky to be implemented, but I’ll consult with my colleagues from development and let you know as soon as I have any updates.
In the meantime please let me know if you want to use the device as a scene controller and I’ll change it for you.
Thank you!
–
Kind Regards,
Daniel Stephen
Mi Casa Verde Inc.
Technical Support Team - ticketing@my.mios.com[/i][/quote]
Could you post a screen-shot of the trigger