Rackpad 1.9.0-beta.5
This beta adds Home Assistant inventory and latest entity readings. It completes
the six standalone feature batches; V2 agents and automation remain deferred.
Earlier batches retain their own release notes.
Configure the Home Assistant HTTP(S) base URL and enter a bearer access token in
the API key field. Credentials remain encrypted and write-only. Rackpad reads
REST /api/states, then authenticates an outbound WebSocket and requests only
config/device_registry/list and config/entity_registry/list. It sends no
subscriptions, service calls or state mutations. MQTT-backed, Z-Wave, Zigbee and
Matter entities are available through Home Assistant; Rackpad opens no direct
broker connection and installs no native radio driver.
Stable registry IDs group entities into devices and preserve bindings across
names changing. Registry-only devices and entities remain visible with unknown
readings. A restricted account can provide entity readings without registry
grouping; Rackpad reports that limitation explicitly. Entity-only identities
without registry access depend on entity IDs and can require rebinding after a
rename. Only identity, selected descriptive attributes, state and units are kept;
configuration URLs and arbitrary provider attributes are not imported.
Numeric values remain unknown health unless the provider supplies a supported
health meaning. Supported binary connectivity/problem/safety and update readings
have normalized health. Intentional off states, disabled entities, unavailable,
pending, maintenance and missing observations do not become false device outages.
Observation time uses last_reported, falling back to last_updated; old reports
can consequently remain stale until the provider reports a newer timestamp.
Collection has one 15-second deadline across HTTP, DNS and WebSocket work. Numeric
address pinning retains the original Host/SNI and certificate-name verification.
WebSocket redirects and compression are disabled, and frame/control/message
counts and bytes are bounded. Inventory/latest readings are capped at 10,000;
the existing inventory preview shows its first 500 records with a limit warning.
Further records remain available as readings and can be bound to manual inventory.
Oversized or ambiguous responses fail rather than silently dropping records.
Inventory adoption and binding are explicit. Polling starts disabled (60 seconds
when enabled), and mapped monitors start disabled. Readings alone do not affect
device health or send alerts; degraded alerts require their own opt-in. No
telemetry history database is introduced.
Schema is 62 with no additional migration in this batch. Logical/native
recovery preserves Home Assistant connections, encrypted credentials, bindings
and latest readings; restored caches require refresh. Keep the matching
pre-upgrade database, configuration and encryption key with the preceding image
for paired rollback. The WebSocket client dependency is pinned to ws@8.22.0.
Validation uses disposable data, synthetic API/protocol fixtures and a temporary
local verified-TLS WebSocket fixture. Candidate CI additionally runs the built
collector against a pinned official Home Assistant container for REST/WebSocket
authentication, demo registry grouping/rename, connectivity transitions and
state normalization. The service test uses HTTP/WS; TLS, Rackpad routes and
credential/recovery behavior retain their separate gates. Real installation,
MQTT/radio and hardware acceptance remain separate. Publication still requires exact committed CodeQL
approval, full MCP/browser and screenshot gates, Net-SNMP interoperability, Linux
storage/user checks, hosted security/quality gates, and AMD64/ARM64 fresh install,
preceding-published-image upgrade, persistence/restart and paired rollback.
The smoke harness accepts predecessor schemas 58–62, including equal-schema
upgrades, with version-gated production API fixtures for references, floorplan
images/markers, latest readings/bindings/disabled monitors and provider
credentials/options. Verified preceding-image pins and actual execution on both
Linux architectures remain required for each publication in the release tracker.
Verify published revision/digests before announcements or issue closure.