Automations file can't be empty with packages

[metbril]

Home Assistant release (hass --version):
0.65.5

Python release (python3 --version):
3.6.3.

Component/platform:
core

Description of problem:
When using automations in packages in combination with a separate main automations file, the latter cannot be empty. It requires at least one dummy automation.

https://community.home-assistant.io/t/automation-editor-with-packages/18427

Expected:

Automations file can be configured and can be empty.

Problem-relevant configuration.yaml entries and steps to reproduce:

configuration.yaml

automation: !include include/automation.yaml

Traceback (if applicable):

Error when automation.yaml is empty

Testing configuration at /config
Failed config
  automation: 
    - Invalid config for [automation]: required key not provided @ data['action']. Got None
required key not provided @ data['trigger']. Got None. (See ?, line ?). Please check the docs at https://home-assistant.io/components/automation/

Additional info:

To get a valid config, as a workaround, at least add this dummy automation

include/automation.yaml

- alias: 'dummy'
  hide_entity: true
  initial_state: false
  trigger:
  action:

[MartinHjelmare]

All automations are validated during the setup phase of home assistant. This is not a bug, but a feature request.

[metbril]

I think it should be possible to have an empty automations file, to be able to add to later. Don't you think?

[MartinHjelmare]

But your file wasn't empty, or do I misunderstand?

[metbril]

I think you misunderstood. (Might be my mistake)
The provided automation is the minimal dummy automation I need to add to get a valid config.
If the file is empty, the provided error is raised.

Update: I will edit my initial post for clarification.

[MartinHjelmare]

Ok, sorry, I read too quickly.

I'm wondering, why do you need the file if you want to use packages? Is it because of the automation editor? If so, did you try with the correct path to automations.yaml in the include, like we discussed in the other issue?

[metbril]

Yes, I would like to be able to add simple (temporary) automations (like debug notifications) through the editor, that I can activate through the UI without a required restart of HA.

I have configured the fixed path for automations.yaml, but still get the same error when the file is empty.

[point-4ward]

This is because an empty include file is the equivalent of just putting

automation:

Which is invalid config. Automation must have a defined trigger and action.

[MartinHjelmare]

But then it's weird that it works with empty file when not using packages.

[MartinHjelmare]

This might still be a feature request, but I'll reopen until we get some clarity on the behavior.

[point-4ward]

Maybe the config checker is 'clever' enough that if it only appears once then ignore it, but with packages it will appear multiple times, so it can't ignore it otherwise it might validate an automation that doesn't have the required keys.

[kellerza]

Top level keys are assigned {} for None in bootstrap, but this was moved before package merging after a recent PR. Needs to be addressed by package merging function ideally.

[metbril]

@mf-social / re. #13412 (comment)

An empty automation config does justice to the automation editor. You can and should be able to add, edit and delete any automation. So the file could be empty by design?