How Do I Set Up the Hubitat MakerAPI?
- MakerAPI app not installed or configured
- Devices not selected to expose
- Wrong or missing access token
Problem Description
You want to set up the Hubitat MakerAPI so external systems like Home Assistant, Node-RED, or custom scripts can read and control your Hubitat devices over local HTTP or the cloud. Most setup issues are selecting which devices to expose, using the right local versus cloud endpoint URL, and the access token.
Why This Happens in Real Homes
MakerAPI is how Hubitat talks to Home Assistant, Node-RED, and scripts, and it only works with the devices you explicitly expose plus the right token and endpoint. In real setups people forget to select devices, or mix up the local and cloud URLs.
Add the MakerAPI app, choose the devices, and use the local endpoint at home with the exact token before debugging the external system.
Symptoms
- External system cannot reach MakerAPI
- Devices not exposed to the API
- Token or authorization errors
- Local endpoint works but cloud does not
- Commands accepted but nothing happens
- Only some devices controllable
- Integration stopped after a change
- URL format confusion
Recognize these? Here's what usually causes it.
Common Causes
- MakerAPI app not installed or configured
- Devices not selected to expose
- Wrong or missing access token
- Using the cloud URL locally or the reverse
- Firewall blocking the local endpoint
- Device not supporting the command sent
- App reinstalled, changing the token
- Endpoint path built incorrectly
Most fixes happen in the first 3 steps.
Do not factory reset your hub unless absolutely necessary as this removes all paired devices, automations, and settings. You will need to re-pair every single device from scratch which can take hours for a large setup. Always try a simple restart first.
Tools & Requirements
These tools will help you complete this fix.
As an Amazon Associate we earn from qualifying purchases.
Step-by-Step Solution
Install the Maker API app
In the Hubitat web interface, go to Apps > Add Built-In App > Maker API. This app creates a REST API that allows external applications to control Hubitat devices and receive events over HTTP. After installing, the app shows a configuration page where you select which devices to expose and get the API endpoint URLs.
Select devices and configure access
In the Maker API configuration, check the boxes next to each device you want to expose via the API. Only expose devices that your external application needs — each exposed device adds to the API response payload. Enable or disable specific capabilities: Allow sending device commands, Allow retrieving device info, Allow retrieving all device info. The API URL shown at the bottom of the page includes an access token — treat this like a password.
Test the API endpoints
Copy the API URL from the Maker API app configuration. It looks like: http://[hub-ip]/apps/api/[app-id]/devices?access_token=[token]. Open this URL in a browser — it returns a JSON list of all exposed devices with their current states. To control a device: http://[hub-ip]/apps/api/[app-id]/devices/[device-id]/on?access_token=[token]. Try turning a light on and off to verify the API works.
Set up event subscriptions with postbacks
Maker API can send device events to an external URL via HTTP POST. In the Maker API settings, enter a URL in the Send Device Events to field. When any exposed device changes state (light turns on, sensor triggers, lock locks), Maker API sends a JSON payload to your URL with the device ID, attribute, and new value. This is useful for building custom dashboards, logging to external databases, or integrating with Home Assistant or Node-RED running on another machine.
Secure the API for remote access
The Maker API access token is the only authentication — anyone with the URL can control the hubs. Never expose the API directly to the internet without additional security. For remote access, use a reverse proxy with HTTPS (like nginx) or a VPN into your home network. You can also enable the cloud API endpoint in Maker API settings, which routes through the Hubitat cloud relay with your Hubitat account authentication, but this adds latency compared to local API calls.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If the hub reconnects then drops every few minutes, check for an IP conflict — two devices sharing the same DHCP address fight each other continuously.
Place your hub in a central location in your home, elevated off the floor and away from your WiFi router by at least 3 feet. This provides the best Zigbee and Z-Wave signal coverage to all corners of your house.
Hub disconnections that cycle repeatedly are almost always IP conflicts — two devices fighting over the same DHCP lease after a router restart.
- MakerAPI app not installed or configured
- Devices not selected to expose
- Wrong or missing access token
- Using the cloud URL locally or the reverse
- Firewall blocking the local endpoint
Before you go — try one of these (they fix most cases).
Most popular upgrades chosen by Hubitat Elevation owners.
As an Amazon Associate we earn from qualifying purchases.
Official Manufacturer Manual
Hubitat provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Hubitat Elevation.
Source: hubitat.com
Need More Help? Hubitat Support
Note: The contact information below connects you directly to Hubitat's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.
Accessories owners commonly pair with Hubitat Elevation.
Amazon Smart Plug, Works with Alexa, Simple Setup, Endles...
TP-Link WiFi Extender with Ethernet Port, Dual Band 5GHz/...
Kasa Smart Plug, Matter Compatible, Energy Monitoring, Co...
As an Amazon Associate we earn from qualifying purchases.
