Companion to homeassistant#170. Fixes that merged dashboard changes don't appear without a manual force-reload: reload_all doesn't re-read YAML-mode Lovelace dashboards (HA caches them until restart or a lovelace/config force=true WS call).
After a pull-merge touching dashboards/ or ui-lovelace.yaml, config-sync now also calls shell_command.reload_lovelace_yaml (defined in the HA repo, packages/lovelace_reload.yaml) which runs a websockets helper inside the HA container to force the re-read. busybox has no WS client, hence the hand-off through HA.
Activation: needs a one-time HA restart to register the shell_command domain (not covered by reload_all), and the config-sync container must reload the new script. Until the restart, reload_lovelace just logs a warning; sync is otherwise unaffected.
Companion to homeassistant#170. Fixes that merged dashboard changes don't appear without a manual force-reload: reload_all doesn't re-read YAML-mode Lovelace dashboards (HA caches them until restart or a lovelace/config force=true WS call).
After a pull-merge touching dashboards/ or ui-lovelace.yaml, config-sync now also calls shell_command.reload_lovelace_yaml (defined in the HA repo, packages/lovelace_reload.yaml) which runs a websockets helper inside the HA container to force the re-read. busybox has no WS client, hence the hand-off through HA.
Activation: needs a one-time HA restart to register the shell_command domain (not covered by reload_all), and the config-sync container must reload the new script. Until the restart, reload_lovelace just logs a warning; sync is otherwise unaffected.
reload_all does not re-read YAML-mode Lovelace dashboards (HA caches them until
restart or a lovelace/config force=true WS call), so merged dashboard changes
never appeared without a manual force-reload.
After a pull-merge that touches dashboards/ or ui-lovelace.yaml, config-sync now
also calls shell_command.reload_lovelace_yaml (defined in the HA config repo,
packages/lovelace_reload.yaml) which runs a websockets helper inside the HA
container to force the re-read. busybox can't speak WebSocket, hence the hand-off.
Needs a one-time HA restart to register the shell_command domain (not covered by
reload_all); until then reload_lovelace logs a warning and sync is otherwise fine.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QiLCinB7NLp7YdCjGYzvfh
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Companion to homeassistant#170. Fixes that merged dashboard changes don't appear without a manual force-reload: reload_all doesn't re-read YAML-mode Lovelace dashboards (HA caches them until restart or a lovelace/config force=true WS call).
After a pull-merge touching dashboards/ or ui-lovelace.yaml, config-sync now also calls shell_command.reload_lovelace_yaml (defined in the HA repo, packages/lovelace_reload.yaml) which runs a websockets helper inside the HA container to force the re-read. busybox has no WS client, hence the hand-off through HA.
Activation: needs a one-time HA restart to register the shell_command domain (not covered by reload_all), and the config-sync container must reload the new script. Until the restart, reload_lovelace just logs a warning; sync is otherwise unaffected.