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

Automation UI creates invalid yaml #20674

Open
4 tasks done
HenryLoenwind opened this issue Apr 30, 2024 · 1 comment · May be fixed by home-assistant/core#116455
Open
4 tasks done

Automation UI creates invalid yaml #20674

HenryLoenwind opened this issue Apr 30, 2024 · 1 comment · May be fixed by home-assistant/core#116455

Comments

@HenryLoenwind
Copy link

HenryLoenwind commented Apr 30, 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

Duration isn't supported, yet the UI offers it and creates an invalid yaml when you enter a value.

Describe the behavior you expected

No error message -- OR -- UI should not offer invalid fields.

Steps to reproduce the issue

  1. Create an automation as in the picture
  2. Press "save"
  3. ?
  4. Profit ...um... fail

What version of Home Assistant Core has the issue?

2024.4.4

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

125.0.6422.4

Which operating system are you using to run this browser?

Windows 10

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

Resetting the duration to 0 does NOT generate valid yaml.

@karwosts
Copy link
Contributor

This is actually a core bug, not frontend, but I've put up a PR there to fix it.

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

Successfully merging a pull request may close this issue.

2 participants