Samsung Buttons - Multiple Presses Recorded (new)

Since this topic by @sburke781 was just closed...

I wanted to note that I just started experiencing the exact same thing (or so it seems) with my Samsung Button.

My button wasn't working (button presses weren't registered) and was possibly low on battery. I replaced the battery night before last and it then began registering the button presses. But, apparently all too well.

When I pressed shortly after changing the battery, I noticed things were acting weird, but I was too tired to mess with it then.

Tonight, the exact same thing happened, so I did some digging.

What I found in the device event log was that the device registered THREE presses, about 2 seconds apart (they were listed as "digital", like every other press).

Because the button was pressed 3 times, it created havoc with my rules... Since NOTHING was changed other than the device's battery--I have no idea what went wrong.

In the mean time, I have added some logic to one of my rules that was impacted the worst to hopefully detect and ignore the extra presses when they are in rapid succession.

Here's the info from my device (it is using the default "Samsung Zigbee Button" driver):

image

I'm not sure if the firmware can be updated or not??

@bobbyD I was wondering if anything definitive was figured out about this issue?

Did you try re-pairing the button?

2 Likes

When I read that topic, it seemed that didn't fix it after all? It did I misread that?

TBH I'm not 100% sure... I don't seem to have the issue anymore.

@bobbyD REALLY odd now...

Now that it's not the middle of the night and I have a moment...I changed my rule temporarily so it didn't go nuts triggering the normal things--but just let me know when the button was pushed.

When I went downstairs to the button and pressed it, it triggered the "push" 3 times in rapid succession.

I walked upstairs with it and pushed it. It only triggered 1 push--as it should have been doing all along.

I went back downstairs with it and tried it again there, and it only triggered 1 push.

That is incredibly odd--but seems like it may have had something to do with the device not getting the proper ACK when it was pushed, so it tried 2 more times??? I'm def not a Zigbee protocol expert.

In any case and although I don't have a proper diagnosis/solution for the odd behavior, it is back to behaving properly for now. I hope it keeps up. :slight_smile:

1 Like