Skip to content

Home Assistant: eero units' status from the DHCP lease logs, after reservations #1228

Closed

Description

@Gerrrt

Show each eero unit's status in Home Assistant for monitoring, with no new firewall rule and no eero cloud. ADR-0019 already declined the cloud integration.

How: all eight eeros take DHCP leases from Kea on morpheus and renew about hourly (≈27 lease lines a day each, measured 2026-10-20). Those lines are already in Loki ({app="kea-dhcp4"}), and Home Assistant's existing reader token can query Loki through the ingest proxy (tested 2026-10-20). A REST sensor per unit, count_over_time(... |= "lease <ip> has been" [2h]) > 0, gives seen in the last two hours. It's coarse (an eero that dies is noticed within about two hours), but it costs nothing new.

Blocker found while testing: the eeros are on pool leases, and network.md is stale for them.

Segment network.md Leased 2026-10-20
Hicks (50) .104, .110, .111 .100, .101, .104
Skids (20) .101, .102, .103 .100, .184, .186
Degens (10) .10, .101 .100, .101

Steps:

  • Kea reservations below each pool: Hicks 10.0.50.11–.13, Skids 10.0.20.11–.13, Degens 10.0.10.11–.12. Map each unit to its reservation from the eero app
    • Done 2026-10-20; all eight units on their reserved addresses by 00:05 on 2026-10-21 (from the lease lines in Loki)
  • network.md: the eight rows at their reserved addresses (OUI only), in the same PR as the package
  • packages/eero.yaml: one binary sensor per unit from Loki, keyed by IP, with no MACs in the repository
  • Optional, later: an ICMP blackbox probe from prometheus for minute-level detection and alerting. That needs its own firewall rows, so it would be a decision of its own

Activity

  1. added this to the Nothing blocks these milestone on Oct 20, 2026
  2. added
    featureA new capability or a change
    sensitivestacks/sensitive on trinity (VLAN 99)
    on Oct 20, 2026
  3. Gerrrt commented on Nov 12, 2026

    @Gerrrt
    OwnerAuthor

    Done. All three required steps were finished and deployed: the Kea reservations on 2026-10-20, then network.md and packages/eero.yaml in #1232, deployed on 2026-10-21. The optional ICMP probe was decided separately as ADR-0112 (docs/adr/0112-probe-the-eeros-by-icmp-from-prometheus.md, #1384 and #1397). Nothing is left on this issue.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureA new capability or a changesensitivestacks/sensitive on trinity (VLAN 99)

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions