v0.1.3

Installation fixes

This release is about making BlueWatch easy to install. Thanks to @skinnypuppy and @buttim for reporting #1.

• Fixed: the web UI did not start in Docker (#1) and after a regular pip install. The logo lived outside the Python package, so it was missing from the Docker image and from non-editable installs, and the web server refused to start without it. The logo (and the bundled data files) now ship inside the package, and a missing asset can no longer stop the UI from starting.
• New: one-command Linux install. ./install.sh now works on Raspberry Pi OS, Debian and Ubuntu: it installs BlueZ, sets up a private virtual environment in /opt/bluewatch, and registers a systemd service that starts at boot. ./install.sh uninstall (--purge to wipe data) removes it. Upgrade with git pull && ./install.sh.
• Fixed: bluewatch.service pointed at the system Python and failed with ModuleNotFoundError; it now uses the installer's virtual environment.
• Fixed: README instructions. The manual Linux install failed on current Debian / Raspberry Pi OS (PEP 668), the clone URL was a placeholder, and cd bluewatch failed on Linux (the folder is BlueWatch).
• Fixed (macOS): ~2 minute startup delay caused by a Bluetooth pre-flight wait (same fix as upstream bluehood #48). install.sh also now verifies that the dashboard really answers, and shows the correct PID.

Removed

• The unfinished /nr (Neighborhood Rhythm) reverse proxy and its nav link. It will return in a later release once it is ready.

Tested

Native install with install.sh: Raspberry Pi 5 on Raspberry Pi OS Bookworm (32-bit, Python 3.11) and Trixie (64-bit), plus macOS (launchd). Docker Compose: Raspberry Pi 5 (Trixie, 64-bit) and Docker Desktop on macOS. Service starts after reboot on both Pi OS versions.

Notes

• Docker on Raspberry Pi needs a 64-bit OS and the Compose v2 plugin (see the README). On 32-bit Raspberry Pi OS use ./install.sh instead.