Repository navigation
TasmoFleet 0.41.0 "Longstone"
·
91 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
Upgrade notes
- Migrations 0051 to 0053: 0051 moves the stored broker ACL confirmation to its new name
MQTT_ACL_WARNING_HIDDEN(a hidden warning stays hidden for the same broker), 0052 adds the columnsheap_kbanduptime_sectobackup_attempts(the device's free heap and uptime at a failed backup), 0053 adds where each device's MQTT password came from and when, and when the device last accepted it, todevices. Nothing to do (#962, #887, #609). - The first start of this version reads each device's MqttPassword from its newest decoded backup and audits every change as
device.mqtt_password(sourcebackup). A password typed before the upgrade counts as typed at the device's last change, so only a backup taken after that replaces it. To keep every password exactly as it is, start this version withTASMOFLEET_MQTT_PASSWORD_FROM_BACKUPS=false(imported into the setting once, then edited on System, MQTT). Devices whose MQTT password was "Not set" then back up and restore over MQTT, so their settings dumps (with their Wi-Fi, web and MQTT passwords, only obfuscated) cross the broker: check the broker ACL (System, MQTT) before the upgrade, or start with the switch off as above (#609)
Added
- Backups and restores over MQTT need each device's MqttPassword, and TasmoFleet now takes it from the device's newest decoded backup: after every backup, and once over the existing backups at start. A password equal to TasmoFleet's broker password becomes "Same as the broker's", an empty one the new choice "No password" (a device without an MqttPassword could not be backed up over MQTT before), anything else is stored sealed like a typed one. The newer fact wins: a password typed after the backup stays until the next backup. Only the source and the backup's date are shown in the audit, never the value. On by default; System, MQTT, "Take device passwords from backups" turns it off (#609)
- The device page's "Device MQTT password" row now says one word (Works, Refused, Not set, Not known, Not tested, Not needed), where the password came from and when, and what it enables (back up, restore, read files and upload firmware over MQTT), with Test and Change…. A password typed or set in bulk shows "Not tested" until the device accepts it: Test asks it, and so does the next finished backup over MQTT. System, MQTT has a new card with the counts, the devices without a password (with the reason and Set…) and "Use the broker password for these…", which sets several devices in one step and tests each one in the background; the password itself is never shown, logged or audited (#609, #457)
- After a change on a device's Settings tab and after Make compliant, TasmoFleet reads every written value back from the device and shows it: "Verified", or "Differs" with the value the device reports. A Make compliant job whose device keeps another value now succeeds and marks that value as policy drift instead of failing; a value it cannot read back still fails the job. Secrets (the MQTT password and user) are never read back: the tab and the Make compliant card say they were set, and they never fail the job when the device answered the write or a value written with them is read back; a secret sent alone to a device that does not answer fails the job. A setting that restarts the device is read back once it answers again, and only from the device TasmoFleet confirms is the one it wrote to. Timezone values are now compared in the form the device reports them (+01:00 for 1), so a policy rule for Timezone no longer shows a device as deviating that has the value (#947)
Changed
- A firmware update now sends its commands (OtaUrl and Upgrade) over MQTT first whenever the device is online on TasmoFleet's broker and its topic is its own, also while its HTTP works; the device still downloads the firmware from TasmoFleet over HTTP, and the firmware check runs right before each command as before. A push upload and the steps through safeboot stay on HTTP while HTTP works, and Upgrade or OtaUrl typed in the console keep their way. The first line of an update's log now says which path it took ("commands over MQTT, firmware download over HTTP"), and the backup before an update over MQTT may go over HTTP, as every other backup of a device without a usable MQTT password does. A job that keeps MQTT reads nothing on a topic another device was found answering on, so it stores no identity from it; the Settings tab of such a device shows no values read there while its HTTP fails (#608)
- A device whose group topic has not been read no longer keeps the changes, backups and restores of every other device on HTTP when it is provably not on TasmoFleet's broker (its MQTT settings name another broker or none, and nothing from it was ever heard on TasmoFleet's): the others go over MQTT first again. A device that may be on the broker still holds the others back, since its group topic could be any device's topic; the "How TasmoFleet reaches this device" card now names the devices that hold a device back, so you know whose identity to refresh. That exemption holds only while TasmoFleet's MQTT connection has heard devices at all (not a broker that lets TasmoFleet send but not read) and no device outside the inventory is online on the broker (it may be one of yours that came back under a new topic): otherwise the device holds the other devices' changes, backups and updates back to HTTP until its group topic is read (#812, #972)
- A restore over MQTT asks the device on its topic whether it has a file system, as the backup does, before it asks anything over HTTP: a device without one (or with firmware too old for files) is asked nothing over HTTP, and the confirmation page and the job say "the device has no flash file system" instead of "files need HTTP"; the files themselves still go over HTTP (#875)
- A backup that fails because the device sent an empty data chunk now says that the device ran short of contiguous memory and that a restart usually helps, instead of "did not hand over its configuration"; a failed backup that the device answered records its free heap and uptime, read with one Status 11 right after the failure, and the Backups page shows them on the failed row (#887)
- The files of a backup over MQTT now come over MQTT too when the device's firmware was built with
USE_UFILESYS_MQTT(Tasmota arendst/Tasmota#25278, not in the stock builds) and has no SD card: the listing and every file on the device's topic, with no request to its address, so remote devices reached only over MQTT keep their files. A stock firmware still sends its files over HTTP only; when that address cannot be reached, the backup now says why ("they need HTTP (this firmware sends no files over MQTT), and HTTP could not be used: …") instead of only "the device took too long to answer", although a device whose HTTP has never answered still waits for that one timeout per backup. The Files fold says which way the files were read. File contents and the MQTT password then cross the broker like the settings dump, and the broker ACL notices and the device's Back up line say so: restrict the device topics with a broker ACL (#924, thanks @Noschvie) - Devices, Backups follows a running backup without a reload: the backups per device, the last run, the Storage card and the status bar change as backups are stored. Ticked rows stay, and the update waits while a row menu, the Storage fold or a dialog is open (#950)
- The red broker ACL notice can be hidden with one option, "Hide the broker ACL warning" on System, MQTT (the old "This broker has an ACL" checkbox, reworded: TasmoFleet cannot see an ACL, and the option no longer says the broker has one). Its hint says what it means: every client of the broker can read device backups, passwords included, and the warning comes back when you change the broker. The notice's second line now reads "Hide it under System → MQTT", and for admins "Hide it" is a link that scrolls to the option and highlights it (#962)
Fixed
- MQTT: the identity checks that vouch for reads over MQTT (the background data refresh and broker read, the network facts read, the Settings tab and the policy poller) now hear every reply on the device's topic within the 1.5 s identity window instead of the first one, so a second device answering on the same topic (with an error too, as a board in minimal firmware does, or without a MAC) refuses the read, nothing of it is cached, the device is marked as sharing its topic and the device page says why its data was not refreshed; when that check learns nothing, the check goes to the device's address alone (#804, #878)
- MQTT: a light change (Dimmer, Color, Channel, HSBColor, White, CT) sent over MQTT is no longer reported done on the strength of another light change on the same device; TasmoFleet reads the light's state with Status 11 right after it and reports that. Channel2, Color2, HSBColor2 and Dimmer2/3 over MQTT no longer time out and send the device's next commands over HTTP for ten minutes. A Backlog with a light change gets a Status 11 as its last part, or goes over HTTP once when there is no room for it (#813)
- MQTT: a discovery config that announces another MAC on a stored device's topic now makes the broker reader check that topic (the router's own check, which hears every reply, at most once per device per 10 minutes and two per 30 s pass), so a second board there marks the device and keeps its writes and transfers off the topic, while a forged config that only the device answers marks nothing (#876)
- MQTT: a check that hears every device on a topic (the end of a "topic taken" mark, the restore's check before its upload) now fails when the MQTT channel closes inside its reply window, instead of taking the replies heard so far as all of them (#877)
- The connection card on the device page no longer repeats the long "another device answers on the device's MQTT topic" sentence in every action row while the topic is marked as taken: the MQTT row says it once, and the rows for reading, changing, Back up, Restore and Update say only "the MQTT topic is taken (see MQTT above)" next to their own path or cause (#879)
- On Devices, Backups the save bar shows only while the schedule has unsaved changes, so it no longer sits over the last rows of the device table when nothing was edited. A refused save keeps it on screen (#949)
- The delete device page reads "The backup is removed." for a single backup instead of "All 1 backup are removed." (#951)
- The lookup field on Add devices is labelled "Not listed? Look it up" (it had grown to ten words); the placeholder still names what it takes: an IP address, a MAC or a topic (#961)
Breaking
- The setting behind "Hide the broker ACL warning" (System, MQTT) is renamed from
MQTT_ACL_CONFIRMEDtoMQTT_ACL_WARNING_HIDDEN, without an alias. A value stored in the database moves to the new name with the upgrade (a hidden warning stays hidden for the same broker); the variableTASMOFLEET_MQTT_ACL_CONFIRMEDis ignored, with a warning at start. Delete it (#962)
Security
- One rule decides what is secret, for the console, its replies and the audit as for the backup comparison, the drift view and the restore preview. Wi-Fi names (SSId, BSSId, RgxSSId) and the MQTT user are no longer shown in a backup comparison or the drift view; MqttUser, BSSId, WCAuth, TmChatId, IfxOrg, KeeloqSet, DzKeyIdx, RfKey and ZbNameKey now have their replies masked like the passwords, over HTTP as over MQTT, and are refused as bulk commands. TLS fingerprints are shown and compared: a fingerprint is no secret. The Settings tab and the restore's MQTT check read the MQTT user from Status 6; a device with MQTT switched off does not report it there, so the Settings tab shows it as not reported (#809)