Issues with AduroSmart ERIA wireless dimmer


#41

Good Morning Everyone,
We would like to give a thank you to the community with a special shout out to @uberrob for creating this thread and @cgmckeever for his solution of modifying the handler. Here are the changes we suggest making to the Handler to address this issue:

private Map parseAduroSmartButtonMessage(Map descMap){

def buttonState = "pushed"

def buttonNumber = 0

if (descMap.clusterInt == zigbee.ONOFF_CLUSTER) {

if (descMap.command == "01") {

buttonNumber = 1

} else if (descMap.command == "00") {

buttonNumber = 4

}

} else if (descMap.clusterInt == ADUROSMART_SPECIFIC_CLUSTER) {

def list2 = descMap.data

buttonNumber = (list2[1] as int) + 1

}

if (buttonNumber != 0) {

def childevent = createEvent(name: "button", value: "pushed", data: [buttonNumber: 1], isStateChange: true)

sendEventToChild(buttonNumber, childevent)

def descriptionText = "$device.displayName button $buttonNumber was $buttonState"

return createEvent(name: "button", value: buttonState, data: [buttonNumber: buttonNumber], descriptionText: descriptionText, isStateChange: true)

} else {

return [:]

}

}


#42

Also while we have attention on this thread from such knowledgeable users, we are going to run a new production and update the handler, are there any requirements or recommendations you would suggest for this product?


#43

@AduroSmartSupport - thank you for the promptness and attention you paid to this issue. As @WCmore said earlier, we’re all impressed by your professionalism. Other OEMs should take the lead from this.

The physicality of your switches are top notch, so I would not change the product design at all – if I were to ask you to consider anything, it would be to make sure that the drivers for your other switches (the ones with additional buttons) are also altered to make the same changes.

Additionally, could you work closely with Samsung Smartthings to have your DH as part of the ST installed drivers? I know that’s a harder ask, but it would be great.


#44

@AduroSmartSupport THANK YOU!!!

I think that Handler will still be error prone.
You took out the if (descMap.clusterInt == zigbee.LEVEL_CONTROL_CLUSTER) … which wasnt triggering anyway (I left it in with a debuug logger)

descMap.clusterInt == ADUROSMART_SPECIFIC_CLUSTER will still trigger multiple for devices 1 and 4 (Im fairly certain)

private Map parseAduroSmartButtonMessage(Map descMap){

def buttonState = “pushed”

def buttonNumber = 0

if (descMap.clusterInt == zigbee.ONOFF_CLUSTER) {

if (descMap.command == “01”) {

buttonNumber = 1

} else if (descMap.command == “00”) {

buttonNumber = 4

}

} else if (descMap.clusterInt == ADUROSMART_SPECIFIC_CLUSTER) {

def list2 = descMap.data

buttonNumber = (list2[1] as int) + 1

}

if (buttonNumber != 0) {

def childevent = createEvent(name: “button”, value: “pushed”, data: [buttonNumber: 1], isStateChange: true)

sendEventToChild(buttonNumber, childevent)

def descriptionText = “$device.displayName button $buttonNumber was $buttonState”

return createEvent(name: “button”, value: buttonState, data: [buttonNumber: buttonNumber], descriptionText: descriptionText, isStateChange: true)

} else {

return [:]

}

}


#45

@AduroSmartSupport for recommendations …

  • The battery level code doesnt seem to work (check this discussion)

  • The #2 key seems to have some wiggle and does start to feel ‘broken’, but when compared to a new switch, they are about the same

  • Id put the mounting lip on the switch plate versus the controller so the controller can lay flat

  • designer colors (Im not super interested, but came up on Amazon)

  • one last thing, I would love it if this switch could mount directly over a ROCKER type switch. Maybe if it came with two mounts. Ive made one out of a rocker cover. That form factor/design would be my dream


#46

Careful what you ask for… :grin:


#47

I installed the CGM handler and still get multiple events for switch 1 and 4. Switch 2 and 3 work, sending only one event. I have tried all 3 handlers and none work for buttons 1 and 4.


#48

@AduroSmartSupport

  1. fixed handler so all buttons presses send only one press
  2. fix battery level indicator
  3. add double pressed and held states for each button so each button can return 3 states, pressed, double pressed, held.
  4. add dimming capability so buttons 2 and 3 can actually be used to dim Sylvania SMART + BR30 Bulbs
  5. Fix the new SmartThings App, I.E show which button is pressed and released, as an example look at the SmartThings Button GUI in App.

#49

@DrRubin in the IDE page, it def. shows that the dimmer has the new device handler? I havent had any issues with it since installing. Also, if it is using the proper device handler, you should be able to see the log messages. I left a bunch of debugs in there, maybe you are catching one of the edge cases that I didnt.


#50

I added your initials (CGM) in the debug description. I hope I am using the latest driver, I can post it here if you want me to.
My log for one press switch 1: (resulted in two events)

[3be187ca-2728-49a4-9b99-fb10a3a9595f] 4:15:21 PM: debug Description (CGM) catchall: 0104 0006 01 01 0000 00 0135 01 00 0000 01 00 parsed to [name:button, value:pushed, data:[buttonNumber:1], descriptionText:Eria Remote Control button 1 was pushed, isStateChange:true, linkText:Eria Remote Control, displayed:true]

[3be187ca-2728-49a4-9b99-fb10a3a9595f] 4:15:21 PM: debug 6

[3be187ca-2728-49a4-9b99-fb10a3a9595f] 4:15:21 PM: debug zigbee.ONOFF_CLUSTER

[3be187ca-2728-49a4-9b99-fb10a3a9595f] 4:15:21 PM: debug 6

[3be187ca-2728-49a4-9b99-fb10a3a9595f] 4:15:20 PM: debug Description (CGM) catchall: 0104 0006 01 01 0000 00 0135 01 00 0000 01 00 parsed to [name:button, value:pushed, data:[buttonNumber:1], descriptionText:Eria Remote Control button 1 was pushed, isStateChange:true, linkText:Eria Remote Control, displayed:true]

[3be187ca-2728-49a4-9b99-fb10a3a9595f] 4:15:20 PM: debug 6

[3be187ca-2728-49a4-9b99-fb10a3a9595f] 4:15:20 PM: debug zigbee.ONOFF_CLUSTER

[3be187ca-2728-49a4-9b99-fb10a3a9595f] 4:15:20 PM: debug 6


#51

I have two different ERIA Switches. The older one gives multiple event for buttons 1 & 4, but buttons 2 & 3 work with only 1 event. My newer ERIA Switch sends multiple events on all buttons. They are using the same handler. I wonder if it is a firmware problem with the switch itself.

My log for one press switch 1: (resulted in 3 events)

fd7e50b2-3f4f-47e9-ba71-f3ecf176f23e 4:36:29 PM: debug Description (CGM) catchall: 0104 0006 01 01 0000 00 5D1F 01 00 0000 01 00 parsed to [name:button, value:pushed, data:[buttonNumber:1], descriptionText:Eria Remote Control 2 button 1 was pushed, isStateChange:true, linkText:Eria Remote Control 2, displayed:true]

fd7e50b2-3f4f-47e9-ba71-f3ecf176f23e 4:36:29 PM: debug 6
fd7e50b2-3f4f-47e9-ba71-f3ecf176f23e 4:36:29 PM: debug zigbee.ONOFF_CLUSTER
fd7e50b2-3f4f-47e9-ba71-f3ecf176f23e 4:36:29 PM: debug 6

fd7e50b2-3f4f-47e9-ba71-f3ecf176f23e 4:36:29 PM: debug Description (CGM) catchall: 0104 0006 01 01 0000 00 5D1F 01 00 0000 01 00 parsed to [name:button, value:pushed, data:[buttonNumber:1], descriptionText:Eria Remote Control 2 button 1 was pushed, isStateChange:true, linkText:Eria Remote Control 2, displayed:true]

fd7e50b2-3f4f-47e9-ba71-f3ecf176f23e 4:36:29 PM: debug 6
fd7e50b2-3f4f-47e9-ba71-f3ecf176f23e 4:36:29 PM: debug zigbee.ONOFF_CLUSTER
fd7e50b2-3f4f-47e9-ba71-f3ecf176f23e 4:36:29 PM: debug 6

fd7e50b2-3f4f-47e9-ba71-f3ecf176f23e 4:36:29 PM: debug Description (CGM) catchall: 0104 0006 01 01 0000 00 5D1F 01 00 0000 01 00 parsed to [name:button, value:pushed, data:[buttonNumber:1], descriptionText:Eria Remote Control 2 button 1 was pushed, isStateChange:true, linkText:Eria Remote Control 2, displayed:true]

fd7e50b2-3f4f-47e9-ba71-f3ecf176f23e 4:36:29 PM: debug 6
fd7e50b2-3f4f-47e9-ba71-f3ecf176f23e 4:36:29 PM: debug zigbee.ONOFF_CLUSTER
fd7e50b2-3f4f-47e9-ba71-f3ecf176f23e 4:36:29 PM: debug 6


#52

That is def. a double event … its getting the zigbee.ONOFF_CLUSTER twice.
I saw this FREQUENTLY in my early attempts. But once I

  • Removed the device
  • Added the latest Handler
  • Re-added the device via the ST App and searching for new devices

It seemed to have gone away.

Notes:

1 - When I installed it this way, it found the device and used my handler IOW - I didnt swap the handler from the existing one. There are some setupy things that need to work under the hood to make things happy
2 - Im not convinced that my handler solves a hardware issue that may be the cause for the double events - -BUT – with that, I havent experienced one since the fresh install

Let me know how it goes, or you need some help.


#53

OK I was about to give up, but I did the three steps you outlined above and now everything is working. By the way, now both buttons behave the same way. I am so happy!!

So pressing Button 1 & 4 creates 8 and 10 log messages, while pressing button 2 & 3 creates 4 log messages, but the logic only decodes 1 push event for each button. Yay

I pressed each button once and pasted the logs here to document this behavior …

a124ed7d-a116-476b-9e63-5cfc744d6e59 1:25:14 AM: debug Description (V3) catchall: 0104 FCCC 01 01 0000 00 0135 01 00 0000 00 00 000300 parsed to [:]
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:25:14 AM: debug 64716
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:25:14 AM: debug ADUROSMART_SPECIFIC_CLUSTER
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:25:14 AM: debug 64716
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:25:14 AM: debug Description (V3) catchall: 0104 0006 01 01 0000 00 0135 01 00 0000 00 00 parsed to [name:button, value:pushed, data:[buttonNumber:4], descriptionText:Eria Remote Control button 4 was pushed, isStateChange:true, linkText:Eria Remote Control, displayed:true]
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:25:14 AM: debug 6
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:25:14 AM: debug zigbee.ONOFF_CLUSTER
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:25:14 AM: debug 6
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:25:14 AM: debug zigbee.ONOFF_CLUSTER
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:25:14 AM: debug 6
Button 4 Pressed
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:25:12 AM: debug Description (V3) catchall: 0104 FCCC 01 01 0000 00 0135 01 00 0000 00 00 000200 parsed to [name:button, value:pushed, data:[buttonNumber:3], descriptionText:Eria Remote Control button 3 was pushed, isStateChange:true, linkText:Eria Remote Control, displayed:true]
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:25:12 AM: debug 64716
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:25:11 AM: debug ADUROSMART_SPECIFIC_CLUSTER
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:25:11 AM: debug 64716
Button 3 Pressed
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:25:08 AM: debug Description (V3) catchall: 0104 FCCC 01 01 0000 00 0135 01 00 0000 00 00 000100 parsed to [name:button, value:pushed, data:[buttonNumber:2], descriptionText:Eria Remote Control button 2 was pushed, isStateChange:true, linkText:Eria Remote Control, displayed:true]
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:25:08 AM: debug 64716
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:25:08 AM: debug ADUROSMART_SPECIFIC_CLUSTER
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:25:08 AM: debug 64716
Button 2 Pressed
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:21:13 AM: debug Description (V3) catchall: 0104 FCCC 01 01 0000 00 0135 01 00 0000 00 00 000000 parsed to [:]
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:21:13 AM: debug 64716
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:21:13 AM: debug ADUROSMART_SPECIFIC_CLUSTER
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:21:13 AM: debug 64716
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:21:12 AM: debug Description (V3) catchall: 0104 0006 01 01 0000 00 0135 01 00 0000 01 00 parsed to [name:button, value:pushed, data:[buttonNumber:1], descriptionText:Eria Remote Control button 1 was pushed, isStateChange:true, linkText:Eria Remote Control, displayed:true]
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:21:12 AM: debug 6
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:21:12 AM: debug zigbee.ONOFF_CLUSTER
a124ed7d-a116-476b-9e63-5cfc744d6e59 1:21:12 AM: debug 6
Button 1 Pressed


#54

AWESOME!!! Glad its working. These are really the best non-HUE switches I have found.

Let me know if you need anything. Ill post here for major updates/etc …


#55

Whoa. Looks like I missed a lot. Should I update the DTH, @cgmckeever, or is it the one from last week?


#56

I think you grabbed this one – It was more or less code clean up before I promoted it. If you have the version before it, it should only require a DH swap in the web ui, and not a hardware refresh.

BUT – of course, if its working for you – best not to shake things sometimes :wink:


#57

Completely agree. :wink: thanks!


#58

My next step would be to set the ERIA UP/DOWN buttons to dim three Sylvania smart+ BR30 lights. The lights are RGBW and I can set color or color temp and level using the ST GUI. A simple script that would increase or decrease the level with each button press. But looks like I can’t set up anything in ST to do this.

I am new to the ST world so would like some advice on how to proceed. Do I need to load webcore to do this? Or make a smart app in ST?


#59

This could work, but only if you can limit yourself to one button press every 5-7 seconds.


#60

Does the ST App allow you to add the three lights to button 2 & 3 and then change their level accordingly? I feel I played with that initially. I dont actually know how the app my devicehandler exposes even works, Ive hooked it up to what you are saying via webcore.

The issue, as @WCmore stated is flooding webcore. At one point I added a check on last press time to the handler, I didnt get it tweaked perfect, but it is an option to not broadcast an event if pressed under X seconds.

However, this adds some usability oddity as pushing buttons then dont seem to act like you’d think - since some are just dead presses