fix: Fixed charge limit sensor to behave like the app around accepted…

… values
BottlecapDave · Feb 7, 2024 · c42a619 · c42a619
1 parent 419653b
commit c42a619
Showing 1 changed file with 5 additions and 1 deletion.
diff --git a/custom_components/octopus_energy/intelligent/charge_limit.py b/custom_components/octopus_energy/intelligent/charge_limit.py
@@ -37,6 +37,10 @@ def __init__(self, hass: HomeAssistant, coordinator, client: OctopusEnergyApiCli
     self._attributes = {}
     self.entity_id = generate_entity_id("number.{}", self.unique_id, hass=hass)
 
+    self._attr_native_min_value = 10
+    self._attr_native_max_value = 100
+    self._attr_native_step = 5
+
   @property
   def unique_id(self):
     """The id of the sensor."""
@@ -105,7 +109,7 @@ async def async_added_to_hass(self) -> None:
         (last_number_data := await self.async_get_last_number_data())
       ):
 
-      self._attributes = dict_to_typed_dict(last_state.attributes)
+      self._attributes = dict_to_typed_dict(last_state.attributes, ["min", "max", "step"])
       if last_state.state not in (STATE_UNAVAILABLE, STATE_UNKNOWN):
         self._state = last_number_data.native_value