How It Works
From a tap in the app to a device changing state — on your own network.
IoTiq is built from three parts working together: the app you interact with, the Hub that runs locally in your home or business, and the Zigbee, Matter and MQTT devices themselves. Here’s what actually happens between them.
The Three Parts
App, Hub, devices.
Each layer has one job. None of them depend on a call centre to function.
IoTiq App
View device state, trigger scenes and build automations from your phone or a browser. Sends requests to your Hub, not to a third-party server, for local commands.
IoTiq Hub
Speaks Zigbee, Matter and MQTT natively. Holds device pairings, runs your automation logic, and keeps a local record of device state.
Devices
Sensors, plugs, lights, locks and thermostats — each one paired to the Hub, reporting state changes back as they happen.
Local vs. Cloud
Only remote access needs the internet.
IoTiq is designed so that day-to-day control and automation happen entirely on your local network. The internet is used for the parts that genuinely require it.
Runs locally
- Device pairing, discovery and control
- Automation triggers and actions
- State reporting between devices and the Hub
- Local app access while on your own Wi-Fi
Uses the internet
- Remote access to the app away from home
- Push notifications and mobile alerts
- Software and firmware updates
- Optional cloud backup of your configuration
If your internet connection drops, local automations and in-home control keep working. You won’t be able to reach the app remotely or receive mobile alerts until the connection is restored.
A Typical Sequence
What happens when a sensor detects motion.
A paired motion sensor detects movement and reports the change directly to the Hub over Zigbee, Matter or MQTT — not to a remote server.
The Hub checks the event against automations you’ve configured in the app — for example, “if motion in the hallway after sunset, turn on the hallway light.”
If a match is found, the Hub sends the corresponding command straight to the target device, without waiting on an internet round trip.
The updated state of every affected device is reflected back in the app, whether you’re viewing it locally or remotely.
If the automation includes a notification, the Hub sends it out over the internet to your phone. This is the one step that needs connectivity.
FAQ
Common questions.
Do I need an IoTiq Hub for every device to work?+
Zigbee and Matter-over-Thread devices need a Hub (and, for Matter, a compatible Thread Border Router) to join the same local network as your automations. Check a device’s protocol on our Compatible Devices page.
What happens if the Hub loses power or restarts?
Device pairings and automation configuration are stored locally on the Hub and persist through a restart. Automations resume once the Hub finishes booting.
Can I use IoTiq without an internet connection at all?
Local control and automation work without internet once devices are paired. Initial setup, remote access, mobile alerts and software updates require a connection.
Does every device support every step in this sequence?
It depends on the device’s capabilities and its compatibility status. See the status badge and notes for each model on the Compatible Devices page.
Next
See which devices this works with today.
Every device is labelled with an honest compatibility status — no guesswork.