v0.3.1

Bugfix: setup no longer fails with a raw CancelledError when the BLE proxy/device is briefly unreachable.

The initial connection is bounded by DEVICE_TIMEOUT (30s) via asyncio.timeout(), so a slow connect raises ConfigEntryNotReady (clean retry) before Home Assistant's bootstrap stage timeout cancels setup. CancelledError is never swallowed. establish_connection now uses max_attempts=3 so failures surface promptly. Matches the core led_ble/yalexs_ble pattern.

CI green (hassfest, HACS, ruff, 44 pytest tests).

v0.3.0 — Radar Map Manager support (opt-in)

Radar Map Manager support (opt-in)

This release adds compatibility with Moe8383/radar_map_manager.

New option: Settings → Devices & Services → LD2450 BLE → Configure → Radar Map Manager support (off by default).

When enabled:

• the per-target sensor.<device>_target_<n>_x / _y coordinate sensors (mm) are enabled — an empty target slot reports unknown so RMM skips it cleanly;
• a new sensor.<device>_presence_target_count sensor (0–3) is added.

Toggling the option reloads the integration. With the option off, behaviour is unchanged (X/Y disabled by default, no count sensor).

Non-English Home Assistant: RMM matches the literal entity-id suffix _target_<n>_x / _y. HA builds that suffix from the translated entity name (e.g. German _ziel_1_x), so rename the X/Y entity-ids to the target_<n> form for RMM. See the README.

No BLE changes, no renamed/removed entities, no breaking changes. Verified end-to-end on real HLK-LD2450 hardware against a live Radar Map Manager install. 42 tests pass.

🤖 Generated with Claude Code

v0.2.0

Connectivity diagnostic sensors.

Adds per-device diagnostic entities (auto-created, no YAML, entity_category=diagnostic) to monitor whether an HLK-LD2450 stays reliably online: ble_connected, connection_state (connected/reconnecting/disconnected/stale), last_seen, last_disconnect, disconnect_count, reconnect_count, offline_duration, online_duration.

Central state tracking in the coordinator (stale watchdog 30s, one disconnect per interruption, reconnect on recovery). No breaking changes to existing entities. reliability_24h deferred (TODO).

CI green (hassfest, HACS, ruff, 35 pytest tests). Verified live on real HLK-LD2450 hardware.

v0.1.1

Documentation update + real-hardware verification.

Verified end-to-end on real HLK-LD2450 hardware (Home Assistant 2026.2.3, bleak 3.0.2): BLE discovery, GATT connection, live ~1 Hz data, and all 40 entities across the six platforms. No code changes were needed - the 0.1.0 logic worked as-is.

• Production-grade README (CI badges, entities table, dev section)
• Version bumped to 0.1.1

CI green: hassfest, HACS, ruff, 28 pytest tests.

v0.1.0

Initial release of the native HLK-LD2450 BLE integration for Home Assistant.

Verified in CI (HA 2026.2.3, bleak 3.0.2): hassfest, HACS, ruff, and 28 pytest tests pass. Also verified locally: imports clean across all platform modules and the integration loads in a live HA dev server.

Features: up to 3 targets (distance/angle/X/Y/speed/resolution sensors), presence + per-target present/moving binary sensors, multi-/single-target switch, area-mode select, 12 area-vertex number sliders, reboot button. Corrected LD2450 sign-magnitude coordinate decode.

Note: not yet verified against physical hardware. Area-filter writes (cmd 0x00C2) are best-effort pending hardware confirmation. Please report logs from custom_components.ld2450_ble if setup fails.