From 479d56ed69b65da5b9773517974eb685d6c087e5 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Thu, 6 Jan 2022 21:36:04 +0100 Subject: [PATCH] Add clarification on the timeout in shell_command (#21065) --- source/_integrations/shell_command.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/shell_command.markdown b/source/_integrations/shell_command.markdown index 0f2e5e02833..51a487a9ece 100644 --- a/source/_integrations/shell_command.markdown +++ b/source/_integrations/shell_command.markdown @@ -47,7 +47,7 @@ The `command` is executed within the [configuration directory](/docs/configurati If you are using [Home Assistant operating system](https://github.com/home-assistant/operating-system), the commands are executed in the `homeassistant` container context. So if you test or debug your script, it might make sense to do this in the context of this container to get the same runtime environment. -With a `0` exit code, the output (stdout) of the command is used as `value`. In case a command results in a non `0` exit code or is terminated by the `command_timeout`, the result is only logged to Home Assistant log and the value of the sensor is not updated. +With a `0` exit code, the output (stdout) of the command is used as `value`. In case a command results in a non `0` exit code or is terminated after a timeout of 60 seconds, the result is only logged to Home Assistant log and the value of the sensor is not updated. ## Examples