CLI
The System Bridge CLI provides commands to interact with the System Bridge backend. Most commands live under the system-bridge client subcommand, while backend, tui and version are top-level commands.
The token is essential to connect to the API/WebSocket. To get it, run the following command:
system-bridge client tokenAlternatively, you can find your token in the application startup logs when running the backend. The logs will show “Your API token is” followed by your token value.
Notification
Section titled “Notification”To send a notification, use the following command:
system-bridge client notification --title "Title" --message "Message" --icon "icon-name"Available flags:
--title: The title of the notification (default: “System Bridge”)--message: The message of the notification (default: “Hello, world!”)--icon: The icon of the notification (default: “system-bridge”)--sound: Path to a sound file to play with the notification (Linux only)--action-url: URL to open when the notification is clicked (Linux only)--action-path: File/folder path to open when the notification is clicked (Linux only)
Discovery
Section titled “Discovery”List Services
Section titled “List Services”To list discovered services on the network, run:
system-bridge client discovery listThis will scan for available System Bridge instances and display them with their hostname, IP, port, and type.
List Modules
Section titled “List Modules”To list all available data modules, run:
system-bridge client data listBy default, this outputs as a simple list. You can also use:
system-bridge client data list --jsonTo output as a JSON array.
Available flags:
--json: Output as a JSON array--table: Output as a table (default)
Run Modules
Section titled “Run Modules”To run a specific data module and get its data as JSON, use:
system-bridge client data run --module cpuFor example, to get CPU data:
system-bridge client data run --module cpuTo run all modules and get a JSON object with all data:
system-bridge client data run --allTo pretty-print the JSON output:
system-bridge client data run --module cpu --prettyAvailable flags:
--moduleor-m: Module name (e.g., cpu, memory)--all: Run all modules--pretty: Pretty-print JSON output
Backend
Section titled “Backend”To run the backend server, use:
system-bridge backendAdd --open-web-client to open the web client once the backend has started:
system-bridge backend --open-web-clientSee Running for autostart and service setup.
Version
Section titled “Version”To get the version of System Bridge, run:
system-bridge versionNext steps
Section titled “Next steps”- Prefer a graphical interface? Use the web client.
- Prefer an interactive menu? Use the TUI.
- Connect to the API and WebSocket to read data and control your system.
- Integrate with Home Assistant.
- Not started the backend yet? See Running.