Howdy;
I’ve got a 3 pack of THIRDREALITY Single Button Zigbee Remote (Model 3RSB22BZ) – I’m on HA v2026.9.1 w/ an rpi5 and have a sonoff usb zigbee antenna/receiver/doohickey
I’ve paired one of the buttons
put in batteries
it’s blinking in pairing mode
do the ZHA discovery and it successfully adds the device (called Yellow Button)
But then my problem/question:
The Yellow Button doesn’t seem to expose meaningful actions/events to use as triggers. If I attempt to add a trigger and select Yellow Button as the target, I get two possible events :
Battery level changed
Battery level crossed threshold
Did I screw something up? There’s no button-related activity listed.
Looking around, I came across this blueprint which does capture button-press functionality, but is a standalone blueprint focused on just the button, which seems like a weird inversion, or I feel like it’s a clunky way to make use of the button’s capabilities, or at least a departure from other devices I’ve added, e.g. a Hue motion sensor exposes temperature, luminance and occupancy states without needing a blueprint.
I’m new to this, so apologies if I’m missing a fundamental distinction. Any wisdom would be appreciated.
That depends on how you are using the word “should”… Should it? Yes, that would be nice… Does it currently? No
Please review this previous post:
No, this has been a long-standing issue with these types of Zigbee devices. An issue that has been, inadvertently, made worse by recent changes to the trigger selector. The blueprints you mentioned can be a little clunky. But, they were a way to make it easier for users to trigger off these devices without having to take the deep dive into Event triggers when there weren’t any other options.
I need to take a look at the changes to triggers you referenced in the post above mine then because that’s always how I used to do it but obviously some changes have been made.
EDIT: was this the blueprint you used? as it seems specific to ZHA and that thirdreality model and adds double tap and hold options but I don’t have that model and use Z2M.
For my own memory, the steps I took:
Under an Automation
+ Add Trigger
Search for “Device”
Select Device under Triggers category
A dialog pops up
Select the “Yellow Button” in the Device dropdown (my name, you pick your own =)
In the Trigger dropdown select from a large array of event types – I picked remote_button_short_press
Finish & Save your automation
Go live your life and stop staring at a screen.
No, this has been a long-standing issue with these types of Zigbee devices inadvertently made worse by recent changes to the trigger selector.
Heh - show me any project over a week old and I’ll show you long-standing annoyances and tech debt. No worries, just grateful for the quick responses from everyone.
