Skip to content

0.1.16

Choose a tag to compare

View all tags
@benjycov benjycov released this 06 Feb 20:32
v0.1.16
0728dbc
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Lots of '429'/too many requests improvements

  1. Much better protection against cloud rate-limits.
  • The integration now carefully spaces out API calls and avoids overlapping reads and writes.
  • This greatly reduces “Too Many Requests (429)” errors.
  1. Smarter handling of changes
  • When you adjust pH, ORP, or schedules, changes are queued and applied safely.
  • Multiple quick changes are merged together instead of hammering the cloud API.
  1. No more read/write collisions
  • The integration will not poll the cloud while a setting change is in progress.
  • A short “settling period” after changes prevents unnecessary follow-up requests.
  1. Improved schedule reliability
  • Schedule updates are applied more reliably, even when making multiple edits.
  • Optional delayed confirmation refresh avoids unnecessary cloud traffic.
  1. New manual refresh feature - you can force a data refresh (though all safety rails still apply)
  2. Optional entities now appear reliably
  • pH and ORP setpoint controls will appear automatically once the device reports support.
  • Temporary startup issues (for example during rate-limits) no longer cause them to disappear permanently.
  1. More robust startup behavior
  • If the cloud is temporarily unavailable during startup, the integration now recovers cleanly once connectivity returns.
  1. Added a 'AWS Status' to the diagnostics. This sensor indicates whether your Exo unit itself is connected to AWS.
Assets 2
Loading