Chromecast is not operable

I have a newly installed HASS on Rasberry PI 3 Model B.

I have 2 chromcast devices. One of them is working fine but the other is not operable.

From ConfigurationIntegrationsGoogle Cast, I see

And the log:

Fri Nov 23 2018 13:05:37 GMT-0800 (Pacific Standard Time)

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py”, line 339, in _async_add_entity
‘Invalid entity id: {}’.format(entity.entity_id))
homeassistant.exceptions.HomeAssistantError: Invalid entity id: media_player.

I searched for this problem - they all said it’s because of the non-latin characters. But in my case, I’m sure there’s no non-latin characters. Any ideas? What’s the best way to debug this?


Here is my configuration.

homeassistant:
  # Name of the location where Home Assistant is running
  name: Home
  # Location required to calculate the time the sun rises and sets
  latitude: 0
  longitude: 0
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: 0
  # metric for Metric, imperial for Imperial
  unit_system: metric
  # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
  time_zone: "America/Los_Angeles"
  # Customization file
  customize: !include customize.yaml

# Show links to resources in log and frontend
introduction:

# Enables the frontend
frontend:

# Enables configuration UI
config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

# Checks for available updates
# Note: This component will send some information about your system to
# the developers to assist with development of Home Assistant.
# For more information, please see:
# https://home-assistant.io/blog/2016/10/25/explaining-the-updater/
updater:
  # Optional, allows Home Assistant developers to focus on popular components.
  # include_used_components: true

# Discover some devices automatically
discovery:

# Allows you to issue voice commands from the frontend in enabled browsers
conversation:

# Enables support for tracking state changes over time
history:

# View all events in a logbook
logbook:

# Enables a map showing the location of tracked devices
map:

# Track the sun
sun:

# Sensors
sensor:
  # Weather prediction
  - platform: yr

# Text to speech
tts:
  - platform: google

# Cloud
cloud:

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

cast:
  media_player:
  - host: 192.168.1.6
  - host: 192.168.1.9

hassio:

Is the IP address correct for the second cast device?

It may have changed if you have not reserved an IP address for it in DHCP in your router.

Can you cast to it with other devices (your phone for example).

Also is the second cast device on?? Mine is always unavailable because it’s powered by a USB port on my TV and it isn’t available unless the TV is on…

I’m sure the IP address is correct, and I’m casting from my iPhone while I’m experimenting this…

The error message is not very clear what’s going on.

1 Like

Have you tried restarting HA?

You could delete the integration and try setting it up again.

If none of that works try setting up the problematic chromecast again.

Remove the lines

media_player:
  - host: 192.168.1.6
  - host: 192.168.1.9

So it just says

cast:
1 Like

I tried this but it didn’t fix the issue.

I also tried restarting HA but it didn’t work too.

I will try resetting my chromcast again. If it doesn’t work, I might need to instrument logging into HA and figure out why it’s media_player. with the trailing part missing, which I currently don’t know how to do…

I don’t have anything to do with cast in my config yaml… it is just picked up by the integration automatically…