I'm trying to work out the reason(s) why some devices appear "disconnected" in the device list (http://{ipaddress}:3000/device).
The cast-web-api is able to display the current status (correct track information) when listing the devices, even though it says it's disconnected.
I also get subscribed events when changing the volume on that device via the Google Home app.
This is the error response for both calls to a disconnected device.
{
"response": "error",
"error": {}
}
Is there any action that I can take to have cast-web-api reconnect to these devices?
I've tried restarting the cast-web-api (docker container) as well as each of the "disconnected" devices, but that hasn't worked.
The devices appear to be functioning properly for anything else.
I'm running version 1.2.1 and autoConnect is enabled in the config.
Hi,
I'm trying to work out the reason(s) why some devices appear "disconnected" in the device list (http://{ipaddress}:3000/device). The cast-web-api is able to display the current status (correct track information) when listing the devices, even though it says it's disconnected. I also get subscribed events when changing the volume on that device via the Google Home app.
However I get an error when either getting the device information (http://{ipaddress}:3000/device/{deviceId}) or when trying to change the volume on that device (http://{ipaddress}:3000/device/{deviceId}/volume/50).
This is the error response for both calls to a disconnected device. { "response": "error", "error": {} }
Is there any action that I can take to have cast-web-api reconnect to these devices? I've tried restarting the cast-web-api (docker container) as well as each of the "disconnected" devices, but that hasn't worked. The devices appear to be functioning properly for anything else.
I'm running version 1.2.1 and autoConnect is enabled in the config.
many thanks,
Cam