It is recommended that you save a configuration or golden configuration before installing any driver.
On the Crestron Home™ Setup App, select the gear icon on the Blackdove driver instance to be updated. Select the Installer Settings tab. Update the Device Name and License information as needed, then press O.K.
After updating the Installer Settings tab, the Control tab information needs to be refreshed by reentering the user name or the password. Rebooting the Crestron Home™ processor from the Setup App is another valid method to refresh the Control tab information.
You need to register an account on our website and order a license for the Blackdove driver. The license is no-charge and per processor. This is to keep track of how many times the driver has been installed. You may request as many license’s as you have processors.
Make sure the username and password that you put in the driver is correct. Another common reason is the player name doesn’t match what was specified. Make sure the player name that you specified in the driver is spelled exactly (case-sensitive) as the name that was set in the Blackdove phone/tablet app. If you need to update, make sure you reboot the UI and the CH processor (so that the latest settings are loaded). If you have done this and still have no control, check to see if you can control the player in the Blackdove phone/tablet app. If you can not, than remove the device and re-pair. Once you confirm the player can be controlled with the Blackdove phone/tablet app, check the player name and reboot the processor and UI. If you’re still not able to control the player through the official Blackdove app on your phone/tablet, then contact Blackdove for further support.
This is a limitation of the current version of Crestron Home. Crestron has stated in the past that they plan to have the ability to have a custom driver also act as a media source in the future. The more technical reason is that the Blackdove driver is developed using the Extensions framework in Crestron’s SDK and currently the Extensions’s framework doesn’t support triggering media actions.