Repository navigation
Scripts and scenes open in LIBI, as automations do. LOAD lists your automations, scripts and scenes, each kind under its own heading. A script opens as a NET of the Script kind, a scene as a NET of the Scene kind, and both are saved back through Home Assistant's own config API.
Dimming and colours with MOVE. A MOVE sets a light's brightness, colour temperature, colour or effect, a fan's speed, a cover's position, a thermostat's temperature or a player's volume - a fixed value, or a variable read when the automation runs.
Math: MOD, RAND and MUX - and EVERY. The remainder, a random whole number, and input number K of a list: four colours from the dashboard, one after another or at random. EVERY starts a rung every N seconds, minutes or hours. The AI chat builds colours in turn or at random with these blocks.
Every input is a value or a variable, chosen from your helpers by kind, and so is OUT. ADD, SUB, MUL and DIV take up to eight inputs. A tap on a rung opens the + menu by category.
What you draw is what runs. This release fixes many cases where an earlier LIBI saved something other than what the ladder showed. Three of them never ran at all: a P contact on a dashboard value, a MOVE to a light, and a MOVE that read a variable. See After you update.
After you update
- Restart Home Assistant after the download. HACS shows Restart required.
- Reload LIBI's page in every browser and in the Home Assistant app.
- If LIBI says it could not draw this page, reload without the cache: Ctrl+Shift+R, or Cmd+Shift+R on a Mac.
- In the Home Assistant app, reset the frontend cache in the app's settings.
- Check what an earlier LIBI saved wrongly. LIBI never rewrites an automation you did not change, so these stay as they are until you fix them:
- A rung started by a P contact on a dashboard helper (an
input_select, aninput_number, a text) never ran. It was saved to wait foron, which such a helper never is. On a number, a text or a list of colours, that contact now opens with a note that it never holds. To fix it, delete the contact, draw a P contact again, and press SAVE & COMPILE. - A MOVE to a light, a fan, a cover, a valve, a thermostat, a humidifier or a media player was saved as an action named after the device (
action: light.kitchen). Home Assistant keeps it but never runs it. To fix it, draw the MOVE again and save. - A MOVE that read a variable on IN was saved with the variable's id as text (
value: input_number.a), so the helper got those words, or an error. It now opens showing those words as its value. To fix it, choose the variable again with Variable, and save.
- A rung started by a P contact on a dashboard helper (an
Nothing else is required:
- Your projects, NETs and version history open as before.
- A check with two bounds now opens as one CMP RANGE block. Nothing changes in the automation until you change that block.
- The minimum Home Assistant version is still 2025.1.0.
Scripts and scenes
- LOAD (Load from Home Assistant) lists the automations, scripts and scenes that are in no project yet, each kind under its own heading. When the list is long, you can filter it by name.
- A script opens as a NET of the Script kind: its sequence is drawn as an automation's actions are, with no trigger.
- A scene opens as a NET of the Scene kind, with one rung for each entity: a coil for on and off, and a MOVE for any other state or attribute. Each keeps its value as the file has it.
- Saved as automations are:
- through Home Assistant's own config API, with V1 and V2;
- one project per entry;
- updated under the entry's own key;
- never deleted by a save.
- In a scene:
- A light's brightness in % is written as its brightness 0-255, and a light given a value is on. A scene the AI chat built with brightness 50 % used to be refused by Home Assistant.
- A block of the Math category is refused, because a scene sets fixed states.
MOVE: dimming, colours and other values
- Set: a light's brightness (a slider), colour temperature, colour (a palette with ready colours) or effect; a fan's speed; a cover's or a valve's position; a thermostat's temperature; a media player's volume.
- IN: a fixed value, or a variable read when the automation runs, such as:
- an
input_number(a slider on your dashboard); - another light's brightness or colour;
- a text helper holding
#rrggbb; - an
input_selectof colour names.
- an
- What the light can do: the Inspector says when a light only turns on and off (the brightness is left out) or has no colour (the colour is left out).
- A MOVE to a switch is red, says why, and is not saved. A switch is turned on and off by a coil.
- Read from Home Assistant:
- An automation that sets one value of a light opens as such a MOVE.
- A value that only looks like an entity, such as a speaker's id given to a text helper as words, stays those words. It becomes a variable only when you choose one with Variable.
Math: MOD, RAND, MUX - and EVERY
- MOD is the remainder of IN1 divided by IN2. A step that counts up through MOD 4 goes 0, 1, 2, 3 and starts again.
- RAND puts a random whole number from IN1 to IN2 into OUT, which is an
input_numberor acounter. With Never the number OUT holds now ticked, it never gives the same number twice in a row. - MUX chooses input number K of its list (K counts from 0) and sets it on OUT: a helper, or a device as a MOVE sets it.
- ADD, SUB, MUL and DIV take up to eight inputs: + Add an input gives IN3 to IN8.
- EVERY (a time pattern) is a block of its own: how often, as a number and a unit. It starts the rung on the clock. A time pattern from Home Assistant used to be shown as Fixed time, and a change to it was not saved. Now it opens as EVERY, and a change is saved.
- Without LIBI: each block is a standard Home Assistant template, so the automation runs without LIBI and opens again as the same block.
- Red and not saved, with the reason in the Inspector:
- RAND whose IN1 is larger than IN2, or is a fraction;
- RAND of one number with Never the number OUT holds now ticked, which leaves nothing to choose;
- MOD by 0;
- MUX whose K is out of range, or is a fraction;
- an OUT that cannot take a number, such as a sensor or a light.
- Fixed: a constant with a point (
0.5) in a MATH block was read as an entity,states('0.5'), which is 0.
Every input: a value or a variable
- Each IN of a block (IN1, IN2, MIN, MAX, K ...) takes either a value you type, such as
20, or a Variable. - Variable opens a list of your helpers, by kind. It also offers the sensors and device settings, by target and by type. It lists only what holds a value, never an on/off.
- A chosen variable shows its name, its id and what it holds now. × turns it back into a typed value.
- OUT is chosen the same way, from what can take the result:
- for MATH, MOD and RAND: a number helper, a counter or a text (never a sensor, which cannot be set);
- for MUX and MOVE: a helper, or a device that takes a value;
- in a scene: any entity.
The + menu
- A tap on a point of a rung shows the categories: Contacts, Compare, Coils, MOVE, Timers, Counter, Math and Structure. Each shows how many blocks it has.
- A tap on a category shows each of its blocks with its symbol and its name, for example the four contacts
| |,|/|,|P|and|N|, or ADD, SUB, MUL, DIV, MOD, RAND and MUX. - Back, or Escape, returns to the categories.
The P contact on a dashboard value
- A P contact on an
input_select, aninput_number, a text, a sensor or a button starts the rung the moment the value changes. It does not fire when the device drops off or comes back. Before, it waited foron, which such a value never is, so the rung never ran. - On a list that may be on, with
on,offandautoamong its options, it starts on any change, including a change to off. To start the rung only when it turns on, use CMP =on. The Inspector says so. - A NO or NC contact on a value that is never on or off is red, says to use a P contact or a CMP, and is not saved.
Compare: above, below, between
- A check with two bounds (Home Assistant's own between, such as above 20 and below 30) opens as one CMP RANGE block. Before, it opened as CMP > of the lower bound. The upper bound was out of sight, and it was dropped from the automation when the block was edited.
- An edited ≥, ≤ or RANGE is saved. Before, one read from Home Assistant went back unchanged, while the save reported success. This now also works inside an OR, and a time window stays a time window.
- Only the bound you change changes. The alias, the attribute, and a device condition's device, domain and type all stay.
- A state check changed to CMP > is saved as a numeric check. Before, Home Assistant refused it.
- A TON after a check holds the check for a time. Home Assistant can do that only for a state: a contact or CMP =. After a > or <, a range, a template, a zone or the time, LIBI does not save it and says why. One that is already in your automation stays as it is until you change it.
Nothing the ladder cannot draw is lost
- A
notof several checks, or of one check the ladder cannot turn round, was drawn without itsnot, so the logic read the other way round. Now each check is drawn as its opposite, or the wholenotbecomes one block marked kept as it is. - A condition of a kind LIBI has no block for, such as a newer Home Assistant condition or an
and/orthat is turned off, was drawn as an action and saved as one, so the condition was lost. Now it is one block marked kept as it is. The Inspector shows it as Home Assistant has it, and it is written back unchanged. - A template condition written as a plain string was dropped. It is now kept.
More fixes
- Triggers:
- Two triggers with the same id were drawn as one. Now both are kept.
- Three or more rungs joined at one column were saved as a condition built from their triggers, not as the triggers themselves.
- The triggers keep the order the automation had.
- A delay right before an if or a choose, or a cool-down at the end of the actions, is now a step of the rung. A script with such a delay used to be drawn in red and could not be saved.
- Traces shows EVERY (a time pattern) as a pulse of the clock. Before, it compared time pattern as if it were an entity. Traces also reads the inputs of the new blocks.
The AI chat
- Values in turn, or at random: you can ask for colours on a light every 10 seconds, chosen in lists on the card, either one after another or at random (never the colour lit now). The draft is drawn with EVERY, MUX, CTU, MOD and RAND, and the step and the index are kept in counters the card does not show.
- Colour names: a colour given by name must be an English name Home Assistant knows (
red,orange,lime,turquoise...). A light given a name it does not know turns white.- The chat corrects a name it does not know.
- It also tells you when a list on the card holds such a name, whether the light reads that list through a MUX or directly.
- Names that differ only in brightness (
greenandlime,purpleandmagenta) show as one colour on most lights.
Known limitations
- A CMP ≥ or ≤ with a TON after it cannot be held for a time in Home Assistant either. It is not drawn in red. SAVE & COMPILE refuses it with Home Assistant's own message (not a valid option), and nothing is written.
- From 2026.11.11:
- The
notaround a check that has its ownforis fixed. It is now one block kept as it is. - The other limitations listed in 2026.11.11 were not re-checked for this release.
- The
Under the hood
- Websocket:
libi/list_automationslists scripts and scenes too, except LIBI Global's recipients and scenes without an id.libi/get_automationopens an entry by its kind (domain).
- The compiler:
- The Math blocks are written by one function and read back by one (
calc_template,calc_block). - A P contact on a value is a state trigger with
not_fromandnot_toset to[unavailable, unknown]. EVERY istime_pattern. - An edited CMP >, <, ≥, ≤ or RANGE is written from the check it was drawn from (
_bound_condition). A node you did not change is written as it was.
- The Math blocks are written by one function and read back by one (
- Panel build: 3.96.2.
- The review: before this release, a read-only review of all the changes found 10 issues:
- The 6 that changed what is saved or shown were fixed, each with a test that fails without the fix.
- 2 were code tidy-ups.
- While those fixes were checked, the CMP defects above (two bounds, an edited ≥ / ≤ / RANGE) were found and fixed too.
- 2 internal issues are left for a later release. The rule that decides whether a NET is its Home Assistant entry is written in three places in
websocket.py(the three agree today). Andlibi/get_automationreads all three YAML files for every load.
- Tests:
- 577 pytest tests against a real Home Assistant.
- 62 browser test pages (2156 checks), many of them at desktop, tablet and phone widths.
- On a real installation, all 45 automations, 2 scripts and 3 scenes go from YAML to LIBI and back unchanged, and every NET of its projects compiles to exactly what Home Assistant has.
Full Changelog: v2026.11.11...v2026.11.18