Skip to content

FAQ

Portability. Embedded SQLite means a single container with no database service — the whole app state is one folder, which is what makes it work as a Home Assistant add-on, on Unraid, or on a Pi. Backup is copying a directory.

Does the camera work over http://<lan-ip>:8080?

Section titled “Does the camera work over http://<lan-ip>:8080?”

Partially. Browsers only allow the live viewfinder in a secure context — localhost and HTTPS count, http://192.168.x.x doesn’t. Over plain HTTP, photo capture falls back to the file picker and everything else still works. For the full experience use HTTPS, the HA ingress URL, or localhost.

~200 MB idle. Photo similarity (CLIP) loads lazily on first use and brings it to ~450–550 MB warm. STACHE_NO_ML=1 disables embeddings on tiny hosts; everything else keeps working.

It’s on by default, but you don’t have to think about it — it just suggests names/tags/descriptions in the background and you confirm or ignore. Everything works with it off too (STACHE_NO_ML=1, or the toggle in Settings). See AI suggestions.

Stache is a PWA — open it on your phone and “Add to Home Screen.” It works offline too: photos and scans queue locally and sync once your server is reachable again. Things that need the outside world — barcode lookups, a remote AI provider — wait for a connection; everything local keeps working.

Everything lives in /data — copy it and you’re backed up. There’s also an optional built-in scheduler. See Backups.

Only the first account is open signup. After that, accounts are created by logged-in members (Settings → Household) — there’s no public registration to accidentally expose.

Shared items only — private items are never exposed. Connections are individually revocable and can be read-only. See MCP connections.

Something’s broken — where are the logs?

Section titled “Something’s broken — where are the logs?”

docker logs on the container (or the add-on’s Log tab in Home Assistant). Issues go to the GitHub tracker.