v0.0.17 — receiver request scoping and connection recovery
- Restore the listener owner's Hermes home and profile-secret scope for every health/WebSocket request and awaited Assist callback (#53). The registration-time v0.0.16 change was insufficient for the multiplexed gateway reported in #49.
- Retry failed initial Home Assistant WebSocket connections when Hermes becomes available (#52).
- Align the package, HACS integration, add-on scaffold and both Hermes plugins at 0.0.17; update installation and release documentation (#54).
Upgrade
Update the Home Assistant integration through HACS, then reinstall the Hermes-side plugins:
python3 -m pip install --upgrade "hermes-voice-ha-integration @ git+https://github.com/rusty4444/hermes-voice-ha-integration.git@v0.0.17"
hermes-ha-install-pluginsRestart Home Assistant and Hermes. Updating HACS alone does not replace the Hermes-side plugins. The wheel is plugin-focused; the source distribution/tag also includes the HACS component and add-on scaffold.
Verification and limits
CI passed on Python 3.11 and 3.12 for this exact tag; attached artifacts come from its Python 3.12 release-dist. Local tests: 196 passed, one optional Edge TTS synthesis check skipped; compile/build/version/packaging checks passed. Automated mocks and loopback clients do not establish live HA or end-to-end voice compatibility. The add-on remains an early scaffold.
Issue #49 remains open for reporter confirmation on Hermes 0.22.2/Python 3.14, including authentication, Assist replies and reconnection after a gateway restart. Thanks @hanleymk for the detailed multiplexing traceback and verification report. Maintainer preparation/review used Hermes Agent assistance.