[Bug] Pairing failed

[Hubszo]

Description

LumaSync pairing failed during initial setup of Hue Bridge Pro.

Steps to Reproduce

1. Hue Bridge correctly discovered on the network
2. Button pushed on Hue Bridge Pro
3. Pair chosen in the LumaSync
4. Pairing failed with message 'Auth error/Credentials expired'
5. Re-pairing gives same result

Expected Behavior

Pairing successful

Actual Behavior

Pairing failed

Environment

• OS: Windows 10 Pro version 22H2 (OS Build 19045)
• App version/commit: LumaSync 1.5.3
• Device/setup (if hardware-related): Hue Bridge Pro connected with LAN, PC connected with LAN

Logs and Evidence

• Relevant terminal logs
• DevTools logs (if frontend-related)
• Screenshots/videos if available

Additional Context

Anything else that helps triage.

[voyvodka]

Thanks for the detailed report — the screenshots made this one easy to pin down.

Root cause: the Hue Bridge Pro serves its local API on HTTPS/443 only; port 80 is closed. LumaSync's pairing, IP verification, and credential validation calls were still hardcoded to http://<bridge-ip>/... (the CLIP v1 surface), so on a Bridge Pro they fail at the transport layer before the bridge ever sees them. Discovery worked because it runs against discovery.meethue.com and mDNS, neither of which touches the bridge's HTTP port — which is why you got a correctly discovered, named bridge that then refused to pair.

The "Auth error / Credentials expired" wording was a second, separate bug: a rejected link button was being rendered as an expired-credentials state, so the message pointed at a problem you did not actually have.

Both are fixed in #169: the CLIP v1 calls now try HTTPS first and only fall back to plain HTTP for older bridges, and the link-button case gets its own state.

I do not have a Bridge Pro to test against, so a real-hardware confirmation would be very welcome before this ships. If you are able to build from the fix/hue-bridge-pro-https branch, that would settle it — otherwise I will ping you here when a release with the fix is out.

[Hubszo]

Thanks for reply and update. I will test this new version and come back to you.