Skip to content

fix(philips_hue): retry on transient bridge blips, not just IP changes#187

Merged
AVADSA25 merged 1 commit into
mainfrom
fix/hue-transient-retry
Jun 8, 2026
Merged

fix(philips_hue): retry on transient bridge blips, not just IP changes#187
AVADSA25 merged 1 commit into
mainfrom
fix/hue-transient-retry

Conversation

@AVADSA25

@AVADSA25 AVADSA25 commented Jun 8, 2026

Copy link
Copy Markdown
Owner

Problem

The self-heal from #183 only retried when rediscovery returned a different IP. So a momentary ConnectionError while the bridge stayed at the same address (a brief Wi-Fi/bridge blip) still surfaced as 'Could not reach Hue Bridge' — observed live after #183 merged.

Fix

On ConnectionError: (1) a quick retry at the same IP absorbs a brief blip; (2) if still failing, rediscover (which verifies the bridge is actually reachable) and retry at its current address — same IP or new. A confirmed-reachable bridge is always worth one retry.

Test

tests/test_philips_hue.py: transient ConnectionError at an unchanged IP must not error (RED before, GREEN after). 19 hue/discovery tests pass; ruff clean; manifest regenerated.

🤖 Generated with Claude Code

Self-heal (#183) only retried when rediscovery returned a *different* IP, so a momentary ConnectionError while the bridge stayed at the same address still surfaced as 'Could not reach' (observed live). Now: a quick retry absorbs brief blips, and the rediscovery retry fires whenever the bridge is verified reachable — same IP or new. Adds a regression test (transient at unchanged IP must not error).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@AVADSA25 AVADSA25 merged commit 4e7ab76 into main Jun 8, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants