MQTT climate ON/OFF

[green glade]

I see there's both modes: [auto, off, cool, heat, dry, fan_only] that includes off (and produces a button on the UI control in the mode row) as well ass the power_command_topic, payload_off, payload_on, power_command_template family of properties.
However, I didn't manage to find a way to trigger climate.turn_on and climate.turn_off from the UI element.
Is this intentional? What is a normal guest/user supposed to do, use the off mode instead?
I probably just don't see the massive power button because it's late, so I will go to bed now.

I understand how to conceal the mode with something like ```yaml
mode_state_topic: mits/dining
mode_state_template: '{{{"Auto":"auto","Cool":"cool","Heat":"heat","Fan":"fan_only","Dry":"dry"}[value_json.mode] if value_json.drive else "off"}}'
mode_command_topic: mits/dining/set
mode_command_template: '{{{"mode": {"auto":"Auto","cool":"Cool","heat":"Heat","fan_only":"Fan","dry":"Dry"}[value]} if value != "off" else {"drive":false}|to_json}}'
current_temperature_topic: mits/dining

[slim sundial]

I think the off is indeed part of mode. So what you have don't seems hacky to me 🙂

[green glade]

Butt what about power_command_* and payload_*? Are they deprecated or upcoming?
Because I tried issuing climate.turn_off with dev tools, and it operated my MQTT as expected and didn't produce a warning in logs, but there was no change to the UI card.
Literally just stayed looking like let's say heat mode, despite me not disabling optimism.
I thought this might be for something like when circumstances mean the aircon is disabled, but the UI card was completely unaffected

[slim sundial]

Good point, looks like you also need those if device really supports a on/off. The off command is basically a copy of what you have. For on you have to see if there is a seperate on command of that you will have to pick a "default" mode to turn it on.