Announcing a solution to allow real-time bi-direction updates between Hubitat and SmartThings devices, modes and scenes utilizing the SmartThings OAuth Cloud API. Includes the ability to have multiple ST locations with multiple ST hubs replicated to a single Hubitat hub. It is not a requirement to have a ST hub to operate mirror functions to cloud native ST devices.
This solution requires a reasonable degree of understanding of both Hubitat and SmartThings. The original design was to mirror the few devices I have remaining in SmartThings to Hubitat in a real time fashion, but grew into a full project thanks to @Alwas, @bthrock, @hendrec, @swade, and @hendo25.
One primary use is to allow ST webCoRE users to continue enjoying that application operating on Hubitat. Please note, this is NOT a replacement for HubConnect and doesn’t operate the same. Obvious shout out to both incredible products.
The HubiThings Replica application collects the capabilities of the ST device and stores the information in the HE device data section. Then using ‘rules’ to define commands and attributes from both the ST device and HE device establishes mirror functions. The HubiThings OAuth application drives real-time communication between ST and HE and issues those events to Replica. There are native Replica devices handlers and they auto-configure ‘rules’ for you - suggest you use them.
We now have native HE<->ST mirroring support for the following devices with more coming every day:
As an Alpha Tester, it was a privilege to go on this journey with you. This is truly well done, a professional effort at every level, and I’m excited to see it shared with the community at large at last in BETA form.
With HubiThings Replica and a Hubitat Hub, webCoRE is back for SmartThings users!
I have tagged this with “edge_services” even though it’s using the REST API because I think that’s where most people will see it on the quick browse lists when they are looking for third-party integrations, including hubitat.
It should be possible with a combination of Virtual devices and some state mirroring. The question is can HubiThings Replica use a built in Virtual Device. If not you would need to further replicate the state from the Hubireplica device to an official virtual device.
New release Replica 1.3.02 today to support ST event data:[:] and unit:“” arguments.
Replica Lock 1.3.2 updated to support:
Hubitat Lock Code Manager (LCM) application
LCM support has proven difficult with the differences between ST & HE lockCode capability. ST does not expose ‘codes’ so if they are set local or within ST app, HE will not know the new code and update to ‘local’ status. Also, very little documentation (none) on how LCM actually works with data:[:] structure, so YMMV on how well it works for you.
If you use webCoRE, you can see the data:[:] value as shown below (ST lock must support):
New release Replica 1.3.05 supporting ST Scene mirroring, 200+ ST devices. Install instructions here with HPM updated to match.
Support for ST Scene replication.
Support for 200+ ST devices.
Increased OAuth device subscription from 20 to 30.
Replica Scene Knob DH 1.3.0:
Used for ST<->HE Scene mirroring.
NOTE: A SmartThings virtual switch will be created, and it must be added to the SmartThings Scene ‘actions’ in the mobile ST app and set to update the switch to ‘Turn on’ when the scene is triggered as shown:
SAMSUNG DRIVERS+ BY DAVE
Please see here for new @djgutheinz device handlers and information.
New release Replica 1.3.06 supporting ST Natural order sorting for device input dropdown selectors and large device lists greater than 25 items. Install instructions here with HPM updated to match.
Natural Order on device input dropdown selectors.
Natural Order with device lists greater than 25 items using the jQuery DataTables widget.
Replica UI device list warning for HubiThings defined in HE but missing ST device (Not Authorized).
Possible HubiThings Device List errors:
Offline: SmartThings device has been declared offline by ST. This is also available as an event attribute in each Replica Device Handler.
Solution: Check ST UI to determine device status for resolution.
Not Authorized: ST device assigned to the HE device is no longer available.
Solution: Select new ST device for subscription in OAuth application and then return to ‘Configure HubiThings Devices’ and use the ‘Replace’ function to update the HE device [if required].
No Rules: The HubiThings device is missing ‘rules’ to describe mirroring between ST<->HE. This is required when not using Replica Device Handlers as child devices.
Solution: Use ‘Configure HubiThings Rules’ to match ST attributes/commands to HE attributes/commands as required.