Skip to content

v2.7.1 - MQTT stale-client sync fix

Choose a tag to compare

View all tags
@eyalgal eyalgal released this 19 Jun 22:55
v2.7.1
31d90b8

This release fixes issue #112, an MQTT synchronization race that could cause a running timer to be force-ended when another client wakes from background with stale cached timer data.

Fixed

  • Fixes #112: prevent stale wake-up clients from overwriting newer MQTT timer state.
  • When MQTT timers are loaded from cache/shadow (not from the live sensor_entity snapshot), they are now treated as non-authoritative.
  • Automatic expiry mutations (expire_action: keep / remove) are blocked until a fresh MQTT sensor snapshot is available.
  • Result: a timer started on device B is no longer auto-ended by device A reopening with stale cache.

Notes

  • This is published as a pre-release to validate the fix across real multi-device MQTT setups before marking it stable.
  • No configuration changes are required.

Full Changelog: v2.7.0...v2.7.1

Assets 3
Loading