hermes-agent/gateway/platforms
teknium1 c45aeb45b1 fix(whatsapp): wait for connected status and log bridge output
The gateway health check broke out of the polling loop as soon as
the bridge HTTP server returned 200, regardless of the actual
WhatsApp connection status. This meant 'Bridge ready (status:
disconnected)' was printed and the gateway moved on, even when
WhatsApp never connected.

Additionally, bridge stdout/stderr were piped to DEVNULL, so if the
session had expired and the bridge needed a QR re-scan, the user had
no way to see that. The 'Scan QR code if prompted (check bridge
output)' message was misleading since there was no output to check.

Changes:
- Health check now has two phases: wait for HTTP (15s), then wait
  for status:connected (15s more). Total 30s budget.
- Bridge output routes to ~/.hermes/whatsapp/bridge.log instead of
  DEVNULL — QR codes, errors, reconnection msgs are preserved.
- Clear warnings with actionable steps if connection fails after 30s
  (check bridge.log, re-pair with hermes whatsapp).
- Removed misleading 'Scan QR code' message.
- Log file handle properly cleaned up on disconnect.

Fixes #365
2026-03-04 04:58:28 -08:00
..
__init__.py Enhance CLI with multi-platform messaging integration and configuration management 2026-02-02 19:01:51 -08:00
base.py feat(gateway): include Discord channel topic in session context 2026-03-01 03:48:24 -05:00
discord.py feat(gateway): include Discord channel topic in session context 2026-03-01 03:48:24 -05:00
homeassistant.py feat: enhance Home Assistant integration with service discovery and setup 2026-03-03 05:16:53 -08:00
slack.py refactor: enhance API interaction and message handling in AIAgent 2026-02-21 04:17:27 -08:00
telegram.py fix: Telegram adapter crash on Windows when library not installed (#304) 2026-03-02 22:03:36 -08:00
whatsapp.py fix(whatsapp): wait for connected status and log bridge output 2026-03-04 04:58:28 -08:00