v2.0.1 - add `development` tag to images built using dev repo - show repo in Kiosk Host Maintenance Center No new images; Use v2.0.0 release, then click "Update to Latest" in Kiosk Host Maintenance Center (`http://devicename:9090/`)

v2.0 With this release you MUST re-setup host device and re-flash superbird. We now have an updater; you will not need to do this again! - added webui for configuration, viewing device screen, browser devtools, simulating button presses, and viewing logs - port is forwarded thru host device, access it on port `80` - added "Host Maintenance Center" webui - access on port `9090` - combined `browser` and `buttons` services into a single `kiosk` service - all config is now consolidated to `/etc/kiosk/config.json` on superbird device - rewrote all build, update, and install scripts for better approach - added `update.sh` to update everything automatically (for future releases) - moved `/scripts/vnc_passwd` -> `/etc/vnc/vnc_passwd` - and you can change vnc password in the webui - added haproxy to proxy chromium devtools for access outside of localhost - access via main webui, or via port `9223`

v1.9 With this release you MUST re-setup host device and re-flash superbird. The only supported host device is now `Raspberry Pi Zero 2W` with `Raspberry Pi OS Legacy (Bullseye) 64bit Lite` changes: - switched to Debian Bullseye - reduce superbird storage usage from 1.5GB -> 1.2GB - older chromium is more performant without gpu - changed boot logo to Home Assistant icon - xorg now defaults to NOT sleeping - separate images for portrait and landscape (different boot logo) - passwordless ssh key from host -> superbird - renamed "chromium" service to "browser" - `/lib/systemd/system/chromium.service` -> `/lib/systemd/system/browser.service` - `/scripts/chromium_settings.sh` -> `/scripts/browser_settings.sh` - `/scripts/start_chromium.sh` -> `/scripts/start_browser.sh` - `/var/log/chromium.log` -> `/var/log/browser.log`

v1.8 * customized the boot logos a little bit, using [`aml-imgpack`](https://github.com/bishopdynamics/aml-imgpack)

v1.7 * switch from `x11vnc` to `tigervnc-scraping-server` for better vnc performance * default password `superbird`, to change: `sudo vncpasswd /scripts/vnc_passwd`, and `sudo systemctl restart vnc.service` * vnc password now survives upgrade via `update_local.sh`

Happy New Year! v1.6 * `build_image.sh` can now create full image from a stock dump without extra steps * `image_config.sh` now contains all user-configurable values for building and updating image * the 256MB `settings` partition is now mounted at `/config/`, used for chromium user profile * reorganize files to make it clearer where they go

v1.5.1 * fixed oops: missing `/scripts/chromium_settings.sh` in prebuilt image v1.5 * moved chromium settings into separate file `/scripts/chromium_settings.sh` * added buttons service, configure in `/scripts/buttons_settings.py` * need to provide your Home Assistant url, and long-lived token * control a light entity brightness by turning knob, pressing toggles on/off * recall scene/automation/script using buttons along edge, and button next to knob * ditched the heredoc'd files in `install_debian.sh`, reorganized files needed for it * added `update_local.sh` which can update an already-running local device running a previous release Starting with this release, your settings are stored in `/scripts/chromium_settings.sh` and `/scripts/buttons_settings.py`, and those two files will NOT be touched during subsequent upgrades using `update_local.sh`, so your settings will survive upgrades. However, your existing settings will NOT be migrated, so if you use `update_local.sh` to upgrade an existing device you will then need to edit those two files. You should setup ssh key with superbird first, so that you don't have to type the password a bunch of time during upgrade. If you are coming from v1.2 you should flash the image from Releases instead, you will end up with much more free space.

v1.5 * moved chromium settings into separate file `/scripts/chromium_settings.sh` * added buttons service, configure in `/scripts/buttons_settings.py` * need to provide your Home Assistant url, and long-lived token * control a light entity brightness by turning knob, pressing toggles on/off * recall scene/automation/script using buttons along edge, and button next to knob * ditched the heredoc'd files in `install_debian.sh`, reorganized files needed for it * added `update_local.sh` which can update an already-running local device running a previous release Starting with this release, your settings are stored in `/scripts/chromium_settings.sh` and `/scripts/buttons_settings.py`, and those two files will NOT be touched during subsequent upgrades using `update_local.sh`, so your settings will survive upgrades. However, your existing settings will NOT be migrated, so if you use `update_local.sh` to upgrade an existing device you will then need to edit those two files. If you are coming from v1.2 you should flash the latest image from Releases instead, you will end up with much more free space.