MarekWo c36d7b5fbf fix(ble): simplify reconnection — rely on container restart for clean state ...

In-container BLE reconnection is unreliable because bleak leaves stale
GATT notification handles after abnormal disconnect, and adapter power-
cycling from within Docker corrupts bleak's internal BlueZ manager state.

New approach:
- On BLE disconnect or keepalive failure, immediately mark as permanently
  failed (no in-container reconnect attempts)
- Health endpoint returns 503, Docker healthcheck triggers container restart
- Docker entrypoint script disconnects stale BLE connections before app
  starts, ensuring clean GATT state for bleak

This is reliable because:
- MeshCore.create_ble(address=...) works on fresh container starts
- The BlueZ daemon on the host maintains adapter state correctly
- Container restart is fast (~5s) and gives a truly clean BLE state

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-04-05 16:39:03 +02:00

..

updater

fix: Improve update UI and install script

2026-01-22 08:18:14 +01:00

watchdog

feat: add BLE transport support for companion devices

2026-03-29 10:03:45 +02:00

check_compat.py

refactor(ui): rename contact type label CLI to COM (companion)

2026-03-21 14:37:30 +01:00

docker-entrypoint.sh

fix(ble): simplify reconnection — rely on container restart for clean state

2026-04-05 16:39:03 +02:00

update.sh

feat: Add update script for easier upgrades

2026-01-20 16:27:18 +01:00