cycle_min: 0 causes 100% load as timer gets scheduled in a loop with 0 delay

[mikz]

Version of the custom_component

main

If it is releveant to regulation performance or optimisation some curves are needed

no

Describe the bug

I configured cycle_min: 0 and Versatile Thermostat goes into infinite interval spawning loop.

versatile_thermostat/custom_components/versatile_thermostat/thermostat_climate.py

Lines 453 to 457 in 077d2d4

	async_track_time_interval(
	self.hass,
	self.async_control_heating,
	interval=timedelta(minutes=self._cycle_min),
	)

will start spawning cycle jobs with 0 delay causing 100% load.

I know this is poor API from homeassistant and other integrations suffer the same (adaptive lighting).

Yet it can be fixed by either requiring > 0 int in the configuration schema or by having some min(1, timedelta(...)) to have at least some enforced delay.

I learned this the hard way, but having a foolproof setup would prevent some folks going down this rabbit hole.

[jmcollin78]

Hello @mikz ,

Yes good point, I will add that. Thank you for your report.