You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Home Assistant integration with the eero API, so device joins are events #98
Device joins and leaves on the eero mesh are currently discovered by accident.
Home Assistant can talk to the eero API; wiring that into an event stream would
make them visible.
Where the events should land is the interesting part. The estate already has a
log pipeline that would take them — Alloy accepts network syslog on 1514, Loki
holds them, and security.rules.yaml is where a rule like "an unknown device
joined the trusted SSID" would go. That is a better home than a Home Assistant
notification, because it is the same place every other security signal already
lives.
Note this depends on Home Assistant existing. ADR-0008 places it on the
sensitive tier on a mini PC that has not been bought, so this is blocked behind
that.
Tracked in docs/roadmap.md; filed as an issue so it has a place to be discussed and closed.
Surfaced while going through awesome-selfhosted for the ADR-0008 service build-out (#129–#150) — noting an alternative here rather than opening a duplicate issue.
The interesting property relative to this issue: it is not blocked behind the mini PC. This issue notes it depends on Home Assistant existing (#134), which depends on hardware that has not been bought. NetAlertX needs neither — it needs a host and a network path, and it works by scanning rather than by asking a vendor's API.
That also makes it independent of eero. If the mesh is ever replaced, an integration built on the eero API goes with it; ARP and mDNS do not.
Where it lands is unchanged, and this issue already has the better answer: Alloy accepts network syslog on 1514, Loki holds it, and security.rules.yaml is where "an unknown device joined" belongs. NetAlertX can post there the same way the eero integration would.
The real caveat: it only sees the segments it can reach. On VLAN 99 it would see 99 and nothing else, because default-deny is working. Seeing joins on Skids or Degens would mean either an interface on those segments or new rules — and the terminal property of those VLANs is worth more than the visibility. That is the argument that keeps this an alternative rather than an obvious win, and it may mean the honest scope is "trusted and management segments only".
Worth comparing against the eero route on those terms — one covers every device the mesh knows about but depends on hardware and a vendor API, the other covers only what it can reach but could run today.
Activity
Gerrrt commentedon Aug 26, 2026
Surfaced while going through awesome-selfhosted for the ADR-0008 service build-out (#129–#150) — noting an alternative here rather than opening a duplicate issue.
NetAlertX
GPL-3.0Docker— awesome-selfhostedREADME.md:1588. Scans for devices on the network and alerts on ones it has not seen before.The interesting property relative to this issue: it is not blocked behind the mini PC. This issue notes it depends on Home Assistant existing (#134), which depends on hardware that has not been bought. NetAlertX needs neither — it needs a host and a network path, and it works by scanning rather than by asking a vendor's API.
That also makes it independent of eero. If the mesh is ever replaced, an integration built on the eero API goes with it; ARP and mDNS do not.
Where it lands is unchanged, and this issue already has the better answer: Alloy accepts network syslog on 1514, Loki holds it, and
security.rules.yamlis where "an unknown device joined" belongs. NetAlertX can post there the same way the eero integration would.The real caveat: it only sees the segments it can reach. On VLAN 99 it would see 99 and nothing else, because default-deny is working. Seeing joins on Skids or Degens would mean either an interface on those segments or new rules — and the terminal property of those VLANs is worth more than the visibility. That is the argument that keeps this an alternative rather than an obvious win, and it may mean the honest scope is "trusted and management segments only".
Worth comparing against the eero route on those terms — one covers every device the mesh knows about but depends on hardware and a vendor API, the other covers only what it can reach but could run today.
Generated by Claude Code
Merge pull request #271 from Gerrrt/gerrrt/home-assistant-eero-integr…
Merge origin/main into gerrrt/pull-based-deployment-ec292b
Merge origin/main, and break the ADR-0019 tie main arrived with