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

assist_timers.yaml:512 gives error when restarting ha #2

Open
ariedeleen opened this issue May 21, 2024 · 4 comments
Open

assist_timers.yaml:512 gives error when restarting ha #2

ariedeleen opened this issue May 21, 2024 · 4 comments

Comments

@ariedeleen
Copy link

Maybe lines below are correct:
entity_id: "{{ timer_tts_target == 'tts.speak' }}"
alias: "Restore device previous volume"

@don86nl
Copy link
Owner

don86nl commented Jun 4, 2024

Does the current package still give this error? I updated the TTS services to support both tts.speak and other service calls.

@mikey60
Copy link

mikey60 commented Jun 5, 2024

line 512 of projects/assist_timers .yaml is incorrect. It looks like a line feed was deleted.

                 entity_id: "{{ timer_tts_target == 'tts.speak' }}"      - alias: "Restore device previous volume"

should be

                  entity_id: "{{ timer_tts_target == 'tts.speak' }}"
      - alias: "Restore device previous volume"

@ariedeleen
Copy link
Author

ariedeleen commented Jun 6, 2024

Just installed the latest HA Core 2024.6 and dl the latest ha_intents did a reboot.
Resulted in an error:

024-06-06 10:19:59.930 ERROR (SyncWorker_0) [homeassistant.util.yaml.loader] sequence entries are not allowed here
in "/config/packages/assist_timers.yaml", line 512, column 75
2024-06-06 10:19:59.932 ERROR (MainThread) [homeassistant.bootstrap] Failed to parse configuration.yaml: sequence entries are not allowed here
in "packages/assist_timers.yaml", line 512, column 75. Activating recovery mode

don86nl added a commit that referenced this issue Jun 9, 2024
@don86nl
Copy link
Owner

don86nl commented Jun 9, 2024

Absolutely right, thanks for point that out. Fixed the line break.
Please let me know if it is fixed now.

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

3 participants