Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 6 additions & 18 deletions source/_integrations/logger.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -173,23 +173,11 @@ data:

The log information can be viewed and downloaded from {% my logs title="**Settings** > **System** > **Logs**" %}

### Viewing logs on Container installations
Copy link

Copilot AI Nov 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The section heading uses "Viewing logs on Container installations" but this is redundant and inconsistent with the parent section "Viewing logs" (line 172). According to the documentation standards, this creates an awkward flow.

Consider simplifying to "### Container installations" to match the style of the removed sections ("Supervised installations" and "Non-Supervised installations"). This maintains parallelism and follows the established pattern in the document.

Copilot generated this review using guidance from repository custom instructions.

### Supervised installations

On {% term "Home Assistant Supervisor" %} based installations, such as the
{% term "Home Assistant Operating System" %} the logs can also be viewed
by logging in through the [SSH add-on](/common-tasks/os/#installing-and-using-the-ssh-add-on) and running the following command:

```bash
ha core logs
```

### Non-Supervised installations

For installations without the {% term "Home Assistant Supervisor" %}
the log information is stored in the
[configuration directory](/docs/configuration/) as `home-assistant.log`
and you can read it with the command-line tool `cat` or follow it dynamically
For {% term "Home Assistant Container" %} installations, the log information is stored in the
[configuration directory](/docs/configuration/) as `home-assistant.log`.
You can read it with the command-line tool `cat` or follow it dynamically
with `tail -f`.
Comment on lines +178 to 181
Copy link

Copilot AI Nov 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The sentence structure could be improved for better readability. The current phrasing "For {% term "Home Assistant Container" %} installations the log information is stored..." is missing a comma after the introductory phrase.

According to documentation standards, this should read: "For {% term "Home Assistant Container" %} installations, the log information is stored in the configuration directory as home-assistant.log and you can read it with the command-line tool cat or follow it dynamically with tail -f."

Additionally, consider breaking this into two sentences for better clarity:
"For {% term "Home Assistant Container" %} installations, the log information is stored in the configuration directory as home-assistant.log. You can read it with the command-line tool cat or follow it dynamically with tail -f."

Copilot generated this review using guidance from repository custom instructions.

You can use the example below, when logged in through the [SSH add-on](/common-tasks/os/#installing-and-using-the-ssh-add-on):
Expand All @@ -198,11 +186,11 @@ You can use the example below, when logged in through the [SSH add-on](/common-t
tail -f /config/home-assistant.log
```

On Docker you can use your host command line directly - follow the logs dynamically with:
On Docker, you can use your host command line directly. Follow the logs dynamically with the following command:

```bash
# follow the log dynamically
docker logs --follow MY_CONTAINER_ID
```

To see other options use `--help` instead, or simply leave with no options to display the entire log.
To see other options, use `--help` instead, or simply leave with no options to display the entire log.