Sengled Dimmer Switch
SmartThings stock Edge driver
This driver expose remote as a dimmer switch, not as a button device, even that it is a button remote. Those buttons are not visible in ABC. It has On, Level Up, Level Down, and Off buttons. If you could add Those Dimmer Switch functions, that would be great.
Ikea Remote Dimmer
SmartThings stock Edge driver
Zooz Double Switch Dimmer
Edge driver created by @krlaframboise. You would need his invite to his channel
have you found any solution to new edge driver switches not showing up by name when you try to add automation to them? i readded three ikea switches and one dimmer and i have a lot of “Button 1, button 2” etc now in the list.
i noticed i can change the names of the buttons in the ide but im worried it would break something.
EDIT:
I tried renaming the child buttons for one dimmer and it worked when i used webcore to program a certain action (+15 level). But, ABC doesnt. When i choose the renamed button i get a new button menu where i have to choose which button within the button (1-40). It would seem that ABC isnt recoqnizing that its just ONE button and thinks of it as a switch with multiple buttons.
an option to catch “all button presses” within a device could do the trick (as wecbore does)
Are you doing something that could be accomplished with Routines or Rules instead?
You’ve taken the effort to put your device on an Edge driver, which gives you local processing and futureproofing. Now you’re setting up automations with a Groovy smartapp, which means you’re back to cloud processing and the threat of the Groovy end of life.
Ah. Yeah, an incremental level adjustment definitely isn’t currently available in routines unless the driver for the device you’re dimming has that as a custom function that can be called.
It might be possible in rules - @nayelyz posted an example showing mirroring between two devices which is a similar level of complexity. I haven’t started messing around with rules yet to know for sure what’s possible though.
Hey guys, sorry to bother you, but I’ve been fighting this odd behavior for days now. I’m using HS-WD100+, HS-WD200+, as well as an odd HS-WS100+. All were working fine with a v2 hub, and ABC leveraging muti-tap controls. Now I started losing 1 of my WD and ended up replacing my hub to the Aeotec and starting over. However, can’t seem to figure out how to get passed the change of 8 to 1 button (with behavior or something). I can force the ST app on my iphone to “show” 8 buttons, but they all say the same thing, which is the last I picked. When I go in it has the right name though it’s missing the picture… and ultimately, whatever I configure to do it doesn’t… Anyone know what I’m doing wrong???
With the recent updates in ST and updates to Homeseer device handlers, I don’t need the ABC smartapp anymore. I can do it all with the standard automations (routines)–even changing the LEDs on the 200/300 series switches.
Hi Brent, thank for using the app, good luck with automation. I’m just pausing the development to see what Smart Things provides so I can redevelop ABC to fit in the new regime.
Is it possible to add a push notification and/or an SMS text via ABC? I am looking but don’t see the options. The old samsung button controller app has those options, but that app won’t work for me any longer. I installed ABC, but don’t see those options and figured I would ask.
Hoping to get some help. I used to use ABC Manager a while back (2-3 years or so) when SmartThings Classic was still working as it should and before the new version came out… I had moved and pulled all my HomeSeer WD100+ dimmers and they’ve been sitting in a box this whole time. Fast-forward this week, I’ve installed all of them back at a new residence and hooked-up SmartThings and set everything up on the new version, but ABC Manager does not work. It says that there are no devices to be selected, though I have like 7-8 Homeseer dimmers around the house and all of them work with SmartThings for On/Off/Dim functions, but I am looking to get the Double and Triple tap actions back.
I’ve updated the code for the ABC Manager and ABC Child Creator, only published the Manager, not the Child Creator, but the same still applies. I am not able to assign any functions to any of the existing dimmers that I have.
I’m also using the Darwin one, but the latest version (which is 1.08). I would suggest updating (if you haven’t already) to the latest DTH and also confirm in the device that it is using that DTH (not sure if you excluded and reincluded when you took them out and reinstalled them).
Mine does NOT look like that… The below is what I did:
https://account.smartthings.com/
Removed the switch from ST by unpairing it (was not able to reset the switch with triple tap up and down)
Removed the old DH for the WD100 dimmer
Readded the DH for the WD100 dimmer from smartthingscode/wd100dimmer.groovy at master · mwav3/smartthingscode · GitHub, and published it
Re-praired the WD100 dimmer in ST
Added the ABC app and published it
Added the ABC child creator app, but did not publish it
Went to Automation > scrolled down to ABC and tried to add a device to it, but says No devices found
I finally figured it out!!!
I had to go to EDIT the device via IDE for the WD100 dimmers and change from Zwave Generic Dimmer and select the DH from Darwin for the WD100.
Now Smart Lighting and ABC is able to pick up the dimmer as it should with the extra functions.
Note that for the future, different accounts are on different cloud “shards,” so have different URLs. But if you go to the wrong URL, you’ll be able to sign in, but might damage your account.
So…to protect everyone, when posting a signin URL to the forum, even if you’re just documenting what you did, please write the universal sign on:
