A home that works together.
NQ2 is a local integrator for devices and applications, with flexible cards, scripts and selective remote access.
One control centre, dedicated applications
NQ2 connects independent applications through MQTT and HTTP. Use cards for everyday actions while dedicated applications handle detailed tasks: pairing Zigbee devices, browsing a Sonos library or reviewing camera recordings.
An integration instance is a provider. It exposes devices that you choose to register in NQ2. Multiple instances of a provider can serve different parts of an installation.
Cards describe what you want to control
A card can combine several devices, show part of one device or work without a physical device. A gate card might bring together a Reolink camera, a Zigbee contact sensor and a relay from another provider. Zones and subzones organise the installation around rooms, floors or buildings.
Cards can record history with a minimum interval between samples. Aggregation can keep daily minimum, maximum and average temperatures, or summaries of energy use, reducing the need to store every reading.
Automations connect events to actions
Device events can trigger scripts when your conditions are met. Cron schedules provide detailed timing and can be enabled or disabled. Scripts can change states, control schedules and make HTTP requests to other services.
For example, a button can start music through Sonos2MQTT, while a presence sensor can stop it after everyone leaves. These scenarios require the corresponding devices, integrations and configuration.
Local first, online by choice
The local installation handles your home. Optional online access exposes selected cards, with configurable actions and value ranges. You could keep full air-conditioning controls locally but allow only switching it off remotely, or limit the remote temperature range.
The described online design sends card states when an online session needs them, while maintaining a service connection. It is not a promise of zero network traffic. External integrations may have their own cloud dependencies.
Access for household members and guests
Administrator, user and restricted user roles provide different scopes. Optional two-factor authentication adds a login check. Guest keys can grant access to selected controls without a conventional login; scripts and schedules can enable or disable access.
Updates are started manually. Review release information, keep backups and apply relevant security fixes. Manual updates give you timing control, but also make maintenance your responsibility.
Strengths and trade-offs
| Strength | What to consider |
|---|---|
| Local control and custom automations | You maintain the host, network and backups |
| Independent integration processes | Shared MQTT, power or network failures can still affect several services |
| Open communication through MQTT and HTTP | Protocol access does not mean the entire product is open source |
| Flexible scripts and cards | Advanced configuration requires technical knowledge and careful permissions |
| Optional, selective online access | The online service depends on connectivity; final pricing is not announced |
NQ2 is currently in preview. Native Apple Home and Google Home integrations are not currently offered. Do not treat possible future features as available today. Preview use is described as free; future online charges are planned to depend on usage, with details still to be confirmed.
Start with a small installation
Choose an installation guide, download the application or installer, then connect one provider and create your first useful card. The core concepts guide explains the building blocks.