Is there an existing feature request for this?
Your feature request
Describe the bug / gap
AppDaemon exposes four configurable log channels via the logs: section of appdaemon.yaml (main_log, error_log, diag_log, access_log). However, there appears to be a separate, unconfigurable HTTP request log that is written directly to stdout in Apache Combined Log-like format, e.g.:
192.168.xxx.yyy [22/Aug/2026:21:53:19 +0100] "GET /api/appdaemon/some_endpoint HTTP/1.1" 200 214 "-" "SomeClient/1.0"
or..
2026-08-23 10:55:00.652 INFO AppDaemon: 192.168.xxx.yyy [23/Aug/2026:09:55:00 +0100] "GET /app/infoboard_image_raw?image=0 HTTP/1.1" 200 234 "-" "ESPHome/2026.7.4 (https://esphome.io)"
2026-08-23 10:56:01.815 INFO AppDaemon: 192.168.xxx.yyy [23/Aug/2026:09:56:01 +0100] "GET /api/appdaemon/infoboard_draw_commands_chunk?index=0&t=641125691 HTTP/1.1" 200 214 "-" "ESPHome/2026.7.4
These lines:
- do NOT appear in the configured
main_log file
- do NOT appear in the configured
access_log file (which only receives AppDaemon's own "API Call to X: status: Y" messages from the internal Access logger)
- DO appear on stdout, and are therefore the only thing visible in the Home Assistant Supervisor add-on "Log" tab for high-frequency polling integrations (e.g. ESPHome components polling a custom endpoint every minute)
This makes the Supervisor GUI log tab unusable for spotting real warnings/errors during normal operation, since it gets flooded with one request-line entry per HTTP call, while the properly configured main_log/access_log files stay clean.
Describe the solution you'd like
A documented way to either:
- Disable this stdout-only request logging entirely, or
- Route it through the existing
access_log channel (so log_size / log_generations rotation and file redirection apply to it too), or
- Set its log level independently (e.g. suppress below WARNING) via
appdaemon.yaml.
Describe alternatives you've considered
Using appdaemon.log (main_log) directly via file access (Samba/SSH) instead of the Supervisor GUI tab — works to redirect my app log entries, but still keeps the raw aiohttp request logs in the GUI channel, which defeats the purpose of the GUI log for users who don't want to set up file-level access just to get a clean overview.
Environment
- AppDaemon version: 4.5.13
- Installation method: Home Assistant Supervisor add-on
- Home Assistant version: 2026.8.3
Is there an existing feature request for this?
Your feature request
Describe the bug / gap
AppDaemon exposes four configurable log channels via the
logs:section ofappdaemon.yaml(main_log,error_log,diag_log,access_log). However, there appears to be a separate, unconfigurable HTTP request log that is written directly to stdout in Apache Combined Log-like format, e.g.:192.168.xxx.yyy [22/Aug/2026:21:53:19 +0100] "GET /api/appdaemon/some_endpoint HTTP/1.1" 200 214 "-" "SomeClient/1.0"
or..
2026-08-23 10:55:00.652 INFO AppDaemon: 192.168.xxx.yyy [23/Aug/2026:09:55:00 +0100] "GET /app/infoboard_image_raw?image=0 HTTP/1.1" 200 234 "-" "ESPHome/2026.7.4 (https://esphome.io)"
2026-08-23 10:56:01.815 INFO AppDaemon: 192.168.xxx.yyy [23/Aug/2026:09:56:01 +0100] "GET /api/appdaemon/infoboard_draw_commands_chunk?index=0&t=641125691 HTTP/1.1" 200 214 "-" "ESPHome/2026.7.4
These lines:
main_logfileaccess_logfile (which only receives AppDaemon's own "API Call to X: status: Y" messages from the internal Access logger)This makes the Supervisor GUI log tab unusable for spotting real warnings/errors during normal operation, since it gets flooded with one request-line entry per HTTP call, while the properly configured
main_log/access_logfiles stay clean.Describe the solution you'd like
A documented way to either:
access_logchannel (solog_size/log_generationsrotation and file redirection apply to it too), orappdaemon.yaml.Describe alternatives you've considered
Using
appdaemon.log(main_log) directly via file access (Samba/SSH) instead of the Supervisor GUI tab — works to redirect my app log entries, but still keeps the raw aiohttp request logs in the GUI channel, which defeats the purpose of the GUI log for users who don't want to set up file-level access just to get a clean overview.Environment