Closed idiotzoo closed 2 years ago
Just a bump to prevent this issue automatically closing
Yeah. Still the same for me.
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment š This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!
Just another bump to keep this issue alive
Issues is still reproduced on 3.3.0 version of Aircast Home Assistant add-on
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment š This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!
Problem/Motivation
Essentially re-opening issue 50. It used to be that aircast would discover the chromecast audio devices more or less immediately, now it seems not to find them until aircast is restarted. This makes it far less effective than it once was. Iām not sure when behaviour changed.
Expected behavior
When chromecast audio Is powered on and joins the network, Aircast should quickly discover this And make it available to airplay
Actual behavior
Chromecast is not discovered until aircast is restarted
Steps to reproduce
Power cycle chromecast audio