Q0RO IoT › Overview
?

Overview

Your LAN devices, directly — no cloud and no Home Assistant in the middle.
Online
0
of 0 devices
Devices
0
no devices yet
Doors
0
no doors configured
Commands
0
recent operations

Doors

Quick access and physical state
No doors yetConnect a relay and an optional door sensor to control an entrance from Q0RO.

Recent activity

Commands, doors and discovery
Nothing yet. Commands and door operations will appear here.

Connect your first device

Q0RO IoT talks to devices on your local network. Choose a protocol, enter the device IP, and Q0RO verifies the connection before saving.

Integrations

Optional adapters — Direct devices keep working without them

Engine

Devices

Relays, locks, sensors and controllers. MAC is the stable identity; IP can change at any time.

Doors

Relay, lock and physical door are three independent states. A relay command is never treated as proof that the door opened.

Safety

Q0RO IoT never replaces the mechanical emergency release of a lock. Keep the lock's own key/override accessible, verify fail-safe vs fail-secure behaviour with the hardware vendor, and test every door with the sensor disconnected before relying on it for access control.

Events

RFID decisions, device commands, MQTT traffic, connections and errors — one timeline.

Integrations

MQTT, Home Assistant and Sonoff LAN are adapters around the same Device Registry. Direct devices never depend on them.

MQTT broker managed

Bundled Mosquitto, per-device accounts and topic ACLs.
Enable MQTTConnect Q0RO to the broker and subscribe to device state and reader events.
Q0RO manages this brokerWrites passwd/ACL into the shared volume. Turn off for an external broker.
TLSEncrypted broker connection.
MQTT is disabled.

Device accounts

One login per reader. Rotate after a key leak; revoke when a device is retired.
DeviceUsernameState

Home Assistant optional

Import devices and keep HA as a fallback channel. Disconnecting never deletes imported devices.

Sonoff LAN eWeLink

Stock Basic R2 without reflashing. Needs the eWeLink device ID and the per-device key.
The devicekey is not exposed by the Home Assistant REST API. SonoffLAN stores it in /config/.storage/sonoff/ on the HA host; copy only the entry you need. Q0RO stores it encrypted and never logs it.

Access control RFID

Cards, readers and server-side decisions. A card UID is never trusted as a secret.

Readers

ESP devices using the Q0RO MQTT protocol.

Cards

Only cards listed here can open a door.

Settings

The appearance, transport and access rules of this IoT node.

Appearance

Theme for this browser. The five Q0RO palettes drive every surface; the preference is shared with the other Q0RO apps.

Account

Signed in.
User
—
Role
—

Network guard

Outbound device access is limited to these private ranges. Everything else is blocked before a connection is opened (SSRF protection). Loopback and the cloud metadata address are always denied unless explicitly enabled.

Door confirmations

Opening a door asks for confirmation by default. Disable it for doors you open often: the command is still logged and still idempotent, but there is no extra dialog. The mechanical release is never affected.

Users

Admins manage the node. Operators control devices and doors. Viewers read state without IP addresses.
UserRoleDevices

About

Product
Q0RO IoT
Version
—
API
/api/iot/…
Realtime
/api/iot/ws
UI
Port 8082
Q0RO IoT is an independent module. It does not require Home Assistant, a vendor cloud or the internet for local device control.

Add device

Q0RO verifies the device before saving it. No simulated devices are created.

Add door

A door combines a relay and an optional door sensor. Keep the mechanical emergency release independent.
Pulse relayRelease the relay after the unlock duration.
Require sensor confirmationFlag the result if the sensor cannot confirm.
Ask before openingShow a confirmation dialog when this door is opened from Q0RO.
Viewers are always read-only.

Add user

Viewers never receive device IP addresses and cannot send commands.

Confirm

Discovery

Devices found on the LAN. Nothing is added automatically: choose a candidate, verify its protocol and save it.

Import from Home Assistant

Q0RO reads the entity list once through the Home Assistant REST API. Imported devices are ordinary Q0RO devices; the session is stored encrypted and used only for these devices.

Add access card

The UID is read by the RC522 reader. Access is decided by Q0RO for the reader's door.
Access all doorsWhen off, select the doors below.
Card enabledDisabled cards are denied immediately.

Reader MQTT credentials

This password is shown once. Copy it into the reader's config.h now; only its hash is written to the broker.
Username
—
Password
—
Status topic
—
Events topic
—
Commands
—
Response
—
Q0RO.IOT

Sign in

connecting