LG NanoCell on Latest WebOS - Doesn't See UMS

[Tizzam]

Hello...

Just got a new LG TV 65NANO75. WebOS is updated to the latest version. I just updated with a clean install of UMS v13.9.0. The TV's media player sees everything else I have as a media server (NAS, Windows OS, etc.) but it does not see UMS.
-Not the firewall. Turned it off to test, same results.
-Not the connection as I forced it to my NIC, when I found "Force network interface" and UMS sees the TV
-Not the subnet. Both on are 10.23.1.x and are even on the same switch

I found this in the log:

Code: Select all

21:52:09 DEBUG UPnP (JUPnP) services are online, listening for media renderers
21:52:09 DEBUG task ended
21:52:09 DEBUG Matched media renderer "LG TV 2023+" based on dlna details "[LG] webOS TV NANO75UQA 10.23.1.59 uuid:7c79ea4c-2904-851d-e862-c6ec736b313b LG Electronics. LG TV 1.0 LG WebOSTV DMRplus http://www.lge.com "
21:52:09 DEBUG Reading RendererName: "LG TV 2023+" (default: "Unknown renderer")
21:52:09 DEBUG Adding status button for [LG] webOS TV NANO75UQA
21:52:09 DEBUG Reading RendererIcon: "lg-lb6500.png" (default: "unknown.png")
21:52:09 DEBUG Created playback timer for [LG] webOS TV NANO75UQA
21:52:09 DEBUG New renderer found: "[LG] webOS TV NANO75UQA" with dlna details: {friendlyName=[LG] webOS TV NANO75UQA, address=10.23.1.59, udn=uuid:7c79ea4c-2904-851d-e862-c6ec736b313b, manufacturer=LG Electronics., modelName=LG TV, modelNumber=1.0, modelDescription=LG WebOSTV DMRplus, manufacturerURL=http://www.lge.com, modelURL=}
21:52:09 DEBUG Adding device: urn:schemas-upnp-org:device:MediaRenderer:1 (RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:7c79ea4c-2904-851d-e862-c6ec736b313b, Descriptor: http://10.23.1.59:1764/, Root: true
21:52:09 DEBUG Subscribing to AVTransport service on [LG] webOS TV NANO75UQA
21:52:09 DEBUG Subscribing to ConnectionManager service on [LG] webOS TV NANO75UQA
21:52:09 DEBUG Subscribing to RenderingControl service on [LG] webOS TV NANO75UQA
21:52:09 DEBUG Created upnp player for [LG] webOS TV NANO75UQA
21:52:09 DEBUG Subscription established: RenderingControl on [LG] webOS TV NANO75UQA
21:52:09 DEBUG Subscription established: AVTransport on [LG] webOS TV NANO75UQA
21:52:09 DEBUG Subscription established: ConnectionManager on [LG] webOS TV NANO75UQA
21:52:10 DEBUG Matched media renderer "LG WebOS TV" based on dlna details "[LG] webOS TV NANO75UQA 10.23.1.59 uuid:071d58db-eeb7-df78-d4aa-b683147119c1 LG Electronics LG Smart TV 65NANO75UQA  http://www.lge.com http://www.lge.com"
21:52:10 DEBUG Reading RendererName: "LG WebOS TV" (default: "Unknown renderer")
21:52:10 DEBUG Adding status button for [LG] webOS TV NANO75UQA
21:52:10 DEBUG Reading RendererIcon: "lg-lb6500.png" (default: "unknown.png")
21:52:10 DEBUG Renewing subscriptions to 
21:52:10 DEBUG Subscribing to webos-second-screen-3000-3001 service on [LG] webOS TV NANO75UQA
21:52:10 DEBUG Created playback timer for [LG] webOS TV NANO75UQA
21:52:10 DEBUG New renderer found: "[LG] webOS TV NANO75UQA" with dlna details: {friendlyName=[LG] webOS TV NANO75UQA, address=10.23.1.59, udn=uuid:071d58db-eeb7-df78-d4aa-b683147119c1, manufacturer=LG Electronics, modelName=LG Smart TV, modelNumber=65NANO75UQA, modelDescription=, manufacturerURL=http://www.lge.com, modelURL=http://www.lge.com}
21:52:10 DEBUG Adding device: urn:schemas-upnp-org:device:Basic:1 (RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:071d58db-eeb7-df78-d4aa-b683147119c1, Descriptor: http://10.23.1.59:1045/, Root: true
21:52:10 DEBUG Subscribing to webos-second-screen-3000-3001 service on [LG] webOS TV NANO75UQA
[color=#BF0040]21:52:10 DEBUG Subscription failed: webos-second-screen-3000-3001 on [LG] webOS TV NANO75UQA:  HTTP response was: 412 Precondition Failed
21:52:10 DEBUG Subscription failed: webos-second-screen-3000-3001 on [LG] webOS TV NANO75UQA:  HTTP response was: 412 Precondition Failed[/color]

I have search all over the settings on the TV, and there are none regarding media servers.

Not sure what to do. Let me know if I need to add any other info.

Thanks,
Tizz

[mik_s]

Could you post your logs so I can see what is happening? See the link in my sig.

[Tizzam]

Here ya go.

ums_dbg_2024-04-25-18-36.zip

(327.7 KiB) Downloaded 17 times

[Tizzam]

I see the log has been dl'ed 14 times....any suggestions?

Right now, I have to re-rip my files and put them on a NAS...I would love to stream again...thanks!!

Tizz

[mik_s]

Sorry I could not reply sooner, been a bit busy. The bots would be responsible for all the downloads.

The original log snippet you posted was for the second screen function of the TV. As UMS is not a screen that will play from the TV then this will fail so this is normal.

I did see a problem with the Netty stream server not starting as the address is already in use. This is a little different that what I usually see for this so it may be due to changes in this version. I know work is being done to use Jetty over Netty for networking stuff but this is as much as I know. Maybe this has broke something but not sure if any of these changes made it to this version

Code: Select all

org.jupnp.DefaultUpnpServiceConfiguration Thread terminated net.pms.network.mediaserver.jupnp.transport.impl.NettyStreamServer@1b96daeb abruptly with exception: org.jupnp.transport.spi.InitializationException: Could not initialize NettyStreamServer: org.jboss.netty.channel.ChannelException: Failed to bind to: /10.23.1.116:5001
org.jupnp.DefaultUpnpServiceConfiguration Root cause: java.net.BindException: Address already in use: bind
net.pms.util.SystemErrWrapper Exception in thread "jupnp-stream-server 1" org.jupnp.transport.spi.InitializationException: Could not initialize NettyStreamServer: org.jboss.netty.channel.ChannelException: Failed to bind to: /10.23.1.116:5001
net.pms.util.SystemErrWrapper Caused by: org.jboss.netty.channel.ChannelException: Failed to bind to: /10.23.1.116:5001
net.pms.util.SystemErrWrapper Caused by: java.net.BindException: Address already in use: bind

I have seen that sometimes when switching to trace mode to do logs that UMS can restart before the previous process has closed and still holding onto the address/port so this may be a red herring. See if this error appears in new logs. To eliminate the possible slow closing issue you can force UMS to be in trace mode on startup by editing UMS.conf when it is not running and setting

Code: Select all

log_level = TRACE

I do see that UMS is detecting your LG TV So it should be appearing in UMS on the GUI.

Code: Select all

New renderer found: "[LG] webOS TV NANO75UQA" with dlna details: {friendlyName=[LG] webOS TV NANO75UQA, address=10.23.1.59, udn=uuid:071d58db-eeb7-df78-d4aa-b683147119c1, manufacturer=LG Electronics, modelName=LG Smart TV, modelNumber=65NANO75UQA, modelDescription=, manufacturerURL=http://www.lge.com, modelURL=http://www.lge.com}

When one device can see the other but not the other way round it is usually a something to do with the network configuration, or something like a firewall/AV could be blocking it, but I know little about about networking besides the basics to be of much help with this.