Your Iotics panels. Your Home Assistant dashboard.
Discover your devices, control supported switches and fans, and bring them into your Home Assistant scenes and automations.
Installation · Supported features · Troubleshooting · Report an issue
An unofficial, cloud-connected integration for Iotics panels. Sign in with your existing Iotics account to discover devices and receive MQTT updates. No separate MQTT broker is required.
Before you install You need your Iotics account and a private
iotics_app_profile.jsonconnection file. The profile is not included in this repository, and this project does not currently provide an automated extractor. Email and password alone are not enough to complete setup.
| Feature | Current support |
|---|---|
| Account connection | Sign-in, automatic device discovery and reauthentication |
| Switches and plugs | On/off for channels reported as bN |
| Fans | Power control; four speed levels for eligible non-BLDC fans |
| BLDC fans | Power only — speed adjustment is not supported |
| Device updates | MQTT feedback, reconnects and availability detection |
| Scenes and automations | Use the entities in Home Assistant's native tools |
Keep using the Iotics app for pairing, curtains, dimmers, BLDC speed, firmware updates and child locks. Importing vendor scenes and schedules is not supported.
Validation status: Account login, discovery, MQTT connection and hardware-status feedback were checked live. No on/off or speed commands were sent during validation, so physical actuation remains unverified.
Open HACS → ⋮ → Custom repositories and add:
| Setting | Value |
|---|---|
| Repository | https://github.com/KANDIYARR/iotics |
| Type | Integration |
Find Iotics in HACS and select Download.
Prefer manual installation?
Download the latest release source and copy its custom_components/iotics folder into your Home Assistant configuration folder. Then continue below.
Copy iotics_app_profile.json into the same folder as configuration.yaml:
Home Assistant configuration folder
├── configuration.yaml
├── iotics_app_profile.json ← Your private connection profile
└── custom_components/
└── iotics/
├── manifest.json
├── config_flow.py
└── brand/
└── icon.png
This is the configuration folder on the machine running Home Assistant. In a container, it is /config; on the host, use the folder mapped to that location. If you use File editor, upload the profile beside configuration.yaml.
The profile contains app connection settings recovered from the user's own Iotics 4.9 package during local analysis. Keep it private. Do not upload it, account credentials or configuration backups to GitHub.
- Restart Home Assistant.
- Open Settings → Devices & services → Add integration.
- Search for Iotics.
- Enter your Iotics email and password.
- Wait for discovery and hardware status, then add the available entities to your dashboard.
You can rename entities, assign rooms, and use supported controls in Home Assistant scenes and automations.
| Stage | What happens |
|---|---|
| Sign in | Your Iotics account supplies an access token and device list. |
| Connect | The integration subscribes to MQTT topics for devices returned by your account. |
| Show state | Cloud values are provisional until the channel sends hardware feedback. |
| Send a command | The displayed state updates immediately after publishing, marked as assumed. |
| Keep current | Device discovery refreshes every 5 minutes; status queries run every minute. |
Commands are not queued for replay while offline. Controls update immediately after a successful local publish, like the Iotics app. The displayed state is assumed, not proof of physical actuation. No hardware-confirmation timeout is raised. Later hardware feedback overrides the displayed state; actual send failures still raise an error and preserve the previous state.
| What you see | What to check |
|---|---|
| Missing or invalid profile | Put iotics_app_profile.json beside configuration.yaml, not inside custom_components. |
| Authentication failed | Verify the same credentials and account verification in the Iotics app. |
| Device unavailable | Check the panel in the Iotics app and outbound HTTPS/WSS access on port 443. Availability requires valid hardware feedback. |
| No fan speed slider | Expected for BLDC fans in this version. |
| Old confirmation timeout still appears | Update to version 0.1.4 or newer and restart Home Assistant. |
| Logo missing in HACS search | Some HACS versions use the central branding service instead of the bundled icon; see below. |
About the logo
Home Assistant 2026.3+ supports the icon bundled in custom_components/iotics/brand/icon.png after installation and restart. The image also appears on this README and the HACS repository details page.
Some HACS search lists still use the central branding service and may show a placeholder. This repository cannot override that URL. See Home Assistant brand-image support and the HACS tracking issue.
Account storage and diagnostics
Account credentials are stored in Home Assistant's configuration-entry storage. Protect your configuration backups. Diagnostic exports omit account identifiers, device tokens and connection credentials.
Version 0.1.4 removes the feedback wait. Switch and fan power controls update immediately after sending; supported fan-speed commands send power first when needed, then the speed. Home Assistant marks the state as assumed until channel feedback arrives. Broker command echoes do not count as hardware feedback.
If a physical device does not respond, download diagnostics from the Iotics integration menu under Settings → Devices & services. Counters show sends, assumed updates, send failures, and incoming feedback without credentials or device tokens.
23 offline tests passed using Python 3.12.14 and Home Assistant Core 2024.11.3. This is a compatibility-test baseline, not a recommendation to install an older Home Assistant version. Current production installation compatibility has not yet been verified.
python -m pip install -r tests_ha/requirements.txt
python -m pytest tests_ha -qGitHub Actions run Home Assistant's hassfest and HACS validation. The central brands-catalog check is excluded because this integration bundles its icon locally.
Found an issue? Open a GitHub issue with your Home Assistant version, device model and a description of what happened. Remove credentials and private connection settings from any logs or screenshots.
Maintained by Vinoth Sakthivel
vinoth@kandiyar.com · MIT License · Releases
This project is independent of Iotics and is available as a HACS custom repository, not part of HACS's default catalog. The MIT license covers this project's code. The Iotics logo and trademarks remain the property of their respective owner and do not imply endorsement.