Closed sebirdman closed 3 years ago
This sounds like it's exactly the same as our climate entity?
It's very similar, but the climate entity is focused on a specific task:
The Climate integration allows you to control and monitor HVAC (heating, ventilating, and air conditioning) devices and thermostats.
Most of the services and attributes of the climate entity are focused on controlling and reporting a human climate. Whereas TemperatureEntity would be more generalized for controlling any temperature.
You can however use the generic thermostat
as a generic thermostat for grill or cooker, that why it is called "generic", dosn't it?
@yuvalabou this is absolutely something that can be "worked around" with a climate or water heater entity. Either workarounds do quite well for just the temperature control element of the entity. The issue comes when attempting to control the device on/off states. Many cooker devices allow a user to remotely turn the device off but not on.
in the case of the generic thermostat, there's a required "heater" field that must be a toggle device
heater string REQUIRED entity_id for heater switch, must be a toggle device. Becomes air conditioning switch when ac_mode is set to true.
Well, true. However I still disagree becouse if we do need a generic thermostat for specific application or device that is not an AC one can make the built-in generic thermostat integration more versatile, say - allow to configure a "device class" or somthing similar, but there is no need to make a whole new platform or integration to achieve this.
@yuvalabou fair point, Do you know if i should make a proposal to make the built in one more versatile or should i just make an MR?
Context
I've been working on an integration for Traeger wifi connected grills. In the past there have been some proposals for cooker entities and cooler entities. These seem to have stalled, and I'm also not sure those proposals are abstract enough for HA.
As @awarecan stated in the cooker entity MR:
In keeping with that comment, I've tried to make sure this proposal is the very base set of features needed to control a temperature.
Proposal
The TemperatureControl Entity is an entity type that manages a feature on a device that a user can adjust the temperature on. This entity:
This entity does not:
TemperatureControlEntity
Much of the proposed state below is taken from climate or water heater entities
Consequences
Positive:
Negative: