Home Assistant: reads checked against a live instance

Inspect on a real Home Assistant showed /api/states answers as the reader expects (1,392 entities, every field it reads present). Docs and the adapter's header say so; no code change.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
bobbanandClaude Sonnet 5.5 committed 2026-11-17 19:51:05 +01:00
1 parent d58fe2027b
commit 3fc2a71812
2 files changed
+2 -2

No files matched your search

+1 -1
View File
@@ -369,7 +369,7 @@ osTicket's API cannot close a ticket, so this is the one place in the app that *
*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.
- **Checked against a live Home Assistant** (Inspect): `/api/states` answered with 1,392 entities (about 600 KB) and every field the reader uses had a value. It was not checked with an entity that is `unavailable` or with a wrong token; those follow the published API and a pretend server. Every field is read defensively. If a read fails, the **Diagnostic Log** has what it answered.
### UPS (NUT or SNMP)