No Option to Stop Stream on Dashboard?

[ZLuckyTraveler 0]

There is no option to stop a stream only for some devices for some reason. Why is it can stop some of them, but not al?

 

[rbjtech 5284]

Are these local or remote clients ?

If remote - are you using a reverse proxy ?

It's likely that 'websockets' are not enabled somewhere on your networking - and it's those that control the ability to remote control the clients.

[ZLuckyTraveler 0]

1 hour ago, rbjtech said:

Are these local or remote clients ?

If remote - are you using a reverse proxy ?

It's likely that 'websockets' are not enabled somewhere on your networking - and it's those that control the ability to remote control the clients.

Yes these are remote clients.

Well I can stop streams for other devices without issue, it seems that is only certain devices which cannot is the confusing part,  because if websockets wasn't enabled then it'd be for all streams that couldn't be stopped.

Edited September 24, 2023 by ZLuckyTraveler

[Luke 42083]

Hi, Some devices require the web socket connection in order to use remote control features, and some just don't support it at all (but most do).

[ebr 16187]

20 hours ago, ZLuckyTraveler said:

because if websockets wasn't enabled then it'd be for all streams that couldn't be stopped.

Each device has its own connection on its end.  That is where the support is either there or not (or being blocked perhaps by something on that end).

[cochize1 55]

Not to start the new topic... I sometimes have this issue of not being able to stop remote stream on some clients. I am behind reverse proxy (not the official pinned guide, just Synology reverse proxy) and I have these websockets enabled. Should I be blaming the client then?

[Luke 42083]

2 hours ago, cochize1 said:

Not to start the new topic... I sometimes have this issue of not being able to stop remote stream on some clients. I am behind reverse proxy (not the official pinned guide, just Synology reverse proxy) and I have these websockets enabled. Should I be blaming the client then?

Hi, the explanations are already in this topic. Did you see them and go through them?

[hthgihwaymonk 34]

On 9/25/2023 at 5:46 AM, ebr said:

Each device has its own connection on its end.  That is where the support is either there or not (or being blocked perhaps by something on that end).

Regarding which devices support websockets -
Is there a list available that shows which devices do not support websockets?
Or is it just trial and error on our end to find out ?

[Luke 42083]

3 hours ago, hthgihwaymonk said:

Regarding which devices support websockets -
Is there a list available that shows which devices do not support websockets?
Or is it just trial and error on our end to find out ?

Pretty much everything does except smart tv's and roku. However your web server, if running a reverse proxy, it could be closing the socket after a period of time. Emby apps won't open a new one until use them next.

Additionally, even the devices that support it, most of them will also close it to save battery when the app is idling.

[hthgihwaymonk 34]

So for the rokus or smart tvs, once a user clicks play, the server basically has no control of the stream (being able to stop it).
As it can not be stopped using websockets.

Is there another api endpoint that can stop the stream on rokus or smart tvs ?
I get the user can simply press play again, but that's a different issue question.

[Luke 42083]

2 minutes ago, hthgihwaymonk said:

So for the rokus or smart tvs, once a user clicks play, the server basically has no control of the stream (being able to stop it).
As it can not be stopped using websockets.

Is there another api endpoint that can stop the stream on rokus or smart tvs ?
I get the user can simply press play again, but that's a different issue question.

There's no way to send the apps an instruction, if that's what you mean.

there's currently no way to abruptly pull the plug on a stream. We can add that, but there's also no telling how the video players will handle it. The user might get an error message, or in the worst case scenario on Roku it could lock up or crash the app. Obviously we have our own error handling and friendly error messages, but it's all dependent on the Roku raising an error that we can intercept. Sometimes it doesn't and just blows up instead.

[hthgihwaymonk 34]

thanks @Lukefor the follow-up reply.

Quote

or in the worst case scenario on Roku it could lock up or crash the app

I don't really see that as a deal breaker

I think for those clients I'll just track the transcoding and if the transcoding continues for x minutes I'll just remove the 4K folder from the share using the api.
That will get my brother-in-laws attention the next time he tries to stream and the 4K content isn't in the dropdown.
Then he'll have to finally change his settings 

Edited October 5, 2023 by hthgihwaymonk

[ebr 16187]

Hi.  Just FYI, you can control the Roku app on your local network - just not remotely.  This is a security measure by Roku.  They will not allow any external app to send a message into the Roku device.