commit a8f57db392763ca79fc6aa286129c6b2f66ceb3f parent 4b3fdf4bd4edfbf9df4837689eb2bfb95011745c Author: Bennet Brünings <bennet@bbruenings.com> Date: Thu, 19 Mar 2026 15:26:57 +0100 Use dynamic model name from cloud API instead of hardcoded HUB-150 The transformer name (e.g. 'SMART HUB 150' or 'SMART HUB 75') is already returned by the cloud API and stored in the config entry. Use it as the device model so both hub variants are correctly identified. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
diff --git a/custom_components/inlite/light.py b/custom_components/inlite/light.py index 76927abdfafa0ddc07ac56388af0a75397326cb2..6a47f609262b058b3b35084aaeaaab8a46335295 100644 --- a/custom_components/inlite/light.py +++ b/custom_components/inlite/light.py @@ -84,7 +84,7 @@ self._attr_device_info = DeviceInfo( identifiers={(DOMAIN, f"{garden_id}_{device_id}")}, name=tx_name, manufacturer="in-lite", - model="SMART HUB-150", + model=tx_name, sw_version=str(firmware), suggested_area=garden_name, )