yes, that is correct. it returns the version of the server that is running.
Is the account that you have linked with the speaker the same one that you used when you went to the Google Developer console? That is the only reason why it wouldn’t authorize you to use the device.
The service manager is actually running on ST. If you are referring to the NodeJS server, that must be running 24/7 as the ST device sends it’s commands to your NodeJS server which sends the commands to your speakers. Otherwise it won’t work. The Service Manager App in ST is used to add devices but that is only in ST that can’t be installed on your adndroid phone. It must be on your hub.
Hi Ryan,
Yes as far as I know it’s the same account. Generally only use this email. Anyway to double check?
Ian Smith
Realtor®, ABR, BBM
Managing Associate Broker / Sales Partner
Cowan-Smith Home Selling
Coldwell Banker Supercity Realty
902-430-5610
Yes, you can see what device is authorized for your google home speaker in the Google Home app. And if you only have one google account, that would have been the one you used to create your account when you followed the steps to activate google on the server, correct?
I am having trouble adding my speakers. I have the ip address where its running but when I search for devices it can’t find anything. What could be the problem?
Hi.
I have about 10 chromecast enabled speakers connected to the ST hub through a Windows PC. It works flawlessly most of the time, but if it hasn’t been used for a few hours, then the Desktop API times out with a “Uncaught Error: Device timeout” message on the log, and will not cast anything until the Desktop API has been manually refreshed.
Any help on this would be much appreciated?
Today something strange happened, one of my displays that was working perfectly stopped refreshing. I tried readding it, but now I can’t even open it’s device page on smartthings because it crashes the app when I do it.
In the logs all I get is this:
2019-09-06T11:36:48.495Z a02da50054e3010eb487931b3d6028b7 CastReceiver.connect(): castDevice.castConnectionReceiver.client error: Error: connect EHOSTUNREACH 192.168.1.11:8009
Any idea why this specific device would be “Unreachable”?
Thank you!
edit: I changed the DHCP reservation ip for that device and it’s connecting again.
I’m using the graphic user interface. Used to be that when I clicked the “x” in the top right, it would minimize to the taskbar but stay online. For the past week, however, when I click the “x”, it minimizes but also goes offline. If I leave the window open, it stays online. I want to be able to minimize it to the taskbar but have it stay online. Not sure how to troubleshoot this.
Hello,
i have installer web-cast 1.2.1 and using webcore i can send text notification on Google Home. I need to execute a notification mp3 on Google Home using webcore and web-cast. I have put the mp3 file on my dropbox and create a pubblic link.
There is a way for reproduce this file mp3 on dropbox directly on Google Home using webcore?
I have never been able to use Drop Box for this since it does not provide a direct link to the file but instead to a dropbox web page that allows the user to save it to their drop box account or download the file directly. What you have to have is a direct file link which allows the file to be downloaded directly from the link, without any other clicks. The easiest solution I found for this was GitHub. Using the github “raw file” link, you put that URL in the first parameter for the command “Play Track” and bingo…it plays your MP3.
thank you for you feedback. I will try.
EDIT:
I tried and go very well!!! -thanks.
Just wondering - is there a different device I need to select after setting up the broadcast feature? I selected all speakers but it continues to use cast/TTS. Not sure if I need to setup a new DTH but the instructions didn’t seem to specify that?
I am having the same issue as ruxban. I installed the cast-web-api-desktop for Windows and running it with the default IP 127.0.0.1 . Created 2 device handlers and one SmartApp. When I tap Discover Devices in the SmartApp, it spins briefly and doesn’t even go to the next screen. In the logs I see that it does see all my devices. Test API connection doesn’t do anything either. 127.0.0.1:3000 in the browser returns {“castWebApi”:“v1.2.1”}. 127.0.0.1:3000/getdevices returns Cannot GET /getDevices. If I change the IP to 192.168.x.x, I get to the next screen when I try to discover devices, but no devices found. Still can see all devices on the log. 192.168.x.x:3000 in the browser is not connecting.
Tried the nodejs command line version. Tried removing everything and installing again. Same as ruxban, I had the command line version installed before and working.
Does anybody have any thoughts on what else I can try?
Hello. Is there away to adjust the volume? The volume is to loud and I would really like to turn it down when say a contact opens.
Getting this error message on my Android phone?
TypeError: Object.values is not a function
at TTLObject.start (/storage/emulated/0/cast-web-api/node_modules/mdns-cast-browser/ttl.js:17:44)
at Device (/storage/emulated/0/cast-web-api/node_modules/mdns-cast-browser/device.js:13:19)
at CastBrowser.foundDevice (/storage/emulated/0/cast-web-api/node_modules/mdns-cast-browser/cast-browser.js:136:20)
at EventEmitter. (/storage/emulated/0/cast-web-api/node_modules/mdns-cast-browser/cast-browser.js:88:11)
at emitTwo (events.js:106:13)
at EventEmitter.emit (events.js:191:7)
at Socket. (/storage/emulated/0/cast-web-api/node_modules/multicast-dns/index.js:49:43)
at emitTwo (events.js:106:13)
at Socket.emit (events.js:191:7)
at UDP.onMessage (dgram.js:548:8)
2019-10-06 11:17:28 : pid 32147 exited
with code : 1 / signal : 0
I’m getting the same issue as a few others, server says its online, doing a test connection in the smart app says its connected, but when trying to discover devices in the smart app nothing gets found. Any ideas?
Hey @vervallsweg,
I am using your cast-web-api in my automation project to be able to test CC playback session.
I used v1.0.2(0). I could get full info about playback on CC receiver using /getMediaStatus that is now not available in v1.2.1.
Could you please assist me in how I can get the following info about current playback on CC receiver:
Just want to clarify before I go through the hassle of setting this up:
Once set up, do they show as speakers in the new smartthings app?
Nop, in my installation, no
And I was not able to send a request to GH as “Hey Google, tell me a joke”
Yes, though the UI is basic, it does not show your presets. However, the speakers are available for use in Automations like Speaker Companion in the New App.