Deprecation warning: Invalid via_device=None in device_registry.async_get_or_create (will break in 2025.12)

[flown-the-coop]

Your exact log entries (copy-paste them).

Logger: homeassistant.helpers.frame
Source: helpers/frame.py:350
First occurred: 3:08:14 PM (4 occurrences)
Last logged: 3:08:14 PMDetected that custom integration 'alarmdotcom' calls device_registry.async_get_or_create referencing a non existing via_device ('alarmdotcom', None), with device info: {'identifiers': {('alarmdotcom', '102898116-127')}, 'manufacturer': 'Alarm.com', 'name': 'Panel', 'via_device': ('alarmdotcom', None)} at custom_components/alarmdotcom/alarm_control_panel.py, line 50: async_add_entities(. This will stop working in Home Assistant 2025.12.0, please create a bug report at https://github.com/pyalarmdotcom/alarmdotcom/issues
Detected that custom integration 'alarmdotcom' calls device_registry.async_get_or_create referencing a non existing via_device ('alarmdotcom', None), with device info: {'identifiers': {('alarmdotcom', '102898116-127')}, 'manufacturer': 'Alarm.com', 'name': 'Panel', 'via_device': ('alarmdotcom', None)} at custom_components/alarmdotcom/binary_sensor.py, line 92: async_add_entities(. This will stop working in Home Assistant 2025.12.0, please create a bug report at https://github.com/pyalarmdotcom/alarmdotcom/issues
Detected that custom integration 'alarmdotcom' calls device_registry.async_get_or_create referencing a non existing via_device ('alarmdotcom', None), with device info: {'identifiers': {('alarmdotcom', '102898116-1200')}, 'manufacturer': 'Alarm.com', 'name': 'Side Door Lock', 'via_device': ('alarmdotcom', None)} at custom_components/alarmdotcom/lock.py, line 60: async_add_entities(. This will stop working in Home Assistant 2025.12.0, please create a bug report at https://github.com/pyalarmdotcom/alarmdotcom/issues
Detected that custom integration 'alarmdotcom' calls device_registry.async_get_or_create referencing a non existing via_device ('alarmdotcom', None), with device info: {'identifiers': {('alarmdotcom', '102898116-127')}, 'manufacturer': 'Alarm.com', 'name': 'Panel', 'via_device': ('alarmdotcom', None)} at custom_components/alarmdotcom/button.py, line 62: async_add_entities(. This will stop working in Home Assistant 2025.12.0, please create a bug report at https://github.com/pyalarmdotcom/alarmdotcom/issues<

Your Home Assistant core version (check Settings > System > About).

Installation method
Home Assistant OS
Core
2026.3.1
Supervisor
2026.02.3
Operating System
17.1
Frontend
20260304.0<

The version of the Alarm.com integration

v3.0.15<

[ibasebcast]

It looks like this warning is coming from how the integration registers devices with Home Assistant. In the current implementation, several entities reference a via_device that does not exist (('alarmdotcom', None)), which triggers the device registry warning shown above. Home Assistant has indicated that this behavior will stop working in a future release.

Because of issues like this and other recent Home Assistant changes, I’ve started maintaining a fork of this integration where I’m working through updates to bring the codebase back in line with current Home Assistant requirements. This includes correcting device registration, addressing entity availability issues some users have reported, and improving overall stability.

My plan is to continue fixing existing issues and expanding functionality as time allows.

I also work directly with Alarm.com systems through a security integration business and have partner-level access to their platform, which allows me to test against real systems and validate behavior more thoroughly than most users are able to.

If anyone is interested in following progress, testing updates, or contributing, the maintained fork is available here:

https://github.com/ibasebcast/ha-alarmdotcom

Updates will be pushed there as fixes and improvements are completed.