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

Value ON or OFF in dictionary cause error loading blueprint #21027

Closed
3 of 4 tasks
SirYasko opened this issue Jun 7, 2024 · 1 comment
Closed
3 of 4 tasks

Value ON or OFF in dictionary cause error loading blueprint #21027

SirYasko opened this issue Jun 7, 2024 · 1 comment

Comments

@SirYasko
Copy link

SirYasko commented Jun 7, 2024

Checklist

  • I have updated to the latest available Home Assistant version.
  • I have cleared the cache of my browser.
  • I have tried a different browser to see if it is related to my browser.
  • I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

image

blueprint:
name: Sir Yasko's Dropdown Test
description: Value ON or OFF cause error loading automation
domain: automation
input:
action:
name: Action
description: Select the action to perform
selector:
select:
mode: dropdown
options:
- value: ON
label: Turn On
- value: OFF
label: Turn Off

Describe the behavior you expected

When you change OFF / ON value to eg: TURN_OFF / TURN_ON everything works like a charm

Steps to reproduce the issue

  1. As above

What version of Home Assistant Core has the issue?

core-2024.6.0

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

No response

Which operating system are you using to run this browser?

No response

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

@karwosts
Copy link
Contributor

karwosts commented Jun 7, 2024

This isn't a frontend issue, but try putting quotes around on/off. I believe yaml interprets those bare words as booleans, and not strings, which are expected. Same for yes/no and true/false.

@karwosts karwosts closed this as not planned Won't fix, can't repro, duplicate, stale Jun 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants