Skip to content

Home Assistant

Ethan Knox edited this page May 8, 2026 · 4 revisions

HA is the central data plane for sensors and monitoring on Defiant. It cuts across Electrical, Nav, Engine, and Plumbing.

Hardware

  • Raspberry Pi 4 running HAOS, at the nav desk on the shared 5V rail (alongside the other nav-desk Pis — see Nav / Interior).

Sensors / devices

ESPHome on UART (ESP32 + ADS1115)

Used for analog sensors with resistive senders / voltage dividers.

  • Fuel sender (resistive, 240–33Ω Wema-style): see Engine
  • Water flow (rainwater catchment + tank fills): see Plumbing

ESPHome on Ethernet

For locations where WiFi is unreliable or off (e.g. spectrum-quiet engine room work):

  • ESP32 + W5500 module as a wired alternative
  • Device list ❓ (no wired devices currently deployed)

Per-circuit current monitoring (in-progress plan)

Plan covered in Electrical § Per-circuit monitoring. Architecture:

  • ACS758 / ACS770 hall-effect sensors (50A or 100A variants) per circuit
  • ADS1115 ADCs aggregating multiple sensors
  • ESP32-C3 SuperMini → ESPHome → HA

Bluetooth proxies

  • TP-Link UB500 USB BLE dongles via a powered USB hub
  • One dongle extended over USB-over-IP / Cat7 to the closet near the MPPTs (for Victron BLE Instant Readout — see Electrical)

Victron via Cerbo MQTT

  • Cerbo GX → MQTT → HA. Carries SmartShunt and MultiPlus data. MPPT data still pending the BLE proxy path (see Electrical).

Propane tank

  • Capacitive sender on the Gas King tank
  • Template sensor for percentage display: (states('sensor.<sender>') | float / <full_inches> * 100) | round(1) (see Safety)

Dashboard

  • LCARS theme (cb-lcars)
  • Screenshots / view layout ❓

Operational state (Defiant mode / location)

HA is the canonical store for boat operational state — current location, mode (underway / anchored / moored / docked / hauled-out), destination and ETA. The entity layout, the auto-detection automations (shore-power → docked, SoG → underway), and the data flow from Signal K and the Victron Cerbo are documented on Vessel-Management-System.

Per-Pi health metrics

Each onboard Raspberry Pi runs rpi-mqtt-monitor as a */2 min cron job, publishing CPU / memory / temperature / disk / uptime / net throughput as MQTT discovery messages. See Pi-Monitoring for the install recipe and host inventory.

Cross-refs

Clone this wiki locally