These are the instructions for removing the old version and installing the new one.
Make sure you updated the App in Hubitat, SmartApp in SmartThings and all the SmartThings DTHs. Everything is located in that new OtherHub2 Repository.
If that doesn't fix those errors let me know.
Thanks … that didn’t help but I figured it out. Turns out I was using a super old firmware version 1.0 (I have Hub #3) that doesn’t suppprt the api call used in your code. So the fix was to update the firmware, reset the OAUTH on the Hubitat side, and then refresh the endpoint push from Hubitat you ST. You might add the firmware update to your install instructions.
Thanks for writing this. It works great. I also appreciate the example code for accessing Hubitat from cloud that I can use in my HousePanel development.
This is great! I finally got some virtual devices from Hubitat created in ST via this app/DTH set and it’s working great, allowing me to keep my logic in its existing ST SmartApps/Routines/webCoRE pistons until I figure out how to re-implement the same in Hubitat, and it also allows me to continue using ST to compensate for missing features (e.g., voice control beyond switches).
Would it be possible to add an “Other Hub Thermostat” as a possibility? Hubitat’s Alexa integration doesn’t work with thermostats at all now, but SmartThings’ implementation of this is mature, so it would be great to move the device itself to Hubitat while still allowing ST to manipulate it. (If not, I’m trying to figure out how to use MQTT to do the same, but my issue is that any “virtual thermostat” DTH I can find doesn’t seem to respond to commands to change its setpoint except via the device tiles.)
None of the virtual devices work for me in AVS unless they’re in a group. I don’t imagine Alexa Groups support thermostats, so you’re going to need a device specific driver.
Do you mean even physical thermostats? I have my Zen Thermostat paired to ST and integrated in Alexa, and it works-as is, but I also have a “Thermostat” group with just this device in it so the name is easier for me to say. I’m pretty sure both work. I don’t think it’s all virtual devices either, as I have virtual switches that Alexa works fine with as well (but not virtual “momentary” switches, as I’m guessing the capabilities they implement do not include ones the ST integration looks for). In any case, Hubitat doesn’t support anything besides switches right now, so long term, that’s what I’d really like to see be improved. I was just hoping I could use OHB to bridge the gap in the meantime without needing to keep my ST ZigBee network up.
EDIT: Didn’t realize you meant virtual switches from Hubitat rather than ST. I haven’t tested that, so you could be right.
If I add a virtual switch from ST to Alexa, it works. If I add a virtual switch from Hubitat, it doesn’t work until I put it in a group. I don’t know if everyone is experiencing this, but I’m not the only one.
Not a big deal to me, as we have been told there is a skill coming post launch and a new Alexa Wizard app coming. Those together should address the issues of devices not being discovered by Alexa that some are experiencing, the group requirement that I and others are experiencing, and allow groups for Alexa to be created within the app.
I use Alexa with virtual momentary buttons all the time and they work great. It is how I control my Harmony hub since I set it up before they had a stable native integration and I am a believer in leaving stuff alone that works well.
OK, maybe something has changed since I tried, or maybe I’m just using an weird DTH for mine. I’ll have to try again—though I really hope Hubitat just gets improved Alexa support soon, anyway. 
I installed my hubitat a few hours ago. Only device is a Xiaomi original motion (a/k/a body) sensor using @veeceeoh 's driver. Motion shows in Hubitat. Went through the OH installation and didn't have any obvious errors. The ST app shows the OH-Xiaomi device and events are ACTIVE or INACTIVE in accordance with the actual device. So far, so good.
My problem is that no ST smartapp sees the OH-Xiaomi as an eligible motion detector. I don't think I have any useful logs since the device is seemingly functioning. Here is the device:
Did I miss something that declares the device to ST smartapps?
I was about to tell you that only the OH bridge should be using the Other Hub Device dth…and then I noticed that my Zwave motion detector was also using this DTH. My Iris motions all show as Other Hub Motion Sensors. I changed the Zwave dth to OH motion in Smartthings and it seems to work fine. Give it a shot.
Thanks, @stephack! I changed the ST DTH from Other Hub Device to Other Hub Motion Sensor and all is good. Just didn’t occur to me to specifically set the correct child. (Bad enough having to learn Hubitat, but now I have to re-learn ST stuff that I haven’t used in a couple of years.)
I just want to point out that the "Other Hub Bridge" was part of the original integration and that code should be deleted from SmartThings because it no longer works.
If you added the original code through the GitHub integration you should delete those devices and use the code in my Other Hub GitHub Repository.
If you installed all of those DTHs before installing the SmartApp and that device supports the Motion Sensor capability, it should have created it as an Other Hub Motion Sensor.
I just finally got a chance to install OH 2.0, and I had the same thing happen to me - my motion sensor got a "Other Hub Device" DTH assigned to it, and my temperature/humidity sensors got the Other Hub Motion Detector" DTH assigned to them. I followed the the install instructions given in post #1, in the order they are listed.
My fault for not reading through the entire thread first, but can I make a suggestion? Perhaps move "Installing the Child Device Type Handlers" section to the top of the instructions if those ST DTHs should be installed first?
Otherwise, this is fabulous, and as I'm using your Dome Alarm DTH and plan to see if your Simple Event Viewer App will work on Hubitat, I've sent my support!! Thank you so much for this.
I created a virtual switch in Hubitat. I checked the box to add it to ST in the pusher app and it appears fine, ST shows it at OH Switch.
Problem is if I try to change the switch on the ST side, it sticks on ‘TURNING ON’ (or OFF) and does nothing on the Hubitat side. I can control it on Hubitat and it works fine.
I've moved the Driver part to the top of the instructions. Thanks for the suggestion.
Did you select "Switch" as one of the capabilities to use for Real-time integration?
Yes
I had a similar issue when I migrated from the first version of the integration; somehow (due to my error) on the ST side the virtual device was using the wrong version DTH for the OH-virtual switch. You should be able to verify what handler it is using by looking at the device in the IDE. It should show a February date in the code.
2.01 code, dated February. I never had installed the earlier version anyway. Just got the hub 2 days ago.
I got Hubitat recently and just added 1 device to start with. I used this solution and it worked without an issue between ST and Hubitat. However, Google home and Alexia didn’t pick them up initially. I opened the Google Home app and it seemed to update on it’s own. I assigned the device to a room, done. I opened the Alexia app and removed the old device listing then had it find new devices. Found it without a problem.
Thanks for the solution.
Download the Hubitat app
