Samsung Smart TV can't play anything via remote access (http)

[Stueck 0]

Hi,

the Samsung client app isn't able to play any video. It is connected via http@8096 (no ssl). Installed via the samsung app store. Connection works (gui content visible)

Router has a port forward from 8096 to 8096 emby server.

Secure connection in server settings is set to disabled.

Samsung emby client shows errors:

1. PLAYER_ERROR_CONNECTION_FAILED, player state: IDLE

2. Playback Error - No compatible streams are currently available

 

Another older Samsung TV UE48J6250  @ 1.0.77 works fine. Also android apps are working with remote connection.

Is there a problem with the app for newer samsung TVs?

Thanks for any help!

 

 

Samsung model number: Samsung Smart TV QE75Q60CAUXXH

Samsung firmware version: T-NKLCDEUC-1402.6 (Tizen 7.0)

Samsung Emby client version: 1.7.0

Emby server version: 4.8.3.0

 

Serverlog: 

Debugging on. Removed Trakt loggings and renamed Movie/folder names

No transcoding logs produced

Log includes tests of three different movies.

 

 

embyserver_renamed.txt

[Luke 42078]

Hi, are you able to try the latest USB install and see how that compares?

https://emby.media/emby-for-samsung-smart-tv.html

[Stueck 0]

Thanks for the fast respond. This is not easily possible as the TV is wall mounted and USB is not accessible. Are there better options?

[Happy2Play 9780]

I would guess this issue is with the older version 1.7.0.

4 hours ago, Stueck said:

Is there a problem with the app for newer samsung TVs?

I guess the question is what version is in the app store as that appears to be a 2023 tv?

 

But once Samsung drops older model support you are forced to USB sideload every 30 days.

[Stueck 0]

I have installed version 1.7.0 which is the latest available in samsung app store on this TV (TV is a 2023 generation TV!) .

Did  you made any changes from 1.7.0 to 1.7.7 which could solve the problem?

Can you predict when Samsung will make the new version available in the app store?

[Happy2Play 9780]

But have no idea and how long Samsung takes to approve app updates.  

[SamES 1057]

I'm not sure why this is not transcoding, but it looks like you have a bitrate set in the client which preventing playback

2024-03-25 10:55:10.813 Info App: Bitrate exceeds DirectPlay limit: media bitrate: 10212125, max bitrate: 7000000
2024-03-25 10:55:10.813 Info App: Bitrate exceeds DirectStream limit: media bitrate: 10212125, max bitrate: 7000000

 

[Luke 42078]

Does removing that get it to play? Not that you should have to, just so we know. Thanks.

[Stueck 0]

Hi,

No, removing the bitrate limit didn't help.

 

embyserver.txt

[Luke 42078]

Hi, are you able to install the latest version via USB and see how that compares?

[SamES 1057]

On 26/03/2024 at 01:29, Stueck said:

Another older Samsung TV UE48J6250  @ 1.0.77 works fine.

Is this older device also using the same remote connection?

[Stueck 0]

On 4/3/2024 at 7:37 AM, Luke said:

Hi, are you able to install the latest version via USB and see how that compares?

No, unfortunately I am not able to install it via USB. Have to wait for a new app store version. Due the wall mount it's not accessible.

 

On 4/3/2024 at 8:02 AM, SamES said:

Is this older device also using the same remote connection?

Yes, same account and remote target

Edited April 7, 2024 by Stueck

[Luke 42078]

OK thanks for the update.

[buymode 0]

 

Ensure your Samsung Smart TV firmware is updated. Check network settings and try using a different device. If the issue persists, contact Samsung support for further assistance.

[Stueck 0]

I have run a few more tests. The connection was previously made via a DynDNS URL. 
When I use the IP, the streaming works. 
It seems to be a problem with the app with DNS resolution (but only for streaming, not for the gui) 

In the meantime, I have also installed a reverse proxy to enable HTTPS/SSL. Unfortunately, this didn't help. I still have to use the IP instead of the URL

Is this a problem with the app or with how the Samsung TV operates DNS resolution?

Edited May 21, 2024 by Stueck

[Stueck 0]

It seems that I have found the solution. 
I have written my DynDNS URL to “external address” and set the public port to 80 and 443 (now via reverse proxy).
I had not previously specified the remote data as I thought this was only required for an SSL certificate via emby.

I don't know if my old setup with port forwarding without reverse proxy and http-only would work now. 

Apparently the Tizen app does not use the server address of the login for streaming (lib listings worked). It worked fine on Android, so I didn't suspect it was due to the “external address”.

Edited May 23, 2024 by Stueck

[Stueck 0]

Oh, I just saw that an app update also landed in the samsung-store recently (May 14). Maybe that was the solution - and not my setup changes.
Anyway, it's working now. 
Many thanks for the help.