Can't set temp with hidden setpoint

[bkaufx]

Describe the bug Hiding a setpoint in the card causes a dual point thermostat to be treated like a single point thermostat. The set_temperature service is called with a single temperature instead of separate target_temp_low and target_temp_high arguments. However, Home Assistant requires both target_temp_low and target_temp_high.

To Reproduce

1. Have dual setpoint thermostat
2. Hide one of the setpoints in the card
3. Try to adjust target temp
4. See error "Failed to call service climate/set_temperature. some but not all values in the same group of inclusion 'temperature' @ data[]"

Expected behavior Even if one of the setpoints is hidden, set_temperature should still be called with both target_temp_high and target_temp_low.

      - type: custom:simple-thermostat
        entity: climate.thermostat
        setpoints:
          target_temp_low:
            hide: true
          target_temp_high:

Screenshots

Browser

• OS: Windows 10
• Browser: Edge & Firefox
• Simple Thermostat version from browser console: 2.4.2 (according to HACS and also found in .js file)
• Home Assistant version: 2021.7.3

[rperciaccante]

I am seeing the same issue with Chrome on Windows 10, Chrome on Android, and Fully Kiosk browser as well.

[brettfire]

Same here

[heffneil]

Any update here? I finally figured out my cards and got it looking right - but now this error is in the way. Any thoughts on a workaround?

[heffneil]

Anyone? Did you guys just stop hiding the other setpoint in the meantime?

[bkaufx]

Yep.

[heffneil]

Any update here? Curious if anyone found a solution to pass the other modes' setpoint hidden?

[brettfire]

I'm planning on looking at this myself when I get some time but don't hold your breath. Will update here if & when I do.

[heffneil]

I had a friend help me fix this. He added CSS to hide the attributes but they will still exist. I don't know really how to show the work. We added to the styles.css and the main.ts. The js file can be found here:

https://pastebin.com/C4q9kPbJ

I apologize is this is the wrong way to do this but I don't know the "right" way to do a pull and update files.

[heffneil]

I did discover a small bug: if you turn the unit OFF you lose both setpoints. Not the end of the world but this is far more functional until the original author can potentially look at it?

[rperciaccante]

I did discovered a small bug: if you turn the unit OFF you lose both setpoints. Not the end of the world but this is far more functional until the original author can potentially look at it?

Possible this was caused by the CSS change?

[heffneil]

Yes this is a bug in the CSS update but I am not interested in fixing it. Hopefull the original author fixes the code the way he originally intended and it isn't a problem :)

[mdedonato]

From what I can tell, when you hide a setpoint, it no longer sends a command to change the hidden setpoint. The home assistant thermostat requires both setpoint values to be set each time the command is sent. I haven't been able to come up with a solution yet, but I suppose that it is as simple as sending a value for the hidden setpoint even though it is hidden.

[heffneil]

thats right just send what's already there. We aren't changing it - thats what the code I setup / proposed is doing. It continues to submit the current value for the hidden one.

[JagerSprinkles]

Anyone find a functional work around for this?

[heffneil]

still nothing on this working. Even my update doesn't seem to have fixed the issue :( Really a big problem for me.