Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Smartthings climate entity missing 'off' feature #141557

Closed
Cheiron1979 opened this issue Mar 27, 2025 · 5 comments · Fixed by #141700
Closed

Smartthings climate entity missing 'off' feature #141557

Cheiron1979 opened this issue Mar 27, 2025 · 5 comments · Fixed by #141700

Comments

@Cheiron1979
Copy link

Cheiron1979 commented Mar 27, 2025

The problem

Since updating to Home Assistant Core 2025.3.0, the thermostat card in Lovelace no longer displays the "off" mode icon. Previously, both "heat" and "off" icons were correctly displayed for climate entities that support these modes.

Now, only the "heat" icon appears, making it impossible to switch off the thermostat from the UI.

Expected behavior:

The thermostat card should display both "heat" and "off" mode icons if the entity supports them.

Actual behavior:

Only the "heat" mode icon is shown, even though "off" is listed in the entity’s hvac_modes.

Steps to reproduce:

  1. Use a climate entity that supports both "heat" and "off" modes.

  2. Add a thermostat card in Lovelace with the following YAML configuration:

type: thermostat
entity: climate.example_heater
features:

  • type: climate-hvac-modes
    hvac_modes:
    • heat
    • "off"
  1. Observe that only the "heat" icon appears, and the "off" mode is missing.

Image

Additional information:

The issue was not present in Home Assistant Core 2025.2.x.

Confirmed on multiple devices and with different climate entities.

Restarting Home Assistant and clearing cache did not resolve the issue.

What version of Home Assistant Core has the issue?

2025.2.5

What was the last working version of Home Assistant Core?

2025.3.4

What type of installation are you running?

Home Assistant Core

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

@home-assistant
Copy link

Hey there @joostlek, mind taking a look at this issue as it has been labeled with an integration (smartthings) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of smartthings can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign smartthings Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


smartthings documentation
smartthings source
(message by IssueLinks)

@joostlek
Copy link
Member

Can you download device diagnostics?

@Cheiron1979
Copy link
Author

Sorry. I've already rolled back to ver. 2025.2.5.
But I couldn't find more problems except this issue. I'm a new beginner. Can you explain what you need then I'll try ..

@joostlek
Copy link
Member

Image

Download this

@Cheiron1979
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants