flixlix/power-flow-card-plus v0.4.0-beta.1

on GitHub

Minor Changes

• #431 a3b6a42 Thanks @flixlix! - Default dot speed is back to how it was before 0.4.0-beta.0: the time per dot shrinks linearly with power (with the defaults, 1000 W takes 3.4 s per dot again). The faster speed-based curve from 0.4.0-beta.0, where twice the power looks about twice as fast, is available with flow_rate_model: speed, and flow_rate_model: relative selects the relative formula. The option replaces the "New Flow Model?" toggle in the editor with a select. use_new_flow_rate_model still works as the older alias (false is relative); flow_rate_model wins when both are set. Energy Flow Card Plus always uses the relative formula and ignores flow_rate_model.
• #423 9954453 Thanks @flixlix! - New accept_negative option on individual devices. With it, a negative reading means the device feeds power to the home (e.g. an EV discharging with V2G): the value keeps its minus sign and the dots and direction arrow flip. Without it, nothing changes: the sign is dropped as before.

Patch Changes

• #432 9ac9962 Thanks @flixlix! - The version line each card writes to the browser console has a new look.
• #424 aa5071c Thanks @flixlix! - The UI editor no longer shows "Display Zero" switched on for individual devices and the non-fossil node when the option is not set. The card hides those nodes at zero unless display_zero: true is set, and the editor now shows the toggle off to match. The non-fossil documentation now gives the default as false.
• #419 90f01f4 Thanks @flixlix! - Docs now state the real flow-rate defaults (no behaviour change): Power Flow Card Plus uses the new flow formula unless use_new_flow_rate_model: false, Energy Flow Card Plus always uses the relative formula (so use_new_flow_rate_model, min_expected_power and max_expected_power don't apply to it), and an unset calculate_flow_rate uses the calculated rate.
• #423 ed57230 Thanks @flixlix! - The direction arrow of an individual device in the right-bottom slot now points the way its dots move. It used to point up while the dots moved from the home down to the device.
• #427 8a0df59 Thanks @flixlix! - Fix: an individual device's secondary info now shows text states such as "heating", as grid and home already did. Unavailable or unknown states stay hidden.
• #426 7dba4d6 Thanks @flixlix! - Cards load again on Google Cast displays (Chromecast, Nest Hub) and other older browsers and wall-panel webviews that Home Assistant itself still supports (Chromium 67 and newer). Before, the cards shipped optional chaining (?.) and nullish coalescing (??), which those browsers cannot read, so the card stayed empty or showed "Configuration Error". The cards are about 5% larger as a result.
• #430 24ecd05 Thanks @flixlix! - Individual device dots and the grid → battery dot no longer run backwards on older Chromium-based browsers, such as Amazon Fire tablets. The cards also no longer stay blank on browsers older than Chrome 92. Nothing changes on current browsers.
• #428 8ad6715 Thanks @flixlix! - On right-to-left Home Assistant languages (Arabic, Hebrew, Persian, …) the flow lines connect the circles again. Before, the circles swapped sides while the lines did not, so grid and home ended up at the wrong ends of their lines. The card layout now stays the same as in left-to-right languages; text inside the circles still reads right to left.
• #425 7f71466 Thanks @flixlix! - Fix: only W and Wh units with an SI prefix are scaled. A water meter in m³ now shows 348.9 m³ instead of 348,900,000 m³, and a sensor in mW is read as milliwatts instead of megawatts. A unit_of_measurement of kW, MW, kWh or MWh on a node or individual device now shows the reading in that unit (1.5 kW instead of 1,500 kW); any other unit still shows the value as read from the entity.