Config UI: allow disabling devices

[andig]

Fix #21144

TODO

• fix init loop to not use nil devices @andig
• ui @naltatis
• do tariffs

[sourcery-ai]

Hey - I've left some high level feedback:

• In configureLoadpoints, when conf.Disable is true the instance remains nil but is still wrapped in NewConfigurableDevice; consider ensuring all consumers guard against a nil loadpoint.API or creating a small disabled stub implementation to avoid potential nil dereferences.
• In configurableInstance, the disabled path leaves instance as the zero value of T without returning an error; consider making the disabled behavior explicit (e.g., early return or a dedicated disabled state) so callers don’t have to implicitly rely on a zero-value instance.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- In `configureLoadpoints`, when `conf.Disable` is true the `instance` remains `nil` but is still wrapped in `NewConfigurableDevice`; consider ensuring all consumers guard against a nil `loadpoint.API` or creating a small disabled stub implementation to avoid potential nil dereferences.
- In `configurableInstance`, the disabled path leaves `instance` as the zero value of `T` without returning an error; consider making the disabled behavior explicit (e.g., early return or a dedicated disabled state) so callers don’t have to implicitly rely on a zero-value instance.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}