Use cases

Smart Buildings

Lighting, HVAC, access, and occupancy coordinated as one system instead of ten — one Bobulator per floor instead of a closet full of gateways.

The average commercial floor runs lighting, HVAC, access control, and occupancy sensing as four independent systems that barely speak. Each has its own gateway, its own app, its own idea of what “the third floor” means. The Bobulator makes them one system with one rule set — and replaces a closet full of single-protocol gateways with a single device per floor.

The scenario: an office floor waking up

It’s 06:40. The first badge taps the lobby reader. Across the next twenty minutes the floor comes to life, zone by zone, ahead of the people — never the whole floor at once, never an empty corner burning power:

rule "zone-precondition-on-approach":
  priority: 30
  when:
    - access.badge.scan within 2min
    - occupancy.zone(badge.destination) == EMPTY
    - time_of_day() in "06:00-09:00"
  then:
    - hvac.zone(badge.destination).setpoint = 71
    - light.zone(badge.destination).fade_to(60%, over=90s)
    - log.info("zone-precondition", zone=badge.destination)

A badge tap doesn’t just unlock a door — it tells the engine who is heading where, and the engine preconditions only that zone’s HVAC and lighting. Occupancy sensors confirm arrival; if nobody shows in ten minutes, an energy-saver rule (lower priority) quietly stands the zone back down. Access, HVAC, lighting, and occupancy are four inputs to one decision instead of four systems guessing independently.

Why it matters here

  • One device per floor. Twelve channels and three radios replace separate BMS, lighting, and access gateways. BLE 5.3 for occupancy beacons, Wi-Fi 6 for the building network, LoRa for long-run sensors in the parking structure.
  • Energy that follows people. Preconditioning by badge destination, not by blanket schedule, is the difference between heating one occupied zone and the whole empty floor.
  • Deterministic access. Door interlocks resolve through the same priority engine as everything else — a fire-alarm unlock always outranks a schedule.
  • Audit trail built in. Every access event and actuation lands in the tamper-evident log — useful when facilities and security need the same source of truth.

Roll it out floor by floor as a mesh, or add the cloud layer for portfolio-wide energy analytics. Next door, the same logic runs a factory floor.

copied!