What the beez miniBMS is
A portable Windows supervision platform: a FastAPI backend, a Mosquitto MQTT broker,
a per-project SQLite historian, and a live web console on
http://localhost:8000. Customers are tenants; each building
is a project whose slug is the riza1 site id and the first MQTT topic
segment (project/system/equipment/point). One EDE 2.3 file drives the entire
onboarding of a project, usually packaged as a one-zip bundle by the miniBMS onboarding
Claude Project.
The console has five tabs: Points (the live table), Trends (the analytics workbench, plus time in state and time in range), Sites (per-building communication health, pause and resume), Graphics (SVG equipment mimics), and Admin (Projects, BACnet, MQTT, Users, and Audit, superadmin and admin only).
The two run modes
| Mode | How it runs | When to use |
|---|---|---|
| Service mode | The installer registers two autostart services, beez-mqtt (the broker)
and beez-minibms (the platform, via run_server.py). They start
at boot in the background (session 0) and are managed with
net start / net stop or services.msc. |
Production machines that should come up by themselves after a reboot. |
| Console mode | run.bat starts the platform in a visible window; Ctrl+C stops it. |
Development and troubleshooting, when you want the log in front of you. |
run.bat detects the conflict, shows
which process holds the port, and offers to stop it; a background service instance needs
administrator rights, which update.bat handles by elevating itself. To use
console mode on a machine that has the services, stop and disable them first:
sc stop beez-minibms then sc config beez-minibms start= disabled
(same for beez-mqtt if you also run the broker yourself).Where things live
| Path | Contents | Touched by updates? |
|---|---|---|
app\ web\ bridge\ tools\ broker\ docs\ examples\, root
.bat and .py files | Platform code | Yes, replaced |
data\minibms.db | Tenants, projects, users, points, bridge assignments | No, never |
tenants\<tenant>\<project>\ | Per-project history.db, graphics, source EDE, onboarding notes | No, never |
config.json | Broker address, bridges, token secret, power factor, storage policies | No, never |
Backing up a project is copying its folder. Schema migrations run automatically at start, so older data directories are always brought current.
Read next
Installation for a new machine, Updating for new versions, Command reference for every CLI command, and Backup and recovery for moving data between installations. The quick team guide stays at /help.html.