-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
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
Comments
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:
Edit 2: |
Having the same issue. Looks like this was also brought up under Hass.io as an issue. Seems to mention the cause as well. |
Did you enable the Cast component by going to the Integrations page? |
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.
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. |
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. |
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. |
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. |
Doesn't work for me either. My config:
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
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. |
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:
and:
Traceback (if applicable):
Additional information:
If I use the old way of adding this devices:
It is available in Home Assistant, but gives this warning on startup:
The text was updated successfully, but these errors were encountered: