Error during setup of component map after initial setup and update of Home Assistant Green

[pschx]

The problem

I recently started my Home Assistant Green for the first time and updated it to the latest version. After the update, I consistently encounter three errors related to the map component setup, which prevent the default_config from loading properly.

Here is the error log I receive:

2024-09-20 17:24:32.630 ERROR (MainThread) [homeassistant.setup] Error during setup of component map
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 416, in _async_setup_component
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/map/__init__.py", line 49, in async_setup
await _create_map_dashboard(hass)
File "/usr/src/homeassistant/homeassistant/components/lovelace/__init__.py", line 282, in _create_map_dashboard
await dashboards_collection.async_create_item(
File "/usr/src/homeassistant/homeassistant/helpers/collection.py", line 316, in async_create_item
validated_data = await self._process_create_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/lovelace/dashboard.py", line 283, in _process_create_data
raise vol.Invalid("Panel url path needs to be unique")
voluptuous.error.Invalid: Panel url path needs to be unique

Could this be related to a conflict in the Lovelace dashboard configuration or a bug introduced in the recent updates? Any guidance or help would be appreciated.

What version of Home Assistant Core has the issue?

System Information version | core-2024.9.2 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.12.4 os_name | Linux os_version | 6.6.46-haos arch | aarch64 timezone | Europe/Berlin config_dir | /config

Home Assistant Community Store

GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok HACS Data | ok GitHub API Calls Remaining | 4983 Installed Version | 2.0.1 Stage | running Available Repositories | 1411 Downloaded Repositories | 1

Home Assistant Cloud

logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok

Home Assistant Supervisor

host_os | Home Assistant OS 13.1 -- | -- update_channel | stable supervisor_version | supervisor-2024.09.1 agent_version | 1.6.0 docker_version | 26.1.4 disk_total | 28.0 GB disk_used | 4.2 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | board | green supervisor_api | ok version_api | ok installed_addons | File editor (5.8.0), Get HACS (1.3.1), Cloudflared (5.1.20)

Dashboards

dashboards | 2 -- | -- resources | 0 views | 1 mode | storage

Recorder

oldest_recorder_run | 17. September 2024 um 18:46 -- | -- current_recorder_run | 20. September 2024 um 17:24 estimated_db_size | 0.87 MiB database_engine | sqlite database_version | 3.45.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

map documentation map source

[home-assistant[bot]]

Hey there @home-assistant/frontend, mind taking a look at this issue as it has been labeled with an integration (lovelace) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `lovelace` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign lovelace` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

lovelace documentation lovelace source _{^{(message by IssueLinks)}}

[AndreasBVB]

Fixed this by deleting the existing Map dashboard and restart HomeAssistant.