Cheers mate, appreciate it
-
pimatic-chromecast
-
Really cool plugin, especially with the possibility to cast text to the Chromecast devices. I ran there in a problem with my network setup. My pimatic installation is proxied through a fritz box with port forwarding. Therefore I am not able to define a “hostname” property in my config. If I do, then pimatic will try to bind to this address and fail. Therefore I would like to have a setting property in the plugin config to define the hostname and port that the TTS interface can use. Using the global settings is of course the best way in most setups, but not with mine.
I worked around the problem my hard coding my desired values in the chromecast.coffee source file.Thanks for integrating this feature request or guiding me to a better way!
-
@frostedkiwi
Interestingly enough, i tested it with a chromecast Hdmi-Stick 1. Gen and the plugin works as it should. Just to let you know. I will try to get my hands on a second CC audio to go into further testing. -
Nope, got a second CC-Audio ans it has the same issue. Doesn’t update when nothing is playing anymore. Still works fine with the hdmi stick…
-
I’ve just published v1.2.0 which contains the following additions:
- Extra error logging when debug option is enabled in plugin @suchalaugh
- Custom hostname and port option for TTS in plugin settings @carlptr
- Added CurrentApp attribute which contains the active app on the Chromecast device
-
@frostedkiwi very cool, thanks!
-
@frostedkiwi
Cheers for that, unfortunately it doesn’t seem to bring me any closer to this.Here is the output of this after restarting pimatic:
(Please note that it’s perfectly fine that the Chromecast HDMI is not responding as it’s currently without power)At 22:41 i started to stream music from spotify alternately to Chromecast Audio Zimmer and Chromecast Audio Küche, it doesnt seem to appear anywhere in the debug log.
-
@frostedkiwi said in pimatic-chromecast:
- Custom hostname and port option for TTS in plugin settings @carlptr
I found a small bug and created a pull request to fix it: https://github.com/FrostedKiwi/pimatic-chromecast/pull/1
-
Please support resolving variables when casting texts: https://github.com/FrostedKiwi/pimatic-chromecast/issues/2
Thank you in advance!
-
Both issues have been fixed in 1.2.2
-
I’ve just pushed v1.3.0 which has two changes:
- Support for Chromecast groups
- Fix for a bug where the devices would not go to a stopped state properly (reported by @suchalaugh)
-
This does fix it indeed, cheers mate, appreciate it