Integrations

Supported device models

MQTT topic contracts

Every model declares the topics it listens on and publishes to. The prefix (myhab by default) comes from mqtt.topic.prefix.

The path segments differ per model on purpose — /state, /value, /mower/, /emeters/, /inverter/ — so the patterns cannot overlap when they are matched in order against a single wildcard subscription.

ESP32

The workhorse. Any ESP32 firmware that follows the topic contract above works — commands arrive on .../cmd, and the board is expected to echo its resulting state on .../state.

# myHAB publishes
myhab/esp_terrace/relay/3/cmd        →  ON

# the board applies it and echoes
myhab/esp_terrace/relay/3/state      →  {"port":3,"value":"ON"}

• Availability is reported on myhab/<device>/status; a broker last-will message marks a board offline when it drops.
• Sensor ports publish numeric values on the same /state shape.
• With admin.ports.autoimport enabled, unknown ports create themselves on first message.

MegaD-2561

Multi-port Ethernet I/O controllers. They speak a flatter topic shape (<device>/<port>) and, unlike the ESP boards, also expose an HTTP interface.

myHAB uses both: MQTT for the fast path, and a periodic HTTP ?cmd=all sweep as ground truth. The reconciliation job compares what the controller actually reports against what the database believes, which is what catches a relay that changed state without an echo — and what raises the “device offline” message when the controller stops answering.

ONVIF cameras

Motion and presence events are bridged onto MQTT by an external ONVIF-to-MQTT gateway, publishing on onvif2mqtt/<camera>/motion. myHAB treats those as ordinary port values, so they can trigger scenarios: turn on the drive lights when the gate camera sees movement after dark.

A surveillance UI can be linked from the header via the surveillance.url configuration key — myHAB does not proxy video itself.

NIBE heat pumps

Tested against the F1145-8 EM; the API is shared across the family.

The dashboard widget renders the sensor set plus the heating circuit's supply/return ΔT and the compressor state. Degree-minutes feed the heating automation job.

Huawei solar

The dashboard widget derives the flow diagram from these: PV production, house consumption, grid import and grid export, with directional arrows. Longer-range analysis is a Grafana dashboard embedded on the Solar Reports page.

Weather (Open-Meteo)

Weather is not just a widget: the sunrise/sunset window backs isDay() and isNight(), and precipitation backs isRaining() and rainAmount(minutes) in the scenario DSL. It is also the fallback source for currentExternTemperature() when no outdoor sensor is available.

Segway Navimow

Notifications cover errors and stuck mowers, state transitions, completed runs, low battery or autonomous return, and token expiry. Commands are also callable from scenarios:

mowerCommand([deviceId: 42, action: 'DOCK'])

…and by voice — “start mowing”, “trimite mașina la bază”.

Telegram

Web push and alerting

• Web Push — with VAPID keys configured, in-app messages also arrive as browser notifications on subscribed devices. Muted messages are suppressed at the source, so a mute rule silences the push too.
• OpsGenie — optional alert escalation. Its keys are only read when an alert is actually raised, so leaving them out costs nothing.

Grafana

myHAB stores time series in PostgreSQL, so Grafana can query the same database directly. Two places embed a dashboard back into the UI: the Solar Reports page and the temperature chart card. Configure grafana.url plus the dashboard (and panel) ids — see Configuration.

Adding a new integration

The shape is consistent, and the existing cloud integrations are the template:

1. Add a value to the device-model enum.
2. Declare its topic contract — inbound match patterns and outbound templates — making sure the path segments cannot collide with an existing model's.
3. For a cloud service, write a Quartz job that polls it and publishes to the broker rather than writing to the database directly. Persistence, WebSocket fan-out and the audit trail then come for free.
4. Add the job's toggle and interval under quartz.jobs.*, defaulting to off.
5. Put any credentials in per-device configuration keys, not in code.
6. If it needs a dashboard widget, register it with the configuration keys it requires so the UI can hide it when unconfigured.