--SOLVED-- Command failed in log, even if it's working

Configuration
1

Hi there.

----- Problem solved, by adding “|| true” after each command, to force the command to end with exit code 0.

I have several command_line in my sensor.yaml with this command:

- platform: command_line
   name: fremløb_temp
   command: "grep -oP '(?<=/boiler_temp=)[^ ]+' /config/custom_components/nbetest-master/readout.log"
   unit_of_measurement: "°C"
   scan_interval: 15

The different in the commands is this part …/boiler_temp
The command extract information from my heating and solar cells.
Everything works as it should, i get all my data, except that after a 5 minutes or so, they all returns with a error in the log… even after that, they are still working.

Logger: homeassistant.components.command_line
Source: components/command_line/__init__.py:41
Integration: command_line (documentation, issues)
First occurred: 20.39.56 (18 occurrences)
Last logged: 20.40.10

Command failed: grep -oP '(?<=/sun_temp=)[^ ]+' /config/custom_components/nbetest-master/readout.log
Command failed: grep -oP '(?<=/boiler_temp=)[^ ]+' /config/custom_components/nbetest-master/readout.log
Command failed: grep -oP '(?<=/shaft_temp=)[^ ]+' /config/custom_components/nbetest-master/readout.log
Command failed: grep -oP '(?<=/photo_level=)[^ ]+' /config/custom_components/nbetest-master/readout.log
Command failed: grep -oP '(?<=/exhaust_speed=)[^ ]+' /config/custom_components/nbetest-master/readout.log

I’am running HA core 2020.12.2 in a docker.

2

Problem solved, by adding “|| true” after each command, to force the command to end with exit code 0.

2 Likes