Repository navigation
v0.4.2-beta.3
Pre-release[Unreleased]
Changed
-
The ChromHA View Assist dashboard is now a clone of your actual View
Assist dashboard, not a hand-built substitute. 0.4.0/0.4.1 generated
original Home/Weather/Controls views from scratch, gated behind a Push
to View Assist target per profile - a mismatch with what people actually
wanted, which was their real View Assist dashboard with ChromHA's colours.It now reads every view file under
/config/view_assist/views/plus the
dashboard's sharedbutton_card_templates, and colour-patches both with
the same substitutionsexamples/view-assist/convert.pyalready applies
to a user's own copy - just automatic, and into a separate dashboard
instead of View Assist's own. A Theme view (colour wheel + Solid/Glass
per profile) is appended. The dashboard is now rewritten on every rebuild
(previously created once and left alone) so it tracks your real View
Assist setup as it changes - the same "generated, don't hand-edit"
contract the theme file already has. New module:dashboard_converter.py.
Fixed
-
The colour picker didn't always stick.
chromha-card.jsfired an
unserialisedtext.set_valuecall on every colour change. Two picks made
in quick succession (a very ordinary way to use a colour wheel) raced:
nothing guaranteed the first call's write couldn't land after the
second's, silently reverting to an earlier colour depending on timing.
Commits are now serialised - never more than one write in flight, always
sending only the latest value - which makes that reordering impossible
rather than just unlikely. -
A stale, wrapped View Assist view file produced an invalid card. If a
file under/config/view_assist/views/was copied in the wrapped
views:/cards:shape instead of a bare button-card - as ChromHA's own
example views did before 0.4.0 - the dashboard clone wrapped it a second
time, producing a card with notype(a broken card in the UI). Detected
and unwrapped automatically now, with a warning logged pointing at which
file is still in the wrong shape on disk. -
Dynamic view titles rendered as literal garbage. A Lovelace view's own
title:is never template-evaluated - only a button-card's own config is- so a view whose title was a
[[[ ... ]]]expression (View Assist's
stocklocateandmusicviews both do this) showed that literal text in
the tab bar instead of anything useful. The generated dashboard now
rejects a templated title and falls back to a plain name derived from the
view's own filename - a ChromHA-dashboard-only substitution; the source
view file is untouched.
- so a view whose title was a
-
Weather's background was still blue after conversion. Not a simple
background-color:line - View Assist's stock Weather view sets it via
card_modCSS text (ha-card { background: #059bf9 }), which the colour
patcher's structural patterns never looked inside. That exact colour is
the Alert view's own deliberate blue, reused here seemingly by copy-paste;
now patched to the theme background everywhere except the Alert view
itself, in bothdashboard_converter.pyandexamples/view-assist/convert.py.