Open caco3 opened 2 years ago
@caco3 I'm in the same boat, the API definitely changed as a CastInfo is required. Unfortunately due to issue #290 client side code can't determine which API to use other than by using requirements file.
See the examples directory, I believe I saw a search demo that has ip/hostname filtering - but I suspect that may not work with your network setup as it appears to be a filter rather than a pointer to go check this address.
You might be able to create a dummy CastInfo object?
This just started happening to me today on 1st gen chromecasts. I have two and neither are found by pychromecast. The pychromecast system hasn't changed, seems something changed on the chromecast.
EDIT: Just as suddenly as it stopped, it started working again.
Today again, it has stopped working. I've rebooted the system, tried pychromecast on other machines, nothing has been working. The network is working fine as far as I know. I would really like to know what is causing this intermittent behavior.
I had a script working fine by connecting directly by IP:
This work fine with pychromecast
7.7.1
.Now I tried to update to update to the latest version (
11.0.0
). I learned that I need to connect differently, but it doesn't find the chromecast anymore:So am I doing something wrong or is it broken?
I tested the
discovery_example.py
example and it works fine:How ever I do NOT want to rely on mDNS!
Notes:
-net=host
already).