4 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 5.5	4c9ed02652	feat(homeassistant): its page offers the metrics scrape under the same sign-in, so one user covers everything (#6744) ... A Prometheus target's token_from names the plugin that supplies its token at each scrape. Read its metrics makes the target; Use this sign-in moves one at that address across, keeping its name, filters and history. A refusal stops the connection, so one Try again or sign-in starts everything, and the sign-in is only sent to its own address. A 404 says how to turn on Home Assistant's Prometheus integration, as Steward doesn't change Home Assistant. Refused also joins the volatile columns a backup check ignores. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-01 12:06:55 -05:00
bvandeusenandClaude Opus 5.5	66a5dd12fd	fix(prometheus): a refused token stops the scraping, as Home Assistant bans an address after a few refusals (#6355) ... Also names the Home Assistant connection by its address in the audit log and timeline, where its id showed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-01 09:41:53 -05:00
bvandeusenandClaude Opus 5.5	0aed863c67	feat(homeassistant): an admin signs in to Home Assistant, with nothing added to it (#6355) ... Replaces the read-only token and the webhook automation, which every install would have had to paste into its own Home Assistant. Connect now goes to Home Assistant's own sign-in page, and Steward keeps the refresh token that comes back, encrypted, and calls backup.create_automatic and update.install directly. The connection page warns that the stored credential has the same access as the user who signed in, and recommends a service account so Steward's actions are easy to tell apart in Home Assistant's logs. A user who isn't an administrator gets the status page and no Install. Those actions answer only when finished, so a request cut off once sent counts as sent and the outcome is read from the entities. Removing the connection, or signing in again, ends the old sign-in on Home Assistant. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-31 12:14:34 -04:00
bvandeusenandClaude Opus 5.5	b2a6e92ed3	feat(homeassistant): waiting updates, backup age, and updates installed after a confirmed backup (#6355) ... A new plugin reads Home Assistant with a read-only token every 5 minutes and shows which Core, OS and add-on updates are waiting and how old the last backup is. Install takes a backup through a local-only webhook, confirms Home Assistant's last-backup time moved, installs, and follows the update to its end, through Home Assistant's and Steward's own restarts. One runs at a time. Each ends as one timeline entry. Steward holds nothing that can act on the house: the webhook's automation can only take a backup or install an allowed update (System 231's ruling). A refused token stops polling, as Home Assistant bans an address after a few refusals. Milestone 576 steps 1 to 5. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-30 23:09:27 -04:00