Releases: randrcomputers/ha-maytronics-dolphin
Release list
v1.17.1
v1.17.0
v1.16.0
Attempting to make bluetooth connection more reliable with all the Home assistant changes to bluetooth recently
v1.15.2
Fixes applied (v1.15.2)
contextlib.suppress instead of asyncio.suppress
Always send SHUTDOWN if a timed run was cancelled or failed after STARTUP
One timed run at a time; don’t stack overlapping slots in the same minute
Card Run 1h/2h still waits for completion; schedule fires in background
v1.15.1
v1.15.0
v1.14.0
Maytronics Dolphin (BLE) — v1.14.0
Highlights
Built-in pool cleaner schedule — no YAML helpers or automations required when used with the Pool Cleaner Card.
New
Daily schedule stored in the integration (.storage), survives restarts
Run 1 — start time + 1 h or 2 h
Run 2 (optional) — second daily start time + duration, with its own on/off
Shared weekdays (Mon–Sun) for both runs
Cleaner schedule sensor — state + attributes for the card
Services: maytronics_dolphin.set_schedule, maytronics_dolphin.run_timed
Schedule checks every minute — changing start time does not require reloading automations
Pool Cleaner Card
Card Schedule backend → Auto (default when a Dolphin device is selected) uses this integration
Requires an updated Pool Cleaner Card with integration schedule support
Migration
If you use pool-cleaner-schedule.yaml, disable those automations or set the card to Schedule backend → helpers — otherwise both schedulers can run
New setups: integration schedule only (no YAML package)
Fixes / docs
Responsive mode description corrected — faster polling only; does not keep BLE connected (use Persistent BLE session for that)
Requirements
Home Assistant 2024.1+
Bluetooth adapter or proxy near the pool
v1.10.2
v1.10.1
All 4 PS_State read strategies — transient BLE errors try the next path instead of giving up
Poll yields to power commands — if you tap power during a poll, the poll stops early and releases BLE
Power confirm retries — after on/off, up to 6 polls over ~7s until PS_State matches
No more fake at_work — working status shows unknown when we don't actually know (card shows "Powered on", not "Cleaning")
Working status stabilizer wired up — after 4 failed reads or hold timeout, status clears instead of sticking forever
CRC reject — corrupted ConfigParamsRead frames are dropped, not trusted
Responsive mode decoupled from persistent session — faster polling without holding the BLE link open by default
More frequent full status polls when the robot is running (every 2nd tick vs every 3rd)
v1.10.0
Always resolve working after merge (uses cached internal + last fffc hex when a live read fails).
Light polls re-infer working from cache (same as surface).
Stabilizer holds last good value while PS is on — no more dropping to unknown after N misses.
Sensor fallback: if PS is on but working is briefly empty → show at_work, not unknown.