Dashboard
Total Users
0
Authorized Users
0
Total Rooms
0
Devices
0
Today's OTPs
0
Today's Device Calls
0
Successful Requests
0
Failed Requests
0
API Request Success Rate
| Display Name | Username | Status | Created Date | Actions |
|---|
| Device Name | Room | Entity ID | Device Type | Description | Status | Perform | Actions |
|---|
Connection Parameters
Configure details for local or remote Home Assistant instances.
Dynamically Compiled Endpoints
Below is the list of auto-generated URL paths for every configured device. All client request endpoints require a valid client JWT token set in the Authorization: Bearer [TOKEN] header.
Interactive Link Parameters
Lumi Gateway API Reference Manual
Clean, comprehensive developer integration guide for triggering smart home actions.
Interactive API Link Generator (Testing Helper)
Type values into the parameters below. The URL paths and cURL commands in the reference manual below will update in real-time for easy copy-pasting.
Authentication & OTP Flow
Clients authenticate using their registered mobile number. The system verifies identity via a WhatsApp/SMS One-Time Password (OTP) before granting access to device endpoints.
1. Requesting an OTP
Send a request with the mobile number in the URL path. This sends a 6-digit OTP code to the registered number on WhatsApp.
2. Verifying the OTP
Verify the code received. On success, the response returns a JWT bearer access token.
Controlling Smart Devices
Once authenticated, devices can be triggered directly in one of three ways by targeting a device's [DEVICE_ID] (find these under the Devices tab):
Option A: GET Request (Direct URL Trigger)
Trigger actions by visiting the URL directly in any web browser, or via Tasker task/widget. Adapts automatically based on selected authentication parameters.
Option B: POST Request (Standard API Trigger)
Send a standard POST API request payload. Preferred choice for custom applications and backend-to-backend commands.
Authorization: Bearer [YOUR_JWT_TOKEN] and Content-Type: application/json
What is the cURL Button & Why is it there?
Under the Generated APIs tab, each device endpoint includes a cURL button.
- What it is:
cURLis a command-line tool used to transfer data with URLs. It runs directly inside terminal shells (like Command Prompt, PowerShell, Linux Terminal, or macOS Terminal). - Why it's there: It allows installers and developers to immediately copy a working request command, paste it in their command terminal, and verify if the backend gateway successfully connects to Home Assistant. It serves as a rapid testing and debugging tool without needing to write custom software.
| Timestamp | Mobile Number | Gateway Request API | OTP Status | Details |
|---|
| Mobile Number | Verified OTP | Expires At | Actions |
|---|
| Timestamp | User / Number | API Endpoint | Target Device | Action Triggered | Response Status | Latency |
|---|
Backup & System Restore
Download a single master JSON file containing the entire system configuration, users, rooms, devices, and histories.
Restore the database state from an existing backup JSON file.
WhatsApp / SMS Gateway Config
OTP & Session Expiry Config
Gateway Security Credentials
Server Host & Health Diagnostics
Change Administrator Password
Ensure security credentials are changed periodically.