Today I received the same double switch and it took me some time to figure out how to get it working (first time fiddling with the parameters for me ;)). I have the same problem vascodp had, but I was already using the 1338 firmware. The problem occurred after assigning a group (number 2) to one of the switches and another device. Before association of the switch the Fibaro was pushing its state to Vera, after associating group 2 the state was polled i.s.o. pushed. I removed the group, but the state is still not pushed ???. Does anyone have any ideas on how to associate this device to a group without losing the push functionality? (I’m going to exclude the device and retry the process using a higher group number)
the Fibaro consists of 3 devices in Vera. Unfortunately the all get the same name.
So you first have to find out, which of them is the master device. I alwas rename them soon as I have found out which is which. The master is the only one that has the status “controlled by zwave”. The other two are controlled by the master switch.
Setting associations is only possible in the properties of the master switch. You can associate Group1 (Switch1) to one and group 2 (Switch2) to another group of devices. The group number are “hardwired” to the two switches, so its not something you could change.
I have attached a screenshot how it looks.
You only have to set the associations in the switch, not in the modules that you want to control.
Remember the device has to be saved and configured before it works.
Thanks for the quick reply! I did rename the devices and had already found one was the master and the others are the devices as mentioned earlier in this topic. I did the association in the device and not in the master, so that probably is the problem. I will try your suggestion tomorrow. Thanks for the screenshot by the way
I could not get the exclude to work as in method 2, but just removing the device from vera did the trick. I then included the device by pressing S1 three times and that again worked like a charm. Now the state was pushed to vera again, so all good. I then create scenes instead of associations, which works perfectly in my situation since I need both devices that are turned (one connected to the relay, the other a remote zwave device) on to be turned off after a specific amount of time.
Ok, I did the association as I think is correct (see screenshot). Now the device nicely pushes its status to vera. However, when I press button 2 the associated device (a fan that is connected to a duwi zwave switch) does not switch on, any ideas?
First of all the good news: I have attached my fibaros to duewi switches as well and they are more than 2 years old, so the firmware in the duewis is not likely to be a problem here.
I once have had problems to attach one duewi as well. It was dimmer module.
Two speculations come to mind: Are you sure, the fibaro is sending on and off commands? I once had the problem that one switch only switched off. I could d´see that on the module which only showed the blue LED when switching. This temporarily went away, when I cut the mains for a few seconds. But this was an unstable setting.
So I set the configuration on the fibaro to the default values. That solved the problem. (see attached screenshot)
Maybe this is your problem as well.
The other would be that I speculated the duewis have to be once associated with a duewi remote. But I couldn’t really confirm that.
Fingers crossed
Umtauscher
I bought from every type of FIBRAR ZWAVE components one piece and test it. The results are very positive. And what I like very much (especially because the service behavior of MicasVerde Support is quite different - I got now no solution for the Merten 4-gang input switch and they don’t want to use the direct contact I arranged - I cannot udnerstand why, because there are not to much devices for input operating with Batterie) ther service is responding very, very quick.
The documentation is quite good and when I have questions regarding ZWAVE custom settings I mostly get feedback between 2 h and 1 day.
The additionally virtual switch is nice and you can arm/disarm the device.
Especially the functionality to use different voltage for controling and switching (even 24V DC - without changing a setting!).
The only issue I currently have is that after changing to 24V DC the device is working but still shows as cannot be configured by VERA. But I think this might be a BUG in VERA. WIll see, what the answer of the support is.
I have now several Fibaro devicess in my installation, and I’m quite happy with it’s performance.
Jut two questions:
Even though my devices push the status to Vera in real time, I allways get a “0” when I call luup.variable_get(“urn:upnp-org:serviceId:Dimming1”, “LoadLevelTarget”, id)
Associations on group 2 (key #2) only work if a working association was created for Group 1 at the same time
Quick question… does the load current ever pass through the toggle switch? I hear (and understand) complaints about having too many mains in one box. Well, if the toggle switch is only used as a relay & never sees load current… couldn’t you just use low-gauge or stranded conductors?
The switches (pushbuttons / toggles or whatever you use) are wired to the mains live, but they don’t carry the load current. It’s pretty safe to use thinner wire or slim stranded cable, as long as you make sure there’s sufficient electrical insulation. Not sure whether or not it meets building code in your neck of the woods…
No idea. I don’t intend to use them for light switches, as I’m well-equipped already; but I’m sure there could be other uses for these than for remote control of an existing switch.
Does anyone have any idea how I can assign group 2 on the fibaro dimmer to a virtual device?
I am not able to find any virtual devices when pressing to ‘set’ for associating group 2.
All I want is that the second button will be used to change state for a virtual device. But I don’t seem to get it working.
Could you set up a scene to turn on/off your virtual device, with [tt]A device is turned on/off[/tt] for the second switch as the trigger? (It doesn’t sound like this device shows up as a scene controller + 2 switches? If it does, you’d use [tt]A scene is activated[/tt] as the trigger.)
Could you set up a scene to turn on/off your virtual device, with [tt]A device is turned on/off[/tt] for the second switch as the trigger? (It doesn’t sound like this device shows up as a scene controller + 2 switches? If it does, you’d use [tt]A scene is activated[/tt] as the trigger.)[/quote]
Thank you so much for your reply.
Yes I am able to set a scene to turn the virtual device on/off. But I am not sure how I could capture the keypressing of the second button as there is only one dimming device after inclusion.
hi all
i have just installaed the fibaro dimmer 211 to a standard 1 gang, 1 way switch… it is wired to 2 x 35w GU10 bulbs.
when i turn the unit of via the vera 2, it leaves the light on about 5%
if i want to control it from the switch, i have to flick the switch twice…
i know i have done something wrong but i dont know what
please please please can some one help me with a confirmation of wiring and programming…???
I read here about attempts to associate devices where the Fibaro zwave root device is associated with other zwave modules.
My understanding is that this is normally achieved by creating scenes where an event (operating one switch on Dashboard or physical switch) triggers a scene that switches the other devices.
Or does the association discussed here create a way to do this without involving a scene ?
And what would be the advantage of that ?
So far I have only made an association for thermostats with the related boiler switch.
In all other situations I created scenes.
The reaction is much faster, as the switch talks directly to the actors. If you use a scene, vera normally takes a few seconds to react.
You can switch even when vera is not working which is the main benfit for me.
The fibaro switches seem to have a firmware problem though, as they tend to stop sending to the associated devices after some time (including to vera). You have to reset them by cutting the mains for a short time to get them working again. (This happens every few weeks in my case) I hope this will get sorted soon.
