Repository navigation
Releases: FezVrasta/ha-notes-vault
Release list
v0.9.0
Fewer notes left on their own in Obsidian's graph.
New
The index links the views and templates. Index.md now opens with a line linking the view notes (Rooms, Devices, Automations and the rest) and one linking the templates. Nothing else links them, so they used to float alone in the graph.
Automations and scripts link the integrations they call. When an automation or script calls an integration that has no entities of its own, like a shell command, Wake on LAN or a notification, its note links that integration. One that only runs a shell command is no longer on its own.
Trigger-based template sensors link what they react to. A template sensor set by a trigger now links the entities in its triggers, conditions and actions, not only the ones in its state template.
Entities without a unique ID get their integration. Their notes now show and link the integration that created them, taken from the platform behind them. Before, they had no integration at all.
Beta. The trash is there for mistakes, but keep /config/notes_vault in your backups.
v0.8.1
A fix for opening notes while the vault is being rewritten.
Fix
Opening a note during a sync. The Notes panel could fail to open a note while a sync was rewriting the folder it's in, with a FileNotFoundError on a temporary file in the log. It showed up right after 0.8.0, whose first sync rewrites every automation note. Files that disappear while a folder is being listed are now skipped.
Beta. The trash is there for mistakes, but keep /config/notes_vault in your backups.
v0.8.0
Automation, script and scene notes now link everything they act on.
Changed
Every entity your logic uses gets a note. An entity that an automation, script or scene uses now gets a note even if it's hidden, diagnostic, a configuration entity or disabled, since the home's logic acting on it makes it worth one. Before, an automation that only pressed a hidden button had no links at all. Entities you've excluded by name in the options still stay out. Expect a few more entity notes the first time this runs.
Automations link the devices they act on. Their notes now link the device of every entity they use, not only the devices they target directly, so an automation shows up on the note of every device it drives.
Fix
Notes about removed HACS devices can be edited again. Notes kept for devices that are no longer generated could be read but not saved.
Beta. The trash is there for mistakes, but keep /config/notes_vault in your backups.
v0.7.0
Tables in the editor, and long notes that don't take over the page.
New
Tables. The editor renders Markdown tables whenever the cursor isn't in one, as Obsidian does, with column alignment and bold, code, links and wikilinks inside cells. Click the table to edit its Markdown. Wide tables scroll sideways instead of squeezing their columns.
Long notes are cut short. On device and area pages, in the dashboard card and in the more-info dialog, a note stops at about twelve lines with Show all. That opens the whole note in Home Assistant's own dialog, a bottom sheet on a phone, where you can also edit it.
Fix
Borders on device and area pages. The notes card is outlined like the cards next to it, including with themes that turn card borders off.
Beta. The trash is there for mistakes, but keep /config/notes_vault in your backups.
v0.6.0
Views of the whole house in Obsidian, and fixes for typing in the editor.
New
Obsidian views. Notes Vault adds a set of Bases, each in a note next to the index that says what it's for: Rooms, Devices, Automations, Integrations, Batteries, Recently changed and Cleanup. Rooms shows a card per room, and each card opens that room's page: its devices, its entities, and the automations, scripts and scenes that touch it. Cleanup lists notes about things Home Assistant removed, devices with no room, and helpers to check.
The views are written once and then yours: change them, delete them, and updates leave them alone. Delete the Bases folder to get the defaults back. The room pages are generated and follow your areas, so write about a room in its own note. There's an option to turn it all off.
Fix
Typing in the editor. Letters like e and c opened Home Assistant's search and command bars instead of landing in the note, and every key after that went there too.
Link completion. Picking a note after [[ left the cursor in front of the closing ]], so pressing Enter split the link over two lines. Completion also offered notes that only happened to contain the same letters in order; it now matches what you typed.
Beta. The trash is there for mistakes, but keep /config/notes_vault in your backups.
v0.5.0
A new editor: notes render as you write them, the way they do in Obsidian.
New
Live preview. Headings, bold and italic, links, [[wikilinks]], quotes and tasks render in place, and the Markdown shows only on the line you're editing. Type [[ to link a note, an entity, a device or an area. Task checkboxes toggle with a click, and Enter continues a list.
The panel saves as you type. Open a note in the Notes panel and start writing, there's no Edit or Save. Saves still check the note hasn't changed since you opened it, so they can't overwrite something an assistant or Obsidian wrote meanwhile. In the more-info dialog, on device and area pages and in the dashboard card, Edit, Save and Cancel stay as they were.
A template menu. Switching template is a Template menu next to the other actions, instead of a dropdown above the note. It's there while the note is still an untouched template.
The editor is downloaded the first time you edit a note (about 120 KB), so pages that only show notes don't load it.
Beta. The trash is there for mistakes, but keep /config/notes_vault in your backups.
v0.4.0
The device folder was mostly things that aren't devices. This cleans it up: on a real install it goes from 232 device notes to about 120.
One note per physical device
Home Assistant 2026.9 splits a device served by several integrations into one registry device per integration. An ESPHome Bluetooth proxy, a Sonos speaker or a phone showed up two or three times under the same name. The parts now share one note with the integrations, labels and entities of all of them, and either part's device page opens it. Automations and scripts targeting one part link to that note.
No more software in the device folder
HACS registers a device for every repository it installs, and integrations and add-ons register "service" devices for themselves (Sun, Backup, each add-on, cloud services). None of them get notes any more. Service devices can be brought back with Include service devices in the options; their entities hang off the integration's note either way.
Readable names
A device with no name was filed under its registry ID. It now falls back to its model, maker or integration. Two devices with the same name are told apart by area, then model, maker or integration ("Studio (Hue ambiance candle)"), with the ID only as a last resort.
Upgrading
Notes for the skipped devices that still hold their untouched template are deleted on the first sync. Anything you wrote in one is kept and marked ha_removed: true.
Also fixed: HA 2026.9's deprecation warning about reading the device registry as a mapping.
Beta: used daily on a real vault. The trash is there for mistakes, but keep /config/notes_vault in your backups.
v0.3.0
Notes Vault is beta now. This release makes sure nothing written to the vault is lost by accident, now that assistants write to it too.
Fix
Stale saves no longer overwrite newer changes. The vault has four writers (the Home Assistant UI, Obsidian over WebDAV, assistants through the actions, and the sync), and none of them checked whether a note changed since it was read. If you had a note open while an assistant appended to it, your save wiped the assistant's text. Saves from Home Assistant now fail with a message if the note changed while you were editing, and WebDAV honours If-Match and If-None-Match.
The Notes panel is lighter. Opening a note or the tree no longer rebuilds every registry just to look up names.
New
A trash. Deleted notes and folders go to .trash/ in the vault, the same folder Obsidian uses, whether they're deleted from Home Assistant, by an action or over WebDAV. So does the previous version of anything an action replaces, since an assistant can't take back what it overwrote. The trash empties itself after 30 days.
A shorter README, with a table of contents. Template matching and the Obsidian plugin tips moved to docs/.
Beta: used daily on a real vault. The trash is there for mistakes, but keep /config/notes_vault in your backups.
v0.2.0
Fewer lonely notes in the graph, an index of what's actually been written, and a skill that teaches AI assistants to use the vault properly.
New
Integration notes. Every integration gets a note in Home Assistant/Integrations/ listing its devices and the entities that have no device. Devices with no area (HACS repositories, add-ons, network clients, cloud services) used to float on their own in Obsidian's graph; now they hang off their integration, the way they sit on its page in Home Assistant. Entities that belong to a device reach it through the device, so a big integration doesn't become one giant star. There's an option to turn it off.
Helpers link to what they're built from. A group links to its members, a template sensor to what its templates read, a min/max or utility meter to its sources, a zone to the people in it. Automations and scripts also link entities they only read inside templates, which Home Assistant's own reference lists leave out. A helper still alone in the graph after this is one nothing uses.
An index. Home Assistant/Index.md lists every note with something written in it, grouped by your own folders, areas, devices, automations, scripts, scenes and entities. Notes still holding their untouched template are left out, so it's the quickest way to see what you (or an assistant) have written down.
A skill for AI assistants. The repository ships a skill that tells an assistant when to read a note, what's worth writing, how to start from a template, and the traps to avoid. Install it in Claude Code with claude plugin marketplace add FezVrasta/ha-notes-vault and claude plugin install ha-notes-vault@ha-notes-vault, in other agents with npx skills add FezVrasta/ha-notes-vault, or upload ha-notes-vault-skill.zip from this release in Claude.ai and Claude Desktop.
Tip
The note templates aren't about anything in your home, so they sit alone in the graph. Hide them with -path:"Home Assistant/Templates" in the graph filter.
Still an alpha. Back up /config/notes_vault before trusting it with anything you'd miss.
v0.1.0
The first release. A notes vault inside Home Assistant, with a note on every entity, device, area, automation, script and scene, built so an AI assistant can write down what it learns about your house and read it back next session.
Notes in Home Assistant
A Notes panel in the sidebar lists the whole vault as a tree, with search, backlinks, folders, and notes you can create, rename, move and delete; links follow renames. The same editor sits in every entity's more-info dialog, on device and area pages, and in the automation, script and scene editors. Wikilinks work: an entity opens its dialog, a device or area its page, anything else opens in the panel.
A note for everything, generated
Every entity, device and area gets a Markdown note whose frontmatter Home Assistant keeps in step with the registries: name, IDs, integration, area, device, labels, and links between them. Automations, scripts and scenes get folders of their own, and their notes link every entity, device and area they touch, so a device's backlinks list the automations that drive it. Rename an entity ID and its note moves, with every link to it rewritten.
Notes start from a template picked for what they're about: a light asks for the bulb and the breaker, a battery device for the battery type and a replacement log. Templates are ordinary notes in the vault, so you edit them like anything else.
For AI assistants
Actions to read, write, append, search and list, all returning data, so any MCP server for Home Assistant can use the vault with nothing to install on the AI side. The README has the instructions I give an assistant so it actually takes notes.
Obsidian and other apps
The vault is a plain folder of Obsidian-style Markdown in your config directory, included in backups, and served over WebDAV for the remotely-save plugin and any other WebDAV client.
Still an alpha. Used on a test instance and one real vault so far. Back up /config/notes_vault before trusting it with anything you'd miss.