Dict-style access to device info is deprecated
As of Home Assistant Core 2026.12, using a DeviceInfo or ChildDeviceInfo like a dict is deprecated. It will stop working in Home Assistant Core 2027.12. Until then, it logs a warning. This is the compatibility layer announced in DeviceInfo is now a dataclass. These uses are deprecated:
- Reading or setting a field by key, like
device_info["name"] - Testing a field with
in get(),keys(),items(), andupdate()dict(device_info)and**device_infounpacking- Comparing a device info with a plain dict
- The
__required_keys__and__optional_keys__attributes
Since Home Assistant Core 2026.11, DeviceInfo is a dataclass with typed fields. The dict-style access was kept so integrations had time to move, and Home Assistant Core no longer uses it. If your custom integration already reads and sets device info fields as attributes, you don't need to do anything.
To check whether you are affected, search your logs for which is deprecated as device infos are dataclasses. Each warning names the use it found, and what to use instead.
as_dict(), comparing two device infos, and the representation of a device info are not deprecated. An entity can also still return a plain dict as its device_info: only a DeviceInfo or ChildDeviceInfo used like a dict is affected.
Read and set the attributes instead:
# Old
device_info["sw_version"] = "1.2.3"
name = device_info["name"]
model = device_info.get("model")
# New
device_info.sw_version = "1.2.3"
name = device_info.name
model = device_info.modelA field which has not been set reads as UNDEFINED, where get() returned None, as explained in unset fields. To test whether a field is set, compare it with UNDEFINED, instead of using in:
from homeassistant.helpers.typing import UNDEFINED
# Old
if "name" not in device_info:
device_info["name"] = "My device"
# New
if device_info.name is UNDEFINED:
device_info.name = "My device"Set each field, instead of using update():
# Old
device_info.update({"model": "My model", "manufacturer": "My manufacturer"})
# New
device_info.model = "My model"
device_info.manufacturer = "My manufacturer"Use as_dict(), instead of keys(), items(), or dict(device_info). It returns the fields which are set:
# Old
data = dict(device_info)
# New
data = device_info.as_dict()To register a device from a device info, pass it to async_get_or_create_from_info, or to async_get_or_create_child_from_info for a ChildDeviceInfo, instead of unpacking it:
# Old
device_registry.async_get_or_create(
config_entry_id=entry.entry_id, **device_info
)
# New
device_registry.async_get_or_create_from_info(
config_entry_id=entry.entry_id, device_info=device_info
)Comparing a device info with a plain dict is deprecated. This is common in tests. Compare as_dict() instead, or compare with another DeviceInfo:
# Old
assert device_info == {"identifiers": {(DOMAIN, "1234")}, "name": "My device"}
# New
assert device_info == DeviceInfo(
identifiers={(DOMAIN, "1234")}, name="My device"
)__required_keys__ and __optional_keys__ come from the time DeviceInfo was a TypedDict. To check whether a field exists, for example to support older Home Assistant versions, use __annotations__. It works both on the dataclass and on the TypedDict of releases before Home Assistant Core 2026.11:
# Old
has_via_device_id = "via_device_id" in DeviceInfo.__optional_keys__
# New
has_via_device_id = "via_device_id" in DeviceInfo.__annotations__If your integration only supports Home Assistant Core 2026.11 and later, you can also use dataclasses.fields(DeviceInfo), which the warning suggests. On older releases, it raises a TypeError.