Repository navigation
T110 doesn't support "Hold Temperature" state when manually setting temperature lower than current temperature. #1608
Description
As described in the title, when I manually set any of my T110s to a lower temperature than it already is in the room, the device immediately becomes unavailable as Kasa puts it into a "'hold_on" state, which appears to be unsupported by the integration currently.
I believe it's the exact same issue experienced by a Reddit user who provided the following logs:
2025-10-18 09:53:00.013 WARNING (MainThread) [kasa.smart.modules.temperaturecontrol] Got unknown state: {'hold_on'}
2025-10-18 09:53:00.014 WARNING (MainThread) [kasa.smart.modules.temperaturecontrol] Got unknown state: {'hold_on'}
2025-10-18 09:53:00.014 WARNING (MainThread) [homeassistant.components.tplink.climate] Unknown thermostat state, defaulting to OFF: ThermostatState.Unknown
2025-10-18 09:53:05.013 WARNING (MainThread) [kasa.smart.modules.temperaturecontrol] Got unknown state: {'hold_on'}
2025-10-18 09:53:05.013 WARNING (MainThread) [homeassistant.components.tplink.entity] Unable to read data for <DeviceType.Thermostat Heizung Fühler (KE110) of <DeviceType.Hub at 192.168.178.56 - Smart Hub (KH100)>> climate.heizung_fuhler: <ThermostatState.Unknown: 'unknown'>
2025-10-18 09:53:10.010 WARNING (MainThread) [kasa.smart.modules.temperaturecontrol] Got unknown state: {'hold_on'}
2025-10-18 09:53:15.021 WARNING (MainThread) [kasa.smart.modules.temperaturecontrol] Got unknown state: {'hold_on'}
2025-10-18 09:53:20.004 WARNING (MainThread) [kasa.smart.modules.temperaturecontrol] Got unknown state: {'hold_on'}
2025-10-18 09:53:20.005 WARNING (MainThread) [kasa.smart.modules.temperaturecontrol] Got unknown state: {'hold_on'}
Hopefully it'll just be a case of adding support for this state! 😁
Activity
MTTPoll commented on Nov 10, 2025
Gehen wir mal davon aus du sprichst deutsch 😁
Ein T110 ist ein Kontaktsenor (Fenster/Tür), dem kannst du ja keine Temperatur geben, das kann der ja nicht. Also der wird ja kaum gemeint sein, ein KE110 hingegen wäre ein externer Temp/LF Sensor, dem kann man zwar schwellenwerte geben, aber ich denke das meinst du auch nicht. Du hast sicher KE100 Thermostate und diese vielleicht in Verbindung mit einem KE110 Raumtemp Sensor? Du hast doch sicher deine KE110 mit den KE100 Verbunden und den internen Thermostatsenor auf externen Sensor umgestellt, wozu willst du dann den KE110 extra Abfragen? Die Temperatur kannst du dir doch über das KE100 dann abrufen.
rytilahti commented on Nov 10, 2025
Hey and thanks for the report! I created two PRs to improve the situation:
After a new release of this library is done and it gets bumped to the homeassistant, we can map the "Hold" state to "Idle" instead of the "Off" one. Until then, I hope we get the HA fix in to avoid unavailable states.