Repository navigation
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 LIBI project: Remove its NET takes the NET out of the project too; Save it again puts the automation back. Before, the next save put it back without asking.
- Changed in Home Assistant since LIBI last saw it, while the LIBI page was open: Replace with my NET replaces that change. To keep the change, choose Cancel and open the project again; the NET of an automation is drawn again from Home Assistant.
- Parts LIBI cannot draw of an automation you changed: they are listed, and Save anyway saves.
- Cancel to any of these saves nothing and changes nothing on the canvas.
A NET never takes another one's place
- A script NET named like one of your scripts used to replace it. For example, a new NET called "Good night" overwrote your
script.good_night. Now it is saved asscript.good_night_2, and yours stays exactly as it is. - The same goes for a script or an automation of another LIBI project. A NET you draw is
n1in every project, so the first NET of a second project used to overwrite the first project's automation. It is now saved as the next free id,n1_2. - A NET keeps the key it was saved under, even after the other one is gone. Before, once you deleted your own
script.good_night, LIBI's NET went back togood_night. That created a second script and offered to deletegood_night_2. The same happened withn1_2andn1. - A copy of a NET is a new automation. Duplicate used to give the copy the id
<id>_copy, as if it had been opened from Home Assistant. The save then wrote it over an automation of yours with that id, or over another project's copy. A copy now gets an id of its own. A copy made by an earlier version is not saved over an automation it does not own: LIBI names that automation and saves nothing. - Two NETs can never be the same automation. One automation loaded into two NETs, or two copies made by an earlier version, used to overwrite each other in the same save. LIBI now names the two NETs and saves nothing.
- An automation you opened from Home Assistant is still that automation: its NET changes it, as before.
Nothing is written over a change made while you decide
- Each change is checked again just before it is sent. While the questions of SAVE & COMPILE are open, you may create or change the same automation, script or scene somewhere else, in Home Assistant's editor or from another LIBI page. LIBI then does not send that change, or anything after it, and says why: press SAVE & COMPILE again.
- Before, LIBI wrote over it. A script you created in the meantime was also counted as one LIBI made, so a later save offered to delete it.
- A LIBI page older than the project saves nothing. When the same project is open in two places, for example on your phone and on your computer, the page opened before the other one saved cannot save. It says so, and you open the project again.
- Before, it wrote its own NETs over the newer save, removed the other page's new NETs from the project, and offered to delete them from Home Assistant.
- One project on a new browser. When there is one project and the browser remembers none, LIBI now opens that project.
- Before, LIBI showed the project's name over the canvas the browser had kept, or over an empty one. A save then replaced the project's NETs with that canvas.
- Delete NET… names the automation. The dialog says which automation, script or scene it would delete, and whether LIBI made it or you opened it from Home Assistant. Like a save, it checks the entry again just before it deletes it or puts V1 back.
Fixes
- A save reported as failed when it had worked. LIBI could say "unavailable: Home Assistant did not accept it" after a save that Home Assistant had in fact saved and reloaded. While Home Assistant reloads, it removes the entity and adds it back, and LIBI took that brief gap for a failure.
Under the hood
- A save, from the HACS review of 2026-11-05:
libi/compile_projectmarks each upsert that creates its entry (new), and listsremovals(only entries the project made) apart fromreleased.libi/save_donetakeskept, the removals you chose to keep.- The project records what it made, under
madein the.libifile. - The key of every NET is checked against what Home Assistant already holds.
- Each NET is compared with the version LIBI last saw in Home Assistant. A NET not changed since is not sent. The plan names what was deleted (
gone), changed (conflict) or cannot be drawn (loses), and what is left as Home Assistant has it (left).
- A save, from LIBI's own review of 2026-11-06:
- A NET with an
ha_idis that automation only when the project owns it, or the automation was opened into that NET. - A key moved aside is kept per NET, under
keysin the.libifile. - Each change of the plan carries a fingerprint of what it found (
before).libi/save_checkcompares it again just before the panel sends the change. - An entry counts as
madeonly with the tokenlibi/save_checkgave when it confirmed the create. - The project has a
revision, one more each time LIBI writes it.libi/compile_project,libi/save_doneandlibi/net_delete_plantake the revision the page opened, and refuse an older one.
- A NET with an
libi/globalalso returnsname_users: for each entity named in LIBI only, the automations, scripts and scenes that hold its whole id.- New websocket commands, all admin only and none of them writing a file:
libi/save_checklibi/phoneslibi/global,libi/global_planandlibi/global_donelibi/global_move_planandlibi/global_move_done
- The panel sends each change to Home Assistant's config API itself, as every save has since 2026.11.04.
- A global variable is kept only in
scripts.yaml. There is no new LIBI file. - A NET saved as a script cannot take a name that starts with
libi_send_to_. Those names are reserved for global variables. - Panel build 3.92.0.
- Tests: 369 pytest tests against a real Home Assistant, and 29 browser test pages.
Full Changelog: v2026.11.04...v2026.11.06