EcoSmart Zigbee Remote

[milandjurovic71 (Milan)]

@SamsungZell and @nayelyz

Marking this post as solved does not solve the problem

Sorry for not responding in timely manner, as I was busy with my work.
Here is the issue that is happening all over, and it can be found in a lot treads.
Many button devices (remotes, switches with button capabilities) are showing more capabilities than they have.

My examples are

1. EcoSmart remote with only Pressed capability, shows Pressed, Double Pressed, and Held capabilities.
   It should be like this
   
   

But now with all added capabilities looks like this

Assigning Actions on device details pages is not working correctly, as I stated. When I assign action to the 1st Button’s Pressed capability, it does save it correctly

When I try to assign Actions on device’s details page to other buttons (2, 3, and 4), it shows them under button #1 in other button’s capabilities.

It is the same behavior described in another @Trakker2 users post

@Hendo25

@Trakker2
I have tested this DH a bit more, and I’ve noticed a problem with storing Actions on the device page on the Smarthings app.

When adding actions for each button (pressed, 2x, held), the actions do successfully get registered in Smartthings, and they appear on the Automations tab. (And they work!)

However - only the actions for button 1 show within the device controls. I can add an action to any other button, it stores correctly on the Automations tab, but on the device controls it says “No actions assigned”.

If I do add an action for another button, that action replaces the action assigned to button 1 in the device controls presentation - even though it doesn’t actually replace the Automation (which works successfully).

I hope this all makes sense.

Have you seen this before, and any guidance how it can be fixed?

Thanks

2. Now when I checked another brand remote it that has 4 buttons with only Pressed and Held Capabilities, that one shows more then dozen (19) capabilities for each button.
   
   

@SamsungZell You are telling me to remove and re-add devices (which I have more than a dozen), and to loose all Automations doing that. I have removed only one , and added back, and added more, but they all behave the same.
3. I have looked at another Zooz Switch Scene Controller with 4 buttons, and they all have same problem, added all possible button 19 capabilities, as shown bellow, for just one button

Post from another tread by @blueyetisoftware list same problem

[RELEASE] Zooz Scene Controller (ZEN32)

Thanks for the note on the log statement. I saw that earlier in the thread. Yes, I am talking about the child devices. Going through the “Automations” tab, these options are not displayed. They are only displayed when clicking on the device in the “Devices” tab and then viewing the “Controls” tab. This shows the state and configuration for each trigger. [Screenshot_20211115-104933_SmartThings]

Only thing that comes to my mind that I might have this problem is that as I am testing Edge drivers, that I have driver with button capabilities loaded on my hub, that creates conflict with all other DTH Groovy devices.
Otherwise Smartthings have this problem all over, and it needs to fix this asap.

How many more users need to post about the exactly same problem, to be looked at?

[Mariano_Colmenarejo]

It seems the same problem that the fibaro KeyFob has with the stock beta driver edge zwave button

[ST Edge] Issues with the driver "Z-Wave Button"

@nayelyz, I have tried the Beta Driver stock Z-wave Button with a Fibaro KeyFob and it works, but the detail view is very very bad. The KeyFob has: 6 Buttons and each Button has actions: Pressed Pressed 2 times Pressed 3 times Held Pressed Pressed down Battery What it shows in the details view: Shows the messy buttons and there are 6 buttons + a main button, which matches in actions with button 1. Each button shows: Pressed 1 to 6 times and only works until pressed 3 times. Pressed up 1 to 6 times Pressed down 1 to 6 times Missing Held Pressed on each button The battery information comes after the Main button instead of at the end. The order of the buttons is shown in details, and Routines: Button 1, Main, Battery, 6, 2, 3, 4, 5 A screenshot with a part of the detaills view…

[milandjurovic71 (Milan)]

@nayelyz @SamsungZell
Looks like the latest app update fixed the issue with multiple capabilities showing for button devices:

Also button’s actions are working correctly now.
They are showing at assigned button.

@nayelyz
Only me being picky, I would ask that current edge driver for zigbee remotes, to be updated to have buttons and battery in correct order, battery should be always on the bottom, as we talked some time ago.

It is possible as edge driver for Hue Remote, created by one of the devs, has everything in right order:

If Samsung developer needs to look at the code, here is the link to the Hue driver, where there is a link to the GitHub

[BETA][Edge Driver] Hue Dimmer Switch / Hue Wall Switch Module (No Hue Bridge)

I made a Edge Driver for “Hue Dimmer Switch” [b95c17641bc945adb714a9b900a25f2f.jpeg] This is a simplified port of my previous DTH. [BETA] Hue Dimmer Switch DTH (No Hue bridge) rewritten - Devices & Integrations / Community Created Device Types - SmartThings Community You can install the driver to your SmartThings Hub with the Invitation link that I’ve created. https://bestow-regional.api.smartthings.com/invite/qWjB0pNyY62y Click Invitation Link → Enroll your ST hub → Goto Available Drivers → Install Hue Dimmer Switch driver → Pair your device Also, I uploaded the source code of the Edge Driver to my github, for anyone who are interested. Edge Driver is still in Beta. It could be unstable, especially with health check. This device don’t send periodic heartbeat packet, so it cou…

[Mariano_Colmenarejo]

@Mariano_Colmenarejo

It seems the same problem that the fibaro KeyFob has with the stock beta driver edge zwave button

@nayelyz, I have tried the Beta Driver stock Z-wave Button with a Fibaro KeyFob and it works, but the detail view is very very bad. The KeyFob has: 6 Buttons and each Button has actions: Pressed Pressed 2 times Pressed 3 times Held Pressed Pressed down Battery What it shows in the details view: Shows the messy buttons and there are 6 buttons + a main button, which matches in actions with button 1. Each button shows: Pressed 1 to 6 times and only works until pressed 3 times. Pressed up 1 to 6 times Pressed down 1 to 6 times Missing Held Pressed on each button The battery information comes after the Main button instead of at the end. The order of the buttons is shown in details, and Routines: Button 1, Main, Battery, 6, 2, 3, 4, 5 A screenshot with a part of the detaills view…

My fibaro keyfob button still shows 22 actions for each of the 6 buttons instead of 5 for each of the 6 buttons

[milandjurovic71 (Milan)]

@Mariano_Colmenarejo Did you update the app to the latest version?

[Mariano_Colmenarejo]

@milandjurovic71

Did you update the app to the latest version?

Yes, updated yerterday.
Driver Change performed and memory cache cleared

[Paul_Oliver (PCO)]

The new app update had eliminated the long list of unusable button options for me.

[jamclam (Larry)]

Bumping this old thread…
I had been using the DTH for my ecosmart remote, which was showing as cloud executed.
I tried switching the driver to ‘Zigbee Button’ so that it would execute locally.
This “sort of worked”; the device still shows as having four buttons, but I can only get the first one to work. Pressing buttons 2-4 seems to have no effect.
Did this happen to anyone else?
(I’d also like to try the edge driver, but I’m not sure it’s enabled yet; see Hub Connected Devices Now Use Edge Drivers - #89 by jamclam)

[Terri_Baker (TeBa)]

@jamclam

like to try the edge driver

I’ve been using this edge driver with the ecosmart remotes for a while now and it works great. It doesn’t support the group binding that this driver was developed to support but all the buttons work.

[lmullineux]

@Terri_Baker as the group functionality doesn’t work for you, you may as well use the official Samsung ZigBee button edge driver that my driver is based upon

[Terri_Baker (TeBa)]

@lmullineux

you may as well use the official Samsung ZigBee button edge driver

I couldn’t ever get it to work correctly.

I’m still playing with group options in your driver, just haven’t had time recently

[lmullineux]

I’m not sure they work for your remote, I don’t have one to test myself, and another user reported they don’t work

[blkwll (James)]

Figured I’d put this here…

So, I’ve been playing catch-up, realizing my Ecosmart remotes will soon need an alternative to webcore.

So, for now, I just took out the device specific (fingerprint) info from the custom DTH I’ve been using, so I can still use that handler without Smartthings defaulting to it upon pairing. This allowed me to have the Edge driver option for testing one remote while keeping my existing remotes on the custom DTH, for now. Maybe no one else would have that problem, anyway, but…

I know the official Edge Zigbee button driver has the Ecosmart remote fingerprint and that is apparently the only that does, but being that buttons 2 and 3 support “held”, I’m curious how they may be made workable with the Edge driver.

I’ve not got to the point of understanding how to use/edit custom edge drivers, but am working on it.

[ronczap (Yorkies Rule!)]

WOW! Thanks @milandjurovic71
I got the EcoSmart 4 button remote to work.

I deleted the device from the app
I clicked the large “+” and selected “Add a device”
I chose “Select from list of devices” and selected “SmartThings”
Then I selected Remote/Button
It showed a screen the single SmartThings button and I clicked “Start”
I used a straight pin to push the reset pin thru the hole in the battery cover

It added the device defaulting the name to EcoSmart Remote Control.
I clicked the device tile/icon to get to the settings:
There are five groups - Main, Button1, Button2, Button3, Button4
I did not assign any action to Main
I set up the other four actions and backed out of the setup.

They all work perfectly!!
I did the same with my other remote as well.

The “Driver” screen shows it as Zigbee Button with SmartThings as the developer.
The Groovy IDE shows the Type as placeholder like the Edge driver devices.

[Sddabrow1 (Shane)]

I love these remotes. I have 5 of them, got them for like $4 a piece + bulb, unreal deal back in the day. Hope nothing changes with their functionality with the groovy changes.

[Leitmotif7]

Sorry to revive this, but I cannot pair neither the bulb nor the remote to my hub to save my life.
I unpaired the two using EcoSmart method. The bulb now flashes RGB 3 times when it’s turned on, and then goes into solid white. I tried flicking the switch off and on 6 times (1 sec interval), same behavior. The remote, I am holding next to my hub, pressing the button, it flashes red for a few seconds, then stays solid red for a few more seconds, and then the light stops.

I tried using both “Search Nearby” options and Third Party partner, EcoBee.

Any ideas, or am I just missing something?

Thanks!

[surils]

These are EcoSmart and not EcoBee. I have the Zigbee Button Groups driver installed from Lrmulli.

Zigbee Button + Groups - Alpha Test - Devices & Integrations / Community Created Device Types - SmartThings Community

[Leitmotif7]

I definitely meant EcoSmart, not sure why I typed Ecobee. Long day. I’ll try those and see what happens.

Thanks.

[epukane (Toni)]

Did you get it working?

Mine are just using the stock Zigbee Button driver for the remote and stock Zigbee Switch driver for the bulb.

[Leitmotif7]

Did not. I could not get either device to show up when I searched for them in Smartthings app.