Start with a known poll template, one device on the bus and a short cable. Only after stable values add norms and alerts in bbxGrid.
OTA discipline for a device fleet
Do not update the whole fleet at once. Start with a bench unit and one canary, then a group. Keep the previous image ready for rollback.
When to pick Main instead of DIN or LoRa
Main is the general site board: lockers, doors, I/O expansion, mesh and readers. Choose DIN for a single power channel with metering. Choose LoRa when Wi‑Fi is unreliable and you need a remote uplink.
Rule of thumb: when unsure and power is available on site — start with Main + sidecar.
The offline-first habit
Set the local admin password, codes and a test card before pointing the board at a server. You always keep a fallback control path if the cloud is down.
Where to place a mesh hub
Place the hub where uplink exists and near the geometric center of neighbors. Metal cabinets and thick walls hurt more than expected — one extra node beats chronic offline states.
Offline card cache: what really works
After issuing a grant on the server, wait for sync to the board. Test unlocks with uplink disabled — that is the incident behavior your client will see.
Standalone first — cloud when ready
bbxTron is built to run doors and lockers from power-on: local UI, on-device credentials, mesh and sidecar without a server. bbxGrid adds organizations, analytics and AI later — without rewiring.
Choosing a model: Main, ETH, DIN or LoRa
Main is the general site board. ETH fits cabled cabinets. DIN covers single-channel power plus metering. LoRa serves remote gates. Sidecar cheaply expands slots next to Main.
Mesh without rewiring
One online controller hubs neighbors and sidecars while bbxGrid shows topology and status — a common path for warehouses and utility rooms.