You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A bug-fix release on top of v4.4.0. No feature or breaking changes.
Fixes
Photo-proof upload no longer fails on long sessions. The child card uploaded evidence photos with a manually-cached access token that expires after ~30 minutes, so an aged browser session got a 401 that the card showed as the misleading "Upload failed. Check your connection and try again." It now refreshes the token when expired before uploading, and on a 401 forces a refresh and retries once. (fix: refresh stale token before photo upload; guard panel define #636)
No more taskmate-panel "name already used" console error after an upgrade. Right after a version bump the browser can briefly hold both the old (?v=previous) and new (?v=current) panel modules; the unguarded customElements.define() threw an uncaught error on the second load. The define is now guarded so it is a no-op if the element is already registered. (fix: refresh stale token before photo upload; guard panel define #636)
Configuration-entity defaults now match the applied bonus. The weekend_multiplier and perfect_week_bonus number entities defaulted to 1.0 and 0, but the bonus logic falls back to 2.0 and 50 when those settings are unset — so a fresh install displayed values that did not match what was actually applied. The entity defaults are aligned (2.0 / 50). (fix(number): align config-entity defaults with runtime (weekend 2.0, perfect-week 50) #635)
Upgrade
HACS → TaskMate → Redownload → pick v4.4.1, then restart Home Assistant and hard-refresh the browser (the cards are cache-busted by the manifest ?v=).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
🚀 New Release: v4.4.1
TaskMate v4.4.1
A bug-fix release on top of v4.4.0. No feature or breaking changes.
Fixes
401that the card showed as the misleading "Upload failed. Check your connection and try again." It now refreshes the token when expired before uploading, and on a401forces a refresh and retries once. (fix: refresh stale token before photo upload; guard panel define #636)taskmate-panel"name already used" console error after an upgrade. Right after a version bump the browser can briefly hold both the old (?v=previous) and new (?v=current) panel modules; the unguardedcustomElements.define()threw an uncaught error on the second load. The define is now guarded so it is a no-op if the element is already registered. (fix: refresh stale token before photo upload; guard panel define #636)weekend_multiplierandperfect_week_bonusnumber entities defaulted to1.0and0, but the bonus logic falls back to2.0and50when those settings are unset — so a fresh install displayed values that did not match what was actually applied. The entity defaults are aligned (2.0/50). (fix(number): align config-entity defaults with runtime (weekend 2.0, perfect-week 50) #635)Upgrade
HACS → TaskMate → Redownload → pick
v4.4.1, then restart Home Assistant and hard-refresh the browser (the cards are cache-busted by the manifest?v=).Full changelog: v4.4.0...v4.4.1
Upgrading
Update via HACS or by downloading the latest release and copying to
/config/custom_components/taskmate/.After updating, restart Home Assistant. Lovelace resources will update automatically on restart.
💬 Questions or issues with this release? Reply below or open an issue.
Beta Was this translation helpful? Give feedback.
All reactions