Network technician helping fix WiFi mesh restarting issues

Steve H.

Expert ★★★★★ 27,853 satisfied customers

Specialities: smart button trigger loss after firmware changes, scene controller event mapping, Zigbee and hub re-sync checks, automation trigger diagnostics.

After a firmware change, start with safe checks: trigger types, scene mappings, hub status, and whether some button events stopped reporting

Technician avatar Technician
Since this started after a firmware change, the first question is not “is the button dead?” but “which events survived the update?”

Let’s start with the safest checks first. I do not want you removing the device or rebuilding all scenes before we know whether the missing actions are caused by lost mappings, renamed events, or a partial re-pair.

Which actions still work right now — single press, double press, long press, or only one of them?
Customer
Single press still works. Double press and long press used to trigger scenes, but now they do nothing.
Technician avatar Technician
That pattern is useful. When one press type still works and the others stop after firmware, it often means the button is alive but the event names, trigger types, or controller integration changed.

Before we assume the scenes were deleted, tell me this: are the scenes still present in your app or hub, and do they run manually if you tap them on screen?
Customer
Yes, the scenes still exist. If I run them from the app, they work fine. It’s only the button that stopped doing half of them.
Technician avatar Technician
Good. That points away from broken scenes and more toward missing button events or stale automations that no longer match the device after the update.

A few details can narrow it fast:
1) What brand or ecosystem is the smart button in?
2) Does the app still show the same number of available actions for that button?
3) Did the hub or bridge update too, or only the button firmware?
Customer
It’s an Aqara button in Home Assistant through Zigbee. I think only the button updated. The automations are still there, but I’m not sure if the action names changed.
Technician avatar Technician
That makes sense. Firmware or integration changes can keep the device online but alter how events are exposed — for example, old automations may still be waiting for an event label the button no longer sends.

Trust moment: I would not delete and re-add the button yet. That can wipe clues from the current setup and make it harder to see whether this is an event mismatch or a pairing issue.

In your logs or event viewer, do you still see activity when you double press or hold, or is there only activity for single press now?
Customer
I checked the logbook and only the single press seems to show up clearly. I do not see anything obvious for double press or hold anymore.
Technician avatar Technician
That is an important clue. If the extra presses are not appearing at all, the problem may be below the automation layer. It could be a changed device mode, a partial firmware issue, or an integration that now interprets only basic button events.

Let’s separate two possibilities safely:
• the button still sends all presses, but the hub no longer names them the same way;
• or the device truly stopped reporting those extra actions after the update.

Do you know whether this model supports multiple modes, like command mode, scene mode, or integration-specific exposure?
Customer
I’m not sure. I remember it had multiple action types before, but I did not change any mode myself.
Technician avatar Technician
That is common after updates. A device can keep working “just enough” to look healthy while one or two action types silently stop exposing the same triggers.

Another low-risk check: when you open the device page now, does it still show entities or events for hold, double press, or multi-click, or is it reduced to a simpler event list than before?
Customer
It does look simpler now. I only see fewer event options than I remember.
Technician avatar Technician
Then the update may have changed how the integration exposes that controller, not just the scenes attached to it. That is why half the actions appear lost even though the button still responds.

I also want to rule out a misleading battery issue. Some scene controllers behave oddly after firmware if the battery is weak and complex actions stop registering first. Has the battery level changed recently, or does the device feel slower to wake than before?
Customer
The battery is not new. It is around 35%, and now that you mention it, the button sometimes feels a little slow.
Technician avatar Technician
That matters because double press and hold can be more timing-sensitive than single press. A firmware change plus a borderline battery can make the problem look like broken automations when it is really unreliable event detection.

Let’s keep this careful: I do not want you changing battery, removing the device, and rewriting automations all at once. One variable at a time gives a much cleaner answer.

If you press very deliberately now, do double press and hold ever work once in a while, or are they completely gone?
Customer
Double press worked once earlier, but I cannot get it to repeat. Hold still seems dead.
Technician avatar Technician
That mixed behavior usually points to one of three things: a changed event model after firmware, a battery or wake timing problem, or old automations listening for the wrong trigger values.

Because your scenes still run manually and single press still works, this does not look like a full device failure. It looks more like the button and the automations are no longer speaking exactly the same language after the update.
Customer
That description fits what I’m seeing. It feels half alive, not completely broken.
Technician avatar Technician
Exactly. The safest next step is to confirm which press events are still being published right now, compare them to the triggers your automations expect, and only then decide whether the battery, integration, or mapping needs attention. That keeps you from rebuilding everything for what may only be a changed event name or reduced action exposure after firmware.
Customer
That helps a lot. I was close to deleting the button and starting over, but now I can see it may just be the event mapping after the update.

Quick answer: the accepted fix

Accepted first approach when a smart button loses some actions after a firmware change:
• Confirm which press types still appear in logs before editing scenes or removing the device
• Compare current button events with the trigger names or mappings your automations expect
• Check whether the integration now exposes fewer actions or a different controller mode than before
• Rule out weak battery or slow wake behavior if complex actions fail more than single press
• Change one variable at a time so you can tell whether the issue is firmware exposure, device state, or automation mismatch

Why scene buttons can lose some functions right after firmware changes

A firmware update can leave a smart button online while changing how double press, hold, or multi-click actions are reported to the hub. In some cases the scenes are still fine, but the event names or trigger types no longer match older automations. A weak battery or slow wake-up can make the change look even worse by causing only the simplest action to register reliably.

What to check first before rebuilding your automations

Start with simple checks: which button actions still show up in logs, whether the scenes still run manually, and whether the device page exposes fewer events than before. If only single press works, compare current triggers with the ones your automations expect. Avoid re-pairing or deleting the controller until you know whether the real problem is missing events, changed mappings, or a weak battery.

Tip: don’t remove the smart button until you know whether the missing actions still exist in logs

A partial action loss often comes from changed event exposure, not a dead controller.

If the scenes still run manually and at least one press type still works, the device may still be paired correctly. The safer path is to compare live button events with your automation triggers before rebuilding anything. That usually shows whether the update changed action names, reduced available presses, or exposed a battery timing issue.

Disclaimer: This information is AI-generated and intended for general guidance only. Steps vary by smart button brand, hub integration, and firmware version. For exact instructions for your setup, consult the manufacturer’s support site.

Understand what these prompts mean

Getting Started Is Easy

Low-risk diagnosis first

Start by checking live button events, scene behavior, and current trigger exposure before changing the whole setup.

Identify what changed

Firmware, integration behavior, or event naming can shift after an update even when the button still appears online.

Avoid “random fixes”

Changing one thing at a time makes it much easier to see whether the issue is the battery, mapping, or controller exposure.

FAQ

Why did my smart button lose some actions after an update?

Firmware can change how press events are reported to the hub. The button may still be online, but double press or hold may use different trigger values or stop reporting correctly. Scenes can remain intact while the button mapping changes underneath them.

Is this a scene problem or a button problem?

If the scenes still run manually, the scenes themselves are usually fine. The issue is often with the button events, controller mode, or automation triggers. Logs can show which layer is actually failing.

Can low battery make only some button actions stop working?

Yes, sometimes it can. Timing-sensitive actions like double press or hold may become unreliable before single press fails. That can make the problem look like broken firmware when battery or wake timing is involved too.

Can this be checked safely at home?

Yes. Start by comparing live button events with the triggers your automations expect. Make one change at a time and avoid deleting the device until you know whether the missing actions are gone or just renamed.

Sources

Joe Verified Icon
Steve ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,853 customers
Avatar
Alex · Expert's Assistant
5 Tech Support Specialists are online right now.