Files
haos-hacs-immich-album-watcher/plans
alexei.dolgolyov ab1c7ac0db
Some checks failed
Validate / Hassfest (push) Has been cancelled
Add HAOS-Server sync for optional centralized management (Phase 5)
Enable the HAOS integration to optionally connect to the standalone
Immich Watcher server for config sync and event reporting.

Server-side:
- New /api/sync/* endpoints: GET trackers, POST template render,
  POST event report
- API key auth via X-API-Key header (accepts JWT access tokens)

Integration-side:
- New sync.py: ServerSyncClient with graceful error handling
  (all methods return defaults on connection failure)
- Options flow: optional server_url and server_api_key fields
  with connection validation
- Coordinator: fire-and-forget event reporting to server when
  album changes are detected
- Translations: en.json and ru.json updated with new fields

The connection is fully additive -- the integration works identically
without a server URL configured. Server failures never break HA.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-19 14:10:29 +03:00
..

Plans

This folder contains the primary architecture plan and phase-specific subplans for the Immich Watcher project restructuring.

Structure

  • primary-plan.md -- Master plan with architecture decisions and phase overview
  • phase-1-core-library.md -- Extract shared core library
  • phase-2-haos-refactor.md -- Wire core into HAOS integration
  • phase-3-server-backend.md -- Build standalone FastAPI server
  • phase-4-frontend.md -- Build SvelteKit web UI
  • phase-5-haos-server-sync.md -- Optional HAOS-Server integration

Tracking

Each plan uses checkbox tracking:

  • [ ] -- Not started
  • [x] -- Completed
  • [~] -- In progress
  • [-] -- Skipped/deferred

Phase subplans are created when work on that phase begins (not all upfront).