nielsfaber / scheduler-card

HA Lovelace card for control of scheduler entities
GNU General Public License v3.0
903 stars 113 forks source link

Thermostat regulate missing when current mode is not in regulate mode #658

Closed tykeal closed 1 year ago

tykeal commented 1 year ago

Checklist

Card Version

v2.4.1

Component Version

v3.2.14

Bug description

When a thermostat is currently not in regulate mode (it's in heat, cool, or off) it is not possible to configure a schedule that configures regulate.

I'm not 100% certain, but I believe this bug may have been introduced with 12565a871284ea9617180eaa335c501a0ffbf083

Steps to reproduce

Additional info

I don't know if this is a by-product of the thermostats that I'm using, but I've got access to two different brands of thermostats:

In both cases, when not configured to be in the regulate mode, both brands report having target_temp_high and target_temp_low attributes which are set to null while the hvac_modes available are off, heat, cool, heat_cool

nielsfaber commented 1 year ago

target_temp_high and target_temp_low must not be null but type float. See also here. Scheduler uses these properties to evaluate whether the setpoints need to be updated or are equal to the current setpoint.

tykeal commented 1 year ago

That may be, but I have zero control over what the climate device is reporting when it is in a different mode. I'm seeing this same behavior with two different brands of thermostat, so it might be the climate device / entity itself doing this. I dunno. But the device reports that heat_cool is an available hvac_mode and the regulate option does not show up when building out schedules for these devices unless the device is currently in heat_cool. As soon as the device switches to that mode then the target_temp_high and target_temp_low do have values and you can then create schedules around it that way.

My biggest issue is that I've got some variability in how I need my schedules set. During the warmer months, I need to make sure that I've got a regulate schedule in play as temperatures around my properties can vary from very cold in the morning to very warm during the day and fairly late into the night, but during colder months, I need the schedules in a pure heat only mode.

Makes it hard to properly build out the schedules when you can't access an item because the device is in a specific mode that the card doesn't seem to recognize

tykeal commented 1 year ago

I will note, that once a schedule is created, turning it on does the correct thing. It's just a little painful getting it properly created if the climate device isn't in a regulate mode while doing it. And you can't properly edit a schedule that is in regulate mode if the climate device isn't currently in that mode either.

github-actions[bot] commented 1 year ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days