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’).
what kind of button are you using toggle or retractive as that makes a differance to which scene id you use.
I used this for scene ids
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.
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 ?
Can you include a virtual device in the scene and have that virtual device coming on be the sharptools trigger?
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)
You can wait for the automatic migration to the stock Z-Wave Switch driver and when you have them all working with edge driver you can try to easily change any of them with the app to my Z-Wave Switch and Child Mc driver and try to see if the scenes work for you
Button 1 will emit the scenes (single / double / triple click / hold) of the S1 and button 2 will emit the scenes (single / double / triple click / hold) of the S2
Just to clarify that the SmartThings IDE is part of the legacy platform (tied to Groovy) that’s in the process of being shut down as well. It does not use the new SmartThings API. You can either check the REST API directly or some people find a tool like the API Browser by TAustin to be helpful for this.
Based on what you described, it sounds like it’s a Custom Groovy DTH. That itself isn’t a problem – the problem is that Groovy DTHs could define custom attributes without defining them as part of a capability. In the post-Groovy world, SmartThings requires that attributes are defined as part of a capability and the new SmartThings APIs will not expose legacy custom attributes that weren’t part of custom capability.
The distinction is really critical. SmartThings is in the process of shutting down their Groovy platform and their new APIs fundamentally won’t show these legacy custom attributes (which makes sense since they’re in the process of completely shutting down Groovy). If you had joined SharpTools ~6 months ago, we were still using a Groovy SmartApp at that point in time and our Groovy SmartApp had access to all the Groovy stuff (including Custom Attributes that weren’t defined as part of a Custom Capability). But the new SmartThings APIs fundamentally don’t share this data.
In other words, there’s no going backwards. Only forwards. Either the Groovy DTH would have to be updated to implement a Custom Capability (kind of silly with Groovy being shut down soon) or you would need to migrate to a new driver like Mariano’s “Mc” drivers.
I understand that you’re in a bit of a limbo state at the moment as those Groovy devices haven’t automatically been migrated yet even though the Groovy SmartApps you used are already deprecated, but that’s the reality of the current state of SmartThings.
Sounds good, I’ll wait and hopefully my devices migrate to a stock Z-Wave edge driver.
I’ve installed the Z-Wave Switch and Child Mc driver in readiness.
I may actually comment out the fingerprint in the DTH then exclude and include a single Fibaro Dimmer (there is 1 particular switch in my house which uses scenes on a daily basis so if this was on Edge Drivers now that would help). Do you have any guidance / instructions on doing so ?
Thanks for your help.
Thanks for the explanation, I didn’t realise the IDE was disappearing too.
I really am stuck in limbo because WebCore has stopped working (by surprise as I haven’t been keeping an eye on the forums) so I’m in the process of migrating all my logic to SharpTools. Currently I’m missing some functionality which I’m not likely to get until my devices are on Edge Drivers by the sounds of it.
If I understand correctly; To get that functionality now means I have to manually exclude and include all devices (not something I’m in a rush to do), or if I’m prepared to wait (in limbo) then hopefully the devices will transition from my custom handlers to standard Edge Drivers automatically at which point I can revise the Edge Drivers to beta / custom drivers as required (without needing to exclude & include).
However, if I go to the effort of re-coding all of my logic in SharpTools now and auto migration doesn’t work for some devices then I’m back to square-1 (physically moving, excluding & including those devices and re-doing the SharpTools logic).
SmartThings sure haven’t made it easy for people. They should have made the drive migration more seamless and allowed WebCore to operate until users have logic implemented on an alternative platform.
In this post and following of the thread can see as implemented and tested by another user.
Once the sending of scenes is activated in settings device, Basically the routines are made as if they were the push of a button. Button two of the device details view corresponds to the scenes sent by S2
Button2 = I press 1 time
Execute xxxx actions
And so for pressed 2 times, 3 times, maintained