2.8.2b1

What's Changed

Integration

• Relax the aiohomematic version gate in async_setup_entry from an exact-match check to a minimum-version check. Setup is now only blocked when the installed aiohomematic is older than the version this release was built against; a newer (patch) aiohomematic no longer aborts setup. This fixes spurious "requires aiohomematic version X, but found version Y / setup blocked" failures (#3275) that occurred when HA/pip resolved a newer aiohomematic than the manifest pin via transitive, upper-bound-less dependencies

Dependencies

Bump aiohomematic to 2026.7.2

• Fix CUxD/CCU-Jack devices going unavailable after init (#3228): the per-parameter getValue fallback is now disabled for these JSON-RPC interfaces (added to INTERFACES_SKIPPING_INIT_GETVALUE_FALLBACK), which previously flooded the CCU session pool during initialization and marked the devices unavailable. Values now arrive via the bulk get_all_device_data fetch and MQTT events instead, and a contract test guards the behaviour
• Fix a JSON-RPC session login race on cold start: concurrent login attempts previously created multiple CCU sessions simultaneously, risking "too many sessions" errors. _login_or_renew now serializes login/renew with an asyncio.Lock (with a lock-free fast path for recently refreshed sessions), so only one session is created at startup