Yeeeeeeep, this very reason is why support for the button is limited to the v2 and v3 hubs.
1 Like
Will we ever have options to define our own groups and bindings? These remotes, like the aforementioned IKEA ones, could be beneficial for bulbs to do direct dimming without the cloudās interaction. 
(I have read that some grouped directly with some Xiaomi plugsā¦)
So, couple things to point out off the bat and the main one being that the groups these remotes are part of is hard coded and we can not change it (it may be changeable, but at least not in a standard way) so it wouldnāt be possible to have 2 different remotes control 2 different groups. However, we recently added device groups to the new mobile app, which is backed by protocol level device groups. This means if you create a device group of Zigbee devices there will be a Zigbee level group created that the devices are bound to. Iād have to go back and look at how much of the group stuff is cloud driven vs local but anywhoooo
1 Like
Thatās sounds really promising! I will try to play around with that when I will get home and have some time to tickle. But that would be awesome to use the dimmer functionality from a button (which supports it by design) directly with other zigbee bulbs. Nice! Does this option applies to motion sensors too?
I donāt want to hijack this thread more, but nice to know these new things.
(By the way, as you nailed down this remote, the next should be this one https://www.ikea.com/se/sv/p/tradfri-genvaegsknapp-vit-40356381/ )
Thanks for all the info @broderickcarlin! 
So i wanted to make a contribution to this thread to help out since everyone has been awesome throughout this endeavor. Here is the piston i built in WebCore today. This is the first piston i ever made so iām sure someone can make it better. This makes functionality pretty similar to original with a few exceptions. Button 1 is power on/off. Button 2 is a 3 stage dimmer, like a 3 way bulb. Easily adjusted in the code if you need more steps but lo/med/high was good enough for me. Button 3 cycles color temp, again 3 steps. Soft white (2700k), Bright white (4000k), and daylight (6500k). Button 4 is a favorite setting. For me itās 25% brightness and 2700k. You can change to whatever you want. I used a variable for the bulbs themselves so you should only have to add your group of bulbs once. You will have to adjust remotes though as i couldnāt get that to work with a variable. This is configured for 2 remotes but you could use as many as you want. Hope this helps most get a headstart at least.
9 Likes
I switched over to the official DTH release tonight, I have to change them to some other DTH to delete the old one. When it came time to change the DTH to the official release, it wonāt let me. It says the change was successful but then it still shows whatever the previous DTH was and wont met me change it. I tried adding the pre-release version of the DTH again but that didnāt work either, now im stuck with a bunch of remotes Iāve already has set up that dont work because I cant select the DTH.
Any ideas whats going wrong?
So, if not available in the mobile app, where is it available?
Thatās all it takes. The remote will join as a device, allowing you to set all 4 buttons for whatever you want.
1 Like
EDIT: Just discovered theyāre under sensors, not actuators. Thanks again for this!
This is amazing, thank you so much! One quick question: Iāve imported this and I think Iāve got it all set up, but Iām unable to see each individual button as a separate device in webCoRE, just the whole remote. This is my first time ever using webCoRE, so Iām probably missing something, but if Iām understanding correctly, each button should show as a separate device, right? E.g. Keypad 2, Keypad 7, etc. in your code. Would you mind sharing how to get each button in as a possible trigger?
I had the same experience and ended up deleting and re-pairing each remote. The process is not as complicated as some have said. Just stick a pin in the reset until it blinks quickly and add it. They can take up to 30 seconds to show up when the hub is scanning but Iāve added them from a couple rooms away from my hub with no issues.
Weird, I see the new handler under the IDE, but when I try to update it from the self-published IDE it doesnāt update. Says it updates, but it doesnt change the device type.
The device type wonāt visibly change since the one you self published is the same type as the official one 
I edited the code so the name was differentā¦ It still shows the different name I applied and it wonāt let me delete the self-published DTH, because it says it is still in use.
May have to just delete all the remotes and re-add?
shoot me a PM with the email address associated with your account and Iāll take a look for you
3 Likes
Awesome support, thanks for getting me all squared away! This is why I love the ST community
2 Likes
Newbie Q. I have an ADT hub, I know there are differences with this and the V2 and V3, so am I in the same boat as a V1? Will these remotes work at all or just at a limited capacity? If they will as ābuttonsā, does it mean that it can still turn on and off other devices/non-ecosmart bulbs? Just no long presses like for dimming? Then I just do the dimming/color temp thru the app right? If I want to group multiple Ecos bulbs, can I control all of them with the same Ecos remote or remotes? Or Im stuck with TouchLink which will be for a bulb only and not for the group?
Thanks
Iām having the same problem. I even changed the DTH to something completely different, was able to delete the manually added one, but canāt get it to switch to the official one.
Yeah, the answer was an issue with child devices. Best just to delete all the remotes, then delete the self-published DTH. Then re-add the remotes and it will automatically find the new ST published DTH.
They are working on a fix for our issue, but might be a week or two. By deleting it an d re-adding, this manually solves the problem.
1 Like
Another huge shoutout to @Druknmonkey for providing a framework for recreating the functionality of these remotes. I tweaked it just a little, specifically I made variables for the buttons. Since I have like 10 of these remotes, this made it a little easier for me to duplicate the piston for various rooms so all you hafta do now is update the bulbs and buttons at the top.
Thanks again for everyoneās help in this thread!
8 Likes
@Reno.nv You are correct. If you add remote to hub, it will function as any other 4-button remote. You ca assign any action to those buttons, and turn on/off any device. But that way you can control same lightbulbs that came with, but with no dimming or Temperature changes. Or if you are using ABC you can assign even those.
You canāt use it as TouchLink remote anymore!!!
If you are using remote as TouchLink only you can still control those same bulbs as factory intended, on/off, dimming, temp, and memory, but you canāt use it with hub to assign any actions, and control other devices.
2 Likes