October 24Oct 24 TasmoFleetCurrent release: 0.36.0 "Fisgard" (2026-11-13) · Release notes · ChangelogDescriptionTasmoFleet is a self-hosted web app for managing a fleet of Tasmota devices, an alternative to TasmoAdmin (it can import your TasmoAdmin device list).Configuration backups: scheduled and on demand for the whole fleet, diff between backups, restore with one click, also onto a replacement device. An ESP32's flash files (Berry scripts, tlskey) are backed up and restored too.Settings policy: define the settings every device should have, see compliance per device, and fix deviations in one go ("Make compliant").Safe bulk firmware updates: server-side jobs with a chip-family safety check before every update; 1 MB ESP8266 devices go through tasmota-minimal automatically.Live status over MQTT, with HTTP polling as fallback; devices HTTP cannot reach are managed over MQTT.Notifications by webhook (Home Assistant) or e-mail, and stability per device: restart reasons, boot loops and weak Wi-Fi.Bulk commands and a device console.Sign-in via OIDC/SSO or local accounts.ProjectProject / docs: https://github.com/hellwand/tasmofleetWebsite: https://hellwand.github.io/tasmofleet/Static demo (no install): https://hellwand.github.io/tasmofleet/demo/Image: nofuturekid/tasmofleet (Docker Hub), also ghcr.io/hellwand/tasmofleetTemplate: https://github.com/nofuturekid/unraid-templatesSetup notesWeb UI: container port 8080, host port 8443 by default (self-signed HTTPS; plain HTTP behind a reverse proxy, see the README). Upgrading from 0.16 or older: see the upgrade notes in the release.Firmware port (default host port 8081): your Tasmota devices download firmware from it during updates, so it must be reachable from their network/VLAN.Appdata (/mnt/user/appdata/tasmofleet) must be owned by 65532:65532.On first start the log prints a one-time setup link for the first admin account.StatusPre-1.0, single maintainer. Breaking changes are to be expected before 1.0 Read the release notes before updating.Built with Claude Code (AI-assisted) and reviewed and tested by me on my own fleet.Please report general bugs and feature requests as GitHub issues; this thread is for Unraid-specific questions.Screenshots Edited November 13Nov 13 by NoFutureKid Release 0.35.0
October 30Oct 30 Author TasmoFleet 0.21.0 "Tower of Hercules"Upgrade notesNothing to change in the template, no database migration.Older patch images of 0.11 to 0.19 are removed from Docker Hub and ghcr.io; use :latest or the newest patch of a minor.What's newRestore over MQTT for devices TasmoFleet cannot reach over HTTP: safety backup, identity check, upload and verification over the same pathRelease names: every minor release is now named after a lighthouseRelease notes · Changelog
November 1Nov 1 Author TasmoFleet 0.26.0 "Skerryvore"Upgrade notesNo database migration, nothing to change in the template. Update via the container's Update button (:latest).Restore over HTTP now works on official Tasmota builds. Up to 0.25.0 it failed with "unknown command" (WebGetConfig) and left the device unchanged; only restore over MQTT worked. It no longer needs the firmware port or FIRMWARE_BASE_URL.What's newFiles in backups and restore: an ESP32's flash files (Berry scripts, folders, tlskey) are backed up with each run, shown per backup on the Backups tab, and written back by Restore and Replace device (#324)First-run setup over plain HTTP fixed: the account form no longer fails with 403 in Chrome on http://<ip>:8080 (#429)"No backup" filter on the device list (#381, thanks Noschvie)Community Apps screenshots fixed (#423)Release notes · CHANGELOG
November 2Nov 2 Author TasmoFleet 0.27.0 "Cordouan"Upgrade notesNo template change, no database migration.Navigation changed: Devices is now List · Policy · Add (one Add page with four boxes). Database snapshots moved to System → Snapshots. The old /discovery and /import/tasmoadmin pages are gone without redirects, so update your bookmarks.New GPIO templates tab changes devices: only admins can apply, every device is backed up first, and it restarts.What's newGPIO templates (Policy page): compare devices by template and chip, preview the exact Template command, apply to several devices one at a time, stop after the first failureCleaner navigation and a System → Snapshots page (#410, #440, thanks Noschvie)Commit of CI builds shown with 7 characters (#436, thanks Noschvie)Release notes · Changelog
November 5Nov 5 Author TasmoFleet 0.28.0 "Cape Byron"Upgrade notesThe power restore after updates is gone. TasmoFleet no longer switches relays back on after a firmware update. To keep the relay state across updates and power cuts, set SetOption0 1, PowerOnState 3 and SaveData 1 on those devices. A Policy rule for each plus "Make compliant" does it for the whole fleet. The update dialog has no "Power after update" choice any more.ntfy or Gotify webhooks: open Settings, Notifications and set the webhook Format to ntfy (or Gotify). Until then the webhook keeps sending JSON, which ntfy shows as raw text.Database migration 0042 runs on start (data only); a .pre-N copy of the database is written first. The setting OTA_POWER_MAX_AGE is gone; the template needs no change.What's newntfy and Gotify as webhook formats, with title, priority and a link to TasmoFleetDashboard: "No backup" tile for devices without a backupDevice page: the MQTT broker is shown only when the device uses another broker than TasmoFleetSafeboot and minimal firmware are detected live and no longer asked for settings; the device shows as "Not judged"Fixes: a device cannot be deleted while a job runs on it; Drift no longer reports sensor readings as differencesRelease notes · Announcements · Changelog
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.