copilot-swe-agent[bot] 0b4da732ca Fix Settings.yaml corruption: move bashio::log calls outside stdout redirect block ...

The bashio-standalone.sh library writes log output to stdout (fd 1), not to
a preserved LOG_FD like the real bashio library. When bashio::log.info calls
were inside the { ... } > Settings.yaml block in immich_frame's 99-run.sh,
log messages leaked into the generated YAML file, corrupting it and causing
ImmichFrame to fail to parse account configuration correctly.

Changes:
- bashio-standalone.sh: redirect log output to LOG_FD (if available) or
  stderr, matching real bashio behavior
- bashio-standalone.sh: add missing bashio::log.fatal and bashio::log.notice
  aliases
- immich_frame 99-run.sh: move all bashio::log calls outside the
  { ... } > Settings.yaml block so only YAML content goes to the file

Agent-Logs-Url: https://github.com/alexbelgium/hassio-addons/sessions/87f542ba-1e4a-4b71-a787-e979818997df

Co-authored-by: alexbelgium <44178713+alexbelgium@users.noreply.github.com>

2026-04-17 12:06:52 +00:00

..

etc/cont-init.d

Fix Settings.yaml corruption: move bashio::log calls outside stdout redirect block

2026-04-17 12:06:52 +00:00