Every client now hears when System Bridge sends a notification, with its title, message and buttons, so anything following its clicks and closes can tell which notification they belong to. The web client lists recent notifications and can add buttons, and the Home Assistant dashboard gets a Notifications section.
Notifications
- Broadcast
NOTIFICATION_SENTwith the idsystemto every client when a notification is sent, carrying itsid,title,messageandbuttons. The sender's own reply keeps its request's id, as before (docs) (#4594) - Document that buttons and click events work on Linux and Windows, and that only Linux sends
NOTIFICATION_CLOSED(docs)
Web client
- List recent notifications on the System page, sent from any client while the page is open, with what happened to each: clicked, a button by its label, or closed and why
- Add up to 3 buttons to the notification form
Home Assistant dashboard
- Add a Notifications section to the System page, with the notify entity and the notification event entity, shown once Home Assistant has them
Connector
- Pass sent notifications to
notification_event_callbackin the Python connector andnotificationEventsin the TypeScript connector, withtitle,messageandbuttonsonNotificationEvent
Media
- Report a paused player with no track as stopped
MCP and CLI
- Add
system_bridge_list_media_directoriesandsystem_bridge_list_filesMCP tools, and mark the tools that only read - Add
system-bridge agent toolsandsystem-bridge agent call, which list and run the MCP server's tools from the command line (docs)
Dependencies
- Update Groundwork and @timmo001/docs-kit to 0.12.1
- Update Vite to 8.3.6 (#4586), @astrojs/cloudflare to 14.4.6 (#4590) and Ruff to 0.17.4 (#4591)
- Update jdx/mise-action (#4593) and docker/login-action (#4589)
Maintenance
- Review the Home Assistant frontend 20261028.5 and BlueZ 5.88
- Run Nix rootless through nix-portable instead of Docker for hash updates
- Add an OpenCode plugin for the
system-bridgeCode Mode namespace
Full Changelog: 5.26.0...5.27.0