Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manual cast: entry not working #15401

Closed
ludeeus opened this issue Jul 10, 2018 · 8 comments · Fixed by #15630
Closed

Manual cast: entry not working #15401

ludeeus opened this issue Jul 10, 2018 · 8 comments · Fixed by #15630
Assignees

Comments

@ludeeus
Copy link
Member

ludeeus commented Jul 10, 2018

Home Assistant release with the issue: 0.73.1

Last working Home Assistant release (if known): N/A

Operating environment (Hass.io/Docker/Windows/etc.):
Hassbian.
Home Assistant installed in a python virtual environment on a Raspberry Pi 3.

Component/platform:

https://www.home-assistant.io/components/cast/

Description of problem:
When addin a google cast device manually to the configuration, it does not get loaded/added to Home Assistant.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
Tried this from the docs:

cast:
  media_player:
  - 192.168.2.188

and:

cast:
  media_player:
    - 192.168.2.188

Traceback (if applicable):

2018-07-10 06:26:15 INFO (MainThread) [homeassistant.loader] Loaded cast from homeassistant.components.cast
2018-07-10 06:26:17 INFO (MainThread) [homeassistant.setup] Setting up cast
2018-07-10 06:26:17 INFO (MainThread) [homeassistant.setup] Setup of domain cast took 0.0 seconds.
2018-07-10 06:26:17 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=cast>

Additional information:
If I use the old way of adding this devices:

media_player:
  - platform: cast

It is available in Home Assistant, but gives this warning on startup:

WARNING (MainThread) [homeassistant.components.media_player.cast] Setting configuration for Cast via platform is deprecated. Configure via Cast component instead.
@alexhardwicke
Copy link
Contributor

alexhardwicke commented Jul 10, 2018

I have the same problem with cast.

Running Home Assistant in a container on an Ubuntu Server 18.04 host.

It worked on previous versions of Home Assistant but stopped, unless I use the deprecated method mentioned above.

The hardware device is a Google Home.

I've tried going through Configuration - Google Cast, but it doesn't find the device (and as I'm running the container bridged, not home/host, I'm not surprised).

Edit:
Have also tried with

cast:
  media_player:
    - host: xx.yy.zz.aa

Edit 2:
I've changed my setup so that my home-assistant container runs host networking, which means that discovery and Configuration - Google Cast now works. I've not tried a manual config and don't really need/want to now. Everything's version controlled, so I can go back if that'd help figure anything out, but the issue itself isn't relevant for me any more.

@cmacnichol
Copy link

Having the same issue. Looks like this was also brought up under Hass.io as an issue. Seems to mention the cause as well.

home-assistant/home-assistant.io#5673

@mnoorenberghe
Copy link
Contributor

Did you enable the Cast component by going to the Integrations page?

@cmacnichol
Copy link

cmacnichol commented Jul 14, 2018

I was having to many issues with Discovery, that an I prefer to manually add things, so I disabled Discovery.

I am currently on 72.1 due to the DHT sensor issue in 73.

cast:
  media_player:
  - host: 192.168.2.49

With this setup, the device does not show up. Trying to add through integration page just says it is not found on the network. It is visible on my router though, so I know it is there.

@mnoorenberghe
Copy link
Contributor

Trying to add through integration page just says it is not found on the network.

Can you attach a screenshot of this… I don't know what you mean. 72.1 has the bugfix related to this so it should work. I also don't use discovery.

@cmacnichol
Copy link

Sure, I will get it up later tonight. Only thing that might impact this, is that I did a downgrade from 73.1 to 72.1 after finding the DHT issue. Not sure if it retained any of that.

On the flip side, I am actually going out in a bit to get a new RPI3 B+ to replace my 2B. Going to do from scratch install to correct some mistakes I made when first setting it up. See what happens then.

@hafffe
Copy link

hafffe commented Jul 19, 2018

Anybody know what's the difference between the cast component and the old media-player component? with the old media-player component as mentioned above I can with no problems manually define and add the devices with the old media-player component, but when trying to do the same with the cast component I can't find my devices. also tested to find them with the Integrations feature.

also as mentioned above, I can find my devices on the network. but not in home-assistant.

Running with docker and no network_mode specified.

@dersger
Copy link
Contributor

dersger commented Jul 19, 2018

Doesn't work for me either.

My config:

#discovery:

cast:
  media_player:
  - host: 192.168.123.45

I'm not sure if I'm supposed to click CONFIGURE in Integrations (why should I?), but if I do I get a window with

Aborted

No Google Cast devices found on the network.

Edit with additional info: I run home assistant inside docker without host networking (i.e. without --net=host). It works with the old way of configuring cast.

@ghost ghost assigned balloob Jul 23, 2018
@ghost ghost added the in progress label Jul 23, 2018
@ghost ghost removed the in progress label Jul 23, 2018
@home-assistant home-assistant locked and limited conversation to collaborators Oct 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants