After the update my Buttons haven’t worked properly. It’s a lottery… Some of them work and most of them don’t. You have to to activate them by pressing the Button several times before a routine activates - and mostly nothing happens. I have a v3 Hub.
Hi, @Matti_Koskinen
I moved your post here since this needs further investigation.
Are the button devices the only ones having problems with automations?
It would be really helpful if you help us check the following:
- Enter the device’s details of one of those buttons
- Then, press the button and check if the status of “Standby” changes to “Pressed” or the corresponding value, depending on what you did with the button (Held, double pressed, etc.)
- If the button isn’t showing a status change there and then, when it does the Routine finally works, then we need to see where the commands are delaying.
- Is this the Routine running locally or in the Cloud?
Hi!
Sorry for the delay. I’ve had similar problems with the last updates (except the last one before this).
Are the button devices the only ones having problems with automations?
Yes, the issues appear to affect only the Button devices. Other devices seem to work normally without automation problems, but It seems that there isn’t a clear logic with the issue. The situation varies with different Buttons in different rooms. I would like say that the problems come up mostly when the Button hasn’t been pressed for a long time (hours).
Enter the device’s details of one of those buttons
Here are the details for one of the buttons:
-
Model: button
-
Manufacturer (Code): Samjin
-
Connection Type: Zigbee
-
Connected Hub: KalaHub
-
Firmware Version: 00000014
-
App Version: 2.3.57-22
Then, press the button and check if the status of “Standby” changes to “Pressed” or the corresponding value
When the button works correctly, the status changes to Pressed (or Double pressed, etc.), as shown in the activity log. However, when the issue occurs, the status does not change at all — the button doesn’t respond until it’s removed and reattached. After that, the green LED turns on and the button starts working again.
If the button isn’t showing a status change there and then, when it does the Routine finally works, then we need to see where the commands are delaying.
That matches what happens: the routine only runs once the button finally reports its status again after reconnecting.
Is this the Routine running locally or in the Cloud?
According to the routine list:
-
Pressed → Cloud
-
Double pressed → Local
-
Held → Cloud
Best,
Matti
Hi, @Matti_Koskinen
Thank you for the feedback, it is super helpful
So it seems that the devices are losing connection to the hub since it doesn’t send status reports until you rejoin them. If they took a while but responded by themselves, then the issue would be that they are sleepy.
Buttons are configured not to be marked offline/online since they can be moved outside the house/location and then come back.
So, please help us submit the hub logs after you run this tests:
- In a device that isn’t responding, push the button a few times and take note of the date and time, and share it with m,e including your timezone.
- Then, submit the hub logs as follows:
- In the Advanced Users app, enter the “Hubs” section
- Enter the corresponding Hub and click on “Dump Hub logs”
- Confirm the process by clicking on “Dump Hub logs” again in the pop-up.
- You’ll get a green box at the top confirming the Hub logs were requested.
- Share the name of the device you tested so I can find it in your account
- Finally, provide support access to your account:
Hi, @Matti_Koskinen
Just following up on this case, are you still experiencing it? In my previous reply, I requested additional information to be able to report the issue in case you do.
1 Like
Hi, @Matti_Koskinen
Following up, the engineering team mentioned there isn’t enough information in the Hub logs shared before.
So, when the issue happens again, please send us the information I mentioned here:
1 Like
I tried with three of the buttons and one worked with a slight delay, the second on after several long presses and the third one is unresponsive (light on the button activates, but nothing else happens). Time 14:54 (GMT+2). I dumped the hub logs.
Hi, @Matti_Koskinen
Can you provide the names of the devices you tested, please? this is to let the engineering team know which device ID to look for in the hub logs you sent.
Hi @nayelyz,
the first was eteinen (slight delay), second was vierashuone (required several clicks) and third olohuone (unreaponsive).
ti 25.11.2025 klo 23.15 SmartThings Developer Support via SmartThings Community <notifications@smartthings.discoursemail.com> kirjoitti:
Hi, @Matti_Koskinen
The engineering team checked the logs and they don’t see any issues with the Zigbee network or hub.
However, they noticed that those buttons are constantly timing out during the re-discovery process and try to re-join through different parents on the network during each attempt without success.
It’s not obvious from the logs why this is, so please help us check the following in your environment or network configuration:
- Distance / reliability of any Zigbee routers. If the Buttons are far from the hub, they need the support from Zigbee routers/repeaters that can extend the network to reach them and they be able to connect to the Hub.
- Outside interference between the button(s) and the hub. Is it located near other networking equipment that could be causing interference? This could also be a baby monitor or other routers with a strong signal.
The environment has been stable. The distance between different devices is max 4 meters. The only change is that I have had only one hub for a couple of months. Has there been FW updates on Smartthing Buttons? I recently bought an Aqara Mini Switch and there’s no problems with it.
Please ignore if I interfere with the investigation again…
Maybe these old devices don’t like the Zigbee channel…
Different device, but from the same era:
2 Likes
Sorry for the delay in answering this question. The oldest Hub logs the team could track, from November 11th, show that a check was made to see if new firmware was available, but there wasn’t. The current firmware version displayed in that log is 20. So we don’t know about October, which is when you first posted.