-
Notifications
You must be signed in to change notification settings - Fork 21
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
Support for audio groups #3
Comments
I think using friendly name instead is possible, though the ip address in the MQTT topic is also used for connecting to the chromecast if it has not been discovered yet, meaning that would not work anymore (but you could still implement some sort of cache that would map previously known friendly name to IPs). Regarding the second issue. According to home-assistant-libs/pychromecast#65 pychromecast supports multi-room setups. My educated guess would be that this is because the same IP address is being used for multi-room and single-chromecast devices and there is no special handling build in by now (and I haven't tested this with multi-room setups actually). You could still check if you see log lines beginning with:
If these log lines show the correct properties when streaming to a group, then the problem lies definitely somewhere in the MQTT connector code. |
Update: I talked to a friend who owns a multi-room setup and he controls it successfully via pychromecast. |
I would love for this to be supported as well. In addition I think friendly name as the queue name would be much better when integrating with other solutions. :) Great work! |
@anderssv Hey! I would love that too, but fortunately I currently do not have time to implement this. But if you are willing to implement that function and submit it as a PR I would gladly welcome that. 👍 |
Have proposed a pull request that publishes topics using friendly_name. This also allows groups to be supported. |
At the moment audio groups are not supported because they have the same IP as one of the devices.
Do you think its possible to use the friendly_name instead?
Also the player_state and some other propeties of the single devices are not correct if i stream something to a group (Maybe this is a limitation of pychromecast?).
The text was updated successfully, but these errors were encountered: