Respectfully, every single device discussed so far in this thread is also on that FAQ list. Plus at least a dozen more. I understand your frustration in not being able to find the perfect button, but the community has worked pretty hard to keep that list up-to-date and comprehensive. So I’m not sure what you were expecting, but we can’t list devices that don’t exist.
Yep this will work! Although I’ve seen quite a few people now comment on it’s appearance. I’ll see how one looks when it comes in. It doesn’t look so bad in the photos… but I live in a fixer upper soooo maybe any switch looks good
Here’s an update on ST button-testing extravaganza:
Iris button: cancelled the order after the wave of “yea this is crap” came in (TY ST community)
Lutron remote switch: As @JDRoberts said it would, not ST Compatible without it’s own ($189) bridge. Nope. Still a little bitter about the misleading product desc, but I should’ve researched more before buying.
Aeon Wallmote: Ding ding, we have a winner for a mere 3x the price of the former 2. This thing is pretty cool. Slick looking, and it never occurred to me that it’d be beneficial to have a switch that guests can pop off the wall and set on the nightstand to turn off bedroom lamps at bedtime (especially since it’s important that I discourage them from using the lamp’s own switches, which render the remote button solution useless).
Sylvania - That comes in tomorrow. I have another room with no light switch (yea… this is a scalable problem!) to try it in.
That’s the fun part. The before and after. Keep documenting your progress. One new shiny light switch at a time.
That got me thinking. How about putting an Echo Dot (cost containment) in each room and leaving everything very simplistic for now? Anyone that walks into any bedroom, “Alexa, turn the lights on/off”. Whallah, no additional trials and tribulations with switches slapped on the wall or just as an addition to compliment and voice automated without the need for any physical buttons to touch.
LOL and don’t neglect the carpet or the garage doors for too long.
Just so you know, the “Lutron connected bulb remote” (LCBR) actually doesn’t work with the Lutron SmartBridge. It’s a completely separate device on a completely different protocol, only intended for control of smart bulbs, not for any of the other Lutron devices. It’s the Lutron Picos that require the bridge.
As it happens, the protocol the LCBR is using, zigbee, May be able to connect to A SmartThings hub, it’s just that it’s not really easy and a lot of people report it won’t stay connected. So personally, I would recommend just returning it, but if you do want to play around with it a little more, see the following thread. ( assuming you actually bought an LCBR and not a pico.) But be prepared for a lot of very technical discussion and a lot of “it worked for me.” “It didn’t work for me” conversation going back-and-forth.
The wallmote is a really elegant device. Lots of reviews that the battery life is terrible, though, maybe 3 to 4 weeks, so it would be a good idea to test it each time before your guests arrive. But personally I think that’s less of an issue for a guest-room that it is for everyday use since you can just charge it up for each visit.
A little more complicated, but you get four button options instead of two.
There is a community – created device type handler which will let you use the long hold on both the top and bottom button, so you get four choices instead of two.
A super fast option with dimming but will only work with a few specific lightbulbs.
OK, pay close attention, because this part is important to avoid getting frustrated. Option one and two above will allow you to use the Sylvania switch to control anything that SmartThings controls. You could use the buttons to run a routine that arms smarthome monitor, you could use them to turn on A zwave pocket socket or a Wi-Fi bulb, again, anything that smartthings can control. That’s because for option one and two the Sylvania device will send a message to the hub and then the Hub will use that based on the automations you set up.
One community member was frustrated because the Sylvania device was designed for use with their gateway and in that scenario it could also do dimming. And he really wanted dimming.
So he wrote a device type handler which will allow the device to be used on a SmartThings network in the same way as it was originally designed. But, it will only work with ZIgbee bulbs. You won’t be able to use it to run a routine or control a device of a different protocol or control devices further away than one hop. It will communicate to nearby zigbee devices directly, which is why it is so fast. But you are going to be very limited in the devices that it can work with. And the set up is much more complicated than for the other two options because you’re going to have to go in and actually find the network IDs of the bulbs that you want to control. But when you’re all done, you will have dimming from the device.
So there you have it. Three different options for setup of the Sylvania dimming Switch which will give you three different types of feature control when you are done.
For most people, just using the official DTH, option one above, will be fine. They’ll end up with a two button device that will work with the official smartlighting feature, routines, and webcore. It will be fast to setup and intuitive if you just want on and off, and it’s a nice option for some things like setting SHM to armed and disarming it.
If you want to get a little fancier, use option two, and now the long hold will also work. Some people use that to create a 50% dim setting, for example.
If you want the full functionality of the device, you can get it by using option three, but then you’ll be limited to what it can control, specifically other zigbee devices that are nearby. And setup is much more complicated.
All three of these are good options, but different ones will work for different use cases.
Understood, thank you for sharing. To power-users of the ST community forums, I see how it could be distinguishable as an organized list. For those who are not as familiar with the forum setup, it does not look like a list and is difficult to disseminate info from due to its volume. I recognize the hard work that’s gone into keeping it up, and I went back and read the whole thing now that I’m getting more familiar with the forum structure and how the posting/conversation goes. I’m sure as a regular user it can be frustrating to see redundant posts/questions. From the perspective of a newbie trying to learn, it’s nearly impossible to avoid accidental redundancy. We are lucky to have patient, knowledgeable experts willing to sometimes repeat yourselves in the community, otherwise I’d be literally buried in buttons. Thank you for your time repeating info for me. I will continue to invest time researching before posting new questions.
Already had the battery die 48 hours into install, BUT the wallmote arrived at 59% charged and I messed with it quite a bit in the beginning (as did my visiting mother, apparently giddy with light-up button fascination). So remains to be seen, but initial thought is that yep it dies fast. 59% to 0 in 2 days is not good even with messing with it. I turned off all button feedback except for the light-up (turned off vibration) to hopefully improve battery.
Unfortunately, because I rely on text to speech, I can’t contribute to tables in the community – created wiki.
There are other members who have been working on a table format of the buttons list, but while it has been started, it is missing a lot of the items that are in the forum thread and it doesn’t have pictures yet.
I would like to see a lot more tables of this type in the wiki, so hopefully in the future.
For its first generation, Iris used a proprietary version of zigbee which is not compatible with SmartThings. Only the second generation those zigbee devices, the ones which are certified to the “zigbee home automation” standard (ZHA) will work with SmartThings.