MQTT-connected gateways. Status refreshes every 5 s.
A site is the tenancy boundary. A gateway only ever handles locks in its own site, so assign each gateway to a site before registering locks on it.
| ID | Name | Gateways | Locks | |
|---|---|---|---|---|
| Loading… | ||||
| Gateway | State | Site |
|---|---|---|
| Loading… | ||
| Device ID | Site | State | Version | Last seen | Keepalive | |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Scan for nearby BLE devices from a gateway Pi.
Results from as of
| Address | Name | RSSI |
|---|
Scan the QR code on the lock or enter its ID manually. All online gateways will scan automatically — the one with the strongest signal becomes the primary, with the rest as fallbacks.
Leave blank for first-time registration (factory defaults assumed). Fill in if the device was previously provisioned and the factory reset during removal did not succeed — use the credentials that were stored in the DB at time of removal.
Loading…
Testing tools. The cycle runs against every registered lock: unseal → wait for result → seal → wait for result, repeated as many times as specified.