ui_lovelace.yaml vs ui-lovelace.yaml

[DelroyTaylor]

Readme.md Usage instructs thus: "This integration changes the way Home Assistant parses your ui_lovelace.yaml before sending the information off to the lovelace frontend in your browser. It's obviously only useful if you are using YAML mode."
Then "Important: For some reason, which I can't seem to nail down, things stop working if you add # lovelace_gen to ui-lovelace.yaml. Adding it to any file included from ui-lovelace.yaml works, though."
Other Homeassistant documents also use ui_lovelace.yaml and ui-lovelace.yaml
Please clarify which is the correct yaml filename.

[thomasloven]

Neither. Home Assistant has updated since this was written.

lovelace_gen does not work on whatever file you have set in your configuration.yaml as being the main file for a lovelace panel. It does work on files !included from that file, though.

[DelroyTaylor]

Thanks Thomas

Do we still need to add this to our configuration.yaml since lovelace_gen work on whatever file we have set in the configuration.yaml? Assume lovelace_gen will find files automatically?

lovelace_gen:

lovelace:
mode: yaml

[thomasloven]

lovelace_gen: is still a requirement. The rest is up to your configuration.