A command_line sensor became unavailable after HA update

I have a command line sensor reporting CPU temperature since… lat year I think, and used to work flawlessly up until today.

After I installed most recent HA core and HA OS updates today - it’s not available in the dashboard anymore (Entity is currently unavailable: sensor.cpu_temperature. This entity is no longer being provided by the command_line integration. If the entity is no longer in use, delete it in settings.).

Reboot didn’t help. Removal of the entity didn’t help either - it didn’t re-appear.

Here’s my config/configuration.yaml

# Loads default set of integrations. Do not remove.
default_config:

# Text to speech
tts:
  - platform: google_translate

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

sensor:
  - platform: command_line
    name: CPU Temperature
    unique_id: '99985e2b-7c60-4cf6-aa1f-43cf5c4b399d'
    command: 'cat /sys/class/thermal/thermal_zone0/temp'
    unit_of_measurement: '°C'
    value_template: '{{ value | multiply(0.001) | round(1) }}'

lovelace:
  mode: yaml
  resources:
    - url: /hacsfiles/button-card/button-card.js
      type: module

What version did you update from?

This is from the 2023.06 update:

https://www.home-assistant.io/blog/2023/06/07/release-20236/#backward-incompatible-changes

The documentation for this:

The depreciation after 6 months may have been missed as a breaking change in the 2023.12 release notes though.

2 Likes

What version did you update from?

From the previous 2023.11.* version (don’t recall exactly)

This is from the 2023.06 update:
https://www.home-assistant.io/blog/2023/06/07/release-20236/#backward-incompatible-changes

Oh, right. The funny part is that I looked at my config, at the config on the documentation page you referenced and didn’t spot the difference.
I updated the configuration format and the sensor became available again.

The depreciation after 6 months may have been missed as a breaking change in the 2023.12 release notes though.

This would have helped. Anyway, I’m glad we have this wonderful community to address even silly questions like mine.

Thank you sir!

1 Like

Actually I just found out there is no plan to include breaking changes that depreciate after 6 months in the release notes when the 6 months is up. Instead it is planned that you will not be able to update until you have fixed the things listed in the Repairs menu.