shaikedem
(Shaikedem)
November 16, 2025, 8:59am
1
hi
after upgrading to HA 2025.11.1 2 days ago and 2025.11.2 now,
i dont see the log file of HA under /config anymore in the ssh shell
in the UI, settings → system → logs i can see logs
HA is working all OK otherwise
but the file simply does not exist …
did it move elsewhere ?
i only see old log files before the upgrade
the logger config in my config yaml was not changed
logger:
default: info
logs:
custom_components.multiscrape: debug
homeassistant.components.bluetooth: debug
pyscript: debug
shaikedem
(Shaikedem)
November 16, 2025, 9:22am
2
ok, i see 2025.11.1 removed the actual file
you can only see it now in UI for some reason …
dev ← no_log_file_on_supervisor
opened 07:25PM - 12 Jun 25 UTC
## Proposed change
On supervised installations (such as Home Assistant OS), t… he logs are sent to systemd journal, in addition to the Home Assistant log file `home-assistant.log`. This PR stops logging to the `home-assistant.log` in order to reduce the ammount of writes to disk.
## Type of change
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [x] Code quality improvements to existing code or addition of tests
## Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/41046
- Link to developer documentation pull request:
- Link to frontend pull request:
## Checklist
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [x] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
Those logs are nice in a way, and they have been there for quite some time. So that was not added, but the alternative file version was removed.
The downside of the removal is that HA needs to run for you to look at the GUI version. If it crashes, you’ll need linux knowledge to get to the logs. The GUI logs are also harder to share with tech support, harder to analyse and it is not really possible to construct a timeline of events when the individual, related events occur more often. A technica…
Petro was good enough to come up with an integration that replaces/recreates the log file functionality if you still want that, a-file-logger .
Just be sure to place the configuration.yaml entry at the top (or close to the top) of the file so that it loads as early as possible on start up.
BullFrog
(BullFrog)
November 17, 2025, 3:17pm
4
Why do they dumb it down? its a Smart Home, Z2M creates 26mb of log files each day, HA is logging everything, why the hell did they have to remove it?
There is an UI? Good thing! But why remove something thats already there?
Why do I need to install an addon for a PRIMARY functionality?
1 Like
maurizio53
(Maurizio Fabiani)
November 25, 2025, 3:25pm
5
I am using that custom integration and i am seeing it creates an home-assistant.log, an home-assistant.log_1 and an home-assistant.log_old.
Is this behaviour correct?
I’ve home-assistant.log, an home-assistant.log.1 and an home-assistant.log.old… no underscores. The important thing would be if the logs within the files are actually up to date.