Skip to content

v2026.11.04

Choose a tag to compare

@GuyAzria GuyAzria released this 04 Nov 11:55
· 13 commits to main since this release

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

  1. Restart Home Assistant after the download. HACS shows Restart required.
  2. 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.
  3. Home Assistant now writes the files. When it saves a change to automations.yaml, scripts.yaml or scenes.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 id gets one.
    • LIBI sends only what it changed, so a save with no changes writes nothing.
  4. 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-row row. 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.now and datetime.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, and local_names.json (the names given in LIBI only). It only reads automations.yaml, scripts.yaml and scenes.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_plan and libi/net_removed for saving and deleting;
    • libi/local_names and libi/local_name_set for the names in LIBI only.
  • libi/save_automation and libi/delete_automation now 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