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

File Editor - YAML error identified in Home Assistant File Editor, but not in ESPHome Dashboard File Editor #3466

Closed
philpownall opened this issue Feb 14, 2024 · 1 comment
Labels

Comments

@philpownall
Copy link

Describe the issue you are experiencing

Home Assistant File Editor identifies the following "unkown tag" error on a lambda in an esphome .yaml file:

unknown tag !<!lambda> (218:47)

215 | ...
216 | ... write:
217 | ... servo_1
218 | ... l: !lambda 'return x / 100.0;'
------------------------------------------^
219 | ...
220 | ... r template to control servo 2

There is no error identified in the ESPHome Dashboard File Editor:

    set_action:
      then:
        - servo.write:
            id: servo_1
            level: !lambda 'return x / 100.0;'

If the issue is that I should not be editing ESPHome yaml files in Home Assistant File Editor, or a FIle Editor configuration issue, I apologize for using your valuable time.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

File editor

What is the version of the add-on?

Home Assistant File Editor 5.8.0, ESPHome 2023.12.9

Steps to reproduce the issue

  1. Open File editor Add-On in Home Assistant
  2. Navigate to the esphome directory
  3. Open a yaml file (that has a !lambda in it)
  4. Open the error flag button to see the error

Alternately,

  1. Open ESPHome Dashboard Add-on in Home Assistant
  2. Open a yaml file using EDIT button
  3. No error is found
    ...

System Health information

There are currently no repairs available

Anything in the Supervisor logs that might be useful for us?

No response

Anything in the add-on logs that might be useful for us?

No response

Additional information

No response

Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Mar 15, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant