We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Home Assistant release with the issue:
0.81.2
Last working Home Assistant release (if known): N/A as thermostat card was introduced in 0.81
Browser and Operating System:
Firefox / Chrome on Windows 10
Description of problem:
Thermostat card not showing up for Honeywell climate component. When I add the Honeywell Climate component in an entity card it shows up as expected.
Javascript errors shown in the web inspector (if applicable):
TypeError: stateObj.attributes.operation_list is undefined
Additional information: Configuration:
climate: - platform: honeywell username: !secret honeywell_username password: !secret honeywell_password scan_interval: 600
ui-lovelace.yaml:
- title: Climate icon: mdi:temperature-celsius cards: # working entity card - type: entities title: Climate show_header_toggle: false entities: - entity: climate.thermostat # not working thermostat card - type: thermostat entity: climate.thermostat
The text was updated successfully, but these errors were encountered:
Will be fixed in next release. Fixed in #1901
Sorry, something went wrong.
No branches or pull requests
Home Assistant release with the issue:
0.81.2
Last working Home Assistant release (if known):
N/A as thermostat card was introduced in 0.81
Browser and Operating System:
Firefox / Chrome on Windows 10
Description of problem:
Thermostat card not showing up for Honeywell climate component. When I add the Honeywell Climate component in an entity card it shows up as expected.
Javascript errors shown in the web inspector (if applicable):
Additional information:
Configuration:
ui-lovelace.yaml:
The text was updated successfully, but these errors were encountered: