The problem

I moved away from the custom Volvo Integration (thomasddn/ha-volvo-cars) and adopted the now officially supported version in HA core.

However —unless what is documented on the website, I don't get a sensor for the engine running.

This is a useful sensor as I was using this to trigger certain automations. E.g. auto-lock car after x minutes.

What version of Home Assistant Core has the issue?

System Information version | core-2025.12.2 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true container_arch | aarch64 user | root virtualenv | false python_version | 3.13.9 os_name | Linux os_version | 6.12.47-haos-raspi arch | aarch64 timezone | Europe/Brussels config_dir | /config

Home Assistant Community Store

GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok HACS Data | ok GitHub API Calls Remaining | 4988 Installed Version | 2.0.5 Stage | running Available Repositories | 2470 Downloaded Repositories | 13

Home Assistant Cloud

logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok

Home Assistant Supervisor

host_os | Home Assistant OS 16.3 -- | -- update_channel | stable supervisor_version | supervisor-2025.12.2 agent_version | 1.7.2 docker_version | 28.3.3 disk_total | 457.7 GB disk_used | 114.2 GB nameservers | 192.168.10.1 healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | board | rpi4-64 supervisor_api | ok version_api | ok installed_addons | Advanced SSH & Web Terminal (22.0.3), Let's Encrypt (5.4.9), Duck DNS (1.26.0), Samba share (12.5.4), Mosquitto broker (6.5.2), AirSonos (5.0.2), AirCast (5.0.2), Matter Server (8.1.1), AdGuard Home (6.0.3), Studio Code Server (6.0.1), Zigbee2MQTT (2.7.1-1), Home-Assistant-Matter-Hub (3.0.2), NGINX Home Assistant SSL proxy (3.14.0), Claude Terminal (1.3.2)

Dashboards

dashboards | 4 -- | -- resources | 4 views | 8 mode | storage

Network Configuration

adapters | lo (disabled), end0 (enabled, default, auto), docker0 (disabled), hassio (disabled), vethf95f401 (disabled), veth8b8f23e (disabled), vethc18dd53 (disabled), veth8684e8b (disabled), veth396c2b9 (disabled), veth411ed9b (disabled), veth3e97d6c (disabled), veth2166344 (disabled), veth073ac32 (disabled), veth276dc49 (disabled) -- | -- ipv4_addresses | lo (127.0.0.1/8), end0 (192.168.10.100/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), vethf95f401 (), veth8b8f23e (), vethc18dd53 (), veth8684e8b (), veth396c2b9 (), veth411ed9b (), veth3e97d6c (), veth2166344 (), veth073ac32 (), veth276dc49 () ipv6_addresses | lo (::1/128), end0 (fdd1:aa1b:8f87:a63e:8c78:5a22:c9ee:f8de/64, fe80::448d:687:63ef:9eb7/64), docker0 (fe80::90fa:c9ff:fea5:97e9/64), hassio (fe80::ac55:3fff:fe94:6744/64), vethf95f401 (fe80::5419:f2ff:fed7:6df7/64), veth8b8f23e (fe80::855:61ff:fe0e:5edc/64), vethc18dd53 (fe80::4c7f:b8ff:fe9f:4f8f/64), veth8684e8b (fe80::f4aa:51ff:fe41:32aa/64), veth396c2b9 (fe80::c3d:32ff:feb0:31d2/64), veth411ed9b (fe80::c84a:6ff:fe65:abc9/64), veth3e97d6c (fe80::c4df:5fff:fe5b:8f8d/64), veth2166344 (fe80::b8bd:44ff:fe04:539c/64), veth073ac32 (fe80::60a2:d6ff:fe6d:f5f0/64), veth276dc49 (fe80::eca0:8eff:fe03:d783/64) announce_addresses | 192.168.10.100, fdd1:aa1b:8f87:a63e:8c78:5a22:c9ee:f8de, fe80::448d:687:63ef:9eb7

Recorder

oldest_recorder_run | November 28, 2025 at 13:50 -- | -- current_recorder_run | December 9, 2025 at 08:08 estimated_db_size | 702.57 MiB database_engine | sqlite database_version | 3.49.2

Spotify

api_endpoint_reachable | ok -- | --

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response