CZ: Opraven pád výsledné obrazovky. Web 1.1.0 používá pouze HTTP; odstraněny zastaralé volby a nápovědy. Vyřazené položky se převádějí deklarativně. Ověřeno skutečnou aktualizací na VM200. EN: Fix final outcome rendering, remove Web UI TLS, and migrate module-declared retired settings. Validated with actual VM200 installation/update, HTTP authentication and bilingual form tests. |
||
|---|---|---|
| docs | ||
| examples/checkers | ||
| schemas | ||
| tests | ||
| wdinstaller | ||
| .gitattributes | ||
| .gitignore | ||
| .install-watchdog | ||
| CHECKERS-RELEASE-NOTES.cs.md | ||
| CHECKERS-RELEASE-NOTES.en.md | ||
| CHECKERS-VALIDATION.md | ||
| HTTP-ONLY-RESULT-VALIDATION.md | ||
| MATRIX-SETUP-VALIDATION.md | ||
| MULTI-INSTANCE-VALIDATION.md | ||
| NOTIFIER-SETUP-VALIDATION.md | ||
| NOTIFIERS-VALIDATION.md | ||
| README.en.md | ||
| README.md | ||
| RELEASE-NOTES.cs.md | ||
| RELEASE-NOTES.en.md | ||
| RELEASE-VALIDATION.md | ||
| watchdog-installer | ||
| WEB-HTTP-VALIDATION.md | ||
| WEB-UI-VALIDATION.md | ||
WatchDog 5 — Core 1.6.0 / Home Assistant 2.5.1 / installer 3.6.1
WatchDog runs independently, monitors targets, keeps history and incidents, and provides a live console view. Home Assistant is optional. ICMP ping is built in; optional TCP and HTTP/HTTPS checkers 1.0.0 verify actual services; see docs/modules/tcp-http-checkers.md.
Install WatchDog
Target: Debian 12 / TurnKey 18.1 x86_64, Python 3.11, systemd; root.
git clone https://git.pandafun.cz/administrator/watchdog-5.git watchdog-installer
./watchdog-installer/.install-watchdog
The default branch is installer-v3. The independent installer fetches selected modules' small declarative menus first and acquires runtime only after plan approval. Defaults: /opt/watchdog5 and service account admin. It supports install, update, maintenance backups, restore and uninstall. Select Czech or English; add languages through catalogs. Update the installer/catalog with git pull --ff-only in its checkout.
Connect Home Assistant
- Select the Home Assistant module during WatchDog installation. Required Core API is enabled automatically on localhost.
- On HA OS add the app repository https://git.pandafun.cz/administrator/watchdog-5#ha-apps in the app/add-on store.
- Install and start WatchDog Home Assistant Gateway. Its package bundles the custom integration and prepares fresh integration files automatically. Existing unowned or modified files require explicit adoption in the app Web UI and are backed up first.
- Restart HA Core after first integration installation or integration file updates. The app does not restart other integrations automatically.
- Open the app Web UI, run its displayed command as root on WatchDog, paste the one-use code and the actual HA LAN IP. After successful pairing confirm the discovered integration. Existing config entries are updated without duplication.
Use Change connection with a fresh code to replace HA, refresh credentials or pin a new host key. A failed change restores the old connection while ownership still matches. Disconnect WatchDog removes only registered transport and revokes runtime access; Core, targets and history remain. Remove the config entry in HA separately when all its devices should be removed.
Administrator SSH private keys are never uploaded. The dedicated runtime private key stays on WatchDog; permanent credentials never appear in the browser. The pairing code is secret and expires within ten minutes. Temporary TLS port 18765 must be reachable from HA and closes after the operation. Runtime SSH defaults to HA port 2222, app HTTP to 8099. The GUI is available through administrator-only HA ingress.
Operate and recover
Target: WatchDog VM, account admin.
/opt/watchdog5/watchdogctl live --config /opt/watchdog5/configuration/core.json --database /opt/watchdog5/data/watchdog.db
Updates preserve UUIDs, targets and persistent data according to the reviewed policy. Backups contain no application code; normal data backups exclude the private credential vault. Re-pair when credentials are lost. HA reconciles removed targets/checks/unused modules only from authoritative healthy snapshots, never an outage. Translating names preserves existing entity IDs. Control actions require explicit Core API scopes and RBAC; read-only defaults are never promoted.
Supported installation profile: Debian 12 x86_64/Python 3.11. The HA app targets HA OS/Supervisor amd64. Other platforms, architectures and indefinite production uptime are not certified by this release. Historical bootstrap 1.x installations are not silently adopted by standalone installer 3.x.
See RELEASE-VALIDATION.md for completed checks. Older docs/operations reports describe historical releases, not the current setup. The source branch retains historical compatibility fixtures; use installer-v3 for normal installation.
Production checkers 1.0.0 and the Core 1.4.2 compatibility fix are documented in CHECKERS-RELEASE-NOTES.en.md and CHECKERS-VALIDATION.md.
Telegram and Email 1.1.0; Matrix 1.1.1: English documentation, production acceptance.
Matrix setup 1.1.1 fix and validation
Web interface 1.1.0
Optional live targets, history, incidents, dependencies, modules and Core health. CS/EN catalogs, read-only access through the shared Core API, with the required API selected automatically by the installer. Web module documentation.
Multiple installations and additional modules — 3.6.1
Installation discovery uses the systemd system manager exclusively, including stopped and disabled services. Core and API are grouped by configuration, database and service account. No application directories are crawled, and historical installer records do not create discovered installations.
Choose Install additional modules, select an instance, then select new modules. Their setup descriptors are fetched from the signed catalog. Existing targets and module settings are preserved; required local API services are installed automatically. Review, full backup and failure rollback use the normal transactional lifecycle. Update the installation first if existing component versions differ from the current catalog.
Each new installation uses UUID-derived service names, its own <installation directory>/watchdogctl command, and an automatic local API port in 28765–29764 when needed. Port 18765 remains available for temporary HA pairing. Legacy installations retain their existing service and command names.
Systemd determines which installations exist. Safe maintenance additionally verifies service and code ownership. New installations also keep a protected local .watchdog-instance.json lifecycle snapshot for recovery when a central ownership record is missing; this file is never a discovery source. Manual installations without compatible lifecycle metadata are visible but are not automatically adopted or deleted. Manually launched processes and containers are outside system-service discovery.
Web 1.1.0 serves HTTP only and has no certificate options.