I have various Fibaro Dimmer 2’s and use them to control dimmable led-lights throughout the house. I used ‘association groups’ with mediocre success (i.e. often not all lights turn of). Now, I added a level of complexity by installing a Ikea Tradfri bulb on the bedside table - and I am stuck.
My goal: use a fibaro dimmer 2 - S1 or S2 switch - to switch off:
the lamp it’s physically connect to (no issue)
various other lamps that have fibaro dimmer 2’s (works, but unreliable through ‘association groups’)
switch of a zigbee device (Ikea tradfri bulb)
I believe, the best solution that allows for freedom and creativty is to use the Smartthings Scenes. Hereby, I don’t mean scenes triggered by the dimmer (i.e. https://i.imgur.com/GjkwXui.png), but scenes like ‘bedtime’ or ‘leaving the house’.
I believe this boils down to the (in essence) simple question:
How can you activate a scene with a Fibaro Dimmer 2?
Despite this seemingly simple question the answer (to me at least) didn’t seem so straight-forward. Been searching tirelessly for the last the last 1.5 days, so I’d love to hear your ideas and help keep my (and my wife’s) sanity
Fibaro scene and smartthings scenes are completely different things the only way to access fibaro scenes to use it to trigger your ikea bulb is to use webcore.
I have the same set up using the s2 button on fibaro dimmer 2 to turn on ikea bulbs in my hallway.
I just installed webcore and am not able to use the S2 button yet. Moreover, I don’t see the scene activation in the log as well when I press the S2 button, despite the fact that I enabled this under setting 28.
Can you share your throughts on how to get this party started in Webcore? A screenshot of your settings would come in handy as well perhaps.
I don’t have 2 devices, but only 1. Never knew that might be an option. If I have 2 devices available for 1 double monetary switch that would greatly simplify my life indeed.
Below the screenshot of the DTH that I have used for many years:
Update: I switched on the first IDE live logging level to ‘info’ and now the S2 button nicely shows up as ‘scene #26’ in the log. Still unsure how to move along with Webcore though.
At the moment I am stuck at this point. I was able to fix the status report by switching on IDE live logging. However, there is no reaction yet on my action of pressing the S2 button, despite the fact that the trigger is seen (and Webcore shows that it is ‘subscribing’).
Fibaro scenes are “zwave central scenes.” SmartThings doesn’t provide any official feature to access these, but many people have written custom DTHs which convert the central scene number for a specific device so that it looks like a button press to smartthings. This allows you to use it with smartlighting or some of the other button handlers. But since it sounds like the OP is already familiar with Webcore, that’s probably the best way to do it. I just wanted to mention that there are other ways as well.
Cool thanks I wasn’t familiar with that I thought only webcore showed the fibaro scenes.
Do you know which device handlers would allow him to use fibaro scenes in smart lighting app?
That’s the problem I originally mentioned: last time I looked no one had updated the Fibaro DTHs to work with the new app. and Fibaro has already said that they don’t want to spend extra company resources just to provide smartthings integration. They feel Zwave certification should be enough and after that if a hub has its own unique requirements, the hub manufacturer should provide them. This is very different from, for example, Zooz and Inovelli, both of which have provided updated DTHs for their central scene devices.
There are at least a half a dozen threads, maybe more, in the forum from people reporting that Fibaro doesn’t work anymore with the new app, so maybe look for some of those. But if webcore is working and the OP is comfortable with it, that just seems simpler right now.
It’s a shame as fibaro make such good hardware but they don’t seem interested in working with smartthings or even making it possible to update their firmware.
But as you’ve said in other posts it seems z wave might be left behind in a few years and if I’d do it all again now I’d probably use cheaper zigbee modules instead of z wave.
Not to get too far off topic, but the biggest advantage of Zwave is that there’s no issue with Wi-Fi interference. And for fixed location devices like light switches, that can be a very real advantage indeed.
I’m one of those who doesn’t feel that the blame really accrues to Fibaro in this circumstance. Their devices are certified to a third-party standard, Z wave. That should be enough. The fact that it isn’t is just highlighting weaknesses in the smartthings Zwave implementation, and I don’t think it’s up to the third-party manufacturers to fill in those cracks every time.
In fact, one of the things that I’m hopeful about for the new partnership where Aeotec is taking over the hub hardware is that maybe that will put pressure on smartthings to begin supporting some of the more advanced Zwave features through the official UI, including associations and central scenes. Aeotec’s other hubs do. So I’m hopeful that, say, two years from now, Fibaro zwave devices will work even better with smartthings. But we will see.
Hi JDR,
I’m in the process of migrating all of my logic from Webcore to SharpTools and one of the features I’m currently missing is the ability of SharpTools to use the ‘scene’ of a Fibaro Dimmer as a trigger.
Any suggestions as to the best way to achieve this since Webcore stopped working on me last week ?
How were you doing things in WebCoRE? As long as it wasn’t dependent on a legacy groovy custom command/attribute (which was not implemented in a custom capability), then you should be able to use the same states in SharpTools.
If it was a custom Groovy DTH, you might want to check to see if there’s a equivalent edge driver which has that functionality properly defined as SmartThings is dropping the ability to have custom attributes/commands which are not defined as part of a custom capability. As long as it gets defined as part of a custom capability, you should then be able to use it again.
Previously I have been using Webcore to monitor Fibaro scenes (Dimmer S2 single / double / triple click / hold). Depending upon the S2 button press, the Fibaro scene value changes to a value between 22 & 26.
I’m not referring to SmartThings Scenes, this is the ‘scene’ attribute of a Fibaro device. The scene value can be seen in the device attributes of the SmartThings IDE.
e.g. a switch is double-clicked & the scene value changes to 24. Webcore was using this change & value as a trigger.
SharpTools doesn’t seem to support this feature natively (or if it does I’m not sure how to set it up), so I’m hoping there is another way to use Fibaro device scenes as a trigger and create an action within SmartThings (e.g. virtual switch change) which i will subsequently use as a trigger within SharpTools.
Understood. As long as it’s not part of a legacy groovy custom attribute (which wasn’t part of a custom capability), you should be able to do it in SharpTools.
But if it was part of a custom attribute in a groovy DTH that didn’t use a custom capability, it’s going to stop working when SmartThings shuts down Groovy anyway, so you should look for an edge driver that replicates this functionality.
If you can’t see that attribute via the SmartThings API, it won’t work when SmartThings kills the groovy DTH soon.
@Andy_Rouse This has already been addressed by Mariano in his Z-wave Mc Edge driver for a year already. Scenes now equate to S1/S2 button actions, press/hold etc and work locally with Routines.
I’m still using a custom DTH and when I view the device in the Smartthings IDE I can see under ‘current states’ a ‘scene’ value of 23. If I change the device type to ‘Z-Wave Switch’ then ‘scene’ disappears from the ‘current states’ section.
I’ve now enrolled in the Edge Beta Program and also the Mariano MC drivers that Alwas suggests, the problem is that I have over 60 physical devices (most hardwired inside and outside the house) and having to physically relocate these to the hub, to perform exclude & include to swap over to the edge drivers is literally going to take me weeks.
I’m hoping there’s:
a) a temporary way for SharpTools to use the Fibaro scene as a trigger (directly / indirectly)
b) an easier way to convert a device from DTH to Edge driver (leaving each device in situ)
and Fibaro has already said that they don’t want to spend extra company resources just to provide smartthings integration. They feel Zwave certification should be enough and after that if a hub has its own unique requirements, the hub manufacturer should provide them. This is very different from, for example, Zooz and Inovelli, both of which have provided updated DTHs for their central scene devices.
