Skip to content

TasmoFleet 0.32.0 "Fastnet"

Choose a tag to compare

@github-actions github-actions released this 06 Nov 01:43
· 207 commits to main since this release
v0.32.0
2eed97a

Added

  • Device data stays current on its own: once a day per online device (spread over the fleet, one device at a time) and after a restart (once, 20 seconds after it settled; a device in a boot loop about once an hour), TasmoFleet reads the Settings values, the values the policy rules check and the GPIO template reading, so the Settings tab and Policy → GPIO templates show them without a click, and it probes the identity again over HTTP after a restart and every 24 hours (without renaming anything: names and topics change only on Refresh identity). Offline and busy devices are skipped, the policy values are not read while the live check is paused, and Status 0 is never sent (#600)

Fixed

  • Import from TasmoAdmin: a row with a problem that does not reject it (an encrypted password without the key file, a bad port) counts once against the 1000-row limit instead of once per problem, so a devices.csv with 501 to 1000 encrypted rows is no longer refused with a false "more than 1000 rows" (#500)
  • A device whose HTTP API is off (SetOption128 0) and which MQTT cannot serve is now refused up front, with the same reason and fix, by everything that used to try and fail: its relay switches and Restart (disabled on the device page with the reason), Refresh identity, direct posts to Console and Settings, retrying a backup, command or Make compliant transaction, Make compliant on cached values, applying a GPIO template, the Drift tab's live read, and the silent policy read every ten minutes (skipped without an error). One wording everywhere ("HTTP API off (SetOption128 0)" and the fix, also in Copy from a device) replaces "likely refuses HTTP API commands", and the fix no longer reads as if it meant MQTT. The connection card's "Since" shows when the API was first found off, not the latest refusal. Bulk Send command applies the write rule only to commands that write (#645)
  • Stopping TasmoFleet (docker stop, a restart) with a browser tab open takes a moment instead of 10 s and exits with status 0 instead of 1, so restart policies and monitoring no longer read it as a crash; and a start that fails halfway now waits for the background tasks before it closes the database (#497)
  • Policy: "Show all" under the devices of an unsaved rule (from a template, a command or Duplicate) works without JavaScript and keeps what you typed, instead of ending on a white page reading "unknown form field"; a mistyped address of New rule or Duplicate shows the error page too (#512)