In the last 2 weeks, I finally decided I had to update my hub (I stopped updating in Sept of 2025 due to HE problems I was having).
After updating, 2 other devices had problems and wouldn't re-connect. I had to delete the devices. (then re-add). I also had to rebuild my DB.
Both buttons needed battery changes. I swapped batteries and went through the usual process of re-adding. Both buttons would sort of re-add (they'd appear in the join but then not function). I realized I had to do the same dance as the other 2 devices that connected but wouldn't work.
I re-built/reindex the DB and added one of the buttons. It added smoothly. When I pushed the button for a trial - THREE entries appeared in the log as seen in the screen cap above. But I pushed the button once. This doesn't feel like normal behavior. The samsung button driver is a native driver so I can't debug it. Anyone have thoughts? I'm about to blow it away and try again but thought I should post.
I have like 6 backup Samsung buttons, I just tried to add one to my Hubitat and it added fine. I will tell you I have had issues where batteries and the button have had issues where I can't use Energizer batteries but other brands like Duracell worked fine.
Whish I could provide more insight to your issue but just wanted to give you my findings.
I have several ST buttons, all use the built-in driver as you are using, all are working normally across all platform updates I've taken of the past several months, beta an official releases. Just tested a couple of them, they are tied to different lights. Lights turned on/off as expected. No issues, normal log reports (one report per press), no false multiples reported .
First button, pressed two times, once to turn light on and then off:
Solved it. So the method/steps to add the button had a really big impact on success.
Previously I had created a virtual button and swapped the device as a means to hold the rules.
When I opened the battery compartment and replaced the battery, the light would flash green. I tried to re-add and it would detect the 'new' device but not completely get re-added. Any further attempt to re-add gets hung up, or creates a non-functioning device.
This time - after removing the real buttons (I have 2), and rebooting with a rebuild, I then put the battery in the device and waited 30 seconds for it to settle.
Then I used the reset hole and pushed - held it in until it flashed red, then started the add process. The unit was detected, and it added correctly. Now, a push creates only 1 push in the log and events.
I repeated the process of adding the battery, then doing the reset and again it worked correctly.
The HE does some form of auto-reconnect to devices I think and once you fail to connect it once, it doesn't recover. The clear of the device and doing the reset in the correct order solves this for me.
You should not go through any steps to re-add the button when you replace a battery. When you put in the new battery, the button's status light will go green for several seconds, and then it will automatically re-connect to your hub and ready to use. I've never had to reconnect my Samsung buttons when changing batteries.
I just replaced a battery in one of my Samsung buttons...put in the new battery, status light on the button went green for a bit then turned off. Button was then ready to use.
Logs after putting in the battery, waiting for green light to turn off, then pressed the button a couple of times:
You can try it again if you want...remove the battery from one of your buttons, wait a few minutes, put it back in and wait for the green light to go out and then try the button. Unless something odd is going w/your hub the button will just work.
thats good info! I've always just re-added the devices after a battery change to force the device to report the new battery level faster. But I can see thats not really necessary if the device just re-connects itself.
Does this work for all battery devices? I've got a hodge-podge of 3rd reality, samsung, tuya, sonoff , generic and Aquara devices - about 40 in all.