Magic Areas will not load HA areas unless there's at least 1 room definition on YAML

I wanted to try this, but HA never finishes starting up and just stops responding completely at some point mid startup. I had only added magic_areas: to my config. Nothing of relevance in the log except this: 2020-11-23 17:46:50 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for magic_areas which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.

Then the log also stops outputting anything. I do have quite a few entities if that could have something to say.

[dvbit]

I can confirm that adding at least details for one area seems to solve

[jseidl]

I just spined up a dev VM with single magic_areas: definition. All the built-in areas were captured and working fine without any further room declaration. Will close this. If anyone goes through this again we’ll reopen.

Config:

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

logger:
  default: info
  logs:
    custom_components.magic_areas: debug

magic_areas: