morfSensor

Read in another language: English (this document) · Français.

Autonomous sensor service — presence (LD2410C) and more — exposed over a local HTTP API and announced on the LAN (morfBeacon).

morfSensor keeps the hardware (presence radar, weather probes, distance, light…) in a separate service, so an application (such as morfDashboard) only has to query an HTTP API instead of driving the sensor itself. Adding a new sensor type touches neither the HTTP server nor the consumers: you write a class and register it.

Principle

    Hardware sensor                  morfSensor (service)              Consumer
  ┌──────────────────┐            ┌───────────────────────┐         ┌──────────────┐
  │ LD2410C (UART)   │──frames──▶ │ ISensor → ModuleRegistry│─HTTP─▶ │ RaspberryDash│
  │ (and others…)    │            │ HttpServer        │        │ (wake screen)│
  └──────────────────┘            │ + morfBeacon heartbeat  │─UDP──▶ │ (discovery)  │
                                  └───────────────────────┘         └──────────────┘

• The consumer drives no hardware: it does a GET /presence (or /sensors) and reads JSON.
• Extensible: each sensor is an ISensor class. The LD2410C and a simulated (mock) sensor ship in the box; temperature, humidity, distance, light… follow the same pattern.
• Cross-platform: Linux x86-64, Windows, ARM64 (Raspberry Pi), like morfBeacon / morfUpdate.

HTTP API (port 8788 by default)

Route	Response
GET /presence	{ "present": bool, "sources": [...], "ts": ... } — polled by the dashboard
GET /sensors	{ "sensors": [...], "count": N, "ts": ... }
GET /sensors/{id}	one sensor's reading (404 if unknown)
GET /status	morfBeacon-compatible (app, host, version, state, uptime_s, metrics, ts)
GET /healthz	{ "status": "ok" }

Reading example (generic, whatever the type):

{ "id": "presence-salon", "kind": "presence", "available": true,
  "state": "ok", "ts": 1784206069,
  "values": { "present": true, "target_label": "moving",
              "moving_cm": 142, "static_cm": 0, "moving_energy": 78 } }

Build

Only needs Qt 6 (Core, Network; SerialPort for UART sensors). morfBeacon is bundled (vendored under third_party/morf/beacon, statically linked), so the build depends on no external repository — it works first try on Windows, Linux x64 and Raspberry Pi (ARM64).

cmake --preset mingw        # or linux / linux-arm64
cmake --build --preset mingw

Qt SerialPort is the only optional dependency: if absent, the LD2410C driver is disabled (core + mock sensor still build) — a warning, never a build failure. On the Raspberry Pi: sudo apt install libqt6serialport6-dev.

To refresh the vendored morfBeacon from its source repo: scripts/sync-morf.sh (or scripts\sync-morf.ps1 on Windows).

Run

# Instant demo, no hardware nor config (simulated sensor):
./build-mingw/service/morfsensor.exe
curl http://127.0.0.1:8788/presence

# With a real configuration:
./build-mingw/service/morfsensor.exe --config config/morfsensor.json

See config/morfsensor.example.json for the configuration (HTTP port, morfBeacon announce, sensor list).

Install as a service (Raspberry Pi)

# Any platform: Linux, Windows, Raspberry Pi
sudo ./service.py install      # build if needed, install, start
sudo ./service.py update       # rebuild, replace the binary, restart
sudo ./service.py uninstall    # deregister, keeping your configuration
./service.py status            # what the system says about it

One entry point everywhere. What this service is — its name, its directory, its configurations — is declared in service.json beside it. The four install steps live once for the whole parc; only the service manager differs by platform.

The former scripts/linux/ and scripts/windows/ scripts still work, unchanged.

Documentation

French documentation in docs/fr/: architecture, HTTP protocol, adding a sensor type, LD2410C wiring.

License

GPL-3.0-only — © 2026 morfredus (Frédéric Biron).