I have a Sylvania 74099 4 button switch (does push, hold and released ) which has been "pretty" reliable. Only issue the wife has is it's easy to hold the button too long and get a HOLD instead of PUSH. I guess I could probably handle that in HE....never thought about it.
1 Like
That's the one. Danke.
I second the AduroSmart ERIA device. I have three of them and while they were a bit tricky at first, they have been rock solid. I use two of them in the living room to control the lights on a ceiling fan and one in the master bedroom to do likewise.
One of the ones in the living room is the master and the other is set up to do a virtual button push on the first one. Logically, it seemed similar to setting up a three-way switch, but no wires are needed. The down side is that battery levels are not reported, but that does not seem to be much of an issue. I've had them nearly a year and the batteries seem to be holding up well.
I tried the Sylvania Lightify 74099 buttons but they were giving me trouble so they got returned and I purchased the ERIA ones instead.
What's the type this AduroSmart ERIA on He ? It can directly connect to HE hub or need a PRO bridge like a pico remote ?
Direct connection, no bridge required.
1 Like
If you're near a home depot, you can get the ecosmart 4 button remote. They're on clearance at certain HD stores for 2.88 now, bulb & 4 button remote. Use brickseek to locate stock
https://brickseek.com/home-depot-inventory-checker/?sku=310288335
I'm using mine on ST via hubconnect
1 Like
I think these are a pretty good alternative to Picos. They mount in a similar way, they fit into a normal Decora plate. They have native drivers in Hubitat.
1 Like
Thanks everyone. I will check out all the suggestions.
Phillips Hue dimmers work well connected directly to Hubitat.
I also had Remotec ZRC-90 zwave remotes and got rid of them when I went totally Zigbee.
2 Likes
I'm not a huge fan of the Eria mentioned above. I guess if you're controlling four separate devices and only using "pushed," it's not bad and isn't too expensive. Trying to use it instead of a Pico or similar to control one light including "held" and "released" events is not my favorite, though--the "held" event takes forever to register. It also doesn't ever "check in" unless you press buttons, so Device Watchdog and the like are not useful here, and there is no battery reporting, so when it dies, you might not know why (or if it did--there's also this thing where it takes a few seconds to register a press if it hasn't been used in a while for some people, possibly related to what repeaters you have). Gluing 4 ST buttons together would not be that crazy of a suggestion in comparison, if you ask me. 
That being said, it looks like you might be headed down the Pico route instead--a great idea if you already have Lutron. The (real) 4-button Picos tend to be a bit more expensive for whatever reason, but I have one controlling four different things and printed custom P-Touch labels so I know what's what. No complaints on that. Just wanted to give you my experience otherwise!
1 Like
Yeah...need to find a good source, but I plan to purchase the 4 button pico. I had my Remotec installed with pictures of what each button controlled. The pushed/held/doubleTap did different things for each device/group. Really wish there was a zigbee equivalent because I love this remote.
Another mention for the Hue button "switch" as they call them. Zigbee buttons.
I don't hate mine. I have 2 and are pretty good I guess. My kids love to take them off the wall and lose them though.
Despite my better judgement and your recommendation, I decided to try the Eria since they were relatively cheap. Looks like I'll end up going with the 4 button pico like I should have from the beginning. I never liked the Hue/Eria form factor, it feels a bit cheap (each button has a different tactile experience) and it consistently falls asleep after not being used for 30 minutes. Not happy with it at all.
I don't think I even noticed the feel of the buttons as being different, but I can add that to the list of things I don't like about them. I can't recommend Picos enough. Here's a 4-button one (on the right) I re-labeled to make some sense to me:
(in order, Hue's "Relax" scene for that room--their standard icon for that, one that turns the window fan on overnight, one that turns on the tower fan on a timer, and another that toggles computer peripherals on/off). The left is the typical 5-button one that I have controlling lights for that room. None are real switches so I probably didn't need to use the faceplate, but I though it looked better with one. The only problem I've had is that sometimes there's a delay with the first press after a hub reboot, something I haven't quite caught onto the cause of yet.
2 Likes
This is normal from my experience with Hubitat + Lutron. I would not worry about it. Hopefully you're not having to reboot your hub too often.
How is this for you? How many gang did you get and can you single, double tap and hold each of the gangs? How's the response? Also, where's the community driver pls?
I just ordered one at AliExpress and want to make sure it works well before paying.
Thanks
I have the 2 gang and single, double and hold all work. Hold does take 5 seconds other respond straight away. There are also leds under the buttons so you know when you have touched the button.
I've never had an issue with it so still recommend.
Driver is here
what kind of battery is that? CR1632?
I had the same problem for the longest time. Actually, mine was worse. No picos would work at all after a system reboot. I had to put a rule in place that on system startup run Initialize on the Lutron Telnet device about a minute after startup ran. Since I did that, every button press on the Picos responds immediately.
How did you get your labels to stay stuck? I did the same thing with my label maker but after using the Pico for about a month the labels are either falling off or are totally illegible. What's your secret? Maybe I just have a cheap label maker. 
I tried that for a while but not sure I waited a full minute, so trying too fast could have been part of my problem. In another thread, I think staff and a couple other users narrowed this down: button-oriented apps behave better if their initialize() method (so app, not device--though both probably matter) is run after a hub reboot (if you care about this delay), otherwise it takes a few extra seconds. Stephan added a this in a recent version of Advanced Button Controller, and I plan to add an option in a future release of a button-related app I have. They might do something at the platform level to address this in the future, but it was unclear to me. I think it's less noticeable in other apps: who'd notice if the mode takes an extra couple seconds to change, and if you have motion-lighting apps, many might be time-restricted and have already woken up when you don't care and then work perfectly fast when you do. (Guessing as to why this might be most noticeable for button-oriented apps.)
I'm not sure I have any secrets (I wish I knew how to get them on straight enough the first time--I usually print two just in case, easy since there's lots of extra room on most labels)...but FWIW, it was a Brother P-Touch labeler with, I think, first-party TZe (P-Touch) tape. 
