fix: IP-independent pairing key fallback; run commands off the paho thread
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -51,6 +51,8 @@ Format: `YYYY-MM-DD: <decision> — <why>`
|
||||
|
||||
- 2026-10-23: TV DHCP-reserved at 192.168.0.20 (Omada) — bscpylgtv keys pairings by IP, so every DHCP drift (7 IPs so far) re-triggered the on-TV auth prompt, and a missed prompt hung `off` past the 60s timeout. New IP seeded with the newest stored key (.31) so no re-prompt. Also: on_message now catches all exceptions — one escaping killed paho's thread while the poll loop kept the process alive (silent zombie).
|
||||
|
||||
- 2026-10-23 (later): Reservation alone didn't hold — the TV came back on .45 minutes later and prompted again. lgtv.sh now falls back to the newest stored key when there's no key for the current IP, so IP drift is harmless. Bridge commands run on a single worker thread so a 60s `off` can't starve paho's keepalive and drop queued commands.
|
||||
|
||||
## Deferred / Rejected
|
||||
- **DHCP reservation for the TV (static IP):** not done — Pi-hole doesn't run
|
||||
DHCP (router does), so it's Seth's action on the router. The cached-IP probe
|
||||
|
||||
Reference in New Issue
Block a user