Better montiring, bug fixes.

README.org

@@ -128,6 +128,48 @@ homey-deploy-rpi-main
 NixOS activates the new config on the Pi immediately, with an automatic
 rollback if activation fails.
 
+* Post-deploy setup
+
+Some services require manual one-time configuration after the first deploy.
+
+** Ntfy — push notifications
+
+Ntfy's admin user is created automatically from sops on first start.  You
+still need to create a phone token and subscribe to the alerts topic.
+
+1. Visit =https://ntfy.zakobar.com= and log in with the admin password
+   (=ntfy/admin_password= in =secrets/secrets.yaml=).
+2. Go to *Account → Access Tokens → Create token* — give it a name (e.g.
+   "phone") and copy the token value.
+3. In the [[https://ntfy.sh][Ntfy mobile app]]:
+   - *Server*: =https://ntfy.zakobar.com=
+   - *Access token*: the token you just created
+4. Subscribe to the =alerts= topic in the app.
+
+** Uptime Kuma — notifications (two-deploy process)
+
+Uptime Kuma monitors are created automatically by the sync script on first
+deploy, but notification channels must be configured in the UI before they
+can be attached to monitors.  This requires two deploys:
+
+*Deploy 1* — services are up, monitors exist, but no notifications assigned yet.
+
+Then, in the Uptime Kuma UI (=https://uptime.zakobar.com=):
+
+1. Go to *Settings → Notifications → Add Notification*.
+2. Choose *ntfy* as the type and fill in:
+   - *Server URL*: =https://ntfy.zakobar.com=
+   - *Topic*: =alerts=
+   - *Token*: use the admin token (or create a dedicated one in ntfy)
+3. Save — you do *not* need to manually assign it to any monitor.
+
+*Deploy 2* — run =homey-deploy-rpi-main= again.  The sync script will detect
+the newly configured notification channel and attach it to every monitor
+automatically.
+
+Any notifications added to Uptime Kuma in the future will also be picked up
+on the next deploy.
+
 * Backing up
 
 Backups use [[https://restic.net/][restic]] and run automatically via systemd on a daily schedule.