v1.5.5 — discovery dispatch hotfix (1.5.4 was a no-op)

PC Nest Speaker 1.5.5

Hotfix for 1.5.4 — the discovery speedup didn't actually take effect.

What was wrong in 1.5.4

1.5.4 changed discover_speakers(timeout=) from 5s default to 3s default, but the CLI entry point at the bottom of cast-helper.py had its own hardcoded fallback:

timeout = int(sys.argv[2]) if len(sys.argv) > 2 else 5

electron-main.js calls runPython(['discover']) with no timeout argument, so the CLI dispatcher always fell through to 5, never reaching the function default. Net effect: the documented 5s→3s change in 1.5.4 was a no-op. Logs in 1.5.4 still printed Scanning network (timeout: 5s).

What 1.5.5 does

• CLI dispatcher default 5 → 3 (matches function default).
• That's it. No other changes.

Confirming the fix

The discovery log line should now read Scanning network (timeout: 3s) and "Slow discovery" warnings should drop from ~7.6s into the ~5s range.

Everything else from 1.5.4 (receiver seek-probe + fastSeek(), group_cc.wait 5→3s) is unchanged and was already correct in the live receiver — the v1.5.4 release just didn't pull the cold-start savings the desktop side promised.

Files changed

• src/main/cast-helper.py — CLI dispatch default
• package.json — version bump