Static demo — actions are disabled. Source and install
TasmoFleet
maren
maren
Admin · Signed in by the proxy
Theme
What’s new Account
Settings
TasmoFleetv0.36.0
Account · maren What’s new
Theme

Settings

Applies to the whole TasmoFleet instance

Events

What is sent. Every channel gets the same events.

One message per job, not per device.
Send when
Counts the scheduled run only. A manual backup shows its error on screen. All devices that fail in one run make one message.
One message per run, listing the devices.
The nightly SQLite snapshot.

Browser

Desktop notifications while a TasmoFleet tab is open. Set per browser; nothing is stored on the server.

Needs JavaScript Browser notifications are set up on this page with scripts on.

Message

Read-only preview.

POST <webhook URL>
Content-Type: application/json

{
  "event": "update.finished",
  "result": "partial",
  "title": "Update job #41: 11 ok, 1 failed",
  "text": "12 devices to 16.1.0; 1 failed",
  "url": "",
  "time": "2026-10-31T03:12:07+01:00"
}
The whole webhook request: request line, headers and body (the secret header is not shown). The e-mail uses the title as subject and the text as body, with the link when TASMOFLEET_PUBLIC_URL is set.

Webhook

Home Assistant, ntfy, Gotify, anything that takes a POST.

POST a message when an event above happens.
Generic JSON and Home Assistant send the same body. For Home Assistant use a webhook trigger and the address http://<host>:8123/api/webhook/<id>; the automation reads trigger.json.event, .result, .title and .text. ntfy: enter the topic address (https://ntfy.sh/<topic>); the message is plain text with a title, a link (with TASMOFLEET_PUBLIC_URL) and a priority. Gotify: enter http://<host>/message and put the application token in the secret header X-Gotify-Key (not in the address).
What the receiver expects. Details under the info icon.
The address is stored as entered. Its path and query can be a secret (a Home Assistant webhook id): the audit log, the status line and the logs show only scheme, host and port.
http or https. Local addresses are fine.
Authentication
None: a Home Assistant webhook id is its own secret. Secret header: a fixed header such as a bearer token, sent with every message.
Sent only to the exact address it was entered for. Change the address (host, port, scheme, path or query) and it must be entered again; a save or a test without it sends none.
Write-only. Empty keeps it, for the same address only.
Not configured Turn it on and enter a URL.
Sends a test message with the values above. Saves nothing.

E-mail (SMTP)

SMTP with STARTTLS, TLS or none. No provider APIs in this version.

One message per event.
Empty if the server needs no login.
Sent only to the server, port, security and user it was entered for. Change one of them and it must be entered again; a save or a test without it sends none.
Write-only. Empty keeps it, for the same server only.
Several addresses separated by commas.
Not configured Turn it on and enter a host.
Sends one test e-mail. Saves nothing.
No unsaved changes Discard

Reset all settings?

Every setting on this page goes back to its default: the device networks, the MQTT broker, the sign-in method and everything else that was saved here. Settings set by the container configuration stay. Devices, backups and users are kept.