Frequently Asked Questions

Yes, and it’s a worst-case number, not a median. The deterministic real-time path — normalize, decide, schedule transmit — runs on a dedicated Cortex-M7 at a fixed 1 kHz tick, isolated from the web stack on the ESP32. A slow API request literally cannot delay a decision. See the per-layer budgets in the architecture.

Yes. BLE 5.3, Wi-Fi 6, and LoRa each have independent antennas and run concurrently. Typically LoRa carries long-haul, low-rate traffic while BLE and Wi-Fi handle the low-latency path — but you route any decision to any radio with a one-line rule.

Every decision is made at the edge, so the device keeps running. In a mesh or hybrid topology, only cloud analytics and cross-site coordination pause; they sync automatically on reconnect. There is no cloud dependency on the critical path.

No firmware. Behaviour is a small declarative YAML DSL — when/then blocks over the normalized signal space. You push rules to one device or the whole fleet over the REST API and they hot-reload without a reboot. Start with the Rule DSL reference, then see the engine for the conflict model and timing path.

The engine resolves deterministically by a fixed three-key sort: explicit priority, then signal freshness, then specificity. Every resolution is written to the audit log with both contenders and the deciding key. It never silently guesses.

Optionally, yes. The Cortex-M7 runs quantized TFLite Micro models (up to 256 KB) with sub-millisecond inference, fully offline. The model’s output is just another input your rules can reference, e.g. when: ml.anomaly_score > 0.8.

A mesh scales from 3 to roughly 200 devices, gossiping shared state and rule updates with sub-2-second propagation. Beyond that, layer the edge + cloud hybrid and run multiple meshes across sites.

Firmware updates are signed with A/B partitioning and automatic rollback. The audit log is hash-chained, so a deleted record is detectable. On-device ML means sensor data never has to leave the building. For regulated environments, the log is your evidence trail.

The WB-1 lists at $1,490; a five-node pilot with onboarding and a rule workshop is $9,800. Stock units ship in two business days. The complete SKU table, current 50-seat cohort status, and optional-cloud boundary are on the pricing and availability page.

A single hub is a power drop and a config push — minutes. A mesh is the same per node plus auto-discovery. Most pilots are orchestrating something real on day one and tuning rules by week one.

That’s the point of the open REST + WebSocket API and the YAML rule layer. Outputs address actuators by a stable domain.zone.id path, so the Bobulator drives anything from a relay board to a cloud ingress without vendor lock-in.

See the changelog for shipped v1.0 features and what’s coming next — multi-site rule templates, a richer ML model zoo, and expanded LoRa mesh routing lead the list.