Feature Request: Support for Range‑Limited / Bounded‑Setpoint Thermostats

[tmaults]

My thermostat is a Zen [Zen-01-W] (https://www.zigbee2mqtt.io/devices/Zen-01-W.html#zen-zen-01-w).

It is a range‑limited, dual‑setpoint thermostat. It requires minimum and maximum bounds for both heating and cooling, and it always exposes both setpoints at the same time, regardless of the active mode.

In MQTT it publishes attributes such as:

occupied_cooling_setpoint

occupied_heating_setpoint

Example payload:

"system_mode": "cool",
"occupied_cooling_setpoint": 23.88888888888889,
"occupied_heating_setpoint": 20

Even while cooling, the device continues to report the heating setpoint because the Zigbee HVAC Thermostat cluster requires both values to remain valid simultaneously.

From what I can tell Climate Scheduler currently assumes a single active setpoint, but thermostats like the Zen operate with paired heating/cooling setpoints and fixed allowable ranges.

[kneave]

I'm trying to avoid supporting specific devices and instead just control Climate entities. That said I do have heating and cooling in some of my rooms and was planning on finding a way to support both from one schedule. I was thinking of creating a virtual thermostat in HA of some kind for this as they are physically two systems in my case.

Does your thermostat present dual setpoints in a climate entity or do you need to control them as separate heating and cooling entities?

[tmaults]

My thermostat shows up as a single climate entity in Home Assistant. I’ve put together a package file that integrates it using the built-in HA schedule system. Your scheduler, though, presents the schedule in a way that’s much easier to use and visualize than the native HA schedule UI.

I’m not asking you to change your integration to support my thermostat specifically. I just want to use your custom scheduler purely as a scheduler — something I can query for the current time and temperature setpoints from within my own integration.

That way, I can keep my existing package and climate entity setup but still take advantage of your scheduler’s much better usability and ditch the HA scheduler.

[kneave]

Cool, so if when a node was hit in the schedule an event (or similar) was emitted that an automation could use as a trigger that'd be a good middle ground?

[tmaults]

Yes. definitely. I would need the node in your scheduler to store the both high and low temps.

[kneave]

I've added the ability to create a schedule without an entity associated with it, you can still set the temperature using the graph or set the "no change" option. You have three freeform numeric fields to play with, events will be fired with the name 'climate_scheduler_node_activated`.

For you I'd recommend creating a generic thermostat to add to the group though, that way you'll get the extra HVAC options to play with.

https://github.com/kneave/climate-scheduler/releases/tag/v1.14.0.1b