Repository navigation
Releases
2026.11.18
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 wri...
v2026.11.11
The AI chat asks how you want to set the days, and both answers keep working without LIBI. When a request sets days and a time on the dashboard, LIBI asks:
- A switch for each day, and a start time: one switch per day, shown as one row of buttons on the card, and the time it starts.
- A schedule: the days, and the hours of each day: one schedule. A block starts the logic, and the end of the block ends it.
Both are Home Assistant's own helpers and card rows, so the automation and its card work even if LIBI is removed.
Set a schedule's days and hours in the Inspector. Click a CMP DATETIME block that compares the time with a schedule. Tick the days, set the start and end times, and press Save to the schedule. LIBI asks first, then saves straight into the schedule. LIBI keeps no copy.
An automation belongs to one project. LOAD lists only the automations that no project holds. The others appear under IN USE, each with the project that holds it.
What you see is what is saved. This release fixes several cases where a change in the Inspector was saved as something else. The most serious: a person compared with a zone was saved as a check that never holds, so the automation never ran. LIBI now also refuses to save a check that could never hold.
Before 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 where a person is compared with a zone.
- If you ever changed that zone in the Inspector, the automation may hold
state: zone.<name>. A person's state never equals that text, so the automation never runs. - To find one, search your
automations.yamlforstate: zone.. - To fix one, delete that CMP block in LIBI, draw it again from the palette, and press SAVE & COMPILE.
- LIBI never rewrites an automation you did not change, so it does not fix these by itself.
- If you ever changed that zone in the Inspector, the automation may hold
Nothing else is required:
- Your projects, NETs and version history open as before.
- An automation that two projects already hold stays in both.
- The minimum Home Assistant version is still 2025.1.0.
The days: a switch for each day, or a schedule
- When LIBI asks: the AI chat asks whenever a request sets days and a time on the dashboard. Each answer brings its own variables:
- A switch for each day: seven switches and a start time. The card shows the days as one row of Home Assistant's own buttons; tap a day to switch it.
- A schedule: one schedule, with no separate start time and no minutes. Its blocks are the days and the hours of each day.
- A switch for each day is offered only when its seven switches fit the plan. A plan that already has many settings and devices gets the schedule.
- A schedule you name in your request is used as it is.
- Changing an existing NET (Update NET 3) keeps the way that NET already sets its days.
- The older days helper (8 bits, LIBI's own card row) is no longer proposed for new NETs. A NET that already has one keeps it.
- The end of a block ends what the start turned on. A reminder that only sends a message has nothing to end, so it has no end trigger.
A schedule's days and hours in the Inspector
- Click a CMP DATETIME block whose IN2 is a schedule. The Inspector shows:
- Now: the days and hours the schedule holds, for example Mon Tue Wed Thu Sun 13:55–14:00.
- One button per day, Monday first. The days that are ticked are coloured.
- From and To: the same hours for every day ticked. To 00:00 means midnight.
- Save to the schedule asks first. The question names the schedule and shows Now and New.
- The save:
- It goes straight into the schedule, not through SAVE & COMPILE.
- Every automation that reads the schedule follows the new days and hours.
- The block on the canvas shows them at once.
- Safety:
- Nothing is overwritten. LIBI reads the schedule again just before it writes. If it was changed or deleted in Home Assistant since LIBI showed it, nothing is saved, and LIBI says so.
- Nothing changed means nothing is written.
- Different hours on different days: LIBI warns that saving sets one set of hours on every day ticked.
- Shown, but not changed here:
- a schedule whose blocks carry extra data;
- a schedule written in YAML;
- any schedule while Traces is on.
- Without LIBI: the schedule works as it is, and its own settings in Home Assistant still change it.
One project per automation
- LOAD lists only the automations that no project holds.
- Under IN USE, the others are listed but cannot be chosen. Each shows where it is used:
- the project that holds it;
- (this project);
- or the NET on this page that shows it, if it isn't saved yet.
- A NET may load its own automation again, for example to throw away your edits.
- LIBI also refuses to load an automation that another project holds, whichever way the request reaches it.
- While a project file cannot be read, nothing is loaded. That project may hold any automation.
- To move an automation to another project: in the project that holds it, use Delete NET… ▸ Remove from LIBI only. The automation stays in Home Assistant unchanged.
The AI chat
- Your language. Everything the chat writes for you follows the language of your last message: the reply, the names of new helpers, the questions and the lines of your request.
- A request in English gets English names, even when your house is named in another language.
- The names of your entities, areas and NETs are quoted as they are, in whatever language they're in.
- Your global variables in the phone list.
- The recipients you keep in LIBI ▸ Global come first in the list, tagged Global.
- One tick sends the message to every phone the variable holds, and a spoken message works through it too.
- The AI can send to a global variable only after you tick it.
- Drafts that would be drawn in red go back to the AI before you see them:
- a rung that ends with no action;
- a check that compares a state with an entity's id.
Fixes: the Inspector shows what is saved
- A person in a zone.
- The cause: IN2 of a person's CMP offered only zones. So the zone chosen on the dashboard, a dropdown of your zones that the AI chat makes, was replaced by a fixed zone.
- The result: the save wrote
state: zone.work, which a person's state never is, so a train reminder never ran. - Now: IN2 of a condition offers Zone, or the zone chosen on the dashboard. A person in a zone is saved as a zone condition, and the zone chosen on the dashboard as Home Assistant reads a helper. A trigger offers zones only, because a trigger never reads a helper.
- ≠ was saved as =. A CMP drawn from a state or zone condition and changed to ≠ was saved without its not, so the logic ran the other way round. A not that was turned off stays off when you change it back to =.
- An edited state trigger kept its old entity and state. The drawing said cool, and the automation still waited for heat. A person leaving a zone is now a zone trigger (leave).
- A ≠ condition could not be saved after an edit. Home Assistant refused it.
- Lists were broken apart or lost:
- An edited list of states was saved as a single piece of text. Now the list is kept, and items that contain a comma stay whole.
- A list of zones, a list of entities, and a one-item list such as
state: [on]are kept as they are. - heat, dry in a new block is two states, for entities whose states never contain a comma.
- A trigger that had only
from:no longer gets an emptyto:after an edit. - A new ≠ against a zone was saved as a check that never holds.
A check that can never hold is refused
LIBI now draws these blocks in red, and SAVE & COMPILE refuses to save them:
- A CMP whose IN2 is an entity's id, such as
sensor.other. Home Assistant compares a state with that as plain text, so it never holds.- LIBI checks this only where the state can never be such a text: on/off devices, a person, a number or a date.
- A dropdown, a text field, a select, a sensor and an attribute may legitimately hold an entity's id, so they are never checked.
- In a trigger, an
input_*helper counts as such a text too, because a trigger never reads a helper's value.
- An IN2 you emptied.
- A ≠ that starts an automation on a state. Use CMP = with the state it changes to, or a P contact for any change.
- A ≠ held for a time (a TON after it). Home Assistant has no form for it.
- A person in a zone with a TON after it. A zone check has no for. A plain delay after it is fine.
IN2 of a CMP of a value is now labelled Value or helper. None of the NETs of a real installation turned red (52 NETs, 45 automations).
Known limitations
- Home Assistant's newer trigger form is not drawn completely. An example is
trigger: light.turned_onwithtargetandoptions. LIBI warns when you load such an automation, and asks before a save would change it. - A
notaround a check that has its ownforis drawn without the not. LIBI warns when you load such an automation, and asks before a save would change it. - A few edits are refused by Home Assistant at save time. Nothing is written, but Home Assistant's message does not say why:
- a person→zone check inside an OR branch whose TON you removed;
- a trigger with two zones;
- a CMP TIME or CMP DATETIME = used as a condition against an e...
v2026.11.09
Traces is now the online view of a PLC. Press Traces and every NET shows what Home Assistant is doing right now: the state of each block, the two values a comparison compares, a TON counting down, and what the last real run did, written under each block.
FORCE TRUE runs the trigger you choose. In Real, click a trigger and press FORCE TRUE ▶ run it in Home Assistant. Home Assistant runs the saved automation for real, as if that trigger happened now, so the rung of that trigger runs. Before, a run started with no trigger at all, from LIBI and from Home Assistant's own Run, so a rung that runs for its own trigger never ran. In Simulate, the default, nothing is sent to Home Assistant: FORCE a block TRUE or FALSE and watch the NET run inside LIBI.
Nothing can be edited while Traces is on. A click only follows the run or FORCEs a block. Turn Traces off to edit.
This release also fixes Traces showing one NET with another NET's states. With two automations opened from Home Assistant, a lamp could be shown off right after it was turned on, and a rung of the other NET lit.
Before 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. A LIBI page left open from before the update saves nothing and says "LIBI was updated: reload this page".
- 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.
Nothing else is required. Your projects, NETs and version history open as before, Traces never writes to your automations, and the minimum Home Assistant version is still 2025.1.0.
What Traces shows
- Open it: press Traces in the header (on a phone, in the menu). The ONLINE bar opens over the NETs, with the clock and the switch between Simulate and Real.
- Over each NET, a monitor shows:
- the clock now
- whether its automation is on or off in Home Assistant, and whether it is running
- its last run
- the value of every variable it uses; one that is offline is red
- Each block shows:
- its state: green when it is TRUE, or for an action while what it drives is on, and grey when it is not
- OFFLINE or NOT IN HA when its entity is unavailable or gone
- for a comparison, IN1 and IN2, for example the clock now and the time it waits for
- for a CMP DAY, the day now and the days ticked on the card, by name: IN1 sun, IN2 sun mon tue wed thu. The monitor shows the days by name too.
- for a comparison with a list of states, such as IN2 rainy, pouring, hail: = is TRUE when IN1 is one of them, and ≠ when it is none of them, as Home Assistant checks it. While it rains, a watering rung's ≠ rain is FALSE, and a simulated run stops there.
- for a comparison with a zone, IN1 against the zone's name, as a person's state names it
- for a TON, the time left, counting down: the for of a trigger, or the delay a run is in
- The last real run, from Home Assistant's own trace, is written under each block:
- RUN ▶ started the run: the trigger that started it
- RUN ✓ true and RUN ✓ done
- RUN ✗ false: stopped here
- RUN ⚠ error, with Home Assistant's reason in the block's menu
- RUN ⏳ 00:01:20: the step it is in, counting down
- RUN – not reached
- A run started with no trigger says so in the monitor. For a NET you drew in LIBI, the run is shown in its monitor rather than on each block.
- NETs are taller while Traces is on, so that every line under a block has room. Turn Traces off and they are drawn as you edit them.
FORCE: click a block
- Click any block to open its menu, next to the block. It shows what the block gives now, what the run did there, and what you can do with it.
- Simulate (the default):
- FORCE TRUE or FORCE FALSE. Release frees the block, and Release all in the ONLINE bar frees every block.
- A trigger forced TRUE runs its rung inside LIBI only: each condition, each action it would run, each TON counting down (⏭ ends one at once). The lines under the blocks start with SIM.
- Nothing is sent to Home Assistant, and no device moves.
- Real:
- Click a trigger, then FORCE TRUE ▶ run it in Home Assistant. LIBI names the automation, the trigger and what it switches, and asks first. When the automation has conditions of its own, you can also run it without them.
- Home Assistant runs the saved automation as if that trigger happened now. The result appears under each block. In Home Assistant, the run's trace says LIBI: FORCE TRUE.
- Home Assistant checks the conditions of each rung itself. To force a condition, use Simulate: a condition's menu has Switch to Simulate.
- What the trigger itself would tell (
trigger.to_stateand the like) is empty in such a run. - An automation whose mode is single and that is already running ignores the run, as Home Assistant does.
- Run without a trigger, over each NET, is Home Assistant's own Run: a rung that runs only for its own trigger does not run.
What Real does not run
- An automation that can reach a lock, an alarm or a cover. That covers one named in the automation, or in any script or automation it runs, however deep. It also covers one in an area, floor, device or label it targets, and one in a scene or a group it turns on. Try it in Simulate, or run it from Home Assistant's own editor.
- An automation LIBI cannot read through: one that picks what it switches with a template, or that calls a script Home Assistant has not loaded.
- A NET with changes not saved. Home Assistant would run what it has, not your drawing. Nor a NET not in Home Assistant yet, or an automation that is turned off.
- An automation changed after you were asked. LIBI checks it again just before the run. If it changed in Home Assistant in the meantime, LIBI does not run it and says so.
- Not checked: another automation that starts because of what the run switched. It runs as it would if you had switched that yourself.
Read only while Traces is on
- A click only follows the run or FORCEs a block. Everything below waits until Traces is off:
- choosing or changing an element, the Inspector, and the entity chooser
- adding, moving and deleting: the + points, Add Rung, dragging, dropping a variable, and right-click Rename
- a NET's name and kind, Load, Versions, Duplicate and Delete NET
- Undo and Redo (and Ctrl+Z, Ctrl+Y), SAVE & COMPILE, and Clear all nets
- opening or creating a project, the AI Chat, new variables and helpers, and Global
- A click on one of those says "Traces is on, so nothing can be edited. Turn Traces off to edit."
- Still there: folding a NET, its YAML and its dashboard card, the Variables bar's tabs and search, Logs, and the automation's on/off switch.
Fixes
- Traces drew a NET with another NET's states. Two automations opened from Home Assistant got the same block ids, so Traces drew one with the other's states: a lamp shown off right after it was turned on, and a rung of the other NET lit. Each NET now has its own.
Under the hood
- New websocket command
libi/online_fire, admin only. It writes no file.- Without
fire, it only says what a run would be, or why LIBI does not run it. - With
fire, sent only after the user confirms, it makes the plan again. It runs the automation only when it is still the one the user was shown (before).
- Without
- The run is the automation entity's own
async_trigger, which Home Assistant'sautomation.triggercalls too. It passes the trigger'sidandidx. Home Assistant checks the conditions, honours the automation's mode and keeps the trace. - What a run can reach is read from what Home Assistant has loaded, never from LIBI's drawing.
libi/project_openandlibi/save_donealso returnkeys, each NET's key in Home Assistant. Traces uses it to find the automation and the trace of a NET drawn in LIBI.- Panel build 3.94.3.
- Tests: 382 pytest tests against a real Home Assistant, and 40 browser test pages. Traces is tested on runs captured from a real Home Assistant.
Full Changelog: v2026.11.06...v2026.11.09
What I checked:
GitHub, on 8762542: CI, Hassfest and Validate (the HACS Action) all passed.
Gate with GITHUB_REF_NAME=v2026.11.09: BLOCKER 0, ERROR 0, HOT_WARN 0, WARN 1, INFO 2, the same as before.
libi.zip built from the current code: 31 files, only the integration, no pycache.
Read-only review of what changed since 2026.11.08: only drawing in Traces, versions and tests. Nothing calls Home Assistant, saves, deletes or writes HTML.
pytest (382) and the panel pages (40) ran here on the same code, before the version bump. CI also ran pytest on GitHub after the bump, and it passed.
One open issue, your call (compile #11):
Traces now compares against a list of states the way Home Assistant does.
But a CMP with a list that you create or edit in LIBI is still saved as a single text value. So for such a NET, Traces can show FALSE while Home Assistant treats the condition as TRUE.
The same bug exists in v2026.11.06.
Automations imported and left unedited are saved as they were, so they're fine.
Full Changelog: v2026.11.06...v2026.11.09
v2026.11.06
Your phones, in one place. The new Global tab, next to Variables, holds global variables: a recipient such as "Guy's phone" or "Yulia and Guy", made of the phones you tick. A MOVE NOTIFY / TTS block sends to the recipient instead of to a phone. When you replace a phone, you change it once, in Global, and every NET in every project follows. LIBI also offers to move your existing automations onto the recipient, including the ones made in Home Assistant's editor. It changes only the ones you confirm.
Your names, in one place too. Every entity you renamed in LIBI only is listed in the Global tab, under Named in LIBI. Every project shows it by that name.
A save never deletes what you did not ask it to. An automation you opened from Home Assistant is never deleted by SAVE & COMPILE, and LIBI asks before it deletes anything it made itself. A NET you did not change is never written again: what you changed in Home Assistant's own editor stays. A NET no longer replaces a script or an automation of the same name that is not its own, and a copy of a NET no longer replaces an automation whose id ends in _copy.
Nothing is written over a change made while you decide. Just before each change goes to Home Assistant, LIBI checks it again. If it changed in the meantime, in Home Assistant's editor or from another LIBI page, LIBI does not send it. A LIBI page opened before another page saved the same project saves nothing, so it never writes over that save.
This release also fixes messages that never arrived. A MOVE NOTIFY / TTS block could be saved with a phone's notify entity instead of the action that sends to it. Home Assistant accepted the save, and the automation failed only when it ran.
Before 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. A LIBI page left open from before the update saves nothing and says "LIBI was updated: reload this page".
- 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 your NETs that send messages. A block whose phone is shown in red was saved with the phone's notify entity, and it sends nothing.
- Pick the phone again in Send to, or press Send with notify.mobile_app_….
- Then SAVE & COMPILE.
Nothing else is required. Your projects, NETs and version history open as before, and the minimum Home Assistant version is still 2025.1.0.
Global: the phones a message goes to
- Where to find it. Open the Variables bar at the bottom and choose Global. Each global variable is a row of the table, showing:
- its name and its type, RECIPIENT
- its devices by name, with their ids
- how many automations send to it
- Make one. Press + New global variable, give it a name, tick one phone or several, and press Save.
- With several phones, every message goes to all of them at once, and a phone that fails does not stop the others.
- Change one. Click its row.
- Save closes the editor, and the table shows what was saved.
- Cancel leaves the variable as it was.
- Delete one with 🗑. LIBI does not delete a global variable while anything still sends to it, and it names what does.
- Send to it. In a MOVE NOTIFY / TTS block, Send to lists the global variables first.
- The block shows the variable's name.
- When a block sends to a global variable, Open Global next to Send to opens that variable.
- When a phone is replaced: open the variable, untick the old phone, tick the new one, and press Save. Every NET that sends to it now sends to the new phone, and no NET has to be saved again.
- Read aloud. A message read aloud (TTS) is read aloud by an Android phone. An iPhone shows the spoken text instead of the word TTS.
- In Home Assistant, each global variable is a script,
script.libi_send_to_<name>, named LIBI Global: <name>.- It is saved through Home Assistant's config API, like every LIBI save.
- If you change it in Home Assistant's script editor, LIBI marks it edited, and Save in LIBI writes it again the way LIBI writes it.
- A deleted variable. A NET that sends to a global variable that no longer exists is shown in red and is not saved.
Named in LIBI, in the Global tab
- Every entity you renamed in LIBI only (right-click ▸ Rename ▸ In LIBI only) is listed in the Global tab under Named in LIBI, below the global variables. Each row shows:
- its name in LIBI and its type (BOOL, INT, FLOAT, TEXT, TIME, or HA for an ordinary entity)
- its name in Home Assistant, and its id
- how many automations, scripts and scenes of Home Assistant use it (point at the number to see which)
- Rename it: click its row. The usual Rename dialog opens.
- Take the name in LIBI away: press 🗑 and confirm. Every project shows Home Assistant's name again.
- Nothing changes in Home Assistant either way.
- The same in every project. A name given in LIBI is kept once, for every project, so every project shows it.
- An entity that Home Assistant no longer has is marked gone.
- The Global tab's number counts these names too.
Replace the phone in your automations
- After you save a global variable, LIBI asks: Send through <name>?
- It lists every automation and script that still sends straight to the variable's phone, including the ones made in Home Assistant's editor.
- Each one is ticked. Untick any you want to keep, then press Replace in N, or Not now.
- Later: a line above the table offers the same, for example "8 automations and scripts still send straight to S23, not through Guy's phone", with a Replace… button.
- Only one thing changes in each one: the action of those steps, from the phone to the global variable.
- The message, title and data stay as they are.
- Home Assistant saves and reloads each one, and LIBI reads it back before it says it is replaced.
- A NET on the page you have open is changed on the page and saved with SAVE & COMPILE. This happens only when the page has no unsaved changes.
- Not replaced (the dialog shows the reason for each):
- a step that sends the phone more than a message, a title and data
- a NET drawn in another LIBI project, because that project's next save would put the phone back. Open that project and replace it there.
- anything, for a global variable of more than one phone: an automation that sends to one of its phones would start sending to all of them
- anything at all, while one of your LIBI projects cannot be read
- Home Assistant writes the old
service:key of those steps asaction:, as its own editor does.
Phones by name in MOVE NOTIFY / TTS
- Send to lists your phones by name, each with the action that reaches it, followed by Home Assistant's other notify actions. The name is the one you gave in LIBI, or else Home Assistant's.
- Choosing a phone from the right-click entity chooser now picks the action that sends to it.
- A phone that cannot be reached is shown in red, with a Send with notify.mobile_app_… button.
- SAVE & COMPILE does not save a changed NET that sends to a notify action Home Assistant does not have, and says which NET it is. Automations you did not change are not stopped.
- Two phones with the same name. When two phones are registered in the Companion app under the same name, they share one action, and it reaches only one of them. LIBI marks those phones and does not offer them. Give one of them another name in the app.
- One name per phone. A name you give a phone in LIBI is shown for both its entity and its action.
- The AI Chat's lists show the names you gave in LIBI too.
A save deletes only what LIBI made, and asks first
- An automation you opened from Home Assistant is never deleted by a save. Before, a NET that left the canvas any other way than Delete NET… took its automation with it at the next SAVE & COMPILE, even one written by hand or in Home Assistant's editor. That happened with Clear all nets, undo, another automation loaded into the same NET, and the AI Chat's Replace.
- Now such an automation stays in Home Assistant as it is, and leaves the project.
- After the save, LIBI names what it left in Home Assistant.
- What LIBI created itself (a NET you drew, a copy, a NET of the AI Chat) is deleted only once you agree. When it is no longer on the canvas, SAVE & COMPILE lists it and asks:
- Delete: it is deleted from Home Assistant, and the rest is saved.
- Keep in Home Assistant: it stays as it is, and leaves the project.
- Cancel: nothing is saved, and nothing is deleted.
- What LIBI saved before this version has no record of who created it, so a save never deletes it. To delete one of those, use Delete NET… ▸ Delete completely.
- Delete NET… asks as before.
- Clear all nets now says what the next save does.
A NET you did not change is never written again
- SAVE & COMPILE sends only the NETs you changed in LIBI. Before, a save also wrote the NETs you had not touched, and that could change the automation:
- What the ladder cannot draw. In an automation renamed in Home Assistant's editor, a trigger that no option of a choose used was dropped.
- A change made in Home Assistant's editor. A script NET was saved back as LIBI had drawn it.
Now both stay as they are, and after the save LIBI names a NET whose entry Home Assistant changed.
- Before a save would do any of the following, LIBI says which automation and asks:
- Deleted in Home Assistant since LIBI saved it, in Home Assistant's editor or from another...
v2026.11.04
LIBI no longer writes your automation files itself. Every save now goes through Home Assistant's own config API, the same one Home Assistant's automation, script and scene editors use: Home Assistant checks each automation, writes it and reloads it, and LIBI says a NET is saved only after Home Assistant has reloaded it.
This release also lets you name an entity in LIBI only, without changing Home Assistant. You can list the variables of one NET or of the whole project, and the ladder stays where you scrolled it when you click an element.
Before 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.
- A page that still runs the previous LIBI does not save. It says "LIBI was updated: reload this page. Nothing was saved or deleted."
- If LIBI says it could not draw this page, the browser is still using an older copy of one of its files. 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.
- Home Assistant now writes the files. When it saves a change to
automations.yaml,scripts.yamlorscenes.yaml, it rewrites the whole file in its own format, exactly as its own editor does.- Comments in the file are not kept. If you keep comments in
automations.yaml, make a copy first. - Every automation or scene without an
idgets one. - LIBI sends only what it changed, so a save with no changes writes nothing.
- Comments in the file are not kept. If you keep comments in
libi_automations.yaml(the file LIBI used before version 3.5.0) is no longer moved or emptied. LIBI leaves it alone. If it still holds automations, the log says so, and you can remove it yourself once you have checked it.
Nothing else is required. Your projects, NETs and version history open as before, and the minimum Home Assistant version is still 2025.1.0.
Rename: in Home Assistant, or in LIBI only
- Right-click an entity's name above a block, or a variable inside the block, and choose Rename. Until now, the variables inside a block had no right-click menu.
- The dialog offers two ways:
- Rename in Home Assistant changes the name Home Assistant shows everywhere. The entity id stays the same, so nothing that points at it breaks.
- In LIBI only leaves Home Assistant as it is. Your name is shown wherever LIBI shows that entity: above the block, inside it, in the Variables bar and in the list of entities. When you hover over it, LIBI still shows the entity id.
- Some entities Home Assistant cannot rename: they have no unique ID, for example because they were written in YAML. For those, LIBI offers In LIBI only. If Home Assistant refuses a rename, LIBI keeps the name in LIBI only and tells you why.
- Remove the LIBI name brings Home Assistant's name back. Renaming the entity in Home Assistant also removes the LIBI name, so it does not hide the new one.
The variables of a NET, or of the whole project
- Click the title of a NET: the Variables bar at the bottom lists only the variables that NET uses, and the NET is outlined.
- Click the project's name in the header: the bar lists the variables of every NET in the project.
- Clicking an element chooses its NET too. The arrow at the right of a NET's title still folds and unfolds it.
The ladder keeps its place
- Clicking an element to open it in the Inspector no longer throws the ladder back to the start. Both the page and each NET's own horizontal scroll stay where they were.
- The right-click menu opens where you clicked, and stays on the screen near an edge.
SAVE & COMPILE: compile first, then save
- Every NET is compiled first and checked with Home Assistant's own validator. If any NET fails, nothing is saved, and LIBI names that NET and gives the reason.
- If Home Assistant refuses a change, LIBI stops there and tells you which NET was refused and how many changes were not sent.
- A reload that fails is reported as a problem with that save, never hidden behind "saved".
Your original automation is always kept
- The first time you open an existing automation in LIBI, it is kept exactly as Home Assistant had it, as V1, the original. An unchanged copy, V2, is the version you work on. A NET you draw from scratch starts at V1.
- The original is never dropped from the history.
- Automations you already opened with an earlier LIBI keep the history they have. The original copy is made for every automation you open from now on.
Deleting a NET asks what happens to its automation
Delete NET… in the NET menu replaces Remove from Net and Delete File. For a NET whose automation is in Home Assistant, it offers:
- Delete completely: the automation is deleted from Home Assistant too. LIBI also offers to delete the NET's local helpers, meaning the ones nothing else uses.
- Delete and go back to V1: the original automation is put back. This is offered when the NET has an original.
- Remove from LIBI only: the automation stays in Home Assistant exactly as it is.
Unsaved changes
Closing a project, opening or creating another one, or leaving LIBI with unsaved changes now asks whether to save them first. Yes runs SAVE & COMPILE; when you close or switch projects, a save that fails keeps you in the editor. Closing the browser tab shows the browser's own warning.
AI Chat
- One window for the NET's settings. The settings the logic reads (start time, days, amounts, the on/off switch) are its local variables, and they all appear in one window at the top. Each one uses a free helper of yours that fits, or a new one LIBI creates when you press the button. All new makes every one of them new.
- LIBI asks its own questions. For an automation that switches a device, LIBI asks the same questions every time:
- an on/off switch for the whole automation (off stops it at once)
- a message when it starts and when it ends: a notification, spoken by your phone (the Home Assistant app on Android), or both
- what to do when the device is offline
- a message when a battery of its devices runs low
- Days and a start time on the dashboard card, like an alarm clock. The days are one helper, shown on the card as seven round day buttons by LIBI's own
custom:libi-days-rowrow. The row also works in the browsers Home Assistant serves its older build to, such as Samsung Internet and older Android WebViews. - Zones and people. Every zone and person is listed. "Being at a place" asks for both who and where, and a zone you choose on the dashboard card is a dropdown of your zones.
- Your request is checked line by line. The chat shows ✓ or ✗ for every line of your request. A draft that misses a line is not saved on its own. LIBI checks every answer from the AI and sends back what does not hold, up to three answers.
- Add / Replace NET saves and compiles at once and reads the automation back from Home Assistant. LIBI asks first when other unsaved changes or a sensitive device would be saved with it.
- Your ticks win. The phones you tick are the ones messages go to, even when your request names others.
- A NET changes only when you name it ("update NET 3 ..."), and the change becomes a new version. Any other request becomes a new NET after the last one.
Ladder
- The ladder uses only the blocks in the palette. A wait is drawn as what it waits for (a contact or a CMP) with a TON for its time limit. A schedule is a CMP DATETIME. A trigger that must hold for a while is the trigger followed by a TON.
- An automation's trigger is drawn once, and the rungs that belong to it hang below it.
- CMP DAY can read the days from one helper. IN1 of CMP DAY and CMP TIME reads
datetime.day.nowanddatetime.time.now. - REPEAT blocks, variables steps and durations written as templates are kept on the way back to YAML.
- 📊 Dashboard card in the NET menu: a card for any NET, built by LIBI from what the NET reads and switches, to copy into a dashboard.
Fixes
- A NET that did not compile could cause its automation to be removed on the next save. Now nothing is saved.
- A deleted NET no longer comes back after the page is reloaded.
- A NET removed from LIBI no longer loses its automation at the next save.
- After an update, a browser could keep an older copy of one of LIBI's files next to the new ones, and LIBI's page stayed blank with nothing in Home Assistant's log. Every file now has a new address with each version. A page that cannot be drawn says so and tells you how to reload.
Under the hood
- LIBI's Python writes only its own files in
config/libi/: projects, their version history, andlocal_names.json(the names given in LIBI only). It only readsautomations.yaml,scripts.yamlandscenes.yaml. - The panel sends each change itself to Home Assistant's config API (
config/automation|script|scene/config/<id>, POST to save, DELETE to remove). - New websocket commands, all admin only:
libi/compile_project,libi/save_done,libi/net_delete_planandlibi/net_removedfor saving and deleting;libi/local_namesandlibi/local_name_setfor the names in LIBI only.
libi/save_automationandlibi/delete_automationnow refuse with the message above.- The manifest now depends on
config. Panel build 3.86.1. - Tests: 298 pytest tests against a real Home Assistant, and 18 browser test pages.
Full Changelog: v2026.10.28...v2026.11.04
LIBI 2026.10.28 – Net versions, an AI chat that knows your nets, and a phone layout
What's new
🕘 Every NET now has versions
Made a change that broke something? Go back.
- When you open a project, every NET is recorded as V1.
- Every SAVE & COMPILE that really changes a NET records the next version: V2, V3, …
- A change you made in Home Assistant's own automation editor is recorded as a new version the next time you open the project.
- The V badge next to each NET's name shows which version is running in Home Assistant right now.
- Click the badge (or Versions in the NET's ⋮ menu) to see every version with its date, time and YAML.
- Put on the canvas brings an earlier version back. Nothing changes in Home Assistant until you press SAVE & COMPILE; that version then becomes the one that runs, and the badge turns orange (V1 · newest V2) so you always know the newest version isn't the one running.
- If you don't choose a version, the newest saved one is the one that runs.
- A save with no change doesn't create a version, and doesn't rewrite or reload anything.
🤖 The AI chat knows the nets on your page
- Ask about your logic: "what does the garden net do?"
- Ask for a change: "water on Sunday, Tuesday, Thursday and Saturday at 5:00, skip it if it rains". You get a new draft and put it in place of the old net with Replace NET. The automation keeps its id.
- The chat can suggest new helpers (days, start time, amount of water…). They're created only when you click.
- When the logic reads settings, you get a dashboard card in YAML to copy, so you can change days, times and amounts from the dashboard.
- The AI still never picks a device on its own. Every entity is one you ticked, and every draft is checked by LIBI and by Home Assistant's own validator before you can save it.
Privacy: with Share the nets on this page and my helpers on (the default), the chat sends only the YAML of the nets open in the LIBI page, your helpers, and the devices that match your request. The rest of automations.yaml, scripts.yaml and scenes.yaml is never sent. Turn the switch off to send less; with Local AI nothing leaves your server.
📱 Works on a phone
- Nothing is wider than the screen any more, so no sideways scrolling.
- ☰ on the left opens Home Assistant's sidebar.
- ⋮ on the right holds Undo, Redo, Collapse and Traces.
- Save is a round button.
Smaller improvements
- A CHAT AI button on the collapsed sidebar opens the chat directly.
- Clicking an element while the chat is open switches straight to that element's Inspector.
Fixes
- Conditions that apply to the whole automation are written back under
conditions:again, instead of being folded into the actions.
Upgrading
- Update LIBI in HACS.
- Restart Home Assistant (Settings ▸ System ▸ Restart). A quick reload isn't enough: until the restart, the Versions dialog asks you to restart.
- Open your project once: every NET gets its V1.
Your automations, scripts, scenes and projects are not changed by the update. The version history is stored in a new file next to each project, config/libi/<project>.versions.json, and is part of your Home Assistant backup.
Under the hood
- New admin-only websocket command
libi/net_versions. - The history is written atomically under the same lock as the saves. A refused save records no version, and an unreadable history file is left untouched.
- Up to 30 versions per NET; the running one is never dropped.
- New tests:
tests/test_versions.py, plus browser tests for the versions dialog, the phone header and the phone, tablet and desktop layouts.
Full Changelog: v2026.10.26...v2026.10.28
LIBI 2026.10.26: safer saving and checked AI settings
LIBI 2026.10.26
Recommended for everyone. This version fixes how LIBI saves automations that you load into it.
Fixed
- Automations with a template trigger. Saving one from LIBI also wrote its trigger into the conditions, which made the automation invalid in Home Assistant. It is saved correctly now.
- Automations you did not change stay as they are. LIBI no longer adds an id to every trigger when it saves, so automations you never touched are not rewritten.
If you saved an automation with a template trigger in an earlier version, open it in LIBI and save it once more, or check it in the Home Assistant automation editor.
Improved
- AI settings are checked before they are saved. LIBI tells you right away when the AI server cannot be reached, the API key is rejected, or the model does not exist.
- Privacy note. The setup screens and the AI Chat now say exactly what is sent to the AI model: your messages and the names of the devices you pick. Your automations, device states and the full list of your devices are never sent.
What the upgrade requires
Nothing. Update in HACS and restart Home Assistant.
Internals
The round-trip check compares both ways, with 20 test cases. Lint clean-ups, and the HACS workflows match Home Organizer's.
Full Changelog: v2026.9.9...v2026.10.26
Full Changelog: v2026.9.9...v2026.10.26
LIBI Ladder Interface & Building Intelligence
What is LIBI?
LIBI is a graphical editor that takes your existing Home Assistant automations and automatically translates them into a LADDER logic representation. It allows you to:
Add and modify automation logic using a visual interface.
Save the resulting logic directly back to standard Home Assistant YAML files.
Execute the automations natively within Home Assistant, just like any standard automation.
Full Changelog: https://github.com/GuyAzria/Libi/commits/v2026.9.9