Racks, notes and to-do, OS support, suggested dependencies, Nginx Proxy Manager and Home Assistant
- Racks page and a network diagram (UniFi tree with servers, printable) - Notes on servers and devices; To do list shown in Coming up and My work - Agents report the operating system (Linux 7, Windows 6); end-of-life badge and alert - Suggested dependencies from where a service is reached - Nginx Proxy Manager integration: proxy hosts page, certificate and host alerts, suggested checks - Home Assistant integration: watch chosen entities, history chart, limit and unavailable alerts - TimeChart gets a "value" scale that fits negatives; docs updated Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
68b41b5586
commit
18ceed62e8
77 files changed
+20432
-35
No files matched your search
+30
-2
@@ -6,10 +6,10 @@ Homelab Manager (Integrations → Add integration, or DNS → Add
|
||||
provider). All credentials are entered in-app and encrypted at rest —
|
||||
nothing is read from environment variables.
|
||||
|
||||
Every adapter listed here except UniFi performs write actions (starting/stopping
|
||||
Every adapter listed here except UniFi, Nginx Proxy Manager and Home Assistant performs write actions (starting/stopping
|
||||
things, editing DNS records, etc.), not just reads — a read-only
|
||||
credential will fail as soon as you use one of those actions, even if
|
||||
the dashboard views themselves load fine. (UniFi only ever reads.)
|
||||
the dashboard views themselves load fine. (UniFi, Nginx Proxy Manager and Home Assistant only ever read.)
|
||||
|
||||
## Integrations
|
||||
|
||||
@@ -248,6 +248,34 @@ the dashboard views themselves load fine. (UniFi only ever reads.)
|
||||
but nobody has run it against real hardware yet. Every field is read defensively, so one a version renames is left blank rather than breaking the read. If a read fails or comes back empty, the **Diagnostic Log** has
|
||||
what the controller answered; tell us and we'll adjust.
|
||||
|
||||
### Nginx Proxy Manager
|
||||
|
||||
- **Config fields:** NPM's admin URL (the address of its web page, usually port 81), an email and a password, and a checkbox to allow a self-signed certificate.
|
||||
- **Required access:** NPM has no API keys: its API is the one its own web page uses, so the app signs in with an email and password (each read signs in again; nothing is kept). Make a **dedicated user** under
|
||||
*Users* and, under its *Permissions*, give it **View only** on *Proxy Hosts* and *SSL Certificates* — that is all that is read. **Nothing is ever written** to NPM.
|
||||
- **What it does:** when **Network → Proxy hosts** is opened (and for the alerts and the suggested checks, at most once a minute) NPM is asked for its proxy hosts and certificates. Nothing is stored in the database:
|
||||
what is shown is what NPM said a minute ago.
|
||||
- Each host shows its names, where it forwards to — and the server that is, when the address (or name) is one of a server's own, exactly — its certificate and whether it is working.
|
||||
- A certificate that an *enabled* host uses and that ends within 14 days (critical within 3) or has ended is an **expiry** alert; a host NPM says could not be set up (its nginx did not accept the configuration)
|
||||
is a **monitoring** alert. A host that is switched off is left alone. Both link to the Proxy hosts page and can be silenced with maintenance on the integration.
|
||||
- The hosts it serves are offered as **Endpoints → Suggested** checks (a web check on the name people use; https when there is a certificate), linked to the server it forwards to.
|
||||
- If NPM cannot be read, the Alerts page says it could not check, and the integration is raised as failing like any other.
|
||||
- **Not verified against a live NPM** — built from the API its own web page uses (`/api/tokens`, `/api/nginx/proxy-hosts?expand=certificate`, `/api/nginx/certificates`) and tried against a pretend one. Every
|
||||
field is read defensively. If a read fails or comes back empty, the **Diagnostic Log** has what NPM answered.
|
||||
|
||||
### Home Assistant
|
||||
|
||||
- **Config fields:** Home Assistant's address (with the port, usually 8123), a long-lived access token, and a checkbox to allow a self-signed certificate.
|
||||
- **Required access:** read only. Make the token on a user's profile page (*Security → Long-lived access tokens*); the user needs no more rights than a viewer's. Only `GET /api/` and `GET /api/states` are used —
|
||||
**nothing is ever sent** to Home Assistant.
|
||||
- **What it does:** you choose which entities to watch on **Monitoring → Home Assistant** (search by name, then *Watch*; at most 60 per Home Assistant). Every five minutes (and on **Read now**) Home Assistant's
|
||||
entities are read in one call and the watched ones are kept: their state, and for a number a reading for the chart (one at most every two minutes, kept 35 days).
|
||||
- An entity that has been *unavailable* or *unknown* — or has disappeared from Home Assistant — for 15 minutes is an alert. A number past a limit you set (*alert when under / over*) is an alert. Both are in the
|
||||
*Monitoring* category, link to the page and can be silenced with maintenance on the integration.
|
||||
- If Home Assistant cannot be read for twenty minutes the watched entities are neither raised nor cleared, the Alerts page says it could not check, and the integration is raised as failing like any other.
|
||||
- A service reached at a server's address (the integration's URL) is offered as a suggested dependency on that server.
|
||||
- **Not verified against a live Home Assistant** — built from its published REST API and tried against a pretend one. Every field is read defensively. If a read fails, the **Diagnostic Log** has what it answered.
|
||||
|
||||
## DNS providers
|
||||
|
||||
### Cloudflare
|
||||
|
||||
Reference in new issue
Block a user