oyvindwe/connectlife-ha v0.37.0 on GitHub

Highlights

New button platform for write-only commands like start/stop/pause, with per-button availability gating on status properties.
Fixes a regression from 0.36 where properties with unavailable: <value> could disappear at integration startup; entities now exist and toggle between available and unavailable as the underlying value changes (e.g. program-gated controls appear automatically once a program is selected — no integration reload needed).
Cloud rejections from any write path now surface as clean Home Assistant notifications instead of raw tracebacks in the log.

Restore entities that v0.36.0 inadvertently hid: properties with unavailable: <value> are no longer skipped at startup. They are always created and report available = False when the current value matches the sentinel, then flip to available automatically on the next poll once the value changes. #530
Wrap cloud-side rejections from select.async_select_option, switch.async_turn_on/async_turn_off in ServiceValidationError so users see a clean notification instead of a LifeConnectError traceback through entity_service_call. #531
Extend the same error wrapping to every entity-level write path (including the new button platform) by centralizing it in ConnectLifeEntity.async_update_device, and to the bypass services (connectlife.set_action, connectlife.update) which call the coordinator directly. #532

Add a button platform for write-only commands. Data dictionaries can declare top-level buttons: entries that map a key to a write payload; buttons can be gated via available_when against a read-only status property (e.g. enable start/stop only when remote control is allowed), and feature overrides can disable inherited buttons on variants that don't support them. #527

Full Changelog: v0.36.0...v0.37.0