Guest QR lasts hours, contractors last days with Friday revocation, staff keep longer grants with audit. One-shot codes stop sticky-note password habits.
When edge actually pays off
Edge pays off when a site must survive hours without uplink: warehouse, checkpoint, locker hall. An office with stable internet often stays cloud-only.
Norms first, AI second
AI explains anomalies well, but without port norms it lacks a baseline. Configure NORMAL/DEVIATION/ALARM first, then enable the operator agent.
Webhooks and idempotency for partners
Partner backends must tolerate retries. HMAC, delivery journal and action idempotency keys are the minimum for a calm SLA.
Go-live checklist for a new site
TLS and passwords, roles, first controller, test grant, Telegram/webhook, clean security banner, and a board-local admin fallback.
Multi-org for a service company
One technician login across many client organizations reduces password chaos. Assign roles carefully: client owners, your operators, viewers for audit.
From scattered relays to one dashboard
Existing Tasmota/OpenBeken devices can join as virtual controllers beside bbxTron. Norms, rules and alerts apply the same way — migration can be gradual.
Building mesh: one uplink, many nodes
Mesh and sidecars adopt nearby boards through a hub, show topology on the server and grow slot count without rewiring every cabinet.
Why edge + cloud beats “cloud only”
Sites lose connectivity. An on-site bbxGrid keeps ports, actions and access cache alive, then syncs events when the uplink returns — service teams stay in control while central analytics continue.
Access control without a vertical lock-in
Issue PIN, QR and BLE like a modern lock UX, then build your own product on the API. Controllers keep an offline cache so doors and lockers still work when the cloud is down.