Configuring Command Line sensor using YAML has moved. Consult the documentation to move your YAML configuration to integration key and restart Home Assistant to fix this issue

77

what is the format if you have command line sensors but they are in the packages folder in command_line.yaml

command_line:
  - sensor:
      scan_interval: 5
      name: Enclosure Temperature
      command: "curl 'http://192.168.1.146/plugin/enclosure/inputs/1?apikey=******'"
      unit_of_measurement: "°C"
      value_template: "{{value_json['temp_sensor_temp'] }}"

  - sensor:
      scan_interval: 5
      name: Enclosure Humidity
      command: "curl 'http://192.168.1.146/plugin/enclosure/inputs/1?apikey=******'"
      unit_of_measurement: "°C"
      value_template: "{{value_json['temp_sensor_humidity'] }}"

This doesnt work.

78

I still could not come up with a solution to this error. In my configuration.yaml I have a list like this:

template:
  - sensor:
      - name: "TV Power Consumption"
        unit_of_measurement: 'kW'
        state: >
          {{ (states("sensor.tv_energy")) | float / 10000 | round(5) }}       
        device_class: power

and

sensor:
  - platform: integration
    name: TV Energy Consumption
    source: sensor.tv_power_consumption
    method: left

I tried moving these to command_line.yaml without any luck. With the platform I get an error saying that platform is not supported, while for the template I get a generic error.

79

Neither of those are using the command_line sensor platform. They do not need to be moved.

Only things that include:

  - platform: command_line

need to be changed.

Not template, not Riemann sum, nothing other than command_line integrations.

1 Like
80

/Flame ON
I just don’t get why anyone thinks “hints” are documentation.

This thread is evidence of a disaster.
The “error” message needs
a) To be much clearer about what has changed
b) To provide a link (short bit.ly link or similar if required) to clear documentation
c) Of What has changed and how to migration from was to what should

Writing code is not doing the job. The job is only done when it is clearly documented and the users can find the documentation.

I hand wrote all my YAML, but I don’t work in HA from one month to the next.
I’m having to wade though this discussion, to try and understand what has changed because hints are not enough. Link to clear documentation required.
/Off

3 Likes
81

You are right. I thought the warning was really cryptic. “Command Line YAML configuration has moved” doesn’t mean anything to me. I thought that some YAML had been moved elsewhere. The “…move your YAML configuration to integration key…” is mystifying in the extreme. What does that even mean?

I don’t think this was well handled.

83

lol “big hints”.
Stuff like this is why I can’t recommend HA to my friends. I don’t want them to hate me.

84

That was a joke.

The only way the “hints” could be less obvious is if they were surrounded by pink boxes, or perhaps use flashing text.

I also agreed that it would be better with a link to the docs concerned.

So what exactly is your issue with the post?

85

the solution is precisely this, you need to move everything under ‘command_line:’
the old formalism with ‘- platform: command_line’ is no longer valid :wink:

86

Hi all,

Very new to home assistant, super excited about the product, and glad I got it to work the way I wanted to… until I suddenly got the “Command line sensor YAML” warning message :frowning: … I read the documentation, but I dont understand how to change what I have to what I need. Would anyone be able to point me in the right direction? THANK YOU so much in advance for your support :slight_smile: - Marco

this is what i have in my configuration.yaml file that I think is causing the warning

sensor:
  - platform: command_line
    command: python3 -c "import requests; import json; import random; dataRequest = requests.get('https://cdn-secure.buienalarm.nl/api/3.4/forecast.php?lat=50&lon=5&region=nl&unit=mm%2Fu&c='+str(random.randint(0,999999999999999)) ).text; dataRequest = dataRequest.replace('\r\n',' '); data = '{\"data\":'+dataRequest+'}';    print(data);"
    name: Neerslag_Buienalarm_Regen_Data
    json_attributes:
      - data
    value_template: 'last_changed: {{states.sensor.neerslag_buienalarm_regen_data.last_changed | default(now())}}'
    scan_interval: 240
  - platform: command_line
    command: python3 -c "import requests; import json; import random; dataRequest = requests.get('https://gpsgadget.buienradar.nl/data/raintext?lat=50&lon=5&c='+str(random.randint(0,999999999999999)) ).text; dataRequest = dataRequest.replace('\r\n',' '); data = '{\"data\":\"'+dataRequest+'\"}';    print(data);"
    name: Neerslag_Buienradar_Regen_Data
    json_attributes:
      - data
    value_template: 'last_changed: {{states.sensor.neerslag_buienradar_regen_data.last_changed | default(now())}}'
    scan_interval: 240
87

Hi guys, after the update my sensors are gone :stuck_out_tongue:
I don’t see breaking changes, but somehow its not working anymore.
Are there people whit the same issue?

sensor:
  - platform: command_line
    name: NUC Motherboard Temperature
    command: "cat /sys/devices/virtual/thermal/thermal_zone0/temp"
    value_template: '{{ value | multiply(0.001) | round(2) }}'
    unit_of_measurement: '°C'
    
  - platform: command_line
    name: NUC CPU Temperature
    command: "cat /sys/devices/virtual/thermal/thermal_zone1/temp"
    value_template: '{{ value | multiply(0.001) | round(2) }}'
    unit_of_measurement: '°C'

  - platform: command_line
    name: NUC WiFi Temperature
    command: "cat /sys/devices/virtual/thermal/thermal_zone2/temp"
    value_template: '{{ value | multiply(0.001) | round(2) }}'
    unit_of_measurement: '°C'
88

Same here
Not find solution yet

89

Wrong notation. See 2023.12: Welcome home! - #158 by tom_l

1 Like
90

Thanks a lot, this was the issue!

91

I have text below in configuration.yalm.
What do i need to change?

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Text to speech
tts:
  - platform: google_translate
automation: !include automations.yaml
binary_sensor: !include binary_sensor.yaml
device_tracker: !include device_tracker.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
ssdp:
sensor:
  - platform: template
    sensors:
      brightness_sun:
        friendly_name: "Sunshine"
        value_template: >-
          {% if state_attr('Sun.sun', 'elevation') > 20  %}
            bright
          {% elif state_attr('Sun.sun', 'elevation') > 9 %}
            mid
          {% elif state_attr('Sun.sun', 'elevation') > -3 %}
            dark
          {% else %}
            black
          {% endif %}
homeassistant:
  packages: !include_dir_named packages/
logger:
  default: info
  logs:
    custom_components.spotcast: debug
92

Nothing. I suppose the relevant YAML you might need to change is in one of the yaml files in the packages folder

93

Hi,
i’m struggling with this update command_line. i made the modification but i still have a error.
Below my Code:
in Configuration.Yaml, I add:
command_line: !include command_line.yaml

in commande_line.yaml File : i put the following code:

# OPTIONAL CPU Raspberry Pi Temp
command_line:
  - sensor:
      name: CPU Temperature
      command: "cat /sys/class/thermal/thermal_zone0/temp"
      unit_of_measurement: "°C"
      value_template: "{{ value | multiply(0.001) | round(2) }}"

I’m still getting the following error when configuration checked :slight_smile:

Invalid config for [command_line]: [command_line] is an invalid option for [command_line]. Check: command_line->command_line->0->command_line. (See /config/configuration.yaml, line 18).
what did i miss in the new code?? Thanks for help

94

Remove “command_line:” from command_line.yaml

95

Thanks :pray:. it works fine.

96

Seems like I am the only one that cannot get this to work.

My configuration.yaml file:

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

# Load frontend themes from the themes folder
frontend:
  themes: !include_dir_merge_named themes
  extra_module_url:
    - /hacsfiles/hass-hue-icons/hass-hue-icons.js  

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

pyscript:
  allow_all_imports: true
  hass_is_global: true

switch:
    - platform: broadlink
      mac: !secret macbroadlink

My command_line.yaml file:


  - binary_sensor:
      name: "Mosquitto Broker Addon Status"
      unique_id: mosquittobroker_addon_status
      device_class: connectivity
      command: 'ha addons info core_mosquitto | grep -q "started" && (echo "Running") || (echo "Not running")'
      payload_on: "Running"
      payload_off: "Not running"
      
  - binary_sensor:
      name: "Node-RED Addon Status"
      unique_id: nodered_addon_status
      device_class: connectivity
      command: 'ha addons info a0d7b954_nodered | grep -q "started" && (echo "Running") || (echo "Not running")'
      payload_on: "Running"
      payload_off: "Not running"

My entity (it’s happening with both of them tho):

image
image581×591 25.3 KB

No way it’s showing as Running. This is what I am getting from terminal:

image
image781×101 3.92 KB

Can someone help me please?

97

been scratching my head for days over this.
Thank you Ruben vad der Steenhoven. This is the solution.

!include sensors didn’t work.
Create command_line: !include cmdline.yaml in configuration.yaml and then create a new file as Ruben mentioned.
All new sensors go in cmdline.yaml.