Anyone had issues in the last 3-4 months where single-press of Samsung Buttons produce multiple digital Events?
Every chance my issues are something else, but thought I would pose the question. Other options may include hub mesh or more likely my setup of rule for managing modes.
I just checked the event log on one of mine and no sign of multiple events. I wish I had bought more of these when they were cheap. They have been very reliable temperature sensors as well as buttons.
Yep, awesome devices in my eyes too, must be something else going on... Also the fact I have seen a few of them with this problem also lends itself to something unrelated to the devices as well.
I’ve seen posts from people complaining of double events with these in the past, but never experienced it myself. Mine are all on the firmware that ends in 14 if it matters. I don’t know if that is the latest since my ST hub is long gone.
Yeah, I'd seen the old digital duplication posts as well, but I expect they may not relate to my situation, but will keep them in mind.
Same here...
I'll have more time over the weekend (most likely tomorrow / today) to review this in more detail....
Here's a recent press of the button...
Here's the Device Details:
Version 11 bug?
Could be a firmware thing, but definitely a change in behaviour, most like prior to the latest beta changes, more likely something else....
I haven't updated the firmware... ever.... Never been paired to a SmartThings Hub....
Try pairing the button again to the hub (without deleting it).
I'm going to put this down as the solution.... Wasn't the most definitive outcome....
I paused the two rules I had setup to change modes, tested button presses and was still seeing triple events recorded, though weirdly no temperature or battery events recorded over at least the last month.
I did the re-pairing multiple times (poking a pin in the rest hole on the back for 4-5 seconds while HE was in pairing mode). It picked up the previously paired button device, with the link to the HE device. I pressed the configure and reset commands multiple times, each time it would report battery and temperature, though the temperature was wildly innaccurate (26+C and we are only in the second day of Spring).
For a good 20 minutes or more any press or hold of the button would not be detected, though throughout this time I was re-pairing and re-configuring the device multiple times. I was about swap out the device in the rules for a virtual one while I removed it from HE and re-paired as a new device, but decided to check out the Zigbee map before I tried this. I don't expect this was what changed things, but it eventually showed up routing through an IKEA repeater downstairs in the garage, odd choice I would have thought. It then suddenly started detecting presses and holds. Must have been taking some time to find a good route. Perhaps I need to adjust the power on the hub, which is currently set to 8.....
Either way, very happy to have it sorted out now. One more button to fix.... I think.
Thanks for the suggestions.
I have unchecked the 'solution' mark - I can now replicate exactly the same problem with an IKEA TRADFRI SHORTCUT Button E1812 :
dev:41862023-09-02 09:55:52.933infoTRADFRI SHORTCUT Button button 1 was pushed
dev:41862023-09-02 09:55:52.926debugTRADFRI SHORTCUT Button processIkeaCommand: descMap: [raw:catchall: 0104 0006 01 01 0040 00 CEBF 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:CEBF, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]
dev:41862023-09-02 09:55:52.918debugTRADFRI SHORTCUT Button descMap = [raw:catchall: 0104 0006 01 01 0040 00 CEBF 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:CEBF, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]
dev:41862023-09-02 09:55:52.903debugTRADFRI SHORTCUT Button parse: catchall: 0104 0006 01 01 0040 00 CEBF 01 00 0000 01 00
dev:41862023-09-02 09:55:52.896infoTRADFRI SHORTCUT Button button 1 was pushed
dev:41862023-09-02 09:55:52.881debugTRADFRI SHORTCUT Button processIkeaCommand: descMap: [raw:catchall: 0104 0006 01 01 0040 00 CEBF 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:CEBF, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]
dev:41862023-09-02 09:55:52.876debugTRADFRI SHORTCUT Button descMap = [raw:catchall: 0104 0006 01 01 0040 00 CEBF 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:CEBF, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]
dev:41862023-09-02 09:55:52.854debugTRADFRI SHORTCUT Button parse: catchall: 0104 0006 01 01 0040 00 CEBF 01 00 0000 01 00
dev:41862023-09-02 09:55:52.849infoTRADFRI SHORTCUT Button button 1 was pushed
dev:41862023-09-02 09:55:52.839debugTRADFRI SHORTCUT Button processIkeaCommand: descMap: [raw:catchall: 0104 0006 01 01 0040 00 CEBF 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:CEBF, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]
dev:41862023-09-02 09:55:52.832debugTRADFRI SHORTCUT Button descMap = [raw:catchall: 0104 0006 01 01 0040 00 CEBF 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:CEBF, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]
dev:41862023-09-02 09:55:52.790debugTRADFRI SHORTCUT Button parse: catchall: 0104 0006 01 01 0040 00 CEBF 01 00 0000 01 00
dev:41862023-09-02 09:55:52.771infoTRADFRI SHORTCUT Button button 1 was pushed
dev:41862023-09-02 09:55:52.765debugTRADFRI SHORTCUT Button processIkeaCommand: descMap: [raw:catchall: 0104 0006 01 01 0040 00 CEBF 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:CEBF, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]
dev:41862023-09-02 09:55:52.760debugTRADFRI SHORTCUT Button descMap = [raw:catchall: 0104 0006 01 01 0040 00 CEBF 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:CEBF, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]
dev:41862023-09-02 09:55:52.748debugTRADFRI SHORTCUT Button parse: catchall: 0104 0006 01 01 0040 00 CEBF 01 00 0000 01 00
Interesting.... Could it be the repeater? Or something else?
BTW, I'm trying out your Zigbee driver for one of my IKEA On/Off devices... Just paired it, will leave it a while after this mornings experience with the Samsung button.
I suppose that by some reason the button push report is not acknowledged by the HE Zigbee coordinator, that's why the device repeats the same message 3 or 4 times.
This is a known issue with some of the Tuya TS004F buttons. But it is the first time I notice the same problem with a non-Tuya device.
So depending on the repeater it is routed through, that may influence how it behaves...?
Could be …
I will first apply a workaround to filter the repetitive events, but the core problem will remain.
When (and if) the button chooses to communicate directly to the hub and if the duplicated events are gone- this will confirm that the repeater in between is the problem.
At the moment my IKEA button is behaving the same as when I re-paired the Samsung button, battery and no button presses. Will leave it this time and see if it comes good, but it is already showing as going through an old Samsung Smart Outlet.
What model is your IKEA button?
With the '"Zigbee Button Dimmer" driver assigned, select "LOAD ALL DEFAULTS" in the driver web page "Configure" command. Then wake up the device (push the button) and at the same time click on the 'Configure' button.
Download the Hubitat app
