Hauser v0.5.0

Release identity

Version	0.5.0
Git tag	v0.5.0 (annotated, 53fb0911)
Source commit	2ca247eda3eba1ff7f1b3ac78dc6aaca33d0c193
Image	ghcr.io/ralleur/hauser@sha256:4e2d5831a4177e3e0cba36a3c5d467928c3bc256d13117c5cadb334a8c60a900
Also tagged	:v0.5.0 and :0.5.0 (same manifest; the Supervisor resolves the unprefixed tag)
Platforms	linux/amd64, linux/arm64
Configuration	Household schema v4; the v1 → v4 migration path is included and verified
Container smoke	verify-container.sh against the published digest: setup_required=PASS, migration_v1_to_v4=PASS, cycles=2, backup_restore=PASS, invalid_config=PASS, invalid_migration=PASS
Source offer	/api/build-info on the published image returns version=0.5.0, revision=2ca247eda3eba1ff7f1b3ac78dc6aaca33d0c193, sourceUrl=https://github.com/ralleur/hauser, license=AGPL-3.0-only
Build run	https://github.com/ralleur/hauser/actions/runs/33118101166

The version number changed shape

0.4.0-beta.10 is followed by 0.5.0, not by 0.4.0-beta.11. Every release
below 1.0.0 is a beta — the version number carries that on its own, so the
-beta.N suffix is gone. Nothing about the project's maturity, support or
license changed with it: Hauser stays a self-hosted AGPL hobby project in its
public technical beta, and v1.0.0 still means the same thing it always did.

What changed

This release rebuilds the Rooms & devices settings page — the page where a
home is actually set up — and takes two everyday annoyances out of the way.

Added — Rooms & devices is a real room list

Each room now shows its current room image, its name and how many devices it
holds. Configure devices opens the room editor, Rename edits the name in
place, the six-dot handle drags the room into position — the arrow keys do the
same without a pointing device — and the overflow menu keeps move, rename and
delete. New room and Save changes sit where the list ends. As before,
nothing is written until the changes are saved.

Added — tapping a room's image opens the image editor

The thumbnail in the list leads straight to the room-image view of the room
overlay, where an image can be uploaded, picked from the library or removed.

Added — the room-image assistant and the library have their own cards

Both sit as illustrated tiles under the room list instead of two anonymous
rows.

Changed — Settings open on Rooms & devices

Coming back within 30 seconds still returns to the section that was open, so a
quick detour costs nothing; a later visit starts fresh.

Changed — resetting is one card with three tiles

Device names and icons, scenes, and re-reading rooms and devices from Home
Assistant. The last one used to be a separate section at the bottom of the
page.

Fixed — the room-image card on the home screen kept coming back

Dismissing it applied to one room only, and only until the next reload. A
checkbox on the card now switches it off for good on that device.

Fixed — saving room changes could be blocked by Jellyfin

Settings has no Jellyfin fields, yet an unverified Jellyfin sign-in disabled
Save changes. The first-run wizard still requires the tested sign-in.

Installation or update

Fresh install (Docker Compose), from a checkout of the tag:

cp .env.example .env
docker compose pull
docker compose up -d
docker compose exec hauser node container/healthcheck.mjs

Home Assistant App users: Settings → Add-ons → Hauser → Update.

Docker and Compose users: back up first (./scripts/backup.sh), then pull
ghcr.io/ralleur/hauser:0.5.0. No configuration migration is required when
coming from 0.4.0-beta.x. The previous immutable reference for a rollback is
ghcr.io/ralleur/hauser@sha256:ae87b24af625e49ad211f11e22881393523150f9c28f36e0b615ba5e2b98ce84
(v0.4.0-beta.10).

Verification evidence

• Tests, typecheck, production build, static demo build and the container
  contract: green in the tagged run above.
• Export and privacy gate: green; the maintainer's private code-modifying AI
  agent is absent from the package.
• Container health, setup-required start, configured start, persistence across
  recreation, backup/restore, invalid configuration and invalid migration:
  PASS against the published manifest digest, pulled after publication.
• The linux/arm64 image build hit a QEMU illegal instruction crash on its
  first attempt and was re-run once; the published manifest comes from the
  successful run. The emulation crash was in the build container, not in
  Hauser.
• Landing page and demo were deployed from the same source commit:
  https://ralleur.github.io/hauser/demo/

Known limitations

• Clean-room evidence is maintainer-operated. The one external installation
  report to date is the Asustor NAS case in
  issue #7; an external real-home
  installation remains the next beta-stabilisation evidence gate.
• The vacuum path follows the documented Home Assistant service set and is not
  yet verified against real hardware.
• Translations beyond German and English have not had a native review.
• Room-image generation requires the user's own OpenAI access and is optional.

Security and support

Hauser is a hobby project without an SLA. Please read
SECURITY.md before
reporting anything security-relevant. Do not expose Hauser directly to the
internet without an authentication and TLS boundary in front of it.