Thermostat-like data from the custom device, which entities to use?

Third party integrations
1

Hello, I’ve been working on the integration of ecoNET300. The device has implemented a thermostat itself and it exposes two following values through the Rest API:

  • mixerTemp - current temperature

  • mixerSetTemp - target temperature

I’m wondering if I should implement these two “entities” as Sensor and Number respectively or implement it as a Climate entity.

What do you think? What would be a better choice?

Unfortunately, I can’t implement it as Sensor and Number and then e.g. use it as “Generic Thermostat” from Lovelace dashboard because the Generic Thermostat requires a switch also which is not available in my device because it works autonomously as I said.