I checked prior posts and found nothing. I purchased when I had a Homey setup and loved using it.
Model # 3RSB01085Z
Third Reality Smart Button ZB2, ZigBee Hub Required,Three Wireless Push Button,Customizable Scenes,Remote Control, Compatible with Home Assistant(ZHA&Z2M), Rechargeable Lithium Battery
Three Buttons, More Actions: Each of the three buttons supports three actions — single press, double press, and hold, giving you up to nine programmable routines to control lights, devices, and scenes instantly.
If ST doesn’t support it, does anyone know something similar? I’m trying to not use 2-3 separate buttons .
That’s interesting since they literally advertise “Works with SmartThings, Aeotec” in the store but might be not true since there’s no sign of a driver for it nor fingerprints in stock drivers and in other places it’s not even mentioned. They even had issues with Home Assistant last month.
Maybe try asking in their official forum THIRDREALITY , so far doesn’t look like anyone asked about SmartThings.
A driver for the device is in development and should be officially available soon. If you already own a SmartThings Hub and absolutely want to use the device now, you could test the driver.
They should not accept the PR as is, the profile uses main component only for the battery with no button capability and three different components for the buttons. That’s not the way to do it in SmartThings. They have to either make main the first button or make main a catch-all button.
The drawback of this is that, should OP use that PR code, he may have to rebuild the automations when the official support is released.
Edit: I’ve commented in the PR, they should just reuse an existing profile instead of creating their own. And that way OP won’t have to rebuild anything, supposing the PR works.
That’s why I said “in development” and that he can test the driver if he really wants to. It’s still better than hastily throwing the buttons away because he doesn’t know if they’ll ever be supported by SmartThings. Rebuilding those few routines shouldn’t be a problem, especially since he’ll have to switch to production eventually anyway, and that involves work too.
Ideally the latter as things stand. The stock IKEA Bilresa dual button handler has main and button2 as component IDs and so you only see actions on one of the buttons on the dashboard tiles which makes it look half broken.
In Matter however it’s a lost cause and there’s no going back or would break all the automations.
To be fair, when I made the driver for IKEA Zigbee buttons I found having to also emit events for main confusing. And users were confused too because they thought main was the first button and automations would do weird things.
To be equally fair, it always has been ridiculous having to do that to fix a display issue. If the app can artificially create a standby I am sure it would be able to display the current button activity without it being spoonfed it.
