Hubitat Integration

Today’s 3.1.0 release introduces an official Hubitat integration. This integration will connect both locally & through the cloud using the Maker API. If you choose to enable both, it’ll prefer the local connection over the cloud connection & use that when available.

All of the fields the Home Remote app needs from you can be found on the Maker API setup page. What’s on that page should match what you give the Home Remote. The page doesn’t list them all specifically as some are embedded in the URLS. For example, let’s look at the screenshots from the Hubitat docs. For that particular install we can see that the ‘App Id’ is 37 & the ‘Access Token’ is that long string of characters at the end beginning with ‘073e93…’. The ‘Hub Id’ will be in the Cloud URLS section. It’s the value sandwiched between /api/ & /apps/. There isn’t a checkbox to enable local access in the Home Remote. To enable local access, just supply an IP address. Leave the IP address blank if you’d like to disable local access.

The integration includes access to all of the devices you’ve authorized on the Maker API setup page. It also includes access to your location’s Mode. When you sync your devices you’ll notice a “Mode” device automatically generated as well.

Any comments are questions, please let me know!

Here’s a link to Hubitat’s Maker API Install instructions.

Installing Maker API

  1. From the Hubitat Web Interface select Apps

Install Built-In App 2.0.png

  1. Choose Maker API from the list of Hubitat Elevation® Built-In Apps.

Install Maker API.png

  1. You can enable Logging if you want to see detailed information in the logs. Remember to open up logs in another tab.

Enable Logging Maker API.png

  1. Select the devices you want to authorize for this API. NOTE : Only the devices you select will be accessible via the endpoints.

Maker API Select Devices.png

  1. Select Update
  2. Next, you will see URLs to get you started. Each endpoint URL is made up of the following segments: http:// [hub ip address] /apps/api/[app id] /[endpoint path ?access_token=[access_token]
  • NOTE : Your access token is an Authorization Token, similar to a username and password. Anyone with this token can access these endpoints. To reset your access token, you will need to remove and re-add the Maker API app.

Maker API endpoints.png
7. Press Done


Great news! Thanks Bill!

I have been using the community built integration and just made the switch to this. Seems to be working well with the short time testing so far! :metal:

Note for those switching like me: I was able to do it effortlessly by deleting the community built integration and then adding the official integration. The device names came in the same so none of my bindings broke.


Oh c’mon! I spent 2 hours yesterday getting the community version up and running and now wake up to this today. :grinning:

Can’t wait to give this a try. I recently purchased a Hubitat hub for testing purposes as my Wink hub just recently became a piece of garbage.

Thanks Bill!


Bill, thanks for the update.

I was able to get working. For other users, your instructions could be clearer if you had a screenshot of where the App ID was located in the Maker API, just highlight and circle. Also, it wasn’t clear that you need to turn on the cloud / remote access to generate the other code.

I have now completely migrated from ST to HE. There was actually little work to do in Home Remote since I used the exact same device names when I moved each device over.

So far, I haven’t really had any issues. Seems rock solid! I’ve never been a fan of “Clouds”. Someone else’s cloud at least…I can build my own damn cloud haha. I live in the middle of nowhere, on a mountain, and I lose internet often. With HE everything stays local and the speed is SO much faster. I can tell easily. I tested the cloud connection while I was out at work and it worked well, but I didn’t tinker with it to much.

I’m going to miss webcore but I think I’ll find work a around for some of my complicated pistons (rules).

1 Like