Released version 15.0.01 to patch support for external applications using the OAuth PAT. You can find the internal and external network links on the OAuth application, both in standard HTTP GET format.
Example webCoRE piston:
1 Like
Thanks for the response. The other night when ST made the switch to requiring token reauth every 24hrs, I was having trouble getting it to work. It was late and I really didn't want to stay up any later to deal with it, but I have a "night" switch in ST which is replicated in HE. It disables lights coming on amongst other things, most of which are in HE. I kept trying to turn it on in HE but it wouldn't work, I'm assuming because it couldn't connect to ST. Eventually the OAuth and PAT issue were resolved but I'd like to figure out a way to avoid this in the future if possible.
Not sure I can help in this use case, you might look into the Mira solution by @coreystup since that is local and allows for HE->ST integration.
I'm using MIra as well. I guess it makes more sense to put the virtual switches under HE since the majority of automations/rules I've transferred over. Then I can just mirror them back to ST. Not as big of a deal if the switch doesn't sync to ST as there aren't many automations that use it.
1 Like
It's the a device handler for tapo cameras? Would the aeotec or Arlo ones work?
There hasn't been a great way to move video around from ST but most cameras support motion sensor events on SmartThings. You could probably use the Replica Multipurpose Sensor to pull in that attribute.
And honestly other than tvs and a refrig, my ST dev days are over and the hub(s) are in the closet. There isn't much 'there' anymore that keeps me entertained.
1 Like
Yeah motion and status probably all I need
Well as of late last night, received the dreaded “reauthorization failure”. Not sure why as my Hubitat was not offline.
When I follow the directions to reauthorize, it takes me SmartThings pop up to reauthorize. SmartThings says token reauthorized. But in Hubitat, hubithings app still says it is not authorized.
When I go to the SmartThings App, it says hubithings is authorized.
I don’t want to delete the api for fear I may lose everything.
Any assistance is very much appreciated.
My assumption is you are up to date with HPM for the application.
Q: When did you create your PAT?
If it was before Jan 1, 2025. Go into the OAuth application and press "Delete API". That will not clear out your devices in the API, just resets the connection to the ST cloud and then will reestablish all your devices. They are saved in the OAuth state settings.
If the PAT was AFTER Jan 1, 2025. You will need to get a 24-hour PAT from ST via the links, update the Replica app with that new PAT, then follow the above instructions.
That was it! Just deleted the API to re-establish the connection.
Thank you!
1 Like
@Bloodtick_Jones I've used this driver for my older Samsung fridge for many years. I just added a newer second Samsung fridge, and cannot figure out how to add it. The older one shows up in all the menus, but not the newer one (It shows up in ST). Please help!
Make sure you can see the device in the SmartThings web UI. Then do a refresh in the Hubitat HubiThings OAuth and you should see the device show up there. It that all works, you should be able to add it as a Replica device. Let me know where this fails and we can take it from there.
Just out of curiosity... I still have my ST account, but I don't run the ST hub anymore. Does that make a difference?
It shouldn’t with a refrigerator and Dave’s HubiThings drivers.
Ok, I was able to install it, but there's a buttload of devices for each fridge. Do I need all of these?
You will need to contact @djgutheinz concerning as the owner of the driver. He does maintain good documentation on his solutions both in GitHub and his own topic.
My answer is "probably not", and I recommend inspecting which devices are doing what and when against the ST web solution. My single refrigerator only has the main device with two child devices.
For context, I’m in "barely maintain" mode with this project since moving off SmartThings and storing the hubs in a closet. I apologize if that’s inconvenient—I'm just tired of SmartThings overhauling development every few years and wasting my time. That said, I understand there really isn’t another solution when it comes to their appliances and Hubitat.
2 Likes
I understand....and thank you for this project. This is really the only ST "thing" I still run, because it's nice to get notifications when the door has been left open for a long time. I love my Hubitat!
(It would be nice to replace the Samsung sensors with Z Wave/Zigbee sensors so I could be completely ST-free, lol)
YES! YES!
I took a look and this is how my configuration looks running on the latest Hubitat firmware. For context, ST will divide up a device into 'componentId' to allow for the device to have more than one similar capability (like a couple of switches). The default componentId is 'main' and the others can be almost any name you want. The refrig does exactly that, a couple or few componentIds and Dave's driver will see that and build out other devices since Hubitat does not have this concept natively.
The Replica solution does allow you to select specific componentIds, but that is not needed with Dave's drivers. He handles it directly.
1 Like
This is what was found. You are free to delete any device you do not want, The number of devices is due to the multiple sensors (for each refrigerator) compartment so that you can set up rules and notifications of doors open, temperature high, etc.
2 Likes
Hi! Thanks for the work on this!
I finally got around to adding my Samsung Range Hood to HubiThings Replica after my remodel, and the closest driver I can find to use is Replica Samsung OCF Microwave Hood, but when I try to use on/off, no luck, and I get errors in the logs:
It does look like set fan speed works, although it doesn't actually turn on the fan, and I do get quite a bit of data coming through when I control via the SmartThings app, but no controls in HE are really doing anything. I also did try to create some new rules with the other commands that I have, but they keep disappearing. Maybe the microwave driver is overriding them, so I'm going to futz around with a new virtual device to see what I can get working. In addition to the "main" component, I also have a "lamp" component that shows up, and if I add that as a switch device type, I can control the over range light, but that's really secondary to being able to control the fan itself.
I guess my real question here is, what do I need to do to look into getting a driver that will work for my standalone range hood? Although a bit out of my wheelhouse (I'm in IT management, not real work 
), I'm happy to try to take the microwave driver and modify it, but I'll need some guidance on where to look for the capabilities, attributes, etc. Or if someone is dying to take this on, I can provide the data needed to make a new driver.
Thanks in advance for any assistance!
EDIT: I see the "new device request" process, so I'll do that. If a new device is the route I need to go, fine, but if there's anything I'm missing on the microwave hood vent, let me know.
UPDATE: Submitted a new device request. I was able to get this to work as two separate devices using (1) main that was able to control the fan/vent on/off and (2) Lamp that was able to turn the light on/off. Couldn't get lamp levels or fan mode (e.g., Smart vs Low, Med, High) to work with any of the existing drivers. The separate devices give me the basic functions and will work for me for now, but would be great to get this all wrapped up into one working device that includes all of the extra capabilities and attributes that this device has (air quality, fan mode, filter reset, etc.) Thank you!
