From ec199cd77b5d133bb43b2da286007ee596aa7156 Mon Sep 17 00:00:00 2001
From: G Johansson <goran.johansson@shiftit.se>
Date: Fri, 6 Dec 2024 20:25:49 +0100
Subject: [PATCH] Add troubleshooting section to command_line (#36190)

---
 source/_integrations/command_line.markdown | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/source/_integrations/command_line.markdown b/source/_integrations/command_line.markdown
index 2bf9e7f01e8..4cf3c88f466 100644
--- a/source/_integrations/command_line.markdown
+++ b/source/_integrations/command_line.markdown
@@ -290,6 +290,22 @@ command_line:
           default: 30
 {% endconfiguration %}
 
+## Troubleshooting
+
+As **Command line** {% term integration %} is a yaml only integration, turning on extended logging needs to be done by setting the logging information in your {% term "`configuration.yaml`" %} file.
+
+Entering this example in your configuration sets the default logging to info, and for `command_line` to debug. Once done, restart Home Assistant to enable.
+
+{% raw %}
+```yaml
+# Set logging
+logger:
+  default: info
+  logs:
+    homeassistant.components.command_line: debug
+```
+{% endraw%}
+
 {% note %}
 
 While `command` is accepting a template for `sensor` and `binary_sensor`, it's only the arguments that can be a template. This means the command name itself cannot be generated by a template, but it must be literally provided.