Add a custom management panel for Irrigation Unlimited

[uspass]

Add a custom management panel for Irrigation Unlimited

Summary

This PR adds a full custom sidebar panel ("Irrigation") that lets users manage all Irrigation Unlimited configuration — controllers, zones, sequences, schedules, adjustments, all-zones defaults, and global settings — directly from the Home Assistant UI, with no YAML editing required.

The upstream config-entry setup wizard / options flow / subentry flow (~760 lines in config_flow.py) is replaced by an instant, zero-step config entry. All CRUD that wizard used to handle is now done through the new panel, backed by a persistent JSON store and a dedicated WebSocket API.

The panel is fully multilingual (English / French / Italian / Romanian / Spanish, easy to extend) and shows a live "running" indicator on zones currently irrigating.

---

What's new

Backend

• storage.py (new) — IUStore: persistent, panel-managed source of truth for all controller configuration (Store(STORAGE_VERSION, STORAGE_KEY)). Provides:

  • Controller / Zone / Sequence / Schedule / Adjustment / Sequence-Zone / Sequence-Schedule CRUD
  • All-Zones-Config (5.2) and global config (5: granularity, refresh_interval, rename_entities, history, clock) CRUD
  • to_iu_config_multi() / generate_yaml() — converts panel storage into the full multi-controller IU config (and equivalent YAML), applying:
    • IU-schema default dropping (omits untouched fields, e.g. enabled: true, allow_manual: false, future_span: 3, anchor: "start", preamble/postamble: 00:00:00, ...)
    • HH:MM / HH:MM:SS time normalization (accepts 8:2 → stores/exports 08:02:00)
    • future_span as int (avoids 3.0 in YAML)
    • entity_id always wrapped as a list (required by IU's iteration)
    • weekday / month / zone_id rendered as YAML flow-style lists ([mon, wed, sat])
  • One-time migration from the old flat {"zones": [...], "sequences": [...]} format

• websocket_api.py (new) — WebSocket commands consumed by the panel for every CRUD operation (irrigation_unlimited/config, save_controller, save_zone, save_schedule, save_adjustment, save_sequence, save_sequence_zone, save_sequence_schedule, save_all_zones_config, save_global_config, generate_yaml, and matching delete_*). Every save/delete schedules a debounced (4s) reload of the config entry so the IU coordinator picks up changes without a HA restart.

  • One-time auto-import: if a panel controller has no zones/sequences yet, and a YAML-configured controller with the same name exists, its zones/sequences are imported automatically.

• config_flow.py (rewritten, 762 → ~30 lines) — single-step, no-form setup. async_set_unique_id ensures only one config entry can exist (the panel manages multiple physical controllers internally).

• __init__.py (rewritten):

  • Registers a static file route (/irrigation_unlimited_static → bundled frontend/) and a custom sidebar panel ("Irrigation", mdi:water).
  • Loads/shares IUStore and registers the WebSocket commands.
  • One-shot migration of any pre-existing entry.data / HA-native subentries into IUStore.
  • async_unload_entry now preserves store / yaml_config / panel & static-path / WS registration across reloads (previously hass.data[DOMAIN] was fully wiped on every reload, forcing re-registration on every panel save).
  • New async_remove_entry for full cleanup (removes the sidebar panel) when the integration is deleted.

• manifest.json — added "integration_type": "hub".

Frontend (new frontend/ directory)

A vanilla-JS Web Component (ES modules, no build step), split for maintainability:

frontend/
├── irrigation-unlimited-panel.js   – class skeleton, lifecycle, finders
├── render-mixin.js                 – panel HTML (cards, lists)
├── forms-mixin.js                  – modal forms
├── actions-mixin.js                – event handling, save/delete, validation, YAML export
└── lib/
    ├── constants.js, translations.js, helpers.js, form-fields.js, styles.js
    └── translations/en.json, es.json, fr.json, it.json, ro.json

Features:

• Full CRUD UI for controllers, zones, sequences, sequence-zones, schedules, sequence-schedules, adjustments, all-zones-config and global config
• Multilingual UI (English / French / Italian / Romanian / Spanish), auto-detected from hass.language; adding another language is just a new translations/<lang>.json.
• Live "running" indicator: a pulsing dot + highlighted row on any zone whose entity_id is currently on, updated on every hass update without a full re-render (no flicker).
• Inline field validation (time formats, numbers, dates) before save.
• Entity picker with autocomplete for switch / input_boolean / valve entities.
• "View YAML" button — renders the exact config IU would load, generated server-side by IUStore.generate_yaml().

---

Documentation

All new files and all modified sections (vs. upstream master) are documented with English docstrings/comments explaining what changed and why, to make future diffs against upstream easier.

---

Testing

• Manually tested: add/edit/delete controller, zone, sequence, sequence-zone, schedule, sequence-schedule, adjustment, all-zones-config, global config; YAML export; language switch ; live running indicator; HH:MM normalization edge cases.

Breaking changes

None for new installs (instant setup). Existing installs with controllers configured via the old options/subentry flow or via YAML are migrated automatically into the new panel storage on first load.

[rgc99]

Hi @uspass, thank you for all your good work on this. I am currently travelling through the Red Centre slowly heading north. I have not had the time to review the changes. It's a little difficult given the resources at my disposal. In fact, there is a bit of a backlog at the moment as didn't expect to receive this many PR's all at once. I am happy for all the support I have been receiving recently.

Thanks for everything.
Cheers Robert

[smoki3]

Hi uspass,

Found one minor bug:
When you open the UI on mobile the sidebar of HA is not visible anymore:

[uspass]

Hi @smoki3,

Thank you for reporting this!
I have fixed the bug.

For any future issues, please open them directly on my GitHub repository — it makes it much easier for me to track, reference and follow up on bug reports.

Thanks again!