Smartthings button events firing without pressing a button

[jm-cook]

The problem

Hi it seems that the smart things integration fires button press events for all buttons all together all at once without actually pressing a button. This in turn causes all connected automations to fire which in turn sends many commands to Homematic to control blinds, which in turn results in being blocked due to flooding the service.

atm I know this report is quite vague, it is difficult to pinpoint the origin but it may have started after upgrading to 2025.6.1

These buttons:

...and these buttons fired at the same time (9:50):

I have checked the ST app and it seems no button presses were recorded, so I am suspecting a glitch in the ST integration that fires events after reboot or some other situation. I did test for this but couldn't repeat..

I have checked as much as possible and it seems like the automation is triggered by button press events, not some other event, but this is difficult to verify.

According to the device log, button press events were recorded only when the relevant button was pressed. The "event storm" doesn't seem to be recorded.

I have reverted to 2025.5.3 until I can more closely discover the source.

What version of Home Assistant Core has the issue?

2025.6.1

What was the last working version of Home Assistant Core?

2025.5.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

smartthings

Link to integration documentation on our website

https://www.home-assistant.io/integrations/smartthings

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @joostlek, mind taking a look at this issue as it has been labeled with an integration (smartthings) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of smartthings can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign smartthings Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

smartthings documentation
smartthings source
_{^{(message by IssueLinks)}}

[github-actions]

🔍 Potential duplicate detection

I've analyzed similar issues and found the following potential duplicates:

• #144945: Device state in HA gets out of sync with the actual state making it impossible to control it
• #145346: SmartThings stopped working. Can't be configured
• #144582: Smartthings integration does not always automatically reconnect when internet connection drops and reconnects

What to do next:

1. Please review these issues to see if they match your issue
2. If you find an existing issue that covers your problem:
   • Consider closing this issue
   • Add your findings or 👍 on the existing issue instead
3. If your issue is different or adds new aspects, please clarify how it differs

This helps keep our issues organized and ensures similar issues are consolidated for better visibility.

This message was generated automatically by our duplicate detection system.

[jm-cook]

This issue doesn't seem to be similar to the 3 potential duplicates apart from being a problem with the smartthings integration.

[joostlek]

How do you mean fired at the same time? Do you mean you built an automation and the automation is fired based on that?

[jm-cook]

Hi again,

I discovered something here:

The ST buttons change state between unknown and unavailable - this causes the automations to fire.
Later on in the automation I check for "pushed", and I think this is actually working. It seems it is not possible to filter for "pushed" in the trigger (which is unfortunate as I could have rejected the change of state where Unavailable or Unknown is involved earlier)

eg:

alias: BR Blinds button presses
description: ""
triggers:
  - trigger: state
    entity_id:
      - event.bedroom_blinds_button1
    id: BR_BLINDS_1_DAY

... more triggers here, then ...

conditions: []
actions:
  - choose:
      - conditions:
          - condition: trigger
            id:
              - BR_BLINDS_1_DAY
          - condition: state
            entity_id: event.bedroom_blinds_button1
            attribute: event_type
            state: pushed
        sequence:
          - data:
              position: 0
            target:
              device_id:
                - dc6ac7497948287c4f31d9153e35f105
                - 898c77666f234fd85b21098d64da3885
            action: cover.set_cover_position
          - data:
              tilt_position: 70
            action: cover.set_cover_tilt_position
            target:
              device_id:
                - dc6ac7497948287c4f31d9153e35f105
                - 898c77666f234fd85b21098d64da3885

mode: single

I also found this relevant bug report:

#146618

I thought this was a symptom of a ST problem but it turns out it is the cause of the issue.

You can close this as the problem is not with ST, its with homematic :-)

But it would be handy to be able to pick out only button presses in the trigger... I don't know why that is, the options are there but cannot be used.

https://www.home-assistant.io/integrations/event/