Good information JD. Thank you!
Does the solo connect to this DTH or does it connect as a thing and then you have to switch to the DTH smartsense Button?
Does it also measure temperature as the DTH says?
The Device was connecting to the DTH smartsense button. I was advised by Third Reality that their engineers made changes to the button and now I see it is connecting to the ‘Ikea Button’. The changes resulted in the button functioning correctly now. The device no longer shows temperature. It does display battery.
If it works fine with the Ikea button and with the smartsense button it didn’t work, I don’t think it will work with my driver which is like the smartsense Button.
If you want I add it and try
Did you find an Edge driver for this button?
I submitted a request on the ST Community for to developer Yakov Gerlovin See: https://community.smartthings.com/t/st-edge-beta-buttons-and-remotes-edge-driver-aqara-ikea-tuya/241708/22
You may want to bookmark this thread for receipt of a potential driver solution.
Released an Edge driver which supports the Third Reality Smart Button. Check details here:
This thread is regarding the Third Reality Smart Button, which didn’t have an Edge driver until Corey released his today.
It isn’t that Third Reality devices aren’t supported in stock Edge drivers, it is that the button in particular hasn’t been added to the ZigBee Button driver yet. We can reasonably expect it to be as it is fingerprinted in the Ikea Button DTH, but now users have the option not to wait.
My button is working with the “CStup Edge Drivers”
Surprised it was missed if it was already in the DTH.
I wasn’t able to add my ThirdReality button initially until I created my own DTH in the IDE, based on the Ikea Button.
There are a few devices like that one across various drivers. It is like the ‘to do’ list was taken from a snapshot of the drivers as they were in July last year and they haven’t all been revisited yet. I think the button was added to the DTH in August last year.
Very possible. I thought another reason because the framework does not yet have cluster 0x0012 (Multi state basic) handling classes generated out and this device uses those to handle all 3 states. The two pressed states you can use existing clusters, and the hold state you might be able to cheat with another. Its on my list to request 0x0012 support be added.
Just set up my Third Reality button with your driver and it works perfectly. Thank you so much!
Thank you SO much for this! My ThirdReality smart button (model 3RSB22BZ) stopped working entirely today, and only a generic Zigbee driver was getting installed. That generic driver offered no control options, but yours worked perfectly!!!
Thanks for creating this driver! My two buttons finally migrated to a stock driver and went dead. Everything with the stock driver looked fine, but nothing would respond. Switched drivers and all fine now. I had to rebuild my few automations, but I assume that’s because I used the built in UI ones for the button vs an independent automation.
@csstup is the developer that I contacted to add the Third Reality Smart Button to the edge driver. I’m glad you were able to discover the driver and get it working. I use the same button to control me studio lights. It works great!
The 3RSB22BZ must have more of a story to tell as it was fingerprinted in the Ikea Button DTH but not ported to Edge and it seems to be going through certification at the moment. This seems rather unfortunate as end users might reasonably expect it met the criteria for migration. That was certainly what I presumed in my earlier comments in this thread.
I don’t use the device myself but it certainly isn’t the only device that was explicitly supported in stock handlers but not ported. One wonders how users are supposed to follow the guidance they are given in these cases.
My switches wound up crapping out 2 days ago too. All the sudden there were about 50 button press options and none of them worked. Reinstalled and ended up as a generic ZigBee thing. This driver got me back in business. Many thanks!