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>