Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disconnected devices #145

Open
Oldjuju opened this issue Nov 23, 2020 · 0 comments
Open

Disconnected devices #145

Oldjuju opened this issue Nov 23, 2020 · 0 comments

Comments

@Oldjuju
Copy link

Oldjuju commented Nov 23, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant