This plug-in is designed to interface Homeseer with any Google Chromecast or any device with Chromecast Built-in (Google Home, Android TV, etc...)
INSTALLATION / CONFIGURATION
System Requirements:
Plugin Installation:
Download and install from the updater ("Media" section), or download package from the Beta Testing thread and follow instructions to install.
Note: On Linux, if you have Mono.CSharp.dll and CSScriptLibrary.dll in the root HomeSeer folder you must move them to the bin folder. (This problem is already fixed on recent HS3 versions)
Plugin Configuration
Start the plugin from the "PLUG-INS > Manage" page and go to the config page "PLUG-INS > Chromecast > Config". If everything is ok, you should see one line for each Chromecast the plugin has detected, as well as one line for each group.
The Test button lets you check if each chromecast is working as expected by sending to it a short announcement message
The Chromecast plug-in acts as a "Speak Proxy", meaning that Homeseer sends every speak action (i.e TTS) to the plug-in so that it can send it to the chromecasts. If you have another HS plugin that behave as a Speak Proxy you may need to untick the "Forward speak events to HS Speakers" checkbox, otherwise both plugins will forward the same speak action to the HS speakers and you will hear it twice.
To troubleshoot any problem set the "Log Level" to Debug or enable "Log To File" and set the "File Log Level" to Debug. In the first case the logs are written the HS logs database in the second case the logs are written to the file Logs/Chromecast.txt
If for some reason the plugin does not automatically discover your chromecasts, you can manually add them:
Edit Config/Chromecast.ini, and add something like the following lines in the [CHROMECASTS] section
abcd1234 is supposed to be the id of the chromecast, you can use any alphanumeric string as long as it is different for each chromecast.
Then disbale/enable the plugin, you should now see the device in the config page.
INSTALLATION / CONFIGURATION
System Requirements:
- This plugin is for HS3 or HS3PRO. It works with both Windows and Linux versions
- .NET Framework 4.5.1 or later, or mono 4.x needs to be installed on your Homeseer machine
- To auto discover Chromecasts, this plugin needs a Zeroconf implementation (i.e Bonjour) to run on your HomeSeer server.
On Windows this is the Apple Bonjour service, if you have installed iTunes (or most of other Apple software), it should already be installed.
If it isn't, you can download it from the following links:
64bits version: https://www.dropbox.com/s/a0lhdxpbd19go4i/Bonjour64.msi
32bits version: https://www.dropbox.com/s/dkoi00zvlhxx2cn/Bonjour.msi
On Linux this is the Avahi daemon. If it is not already installed and running you need to install the avahi-daemon package. On a Debian like distribution the command to install the package is
Code:sudo apt-get install avahi-daemon
Plugin Installation:
Download and install from the updater ("Media" section), or download package from the Beta Testing thread and follow instructions to install.
Note: On Linux, if you have Mono.CSharp.dll and CSScriptLibrary.dll in the root HomeSeer folder you must move them to the bin folder. (This problem is already fixed on recent HS3 versions)
Code:
sudo mv /usr/local/HomeSeer/Mono.CSharp.dll /usr/local/HomeSeer/bin/Mono.CSharp.dll sudo mv /usr/local/HomeSeer/CSScriptLibray.dll /usr/local/HomeSeer/bin/CSScriptLibrary.dll
Start the plugin from the "PLUG-INS > Manage" page and go to the config page "PLUG-INS > Chromecast > Config". If everything is ok, you should see one line for each Chromecast the plugin has detected, as well as one line for each group.
The Test button lets you check if each chromecast is working as expected by sending to it a short announcement message
The Chromecast plug-in acts as a "Speak Proxy", meaning that Homeseer sends every speak action (i.e TTS) to the plug-in so that it can send it to the chromecasts. If you have another HS plugin that behave as a Speak Proxy you may need to untick the "Forward speak events to HS Speakers" checkbox, otherwise both plugins will forward the same speak action to the HS speakers and you will hear it twice.
To troubleshoot any problem set the "Log Level" to Debug or enable "Log To File" and set the "File Log Level" to Debug. In the first case the logs are written the HS logs database in the second case the logs are written to the file Logs/Chromecast.txt
If for some reason the plugin does not automatically discover your chromecasts, you can manually add them:
Edit Config/Chromecast.ini, and add something like the following lines in the [CHROMECASTS] section
Code:
[CHROMECASTS] abcd1234###name=Living Room abcd1234###type=Google Home abcd1234###ipaddress=192.168.1.150 abcd1234###online=True
Then disbale/enable the plugin, you should now see the device in the config page.
Comment