Integration/connectivity monitor

[joshburkard]

Breaking change

Proposed change

The new integration "Connectivity Monitor" helps you keep track of whether devices are online and reachable.

You can use it to monitor network hosts and devices connected through Bluetooth, ESPHome, Matter, or Zigbee. When a device changes status, the integration can notify you and trigger an automation or script after a delay that you define.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: Add connectivity_monitor documentation home-assistant.io#44484
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies a diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hi @joshburkard

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[Copilot]

Pull request overview

This pull request introduces the "Connectivity Monitor" integration, a new Home Assistant integration that monitors the connectivity status of various device types including network hosts (via ICMP, TCP, UDP), ZHA/ZigBee devices, Matter devices, ESPHome devices, and Bluetooth devices. The integration includes alert capabilities with configurable notification and automation delays, a custom Lovelace card for visualization, and comprehensive test coverage.

Changes:

• New integration with network probe, coordinator, and sensor platform modules
• Support for multiple device types (network, ZHA, Matter, ESPHome, Bluetooth)
• Alert handler for notifications and automation triggers with configurable delays
• Comprehensive test suite with 75+ tests covering setup, sensors, and alert logic
• Custom Lovelace card for status visualization
• Manifest and dependency configuration

Reviewed changes

Copilot reviewed 23 out of 26 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
homeassistant/components/connectivity_monitor/	Main integration code with network probe, device helpers, coordinator, and sensor platform
tests/components/connectivity_monitor/	Comprehensive test suite with 1300+ lines covering all integration functionality
homeassistant/components/connectivity_monitor/www/	Custom Lovelace card for displaying connectivity status
requirements_all.txt, requirements_test_all.txt	Dependencies (dnspython, icmplib) added
homeassistant/generated/	Integration metadata files updated
CODEOWNERS	Ownership assigned to @joshburkard

[Copilot]

Pull request overview

Copilot reviewed 23 out of 26 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 23 out of 26 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 24 out of 27 changed files in this pull request and generated no new comments.

[joshburkard]

i added migration code for each needed type of device

Stale

[Copilot]

Pull request overview

Copilot reviewed 24 out of 27 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 24 out of 27 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 29 out of 32 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 29 out of 32 changed files in this pull request and generated no new comments.

[joostlek]

IMO, I think this isn't something that should be a separate integration, but rather something that works in core itself

[joshburkard]

IMO, I think this isn't something that should be a separate integration, but rather something that works in core itself

I do not see an existing core feature that provides this as a unified monitor. Core already has pieces of it: Ping for ICMP reachability, ZHA last_seen and availability, Matter node availability, ESPHome availability, and Bluetooth unavailable tracking. TCP exists, but requires a defined payload and manual configuration. What imo is missing today is a generic, user-configurable layer that brings those signals together, adds network checks beyond ICMP, and exposes them through one monitoring and alerting workflow. That is the gap this PR is trying to fill.