Skip to content

v2026.11.11

Choose a tag to compare

@GuyAzria GuyAzria released this 11 Nov 11:13
· 1 commit to main since this release

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

  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.
    • 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.
  3. 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.yaml for state: 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.

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 empty to: 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_on with target and options. LIBI warns when you load such an automation, and asks before a save would change it.
  • A not around a check that has its own for is 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 entity.
  • Typing "heat, dry" into an existing single-state check saves it as one text, which never holds. Type one state, or draw a new block.
  • An automation loaded into a NET but not saved yet does not yet count as in use for other projects.
  • When you choose "A schedule", a setting whose name mentions minutes or hours (such as minutes before) is taken out of the AI's plan. You can see this in the chat's list of variables before you build.
  • Changing a NET through the chat that already has many settings may leave out some of its day switches (beyond 20 settings and devices).

Under the hood

  • Websocket:
    • libi/list_automations returns the projects that hold each automation, with their NETs (in_use), and the projects that could not be read (unreadable).
    • libi/get_automation refuses a load into a project with in_use or projects_unreadable. It reads the automations and their holders under one lock.
  • The schedule editor:
    • It calls Home Assistant's own schedule/update, which is admin only.
    • That update replaces the whole schedule, so the name, the icon and all seven days are sent.
    • The helper is found by the entity registry's unique id, and schedule/list is read again right before the write.
  • The compiler:
    • An edited CMP = / ≠, or an edited contact of a state, is compiled from the check it was drawn from, including any not around it, in that not's own form.
    • A block's for is its TON.
    • A node you did not change is written as it was.
  • The AI draft check: rungs_without_action and literal_checks. LIBI's own requirement line It ends when the block ends is added only when the logic turns something on.
  • Before this release, an independent review read all the changes six times. Every finding about data or saving was fixed, with a test that fails without the fix.
  • Panel build: 3.95.5.
  • Tests:
    • 440 pytest tests against a real Home Assistant, and 47 browser test pages.
    • Virtual tests on a real installation's 45 automations and 52 NETs. Opening the Inspector on all 232 blocks changed none of them, and every saved NET compiles to exactly what Home Assistant has.

Full Changelog: v2026.11.09...v2026.11.11

Full Changelog: v2026.11.09...v2026.11.11