[Solved] Philips PUS7809 will not connect

[Uppie]

Hi,

my PUS7809 renderer will not connect to UMS. UMS "sees" the IP of the renderer, but UMS is not visible on the TV. Plex and Serviio register immediately and are visible on the TV. Sometimes (after a lot of rebooting of PC and renderer) UMS appears, but very unreliable. Looks a bit the same as viewtopic.php?f=5&t=2985

I've included logs (from 5.0.0b1, logs from 5.0.0. are the same) and the various XML-files the renderer gives when contacting through HTTP.

Thanx for the support and if you need testing, please let me know

Uppie

[Uppie]

Debugging UMS.rar

(26.07 KiB) Downloaded 939 times

and the logs....

[SubJunk]

Hi Uppie, can you please let us know if it's the same with 5.0.0-a1?

[Uppie]

Hi Subjunk,

did a clean install of 5.0.0a1. Basically same results (or lack of ). During the logging period i restarted UMS and also cold-started the TV once. I see some kind of recognition, but no "dialogue" between UMS en TV.

Logs are attached.

Thanx for the effort!

Uppie

ums_dbg_500a1.zip

(19.04 KiB) Downloaded 707 times

[lubo]

I have the same problem, my Philips is 42PFH6309. When install ver.4.4.0 everything work fine. But when install on Linux Server or Windows 8.1 host version 5.0 or 5.01 not see Universal Media Server in DLNA devices. I try with DLNA client form my Android device, and see Media server in network, and may play video files in android device. But my Smart Philips, do not see UMS in the same network.

[infidel]

I see some kind of recognition, but no "dialogue" between UMS en TV

And I see you're already on top of it with philips support . It seems UMS found the PUS7809's split personality confusing:

DEBUG 16:42:23.133 [cling-11] MediaServer found: ... Descriptor: http:/192.168.2.2:49154/nmsDescription.xml
DEBUG 16:42:29.872 [New I/O worker #7] Device at /192.168.2.2 is a MediaRenderer: ... Descriptor: http://192.168.2.2:2870/dmr.xml

See if the patch below fixes it (and post logs either way please). Put the enclosed update.jar next to ums.jar in your UMS program folder, and remove it at the next UMS release:

[attachment removed] - try the patch below.

[lubo]

I try with this update, but not see UMS in my Philips DLNA browser. Attachment content debug.log before placing update, and after, also my UMS.conf. The second log is a device spy log invoking Get Protocol Info.

[infidel]

I try with this update, but not see UMS in my Philips DLNA browser. Attachment content debug.log before placing update, and after

Thx lubo, very helpful . Try this patch (and please post TRACE logs either way):

update-ums-5.0.1-late-recognition2.zip

For ums 5.0.1 only - put update.jar next to ums.jar in your UMS program folder.

(51.76 KiB) Downloaded 1058 times

[lubo]

Thank you infidel for quick reply, now everything is fine.
1, See in main panel Philips TV;
2. See UMS in DLNA browser in my TV;
3. Play mkv file ( with subtitle);

In attachment is my trace log.
I hope that the next version will include the latest patch.
Thnak you

[infidel]

now everything is fine... in attachment is my trace log

Great, patch will be included in the next version !

This isn't actually a TRACE log. Could you please create one manually like so:

• Shut down UMS.
• Edit the file logback.xml in your UMS Program folder, changing <root level> from DEBUG to TRACE (near the end of the file), and save.

  Code: Select all

  	<root level="TRACE">

• Start UMS, play something, and attach your debug.log, which will now include all TRACE messages.