electricity pricing: update prices after config change

[LKuemmel]

Ticket #66004415
Preise wurden nur beim Wechsel des Anbieters, aber nicht beim Ändern von Einstellungen aktualisiert.

[Copilot]

Pull request overview

Updates the electricity pricing module reset logic so price data is cleared and re-fetched when the flexible tariff or grid fee provider configuration changes, rather than only when the provider name changes.

Changes:

• Changed flexible tariff module “config changed” detection from config.name comparison to comparing the full config object.
• Changed grid fee module “config changed” detection from config.name comparison to comparing the full config object.

Comments suppressed due to low confidence (1)

packages/control/optional.py:61

• Same issue as above: self._grid_fee_module.config != value.config will almost always be true for configs that don’t define __eq__, causing unnecessary resets/price clearing whenever the provider config topic is reprocessed. Use a stable config fingerprint or explicit field comparison (excluding volatile runtime fields) to decide when a reset is actually needed.

    def grid_fee_module(self, value: TypingOptional[ConfigurableGridFee]):
        if (value is None or
                (self._grid_fee_module and value and
                 self._grid_fee_module.config != value.config)):
            self.data.electricity_pricing.grid_fee.get = PricingGet()
            self._reset_state(self.data.electricity_pricing.grid_fee)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[LKuemmel]

Umstellung auf dataclasses für die config-Klassen und dann compare=False-Attribut benutzen.

[Copilot]

Pull request overview

Copilot reviewed 12 out of 12 changed files in this pull request and generated 2 comments.

Comments suppressed due to low confidence (1)

packages/modules/electricity_pricing/flexible_tariffs/voltego/config.py:9

• expires_in and created_at are typed as Optional[str], but the implementation treats them as numeric seconds/timestamps (e.g. created_at + expires_in in voltego/tariff.py). Please change these annotations to numeric types (e.g. Optional[int]/Optional[float]) to match actual usage and avoid accidental string values breaking token validation.

class VoltegoToken:
    access_token: Optional[str] = field(default=None, compare=False, repr=False)  # don't show in UI
    expires_in: Optional[str] = field(default=None, compare=False)  # don't show in UI
    created_at: Optional[str] = field(default=None, compare=False)  # don't show in UI