v2026.4.0-beta.3
Pre-release
⚠️ BREAKING CHANGE — This release requires Landroid Cloud 7.
Landroid Card 2026.4.x is NOT compatible with Landroid Cloud 6.
🚨 Breaking Changes
This release is a major adaptation to Landroid Cloud 7 beta, which introduces significant changes to entity IDs across all devices. As a result, Landroid Card 2026.4.x is incompatible with Landroid Cloud 6.
What you need to do before installing this beta
Update all your entity IDs in the card configuration (entity, settings, stats, info_card, battery_card, statistics_card, shortcuts, etc.) to match the new naming scheme introduced in Landroid Cloud 7.
If you are still running Landroid Cloud 6, please stay on Landroid Card 1.2.6.
⚠️ Beta Notice
This is a pre-release version. It has been published to allow early testing alongside the Landroid Cloud 7 beta integration. Some features may not work as expected. The final stable release will be published once Landroid Cloud 7 reaches a stable release.
Please report any issues you encounter: Open an issue
What's Changed
✨ New Features
-
Error sensor in status — When the mower reports an active error, its
translated description is now appended directly to the status line and
highlighted in red (--error-color). No manual translation maintenance
required — text comes from Landroid Cloud viahass.formatEntityState.
(#695) -
Home Assistant action support —
shortcutsandactionsnow accept
full HA action objects (perform-action,navigate,url,more-info)
in addition to the previousservice/service_dataformat.
Old format remains fully supported (backward compatible).
(#685) -
Entity order in visual editor — Entities in the card panels (Battery,
Info, Statistics, Settings) can now be reordered via drag-and-drop in the
visual editor.
(#684)
🔧 Improvements & Fixes
-
Settings Card auto-discovery — When
settings_cardis not explicitly
configured, the card now automatically collects all entities with
entity_category: configbelonging to the mower device.
(#678) -
Status string reliability — Entity names (
party_mode,zone,
next_schedule) in the status line now come fromfriendly_namestripped
of the device prefix, instead of static local translations.
(#694) -
Invalid next schedule date guard — Status no longer appends a
next-schedule time when the sensor returns an invalid or past date.
(#686) -
Wi-Fi signal strength fix — Corrected function name for
wifiStrengthToQualityhelper.
(#673) -
Localize fix —
replace()is now only called when bothsearchand
replacearguments are defined.
(#674)
⚡ Performance
-
Device entities cache — All entity lookups now use a memoized
_deviceEntitiesgetter instead of iteratingObject.values(hass.entities)
on every call.
(#687) -
Card entities cache —
cardEntitiesgetter result is cached per
hass+configreference, avoiding repeated computation on each render.
(#690) -
Settings entities cache —
settingsCardEntitiesgetter is similarly
memoized.
(#691) -
Patched state object cache —
getPatchedStateObjnow reuses the
previous result when the underlying state object has not changed.
(#693)
🛠 Refactoring & Code Quality
-
Replaced entity suffix–based lookups with
translation_keyconstants
(TK_*) — entity resolution is now language- and rename-agnostic.
(#679) -
Replaced the
Map<cardType, boolean>visibility state with a single
_activeCard: string | null— simpler toggle logic, only one panel open
at a time.
(#689) -
Renamed option
settings→settings_card(auto-migration included,
old key still works).
(#677) -
Removed dead code: unused
associatedEntitiesgetter and stale language
imports inlocalize.
(#688,
#675) -
Simplified
getEntityName,shouldUpdate, editor default entity handling,
andfriendly_nameextraction throughout.
⚠️ Breaking / Migration Notes
settings→settings_card: auto-migrated at runtime, but please
update your YAML manually. Support for the old key will be removed in a
future release.actionsas array: if you previously passedactionsas an array,
this was never the intended format — a console warning is now shown.
Useshortcutsfor additional buttons instead.
Full Changelog: 2026.04.0-beta.2...v2026.4.0-beta.3