Mizar 0 Posted December 30, 2018 Posted December 30, 2018 my emby server is up and running well and all my devices detect the emby dlna server. But not so my Samsung TV! I ran out of ideas on how to fix it. I tampered also with the dnla profile for the Samsung smart TV. But that does not change anything. Before I switched to emby I ran Twonky as my media center on the very same device with no change of the network config and the Samsung TV has no problem to detect it. (emby server 3.6.0.81 beta armhf) Can any body help me with this issue?
IceBoosteR 10 Posted December 30, 2018 Posted December 30, 2018 I have found a similar issue, but rather older. https://emby.media/community/index.php?/topic/31942-samsung-smart-tv-no-longer-finding-media-over-dlna/ You could workaround this by installing the Emby app for Samsung. Its more convinient and free to use. Nevertheless, maybe a look in your Emby logfile could show us an error. Just upload it here.
Luke 42078 Posted December 30, 2018 Posted December 30, 2018 Try restarting emby server while the TV dlna app is running.
Mizar 0 Posted December 30, 2018 Author Posted December 30, 2018 Thanks for your answers. Perhaps I am kind of paranoid, but I do not use at all the smart view part of my Samsung TV and, thus, no apps. Moreover, the TV has no access to the Internet. (I learnt that the Samsung TV devices communicate with up to 60(!) internet addresses in the background, telling whoever what you are doing on your TV.) When I ran Twonky, it just appeared as one possible source, i.e., it I could select Twonky when pressing the "Source" button on my remote control. I would have expected that the Emby server also just appears in the sources list after a while. BTW: my router (AVM Fritzbox) also provides a media server which is in the sources list of the TV. So why not Emby? What is special with Emby and the Samsung TV? As said, Emby shows up in all other devices in my home network (smartphones, tablets, internet radios).
Mizar 0 Posted December 30, 2018 Author Posted December 30, 2018 No, sorry. I do not install any app on my TV, because I do not want to use apps at all, as I tried to explain in my last post. But anyway, some sort oft dnla client is running on the TV without having installed any app, because the media server of my router appears in the sources list as did Twonky before. But not so Emby.
IceBoosteR 10 Posted December 30, 2018 Posted December 30, 2018 Mhh I have a Fritz!Box aswell. For me its working. Maybe you have to disable/enable Upnp in your routers config. Nevertheless a restart is sometimes helpful. For the solution with the app: As I said, same router manufacture. I have disabled the internet access for the TV and used the emby app for years. Currently I do switch to the XBOX app for Atmos/DTS:X, but the Samsung App is awesome. In your home network you should be fine. You can control that behaviour with parental control (German: Kindersicherung) so there is no internet access. I saw some traffic still going though (receiver HTTP headers, but thats it...). GL
Mizar 0 Posted December 30, 2018 Author Posted December 30, 2018 Many thanks for your advice. I will try the app. Internet is dissabled for my Samsung Tv with parental control, so it should be safe. But I still wonder why the emby server does not show up in the sources list like Twonky, Fritz!Box Media Server, etc.
IceBoosteR 10 Posted December 31, 2018 Posted December 31, 2018 Many thanks for your advice. I will try the app. Internet is dissabled for my Samsung Tv with parental control, so it should be safe. But I still wonder why the emby server does not show up in the sources list like Twonky, Fritz!Box Media Server, etc. I don't know though. Are you running Emby on docker, physical server, pc or on what device? I mean, in fact that does not matter and on other devices it is running... Maybe a software update for your TV can help, but to be honest, thats only trial and error now....
Luke 42078 Posted December 31, 2018 Posted December 31, 2018 Try restarting the server while the sources list is open.
Mizar 0 Posted December 31, 2018 Author Posted December 31, 2018 When I switch on the TV and open the sources list, it takes quite a while until all network ressources appear in the list. But the Emby server is never recognized. In the dlna section of the emby server configuration there are two settings of timers which I do not really understand. I do not know, how the handshake protocol works. Unfortunatelly in the emby documentation the dlna description is missing completely.
Luke 42078 Posted December 31, 2018 Posted December 31, 2018 Can you please attach the emby server log? thanks.
Mizar 0 Posted January 1, 2019 Author Posted January 1, 2019 Please find attached a server log. Obviously Emby server and my TV (named "Wohnzimmer") talk to each other. I found these lines in the log after I switched on the TV: 2019-01-01 22:01:15.081 Info HttpServer: HTTP GET http://192.168.1.98:8096/dlna/ee0000d99fa842caa114525a6bcfade2/description.xml. UserAgent: SEC_HHP_[TV]Wohnzimmer/1.0 DLNADOC/1.50 2019-01-01 22:01:15.251 Info HttpServer: HTTP Response 200 to 192.168.1.60. Time: 170ms. http://192.168.1.98:8096/dlna/ee0000d99fa842caa114525a6bcfade2/description.xml 2019-01-01 22:01:17.494 Info HttpServer: HTTP GET http://192.168.1.98:8096/dlna/ee0000d99fa842caa114525a6bcfade2/contentdirectory/contentdirectory.xml. UserAgent: SEC_HHP_[TV]Wohnzimmer/1.0 DLNADOC/1.50 2019-01-01 22:01:17.632 Info HttpServer: HTTP Response 200 to 192.168.1.60. Time: 138ms. http://192.168.1.98:8096/dlna/ee0000d99fa842caa114525a6bcfade2/contentdirectory/contentdirectory.xml 2019-01-01 22:01:25.990 Info HttpServer: HTTP GET http://192.168.1.98:8096/dlna/ee0000d99fa842caa114525a6bcfade2/description.xml. UserAgent: SEC_HHP_[TV]Wohnzimmer/1.0 DLNADOC/1.50 2019-01-01 22:01:25.997 Info HttpServer: HTTP Response 200 to 192.168.1.60. Time: 8ms. http://192.168.1.98:8096/dlna/ee0000d99fa842caa114525a6bcfade2/description.xml 2019-01-01 22:01:26.967 Info HttpServer: HTTP GET http://192.168.1.98:8096/dlna/ee0000d99fa842caa114525a6bcfade2/contentdirectory/contentdirectory.xml. UserAgent: SEC_HHP_[TV]Wohnzimmer/1.0 DLNADOC/1.50 2019-01-01 22:01:26.974 Info HttpServer: HTTP Response 200 to 192.168.1.60. Time: 7ms. http://192.168.1.98:8096/dlna/ee0000d99fa842caa114525a6bcfade2/contentdirectory/contentdirectory.xml 2019-01-01 22:02:01.329 Info Dlna: DLNA Session created for [TV]Wohnzimmer - UE32H6410 But the sources list is not updated afterwards (in contrast to, e.g., Fritz!Box Media Server) Is perhaps something wrong with the description.xml? 2019-01-01 215228.log.txt
IceBoosteR 10 Posted January 2, 2019 Posted January 2, 2019 Wow, thats interesting. Even a DLNA session was established. I am out of ideas... Have you the latest firmware of your TV?
Luke 42078 Posted January 2, 2019 Posted January 2, 2019 The dlna session was for the play to feature. So the server detects the TV, but not the other way around.
Luke 42078 Posted January 2, 2019 Posted January 2, 2019 Is perhaps something wrong with the description.xml? Yes it is possible.
Mizar 0 Posted January 2, 2019 Author Posted January 2, 2019 I update the TV software on a regular basis.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now