search

bushvin / hass-integrations

My custom Home Assistant integrations
Apache License 2.0
59 stars 11 forks source link

Platform mopidy does not generate unique IDs. ID 192_168_0_15_6680 already exists #69

Open rtl19 opened 2 months ago

rtl19 commented 2 months ago

Hi, I'm running HA core 2024.5.0 in a docker container on host 192.168.0.15. I have mopidy setup to connect to the host computer that runs the HA container on a specific IP address (192.168.0.15) . The host computer is using Pulseaudio and is playing music directly fine (outside of mopidy).

I added the following lines to the HA configuration.yaml file:

media_player:
- name: media_mopidy
  host: 192.168.0.15
  #port: 6680
  platform: mopidy

In HA log is the following error: 2024-05-27 09:23:08.213 ERROR (MainThread) [homeassistant.components.media_player] Platform mopidy does not generate unique IDs. ID 192_168_0_15_6680 already exists - ignoring media_player.mopidy_server

I'm probably doing something stupid. What am I doing wrong?

bushvin commented 2 months ago

Is it possible it was previously found using uPnP? Check your entities if you already have an entry with that name...

rtl19 commented 2 months ago

When I started home assistant without the 'media_player' configuration settings active but disabled, there were no entities related to the 192.168.0.15 address and no errors in the log.

Then, I went into settings -> integrations -> and re-enabled the mopity server and saw this error in the log:

Platform mopidy does not generate unique IDs. ID 192_168_0_15_6680 already exists - ignoring media_player.mopidy_server

I did see this in the entity list from settings:

Name = media_mopidy Entity = media_player.mopidy_server State = -

Name = media_mopidy Entity = media_player.media_mopidy State = Not provided

Searching for an entity with 192_168_0_15_6680 didn't show any results.