EEBus: accept an inactive §14a limit without a value

[andig]

Addresses the dimmed: not available half of #32125.

A Wolf Link heat pump announces limitationOfPowerConsumption with scenarioSupport [1,2,3,4] and answers the limit read with

{"loadControlLimitData":[[{"limitId":1},{"isLimitChangeable":true},{"isLimitActive":false}]]}

No limit is in effect, so no value is stated. eebus-go discarded the whole structure on the missing value and returned ErrDataNotAvailable, which Dimmed() maps to api.ErrNotAvailable — so evcc could not tell "no §14a limit active" from "no data at all", and the loadpoint aborted every update cycle.

Fixed upstream in enbility/eebus-go#255: an inactive limit may omit its value, an active one may not. Same change in eg/lpc, eg/lpp, cs/lpc and cs/lpp. Until that is merged the module points at the branch via replace.

This is the root cause behind #32126, which suppressed the error in Loadpoint.Update() instead.

---

🤖 Generated with Claude Code

[sourcery-ai]

Hey - I've left some high level feedback:

• The temporary replace github.com/enbility/eebus-go => github.com/andig/eebus-go ... in go.mod would benefit from an inline TODO or comment referencing the upstream PR/issue to make it clear when and under what conditions this should be reverted.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The temporary `replace github.com/enbility/eebus-go => github.com/andig/eebus-go ...` in go.mod would benefit from an inline TODO or comment referencing the upstream PR/issue to make it clear when and under what conditions this should be reverted.

---

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.}