1.2.0 – Site ID optional again

1.1.0 made the Site ID mandatory, which locked out exactly the accounts this integration was written for: those invited to a single unit, with no CAME Connect site of their own. This release makes it optional again.

Setup without a Site ID (single-unit accounts)

• Site ID and SIP password are now optional fields.
• Leave the Site ID empty and discovery falls back to the original /sipaccounts → /sites → /devices chain — the 1.0.0 behaviour — giving the hard-coded Open Door button.
• No AUX buttons on this path: the AUX list only exists in the /plants payload.
• If that chain works except for a missing SIP password (newer CAME accounts no longer receive one), type the SIP password and still leave the Site ID empty — the legacy chain uses the one you typed. A password the API does return still wins.
• The unique ID is email:site_id only when a site is given, so entries created by 1.0.0 keep their identity.

Setup with a Site ID (CAME Connect accounts)

• Unchanged /plants discovery, with the open-door button plus one button per AUX output.
• The SIP password is required here, since that payload never carries it — the config flow now says so instead of failing during discovery.

Also

• Re-discovery in the options flow reuses whichever path set the entry up.
• tests/test_discovery.py covers both payload shapes; runs standalone (python3 tests/test_discovery.py) or under pytest.

Full changelog: 1.1.0...1.2.0

1.1.0 – AUX outputs, /plants discovery, runtime diagnostics

Install or update via HACS.

AUX output support

• One button per AUX output configured on the entry panel (Aux 1–N), each sending a BPT AUX_COMMAND over SIP — the same mechanism as the official app.
• Buttons are named after the AUX alias set in the CAME Access app, with icons mapped from the app icon (slidinggate.png → mdi:gate, light.png → mdi:lightbulb, …).
• Buttons still carrying a generic Aux N label are disabled by default.
• Each AUX button exposes aux_code, last_pressed, last_message_status and last_error attributes.

Discovery via the /plants endpoint (CAME API changes)

• The cloud API no longer returns the SIP password or a usable FCM device token to third-party callers, so the legacy /sipaccounts → /sites/{id}/devices chain can no longer complete setup.
• Discovery now uses the Bearer-only /api/evo/v1/sites/{id}/plants endpoint; the config flow asks for Site ID and SIP password manually.
• xipregister wake-up is now best-effort — skipped with a clear status when no device token is available, since SIP delivery works regardless.
• Unique ID is now email:site_id, so multiple sites per account can be added.

Upgrading from 1.0.0: existing entries must be removed and re-added, because setup now needs the Site ID and SIP password.

Runtime diagnostics

• New diagnostic sensors: last command, result, error, xipregister status, SIP register/message status, busy retries, command duration, resolved SIP proxy, proxy-stale flag, token validity and token expiry countdown.
• Downloadable diagnostics snapshot (secrets redacted) with token state, last action details and stored-vs-live SIP proxy comparison.
• The SIP proxy IP is re-resolved before every command, fixing failures after CAME rotates the address.

Packaging

• CAME brand images (icon + logo, light/dark).
• strings.json added and manifest.json key order fixed so the integration passes hassfest.
• Minimum Home Assistant and HACS versions declared in hacs.json.
• New Validate workflow running hassfest and the HACS action on every push and pull request.

Thanks to @zuchmanski for #1, which is the bulk of this release.

Full changelog: 1.0.0...1.1.0

1.0.0

Full Changelog: https://github.com/LucaCraft89/came_access/commits/1.0.0

Initial release

Not much to say apart from read the README.md