An administrator can make named displays (Hall TV, Office monitor) under
Settings -> Share links, each with an address of its own (/wall/hall-tv), the
pages it rotates through in the board's order, and a rotation speed. The
signed-in wall opens one from its address and can switch between them, and a
wall share link can open one too. The address still wins over the display's
speed, then the browser's choice.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Server cards show load and memory over the last 24 hours, endpoint checks show
their answer times with a tick where a check failed, and integrations that keep
a figure history show their headline figure over the last week. Each list asks
for all its lines in one request, drawn from the history already kept, and each
line has a sentence for screen readers.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
On phones the top bar is now sticky and compact with a 44 px menu button, an
open menu scrolls by itself with finger-sized rows, the page asks for the whole
screen (viewport-fit=cover) and keeps toasts, drawers and the bar clear of the
notch and home bar, text is slightly larger on small screens, toasts and
drawers use the full width, and presses do not wait for a second tap.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A small translation system (the English text is its own key, so anything
without a Swedish entry stays English) and a Language switch in the user menu,
saved on the account (users.language) and following the browser when no choice
has been made. Swedish covers the menu, shared parts (search, tables, dialogs,
relative times), the sign-in page and the everyday pages: Dashboard, Alerts,
Servers, Updates, Maintenance, My work, Coming up, To do, Integrations and the
display settings. Server-written messages stay English for now.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The numbers integrations report (queries and blocked share, queue and missing
items, speeds, photos, documents, failed runs, firing rules, targets down,
monthly cost and more) are kept about every quarter of an hour for five weeks,
then as hours and days for up to two years, taken from each integration's
stored reading. Every card on the 14 integration pages gets a Show the
history button with a chart per figure, how it changed and its lowest and
highest. A stretch when the integration could not be read is a gap.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
An update run can name a second Semaphore playbook that restarts the server
once the updates are in and it says a restart is due. The run keeps the
maintenance window up, follows the restart, waits for the server to report
again and checks from its uptime (or its restart flag clearing) that it did
start again. A server that only needs a restart has a Restart button on the
Updates page, and a patch plan can carry the restart playbook too.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A guest's drawer on the Proxmox page now has a Snapshots section. Everyone
signed in sees them, operators take them, administrators roll back and delete
(each behind a confirmation). Proxmox does each as a task, followed for up to
20 seconds. Audit log and change log entries for all three. An http:// Proxmox
address is now allowed.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
An axe-core check of 37 pages in both themes found and fixed low-contrast text
in the status colours (light) and tabs, pills and the info alert (dark),
in-sentence links with no underline, link targets under 24 px, selects with no
name and map nodes whose name did not start with their text. docs/ACCESSIBILITY.md
says what was found and how to run the check again.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Notifications are written down with the alerts they were about, and the
incident timeline lists each one: which channels took it, which refused and
what they said, or why it was held or not sent. New alerts, recovery notices,
reminders and escalations are all covered.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The typical draws in the Inventory, the price of a kWh and the currency set
there give a cost per device and in all, counted in the totals under an
Electricity category when there is a draw, a price and a three-letter currency,
and said plainly (with what is missing) when there is not.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Kind tags (Integrations, Servers, DNS) are in the brand's colour with its logo
(Simple Icons, CC0), kept readable on both themes; the dashboard cards, the
kind picker and the menu show the logos too, with a per-browser switch for the
menu icons. Settings -> Display -> Badge colours shows the brand defaults and
Use the brand's goes back to them.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
One component, PageIntro, for the text under a page's title: shown as it is
when it fits in two lines, otherwise folded with a Show more, remembered per
page in this browser, opened by tabbing to a link in it, unfolded in print.
Used on 41 pages.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Each change a read of a Fragnet account sees, and each power signal sent from
here with who sent it, is written down (180 days). A server's details show the
share of the last 30 days it was on, starts and stops, a seven-day bar and the
latest changes, with who asked for them.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Every notification is written down with how it went through each channel
(or why it was not sent: held for quiet hours, a routing rule said nobody, no
channel on). Records -> Notifications lists them with a filter, a search and
Send again. Errors are cleaned of every secret in the settings; kept 30 days.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A read of a Fragnet account that shows a server on (running or starting) after
it was off, or off (stopped or stopping) after it was on, sends one message
through the configured channels and routing rules, a line for each server.
A server first seen, one whose state is unknown and one being installed or
moved say nothing. Switch: Settings -> Notifications -> What to send (on by
default).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Duplicati posts its message as a form body by default (message=<URL-encoded
text>). Unwrap it (any field name, other fields beside it), take the job and
operation from the 'Duplicati Backup report for <job>' line, read JSON under
that line, and read the Warnings and Errors lists of the text form.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Each machine's card shows whether the last report was a backup, another
operation that was set aside, or one that could not be read (with the reason),
and counts of each since it was added. Administrators can see the start of an
unreadable report.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The first twenty warning messages of each run are kept with the run and shown
on the job and in its history. A job can be set to raise a warning-level alert
when its last run finished with warnings (off by default; a muted job raises
nothing; maintenance on the machine's server silences it).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Reads /api/admin/cluster/state (Technitium 14+): a Cluster table on the page,
alerts for a node unreachable for ten minutes (primary critical) and for a
secondary that has stopped taking the primary's configuration, and three
/metrics series. A server in no cluster shows nothing; a token that may not
view administration is told so and the rest of the read is unaffected.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Three tick boxes on the Fragnet integration: do not alert about disk space,
memory or backups. The page still shows the figures (a switched-off bar is blue
and the backups tile says not judged); /metrics is unchanged.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The page also gives quarterly and annual reports. The route is unchanged; the
scheduled monthly message in Notifications keeps its name.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Settings -> Display -> Menu: when on, the menu, command palette and shortcuts
omit the pages of integration kinds nobody has added (off by default, the same
for everyone). Pages useful without an integration always stay; adding an
integration brings its page back at once.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
One tile per server, time() - homelab_server_boot_time_seconds, in the Servers
row and following the Server picker.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
When each agent-reported server last started (last report minus uptime), so
uptime is time() - the metric and a reboot shows as it moving.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Linux agent 8 and Windows agent 7 say how long the machine has been up; the
server stores it (migration 0086) and shows it as Up for in the status strip
(left out while offline) and Uptime on the server page.
The Integrations header wraps and its button no longer squeezes, and
.table-responsive is positioned so hidden text in scrolled-off columns cannot
widen the page.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Operators and administrators get a Read now button in the card header of each
enabled integration on these six pages, the same as on the media, download
client and Hetzner Robot pages. No server change: all six kinds were already
in the Read-now list.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Operators can ask the game panel for a backup of a server whose plan has room for backups (Back up on the row, Back up now beside its backups). The panel makes it in the background; the page re-reads every 20 s until it is done. Refused here for a plan with no room, a suspended server, one already being backed up, or the same server within 30 s; the panel's own refusals (plan full, rate limit, permission) are shown in its words. Written to the audit log.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Both send to one fixed address each (api.telegram.org, api.pushover.net), take part in routing rules and the channel count, have a Send test that shows the service's own refusal, and keep their tokens and keys encrypted and out of errors and the audit log. A Telegram message carries one button, and a Pushover message one link, to the page where an alert can be acknowledged, silenced or snoozed.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Each cost item's name, amount, currency, period and kind are kept as versions (cost_item_versions), and Hetzner's estimate is written down once a day (cost_snapshots), so a past month's figure and the changes between can be worked out. History card with monthly bars per currency, month-by-month figures and a list of added, changed and removed items.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
POST /api/integrations/:id/read-now reads one integration at once (operators and administrators; not again within 20 s): a kind with a stored reading is read and judged again, a kind read live is asked whether it answers. The three per-kind lists in the integrations routes (add, change, delete) are now one map in services/integrationSyncs.ts. Button on the Integrations cards and the Media managers, Download clients and Hetzner Robot pages.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Read every 15 minutes (Robot allows 200 requests an hour; read-only): each server's product, addresses, status, rescue system and paid-until, and the storage boxes. Adapter, sync service, hetzner_robot_state table, /api/hetzner-robot, Infrastructure → Hetzner Robot page, metrics and docs.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Each client is read every five minutes (read-only; qBittorrent's sign-in is the only POST): speed, queue and item states, network connection or paused queue, free space, SABnzbd's failures and warnings. Shared adapter, sync service, download_state table, /api/downloads, metrics and docs.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
SQLite lets one writer in at a time and refuses a second at once. A write that landed in the pauses of an in-process transaction (the diagnostic log trimming itself, an agent report) was refused with SQLITE_BUSY, and the refused statement left the next transaction unable to commit. Ordinary writes and the next transaction now wait for the open transaction; reads are never held, and a wait over 10 s is given up.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A New badge, a notice with Show only new and Mark all as expected, and Mark as expected on each row. Uses the same rule as the alert and the server's Ports card.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Alert settings keeps Alert rules, Service levels and Alert tickets; administrators get a link to Settings -> Notifications.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Old addresses (/alert-rules, /service-levels, /settings/notifications) lead to the right tab.
Notifications and Alert tickets stay administrator-only.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Backups → Proxmox backups has a Backup coverage tab and a Proxmox Backup
Server tab (?view=pbs), each keeping its own title and buttons. /pbs redirects
to the second tab so old links and favourites still work; the sidebar's two
entries become one, and the Backup Server's alert and integration links go
to the tab. Docs updated.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
With an optional second user on the NPM integration (Manage on Proxy Hosts,
no two-factor sign-in) an administrator can make, change, switch off and
delete proxy hosts: names, where it forwards to, an existing certificate and
what is switched on. Only what differs is sent, a host's access list,
locations and custom configuration are never touched, and combinations NPM
would quietly undo (Force HTTPS, HTTP/2 or HSTS without a certificate) are
refused with the reason. Delete asks for the host's first name, checked
against the host as NPM has it. The user that reads is still view-only and
never writes. Audited; the managing user can be taken away again.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A Change link on the Identity card sets the hostname (a host name or an
address, written lower case without the trailing dot). It is then kept even
when the agent reports another — marked "set by hand", with what the agent
reports shown beside it — until "Use what the agent reports" gives it up. The
agent's own hostname is always remembered (reported_hostname). PUT and DELETE
/api/servers/:id/hostname, administrators only, audited with from and to.
Migration 0082 adds hostname_pinned and reported_hostname and fills the latter
for servers that have reported. It changes this app's name for the server, not
the machine's.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
An Edit zone panel on the open zone of a Technitium provider switches the zone
off and on (its records stay) and edits who may ask it (query access), who may
copy it (zone transfer, with the TSIG keys the server has) and who is told when
it changes (notify). Only the groups that apply to the kind of zone are shown,
a mode that goes by a list needs it, and entries must be addresses or networks;
only groups that differ are sent, each whole, and the zone is read again
afterwards so anything else that moved is named on the page and in the audit
log. The server's own zones are not touched. Administrators only, audited.
Zones in the list show when they are off and what kind they are.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A Delete zone button on the open zone of a Technitium provider deletes the zone
and every record in it: the name has to be typed, and the server checks it
against the zone as the provider lists it now (so a stale page, a wrong id or
an internal zone cannot be deleted by mistake). What this app cached of the
zone and its records goes with it. Technitium's own refusal is shown and
nothing is changed. Administrators only, audited with how many records were
cached; the adapter gets an optional deleteZone.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A New zone form on a Technitium DNS provider makes a Primary zone (a domain
name, or an address or network for a reverse zone), a Secondary zone (from the
servers that hold it) or a Forwarder zone (where to pass questions, the
protocol, DNSSEC). Names are written lower case, ASCII, without the trailing
dot and refused before Technitium is asked if they are not zone names;
Technitium's own refusal (a zone that exists) is shown as it was said.
Administrators only, audited, and only for providers that can (the adapter
gets an optional createZone). The new zone opens when it is made.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A card in the Network section replaces the generic tile: whether DNS answers
and how fast, the last day's queries and the share blocked, a bar of how they
were answered, blocking left off, a stale reading, and what is wrong (the
first two alerts). It follows the other cards: a status badge that colours the
edge and puts it first when it has a problem, hide and move under Customise,
refreshed every minute from the same data as the Technitium page.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
README and INTEGRATIONS: what it reads, the config and token (15.0 or later),
the DNS test, the alerts and metrics, that its API has no CPU, memory or disk
figures, and how it differs from the Technitium DNS provider. ROLES: the page.
DATABASE: technitium_state, migrations to 0081, 91 tables. MONITORING: the
five alerts. PROMETHEUS-GRAFANA: the homelab_technitium_* metrics.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A new integration type (Network, next to AdGuard Home) reads Technitium's API
every two minutes with a non-expiring API token in the Authorization header:
version and uptime, whether blocking is on, block lists and their next update,
the last day's queries and how they ended, cache and zone counts, the top
clients and names, zone health (expired or unsynced secondary zones), DHCP
leases — and puts one real DNS question to it over UDP. A Technitium page
shows it; alerts: DNS not answering (critical), blocking left off, block lists
overdue, zones expired or not syncing; /metrics gets homelab_technitium_*.
Nothing is changed on the server. Technitium's API has no CPU, memory or disk
figures; the page says a server agent covers that. New table technitium_state
(migration 0081).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Each group in Apps → Authentik → Users and groups gets a Delete button: the
group's name has to be typed, and the server checks it against the group as
Authentik has it now. A group that makes its members administrators is
refused (deleted in Authentik). A group that decides roles in this app may be
deleted after a warning, and the audit log records its member count and that
it decided a role. Members stay, just not in the group.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
README: the top cards can be hidden under Customise like the Overview ones, and
what happens when a whole side or the whole row is hidden. ROLES: Customise is
per person and open to everyone signed in.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Customise now puts a name bar with Hide / Show above Needs attention, My work,
Since you last looked, Getting started and the To do list, like the Overview
cards. Hidden cards are gone outside Customise (dimmed inside it), the choice
is saved on the user record and Reset to default clears it. When every card of
one side of the top row is hidden the other takes the full width; hiding all
removes the row. The standalone To do card is an ordinary card rather than the
side-by-side one.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A To do card lists every open job beside the attention, since-you-last-looked
and getting-started cards on wide screens (under them on narrow ones): soonest
due first, a box to tick one off with an undo, and for operators a line to add
one. It is as tall as the cards beside it and scrolls when the list is long.
Same jobs as the To do page.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Like the users, the groups are read on open instead of behind a Show groups
button, for an Authentik that has the management token. If the read fails the
button stays, as Try again.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The list is the point of that tab, so it is read on open rather than behind a
Show users button, for an Authentik that has the management token. If the read
fails the button stays, as Try again. Groups are still read on request.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Apps → Authentik now has two tabs for administrators: Status (the outposts,
certificates, tokens and alerts, as before) and Users and groups (New user,
Users and Groups). The tab is a ?view=users link like the other pages' tabs;
everyone else sees only the status. Docs updated to name the tab.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A New group form in the Groups section makes a group with a name and nothing
else: it starts empty and is never one that makes administrators of
Authentik. A name Authentik already has is refused in its own words, and a
name that decides a role in this app (Settings → Sign-in) is said to. Admin
only; audited with who made which group.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Apps → Authentik gets a Groups section for administrators: the groups with
member counts, and an Edit form to rename one and put users in and take them
out. Members are changed one user at a time, never by replacing the list.
Everything is checked first and nothing changes unless all of it may; service
accounts, the token's own account and the last active administrator losing
that are refused. Whether a group makes administrators is shown, not changed.
Groups that decide roles in this app (Settings → Sign-in) are marked and ask
first. Audited with who was put in and taken out.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Each person in Apps → Authentik → Users gets an Edit form. The user name is
shown but not changeable. Authentik is sent only what differs, and groups as
what goes in and what comes out on top of the user's current groups, so a
membership added meanwhile is kept; a user whose groups Authentik doesn't
report can't have them changed. The server refuses service accounts, the
token's own account, and an edit that would leave no active administrator.
Audited by field name, never by value.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Apps → Authentik gets a Users section for administrators: a searchable list
of people (service accounts left out) with status, administrator and last
sign-in, and Switch off / Switch on / Delete. Switching off sends only
is_active; deleting needs the user name typed and re-checked by the server.
The server refuses service accounts, the account the token belongs to and
the last active administrator. Each action is audited. The token field is
now "Token for making and managing users".
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
An administrator can make a user (user name, name, optional email, groups)
and gets a recovery link to send them, so they choose their own password;
no password is set or seen here. Uses a separate optional "Token for making
users" on the Authentik integration; reading never uses it, and it can be
removed again from the page. The link is shown once and never stored or
audited; the audit log records who made which user and link.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The health pass keeps the host ports Dockhand says running containers
publish (new table server_container_ports, migration 0080), matched to a
server by its Docker host's name. They name the port on the server's Ports
card and the network Ports table, ahead of a port preset and behind a
label somebody wrote, and in the new-port alert ("8096/tcp jellyfin
(container)"). Never written onto port notes, so a container's port is
still a new port; an unreadable host keeps its names, a day-old name is
dropped. Dockhand is now read on the health pass even with container
alerts off.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A "How many" field (1-20) next to Generate gives that many different
names, none already used by a server and none twice; a list with a Copy
button per name and a "Copy all" appears when more than one is made.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Lidarr and Readarr join the shared *arr reader. Integrations get an Inspect button that
runs the reader once and shows what each request returned as shapes (never values) and
where the result is empty. Operations -> App versions compares each application's version
with its newest GitHub release (lookup off until an admin switches it on; optional alert).
The Alerts page can group by source, kind of problem or type of alert. The shared HTTP
helper no longer reuses connections (stale-socket resets). Migration 0078; docs and tests
included.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
New integration kinds adguard (status, statistics, filter lists and a real DNS question
over UDP; alerts for DNS down/not running, protection left off, stale lists) and grafana
(alert rules firing or failing, data-source health). Optional warning for running Docker
images built more than N days ago (off by default). A server's overview cards can be
folded and arranged, kept per user. Migrations 0075-0077; docs, metrics and tests included.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A "What to do" note (text and/or link) can be written once for a whole kind of alert and
shows beside every alert of that kind; alerts now carry their kind and source type.
New optional setting: warn when a Docker host has N or more high vulnerabilities (off by
default). The wall display gains tiles (Hetzner and game servers running, critical
vulnerabilities, stuck downloads) and a summary line for each group of integrations,
also in share links. Migration 0074; docs and tests included.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
New integration kinds sonarr, radarr and prowlarr (shared adapter and sync, page under
Apps -> Media managers): own health findings, stuck downloads, nearly full disks.
Hetzner now reads load balancers (target health), floating IPs and certificates, includes
them in the cost estimate, and forecasts the month's traffic against the quota.
Migrations 0072 and 0073; docs, metrics and tests included.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
New integration kind "fragnet" reading Fragnet's Pterodactyl-based panel through the
client API (account key). Game servers page under Infrastructure with game, IP:port,
state, memory/disk, backups, schedules and databases; alerts for late backups and
nearly full disk/memory; operators can start/stop/restart/kill (audited). Metrics,
docs and tests included; migration 0071 adds fragnet_state.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
- Speedtest Tracker integration: charts, alerts for a slow line (median of the
last three tests under a share of what is paid for) and for failing tests.
- Costs page (Records): things paid for by hand plus Hetzner's estimate, totals
per currency, bills rolled forward into Coming up as Renewals.
- Status pages: a "Having trouble" state for things that answer but have an open
alert; Speedtest reads as the internet.
- Integrations page and kind picker grouped like the sidebar (one shared types
file); Notifications "What to send" shown one group at a time; Dashboard
integration sections follow the menu groups, with tiles for integrations that
have no widget.
- Docs, tests, and ROLES.md menu table brought up to date.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Closing several alerts together can now also close their osTicket tickets
(one by one, each written on its incident and in the audit log; one that
fails does not stop the rest; Undo does not reopen tickets). The single
and bulk close share one helper. Alerts moves to the top of the sidebar,
and Monthly report and Change log move to a new Records group. Docs updated.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Reference holds Map, Inventory, Admin Links and Generator, leaving
Infrastructure with live systems only. Docs and UI text name the new
locations.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
New Apps group (Home Assistant, Jellyfin, Immich, Paperless, Nextcloud,
Authentik). Hetzner Cloud moves to Infrastructure, NetBox to Network and
n8n to Automation. Docs now name the new locations.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
One integration per project (read-only API token, read every 5 minutes).
Alerts for a server that was running and is off, stuck statuses, traffic
at 80%/100% of the monthly quota, rescue mode left on, and late backups.
The Hetzner page lists servers, volumes, snapshots and a cost estimate; a
server the app knows by its agent gets a Hetzner card on its own page.
/metrics and docs updated.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Reads what Dockhand's scans have already stored (never starts one) every
15 minutes and raises a warning per Docker host with critical findings.
Unknown counts and stale readings are held, not treated as clean.
Settings -> Notifications has a switch (on by default); the Docker page
shows counts, scan coverage and the critical findings; /metrics and docs
updated.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Nextcloud: its own "Cron last run" setup check (GET /settings/setupcheck,
Nextcloud 28+, found by class name) raises an alert when background jobs have
stopped; other checks that report an error are one alert, warnings are shown
on the page. The core version Nextcloud says is available is shown too. Before
28, cron and the checks are unknown, never "fine".
Alerts page: bulk Close... (one reason, written on each incident, undoable) and
Open again. Bulk Wake now leaves closed alerts alone.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The Close drawer can also close the alert's osTicket ticket. osTicket's API
cannot, so this writes to its database with a separate, optional login: the
ticket is set to Closed, a note in its thread says who closed it and why, and
the closed event is recorded, in one transaction. Tables and columns are
checked first, only an open ticket is closed, and a ticket closed by somebody
else at the same moment is left alone. Summary tickets are not closed from here.
"Test closing" (Alert tickets settings) tries every write and rolls it back.
If the ticket cannot be closed the alert is still closed and the reason is
said, noted on the incident and audited.
Not run against a real osTicket: tested against a pretend database only.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Close... on the Alerts page hides an alert with no end, with an optional reason
that is also written on its incident. It opens again only if it gets more
serious than when it was closed (said once) or the problem has been gone for
half an hour; Open again brings it back at once.
Built on the snooze table (kind, severity and note columns), so everything that
holds back snoozed alerts holds back closed ones. Audit log, change log and
/api/v1 alerts carry it.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Three read-only integrations, each with a monitoring page, alerts, maintenance
silencing and held-when-unreadable handling.
Nextcloud: database needing upgrade (critical), maintenance mode, and the data
disk running low; users, files and app updates with an admin app password.
NetBox: no background worker running, counts, and a list of the servers this
app manages that have no address in NetBox (a list, not an alert).
n8n: an active workflow whose last run failed, clearing when it next succeeds.
Disk messages for Immich, Paperless and Nextcloud now use the same units as
the pages that show them.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Bulk snooze: Snooze... and Wake on the ticked alerts, with undo that puts back
each alert's earlier snooze exactly.
Alert rules are judged for a server right after its agent reports, instead of at
the next 15-minute pass; only that server's rule findings change, and the check
is serialized with the pass so neither overwrites the other's state.
Photos on server and device notes: up to 12 each, shrunk in the browser,
accepted by their own bytes (JPEG/PNG/GIF/WebP, 4 MB), kept in the database and
removed with the server or device.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Three read-only integrations, each with a monitoring page, alerts, maintenance
silencing and held-when-unreadable handling.
Prometheus: scrape targets that stop answering (5 minutes, one alert per job)
and alerts that Prometheus's own rules fire (critical when labelled so).
Immich: disk under the library filling, failed background jobs, counts.
Paperless-ngx: worker/database/Redis in error, documents that failed to
import, index and sanity check, disk. Immich and Paperless also in /metrics.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
New Authentik integration (read-only, every 5 minutes): version, workers,
outposts and their health, certificates and API tokens that expire, failed
sign-ins and configuration errors. Monitoring -> Authentik page.
Alerts: an outpost that serves apps has gone quiet (critical), certificate or
token about to run out (critical close to it), no worker, failed sign-ins,
configuration errors. Held by maintenance, held when unreadable, in /metrics.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
New Jellyfin integration (read-only, every 2 minutes): version, restart wanted,
streams and transcoding, failed scheduled tasks, item counts, failed sign-ins.
Monitoring -> Jellyfin page with a peak-streams history, three alerts, /metrics.
When Jellyfin runs on a managed server, an update run asks first if people are
streaming (409 "watching" unless startAnyway), and a patch plan waits up to two
hours for them before updating that server.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Duplicati reports each operation to a secret address (its own send-http-url option), so
nothing calls Duplicati and no password for it is kept. Each machine is a source; each job
is learned by name and shows its last result, duration, size, changes and a history.
A failed run is a warning (critical from the second in a row); one that has not succeeded
for longer than expected (per job, 2 days by default) is a warning, critical at three
times that. Maintenance on the machine's server silences them; /metrics series added.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
With Dockhand connected, an image the app recognises (about 20 with a health endpoint of
their own, plus a few dozen web UIs) is offered as an endpoint check on that app's own
health address, with what a good answer looks like set up as a value check: Immich's ping
says pong, Nextcloud's status.php is not in maintenance, Gitea's health says pass, and so
on. Asked on the Docker host's address at the port the container publishes. Container
ports are now read from Dockhand's list.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
From Dockhand, on the health pass: a container that keeps restarting (critical, with
its exit code), one whose own health check fails, one that stopped unexpectedly, one
created and never started for an hour, and a Docker host Dockhand cannot reach. A stop
is only news when it was seen happen, so stacks switched off long ago stay quiet.
A Leave alone button on the Docker page and a list in Settings; on by default.
Also fixes a date-dependent storage-forecast test that pinned its clock while the code
under test reads the real one.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
For a one-person homelab, "on call" is when you can be reached. Settings ->
Notifications -> When -> Away holds notifications while you are away (a banner on
every page says so) and sends one digest when it ends, at its time or when you say
you are back. Critical alerts can still come through. Quiet hours get the same
"still send critical alerts" option. Escalation steps marked to send in quiet hours
are sent while away too. What is held for one reason is not released while the
other still holds it.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Monitoring -> Service levels: a target (99.9 %) on an endpoint check, a server or an
integration, measured over calendar months. Shows the figure, downtime used, the
error budget left, and how the last six months went. 80 % of the budget used is a
warning and an overspent budget a critical alert. Endpoints are measured day by day,
servers and integrations to the minute from the audit log.
The report page gains Quarter and Year (same figures, with a Service levels section),
and two settings send the quarterly and annual report after the month that ends them.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Each server's CPU load and memory use get a baseline for every hour of the week
(median and robust spread over up to ten weeks, four needed). A clearly high last
hour that never dropped back toward normal is a warning; everything else stays
quiet. Server History -> Trends draws a usual line and band. Setting under
Notifications, on by default.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
New UPS integration (NUT or SNMP v2c, read only). Monitoring -> UPS shows charge,
runtime, load and mains voltage with history and the times mains power was lost.
Mains lost and a nearly empty battery are critical alerts; battery to be replaced
and a heavy load are warnings. The UPS is a node in the dependency map and counts
as down while on battery, so servers that go offline with it are folded under its
alert; the page lists what is on it in the order to shut it down. /metrics series
and docs added.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A web check can read a value out of a JSON answer (power.now, state,
data.result[0].value[1]) and judge it: below, above, equal to, contains, is there.
The value read is shown on the Endpoints page, charted under History, exported as
homelab_endpoint_value and in the read API. A check can also send one header (a
token), stored encrypted, never returned, and not forwarded to another host on a
redirect.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Settings -> Data -> Storage measures the database, backups and sessions and every
table (size, rows, growth, how long it is kept, how far back it reaches), and flags
histories that are not being trimmed or have no limit.
Event webhooks now keep a delivery log (last 100 per webhook, 14 days): what was
sent, how it went, the message itself, and Send again, which resends it exactly as it
was (same id and signature). Resends are audited and in the Change log.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
- A switch (off by default) under Settings -> Notifications -> Who hears what
- ntfy gets buttons (three for one alert, one link for several); phone push gets two buttons handled by the service worker; Gotify, email and the chat webhook get the link as text; escalation messages carry them too
- Each link is a signed token for the alerts in that one message only, good for 24 hours, for three actions; opening it changes nothing, only a POST acts; everything is audited as "from a notification link"
- Docs updated
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
- A card on the incident page, and GET /api/incidents/:id/before and /api/v1/incidents/:id/before: what the app knows happened in the 30 min to 24 h before an alert began (audit log, maintenance windows, update runs and patch plans, other alerts, a step in the server's own figures), scored by how related, what kind and how close
- A host going down is shown once; Likely, Possible and Background; at most ten
- Docs and roles updated
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
- New docs/ folder: SSO, API, Prometheus and Grafana, webhooks, heartbeats and calendar, how monitoring works, and an index; the old root API.md is split across them
- Read API: alerts carry snoozedUntil
- DATABASE.md: table and migration counts, indexes, relations, integration config, settings and internal flags, delete rules, retention
- ROLES.md: the sidebar table rebuilt from the menu
- NOTIFICATIONS.md, INTEGRATIONS.md, BACKUP.md, AGENT_UPDATE.md: what had drifted
- README: links to the guides; accounts cannot be deleted in the app
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
- Monitoring -> Alert rules: CPU, memory, disk use and disk temperature limits with a time, severity and scope (all, one server, a tag); try before saving; findings are ordinary health conditions
- Proxmox storages and Synology volumes are written down on each health pass (hourly, 400 days) and forecast like server disks: badge and history chart on the pages, alert, digest line, /metrics gauge
- Snooze an alert until a time; held back like maintenance, messages held, announced once again if still there when it ends
- Docs updated
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
- The open jobs about a server (or device) are listed on its page, with a line to add another already about it and a box to tick one off with Undo
- GET /api/todos takes ?targetType=&targetId= to list only those about one thing
- README and ROLES updated
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>