Skip to content

Releases: parkghost/pvvx-time-sync

Release list

0.2.0

Choose a tag to compare

@github-actions github-actions released this 02 Oct 04:46

What's new

Next sync sensor

A new diagnostic sensor, Next sync, shows when the next automatic sync runs:

  • On schedule: one Auto sync interval after the last successful sync.
  • After a failed sync: the time of the next retry (15 min, 30 min, 1 h, …).
  • Unknown while Auto sync is off, or after auto sync stopped because the device does not run pvvx firmware.

It updates as soon as you press Sync time, change the interval or toggle Auto sync.

Sync on daylight saving time and time zone changes

pvvx firmware has no time zone or DST rules (pvvx/ATC_MiThermometer#261). It keeps the local time it was last given, so after a DST transition the display stayed an hour off until the next scheduled sync, up to a week with the default interval for hardware-clock models.

The integration now remembers the UTC offset it wrote and syncs as soon as Home Assistant's offset differs:

  • DST transition: syncs at the transition, spread over up to 90 s across devices.
  • Home Assistant down across a transition: syncs shortly after startup.
  • Time zone changed in the Home Assistant settings: syncs right away.
  • Time zones without DST: no extra syncs.

Drift before sync subtracts the offset change, so it still reports the clock's own drift instead of about ±3600 s.

Upgrade notes

  • No configuration needed. The offset is recorded at each device's first sync after upgrading. Until then, DST handling is inactive for that device.

Full changelog: 0.1.0...0.2.0

0.1.0

Choose a tag to compare

@github-actions github-actions released this 30 Sep 12:28

0.1.0 (2026-09-30)

Feat

  • pvvx BLE time sync integration