Skip to content

Releases: albertovincenzi/ha_samsung_dms

v0.7.4 — Reauth, diagnostics download & VRF tuning

Choose a tag to compare

@albertovincenzi albertovincenzi released this 23 Jul 07:31
777bb27

What's new since v0.6.0

Features

  • Reauth flow, options & diagnostics download: reconfigure credentials without re-adding, per-entry options, and downloadable diagnostics with device grouping.
  • VRF-tuned diagnostics: outdoor power/energy sensors and guest use-limits.

Testing & CI

  • Full pytest suite covering config/reauth flows, coordinator, and diagnostics, wired into CI.
  • Hardened GitHub Actions workflows; bumped actions/checkout, actions/setup-python, and github/codeql-action.

Docs

  • Added security policy with private vulnerability reporting.

Full changelog: v0.6.0...v0.7.4

v0.6.0 — Outdoor VRF health diagnostics & warnings

Choose a tag to compare

@albertovincenzi albertovincenzi released this 22 Jul 11:12

Read the outdoor machine like a service engineer

The integration now polls each outdoor unit's cycle-monitoring data and turns the raw refrigerant readings into an actionable health status.

New "Outdoor unit" device per condensing unit:

  • Telemetry sensors: outside / discharge / inverter (IPM) temperature, high & low pressure (bar), compressor current, frequency and run-hours.
  • Derived engineer's metrics: condensing & evaporating temperature, condenser approach (a dirty-coil / cleaning indicator) and suction superheat.
  • Health status sensor — OK / Warning / Alert — that flags a dirty condenser coil, high discharge temperature, inverter overheating, likely low charge, or a communication fault, with a plain-language issues list you can show on a dashboard.
  • Compressor-running, communication-error and maintenance-required binary sensors.

Per-unit warnings you can automate on

Every indoor/EHS/ERV unit now has Fault and Filter binary sensors (problem device class). Point a Home Assistant automation at them to get a notification when a unit errors or when its filter-cleaning alarm trips.

All thresholds are conservative and advisory — this highlights "worth looking at", not a replacement for a technician with gauges. R410A (DVM S/Plus). Verified against live site data.

v0.5.1 — ERV tempering status sensors

Choose a tag to compare

@albertovincenzi albertovincenzi released this 22 Jul 10:12

Adds read-only Setpoint and Operating mode sensors for energy-recovery ventilators.

Note: the ERV Plus does temper incoming air, but investigation of the DMS control protocol confirmed its mode and setpoint are driven by the connected system — the DMS provides no control path for them. Exposing a thermostat would have created non-functional controls, so these are surfaced as read-only sensors instead.

v0.5.0 — Instant feedback & ERV sensors

Choose a tag to compare

@albertovincenzi albertovincenzi released this 22 Jul 10:03

Faster UI feedback

Control commands (power, mode, temperature, remote lock, fan, etc.) now update the entity immediately instead of waiting for the next 30-second poll:

  • The commanded value is shown optimistically and held until the DMS confirms it.
  • Two fast follow-up polls (~4s and ~10s) fetch the real state right after a command, so it confirms within seconds and a rejected command surfaces quickly.

Energy-recovery ventilator sensors

ERV (pluserv) units now expose proper sensor entities — CO₂, outdoor temperature, air temperature, and intake-air temperature — created only when the unit actually reports them. These get long-term history and can drive automations (e.g. boost ventilation on high CO₂).

Update via HACS to get instant feedback if you were on v0.4.x.

v0.4.2 — HACS brand icon

Choose a tag to compare

@albertovincenzi albertovincenzi released this 22 Jul 09:06

Adds a local brand icon (custom_components/samsung_dms/brand/) so all HACS validation checks pass (9/9). The integration now validates cleanly for the HACS default store.

No functional changes.

v0.4.1

Choose a tag to compare

@albertovincenzi albertovincenzi released this 22 Jul 09:00

Version bump. No functional changes since v0.4.0.

v0.4.0 — Remote lock & schedule sensor

Choose a tag to compare

@albertovincenzi albertovincenzi released this 22 Jul 08:55
  • Remote lock switch per unit: turn on to disable the physical wall remote (guests can't change settings), off to re-enable. The raw DMS state (true/false/level1) is exposed as an attribute.
  • Schedule active binary_sensor per unit: shows whether a DMS schedule is currently driving the unit (read-only; schedules are still managed on the DMS).

Both group under each unit's existing device alongside its climate/water_heater/fan entity.

v0.3.0 — Swing control & EHS space heating

Choose a tag to compare

@albertovincenzi albertovincenzi released this 22 Jul 08:42
  • Swing control on AC climate entities: off / vertical / horizontal / both. Each unit only advertises the vanes it actually has (vertical when the unit reports a UD vane, horizontal when useLRSwing is set).
  • EHS space heating: the water-out (leaving-water) side of EHS units is now a second climate entity — heat/cool, leaving-water setpoint, per-mode limits — grouped under the same device as the existing hot-water water_heater.

v0.2.0 — EHS water heater & ERV fan

Choose a tag to compare

@albertovincenzi albertovincenzi released this 22 Jul 08:31

Units are now routed to the correct Home Assistant platform based on their DMS type:

  • EHS / hydro units (e.g. "ACS") become a water_heater: on/off, supply mode (standard/power/force), tank target & current temperature, and away mode.
  • Energy-recovery ventilators (pluserv, e.g. "Recuperatore") become a fan: on/off, speed (low/mid/high/turbo), and ventilation mode as a preset (auto/erv/normal/sleep).
  • Indoor AC units remain climate entities.

Classification uses the tree-view metadata; anything unrecognised falls back to a climate entity so no unit is ever dropped.

v0.1.1 — Real unit names

Choose a tag to compare

@albertovincenzi albertovincenzi released this 22 Jul 08:24

Entities now use the room labels configured on the DMS (e.g. "Reception", "301", "Cucina 507") instead of the internal address, and expose the unit's model type and firmware version. unique_id remains address-based, so renaming a unit on the DMS won't orphan the Home Assistant entity.