Skip to content

Releases: enoch85/ovms-home-assistant

OVMS Home Assistant v1.6.4

17 May 10:14
ba05ced

Choose a tag to compare

Bug Fixes

Valet switch silently failing without a stored PIN (#219)

OVMS shell rejected valet with no argument while MQTT reported success — switch toggled but vehicle did nothing. Now appends stored PIN (over verified TLS) or a nopin placeholder; failures are logged as WARNING. Fixes Fiat 500e climate trigger out of the box.

Phantom entities from other MQTT clients (#222)

Topics under <prefix>/<user>/<vehicle>/client/... from other clients (OVMS Connect, second HA, shared users) leaked through and created bogus entities. New ingress filter drops the full /client/ subtree before it pollutes the topic cache.

Action required if affected: existing phantom entities go unavailable after upgrade. Clean up via Settings → Devices & Services → OVMS → Configure → set Entity Staleness Management to e.g. 24 hours and enable Delete Stale History. Or delete them manually.

Cabin temperature setpoint misclassified as switch (#221)

Substring match on "set" inside "cabinsetpoint" overrode the explicit temperature device_class. Parser now matches parts exactly. Also fixes xsq.use.at.reset on Smart ForTwo.

The old switch.*_cabin_temperature_setpoint becomes orphaned — delete manually in Settings → Devices & Services.

Invalid device_class / state_class combos for energy sensors (#213)

Aligned energy metrics with HA rules: stored battery energy → ENERGY_STORAGE + MEASUREMENT; per-trip accumulators → ENERGY + TOTAL; generic fallback → TOTAL (was TOTAL_INCREASING).

Improvements

  • Smaller (16 px) flash overlay on VW e-UP / Renault Twizy custom cards
  • Stable-release notes now use GitHub's PR-centric auto-generation; git log only for betas

Full Changelog

v1.6.3...v1.6.4

OVMS Home Assistant v1.6.3

20 Mar 16:09
3f43f58

Choose a tag to compare

Please note the breaking changes in 1.6.2!

Read release notes here: https://github.com/enoch85/ovms-home-assistant/releases/tag/v1.6.2

Bug Fixes

Device tracker: fix force_update override

_attr_force_update = False was silently ignored because Home Assistant's TrackerEntity overrides force_update as a property returning not self.should_poll (= True for push-based entities). Replaced with an explicit property override returning False. This prevents redundant recorder writes when coordinates haven't changed, reducing database load and producing smoother map tracks.

Device name: remove redundant "OVMS -" prefix

The HA UI already shows the integration name in the breadcrumb ("OVMS > ..."), so the device name no longer includes the "OVMS -" prefix. For example, OVMS - mycar becomes just mycar. The name updates automatically on next reload — no entity ID changes, no migration required.

Improvements

Custom card templates: dynamic battery icon

The VW e-UP and Renault Twizy card templates now show a dynamic state-icon that reflects the real battery level, with a black lightning bolt overlay when actively charging.

Full Changelog

v1.6.2...v1.6.3

OVMS Home Assistant v1.6.2

19 Mar 22:17
cbc9dd4

Choose a tag to compare

Breaking Changes

Entity IDs have been renamed

All entity IDs now follow the {domain}.ovms_{vehicle_id}_{friendly_name} convention for clarity and multi-vehicle support (#209). Existing entities are automatically migrated on upgrade.

Examples:

Before (v1.6.1) After (v1.6.2)
sensor.ovms_mycar_metric_v_b_soc sensor.ovms_mycar_battery_level
sensor.ovms_mycar_metric_v_b_range_est sensor.ovms_mycar_estimated_range
sensor.ovms_mycar_metric_v_p_odometer sensor.ovms_mycar_odometer
binary_sensor.ovms_mycar_metric_v_c_charging binary_sensor.ovms_mycar_charging_status
device_tracker.ovms_mycar_location device_tracker.ovms_mycar_location (unchanged)

Vehicle-specific metrics now use a suffix instead of a prefix:

Before (v1.6.1) After (v1.6.2)
sensor.ovms_mycar_metric_xvu_b_soc_abs sensor.ovms_mycar_absolute_soc_vw_eup
sensor.ovms_mycar_metric_xvu_v_t_emgcy sensor.ovms_mycar_tire_emergency_values_vw_eup
sensor.ovms_mycar_metric_xrt_b_energy_avail sensor.ovms_mycar_available_energy_renault_twizy

What you need to do

  • Dashboards, automations, and scripts that reference old entity IDs must be updated to use the new names.
  • Entities whose display name was manually customized in the HA UI will keep their current entity_id and are not affected.
  • The custom dashboard cards (VW e-UP, Renault Twizy) in custom-cards/ have been updated with the new entity IDs.

Known limitation

Home Assistant does not track whether an entity_id was manually changed by the user. The migration uses name is None (no custom display name) as a proxy. A user who customized only their entity_id without also setting a custom name will have that entity_id overwritten.

What's New

Device-scoped entity naming (has_entity_name) (#209, #196)

All OVMS entities now use Home Assistant's has_entity_name model. Entity display names are scoped under the device (e.g., "Battery Level" under the "OVMS MYCAR" device) instead of carrying redundant prefixes. This gives cleaner, human-readable names throughout the HA UI.

Vehicle make/model moved to end of entity names (#196)

Vehicle-specific metrics (VW eUP!, Renault Twizy, etc.) now show the vehicle label as a suffix in parentheses rather than a prefix. For example: Tire Emergency Values (VW eUP!) instead of VW eUP! Tire Emergency Values.

Bug Fixes

  • Fix rear tire position abbreviation: Corrected inconsistent LRRL (rear-left) in tire pressure attribute names and cleanup lists
  • Fix device_tracker missing has_entity_name: The device tracker entity now correctly participates in device-scoped naming
  • Updated custom dashboard cards: VW e-UP and Renault Twizy cards updated to use the new entity ID format

Full Changelog

v1.6.1...v1.6.2

OVMS Home Assistant v1.6.1

19 Mar 19:02
4fc39b9

Choose a tag to compare

What's Changed

  • Fix blocky vehicle location history on map cards by @enoch85 in #211

Full Changelog: v1.6.0...v1.6.1

OVMS Home Assistant v1.6.0

18 Mar 19:18
6217b6a

Choose a tag to compare

What's Changed

  • Use native lock domain for vehicle locking by @enoch85 in #198
  • Add secure PIN support for lock/unlock commands by @enoch85 in #208
  • Add pin support for lock/unlock commands by @deosrc in #200
  • Combined bug fixes: entity isolation, location history, issue #202 by @enoch85 in #207

PR #207 Highlights

  • Multi-entry OVMS setups are now isolated correctly: unique IDs, dispatcher signals, and device identities are scoped per config entry to prevent cross-entry collisions and ghost devices.
  • Device tracker updates were reworked to improve GPS history smoothness and align better with Home Assistant's native tracker model.
  • Entity cleanup now leans more on Home Assistant native behavior: redundant custom attributes were removed, staleness handling uses HA timestamps, and lock PIN handling/logging/options were tightened.

Breaking Changes in v1.6.0

If you are upgrading from an earlier version, please note:

  • last_updated attribute removed: All OVMS entities previously carried a custom last_updated attribute. This has been removed because Home Assistant already tracks state.last_updated natively. If you have automations or templates using state_attr('sensor.ovms_xxx', 'last_updated'), replace them with states.sensor.ovms_xxx.last_updated.
  • full_topic and unit attributes removed: These duplicated information already available in HA's native entity properties.
  • Entity unique IDs namespaced: Unique IDs are now scoped per config entry to support multiple OVMS entries. Existing entities are migrated automatically.
  • Device model string changed: The device model now reads "OVMS Module" (previously "OVMS v3" for some entities). This is cosmetic only.
  • PIN stored in config entry: The lock PIN is stored in Home Assistant's config entry storage (.storage/core.config_entries). Home Assistant does not encrypt config entries at rest. The PIN is masked in the UI and redacted in logs, but be aware it is stored in plaintext on disk, as is standard for all HA integration credentials.

New Contributors

Full Changelog: v1.5.1...v1.6.0

OVMS Home Assistant v1.5.1

15 Dec 20:38
cd447c6

Choose a tag to compare

What's Changed

Full Changelog: v1.5.0...v1.5.1

OVMS Home Assistant v1.5.0

06 Dec 14:21
d34d447

Choose a tag to compare

What's Changed

  • GitHub Actions: Bump github/codeql-action from 3 to 4 by @dependabot[bot] in #187
  • GitHub Actions: Bump actions/checkout from 5 to 6 by @dependabot[bot] in #188
  • feat: Add charging/climate switches with configuration-driven approach by @Alenux55 and @enoch85 in #190
  • fix: Nissan Leaf Hx description, icon, units by @ditdafivo in #192

New Contributors

Full Changelog: v1.4.6...v1.5.0

OVMS Home Assistant v1.4.6

28 Sep 11:43
68e58a4

Choose a tag to compare

What's Changed

Full Changelog: v1.4.5...v1.4.6

OVMS Home Assistant v1.4.5

27 Sep 20:52
43a8be5

Choose a tag to compare

What's Changed

  • Fix: Implement stable MQTT client ID generation by @enoch85 in #185

Full Changelog: v1.4.4...v1.4.5

OVMS Home Assistant v1.4.4

25 Sep 21:14
8be9414

Choose a tag to compare

What's Changed

  • use slashes instead of dots for blacklist by @enoch85 in #182
  • Refine CONF_TOPIC_BLACKLIST configuration options by @enoch85 in #183

Full Changelog: v1.4.3...v1.4.4