Nope.
Kevin, when I go to the Other Hub Device Viewer, and select "Alarms", I get null.....even though I have a device in Hubitat and the HE "Other Hub" app with an Alarm capability. Is there something I can check?
Are these the same devices you were originally unable to get Other Hub to detect?
Yes
Can you post a screenshot of the device's "Device Information" section in Hubitat?
Try removing the forward slash from the name.
Hi,
there is no "thermostat" and "lock" device driver for Other Hub integration.
Is it not possible to use a zwave thermostat/lock with Other Hub ?
If that is so, is there another hub link app that supports thermostat and/or locks ?
thanks
There's another app called something like Hub Connect which syncs both ways and most likely supports those devices...
2 Likes
Anyone know how to fix this? I'm new to Hubitat and until I can move from SmartThings I was hoping to use this but it's a pain since none of my Hue devices work due to the / in the network id not being carried over. I'm considering changing the network id's for these devices in Hubitat but I'm concerned that may break something.
Changing the Hue device DNI in Hubitat will break Hubitat's integration because it depends on the DNI being the Hue app integration's app ID, followed by a slash, followed by the Hue-Bridge-assigned device ID.
There are two solutions that could work. In my opinion, the easiest would be just not to share these devices from Hubitat to ST at all. Both platforms have have Hue Bridge integrations that will work for this purpose, so unless you depend on immediate state changes (e.g., for webCoRE piston subscriptions on the ST side), you won't gain anything from doing it this way.
If you do want to share the devices for some reason, HubConnect is an alternative to Other Hub that I know can handle these. I'm not sure if krlaframboise is still interested in maintaining Other Hub (it definitely hasn't been updated in a while), but if so this may indeed be a limitation that might be fixable. Otherwise, there are a few alternative options--hopefully something works for you!
1 Like
Encoding the id in the url would probably solve the problem, but at this point it's not worth spending time on.
I wrote this App when Hubitat was new and didn't support a lot of things so that users could partially transition from ST, but between all the devices/integrations Hubitat now supports and the creation of HubConnect, this App is really no longer needed...
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
