KEF Connect (LSX II) Can’t See Emby DLNA Server – Other Apps Work Fine

[zplusmsz 0]

Hi, I’m having trouble getting Emby to show up in the KEF Connect app via DLNA. I’d appreciate any advice or support.

 

1.Environment

[Emby Server]

• NAS: Asustor NAS (AS3304T)

• IP: 192.168.0.111

• Emby Version: 4.8.11.0 (Premiere)

• “Enable DLNA Play to”: ON

• “Enable DLNA Server”: ON

• Emby app bundled with the NAS is used

 

[Client]

• Speaker: KEF LSX II (Wi-Fi connected / IP: 192.168.0.150)

• App: KEF Connect (iOS and Android)

 

2.Issue

The Emby server does not appear in the list of UPnP servers within the KEF Connect app.

However, the Emby server does appear and function properly in other UPnP-compatible apps such as mconnect.

Additionally, “UPnP Media Server V2” and “MiniDLNA” are successfully detected and playable from KEF Connect.

 

3.Logs

• embyserver01.txt: Log before creating the DLNA profile

• embyserver02.txt: Log after creating the DLNA profile

 

 

embyserver01.txt embyserver02.txt

[Luke 42302]

hi, have you tried restarting the server while kef connect is open?

[zplusmsz 0]

I restarted the Emby Server while KEF Connect was running, but the issue remains the same.

 

embyserver03.txt

[Luke 42302]

Hi, can you try what worked for the user here?

 

[zplusmsz 0]

I tried the suggestions above, but unfortunately the issue still persists.

To verify the situation, I installed MiniDLNA on the same NAS, and KEF Connect detected it immediately — which strongly suggests the issue is related to Emby’s DLNA advertisement or KEF Connect’s DLNA compatibility.

To verify the situation, I installed MiniDLNA on the same NAS, and KEF Connect detected it immediately — which strongly suggests the issue is related to Emby’s DLNA advertisement or KEF Connect’s DLNA compatibility.

Environment:
- NAS: Asustor AS3304T
- Emby Version: 4.8.11.0 (Premiere)
- DLNA Settings: DLNA Server: Enabled, DLNA Play To: Enabled
- Friendly Name: EmbyServer
- KEF Speaker: LSX II
- KEF App: KEF Connect (iOS/Android latest)
- Network Config: Same subnet (192.168.0.x), IPv4, UPnP enabled

What I confirmed:
- mconnect and nPlayer apps can access Emby DLNA server via port 8096 without issues.
- KEF Connect cannot detect Emby, but it can detect MiniDLNA (on the same NAS).
- Emby successfully recognizes the KEF LSX II as a DLNA Renderer, and sends AVTransport control messages to port 16500 on the LSX II.
- Emby and LSX II are on the same subnet (192.168.0.111 and 192.168.0.150 respectively).

Clarification on Ports:
| Port  | Purpose                               | Used By                  |
|-------|---------------------------------------|--------------------------|
| 8096  | Emby DLNA server / Web UI             | Clients like mconnect    |
| 16500 | DLNA Renderer control (AVTransport)   | Emby → LSX II            |

→ Emby’s server side (8096) is working as expected, but KEF Connect seems to ignore or miss the DLNA advertisement.

Log Excerpt (Emby recognizing KEF LSX II):
DLNA Session created for LSX II - LSX II. Description url: http://192.168.0.150:16500/...
POST http://192.168.0.150:16500/Control/LibRygelRenderer/RygelAVTransport

Request:
Is there anything I can do on the Emby side to make it more compatible with KEF Connect?

Is this a known limitation, or something that could be improved in the SSDP/DLNA announcement behavior?

Any suggestions or guidance would be appreciated. Thank you!
 

embyserver.txt

[Luke 42302]

Are you handy with wireshark to try and find the difference compared to minidlna?

[palight 0]

Hi, 

I got the same problem and captured the first connection packets from minidlna and emby as servers with vlc 

Result for minidlna

Quote

User Datagram Protocol, Src Port: 1900, Dst Port: 53652
    Source Port: 1900
    Destination Port: 53652
    Length: 375
    Checksum: 0x862e [unverified]
    [Checksum Status: Unverified]
    [Stream index: 7]
    [Stream Packet Number: 1]
    [Timestamps]
        [Time since first frame: 0.000000000 seconds]
        [Time since previous frame: 0.000000000 seconds]
    UDP payload (367 bytes)
Simple Service Discovery Protocol
    HTTP/1.1 200 OK\r\n
        Response Version: HTTP/1.1
        Status Code: 200
        [Status Code Description: OK]
        Response Phrase: OK
    CACHE-CONTROL: max-age=1010\r\n
    DATE: Mon, 13 Apr 2026 22:42:28 GMT\r\n
    ST: urn:schemas-upnp-org:device:MediaServer:1\r\n
    USN: uuid:4d696e69-444c-164e-9d41-bc2411746e17::urn:schemas-upnp-org:device:MediaServer:1\r\n
    EXT:\r\n
    SERVER: 6.15.3-200.fc42.x86_64 DLNADOC/1.50 UPnP/1.0 MiniDLNA/1.3.3\r\n
    LOCATION: http://192.168.1.181:8200/rootDesc.xml\r\n
    Content-Length: 0\r\n
        [Content length: 0]
    \r\n

Result for Emby

Quote

User Datagram Protocol, Src Port: 1900, Dst Port: 53652
    Source Port: 1900
    Destination Port: 53652
    Length: 346
    Checksum: 0x8612 [unverified]
    [Checksum Status: Unverified]
    [Stream index: 8]
    [Stream Packet Number: 1]
    [Timestamps]
        [Time since first frame: 0.000000000 seconds]
        [Time since previous frame: 0.000000000 seconds]
    UDP payload (338 bytes)
Simple Service Discovery Protocol
    HTTP/1.1 200 OK\r\n
        Response Version: HTTP/1.1
        Status Code: 200
        [Status Code Description: OK]
        Response Phrase: OK
    EXT: \r\n
    DATE: Mon, 13 Apr 2026 22:42:28 GMT\r\n
    CACHE-CONTROL: max-age=7200\r\n
    ST: upnp:rootdevice\r\n
    SERVER: Windows/10.0 UPnP/1.0 EmbyServer/4.5\r\n
    USN: uuid:b37ba2c8-3e87-4bb0-8870-ee5d2fdf78a0::upnp:rootdevice\r\n
    Content-Length: 0\r\n
        [Content length: 0]
    LOCATION: http://192.168.1.182:8096/dlna/b37ba2c8-3e87-4bb0-8870-ee5d2fdf78a0/description.xml\r\n
    \r\n

Let me know if you need other packets, I also captured during browsing of both server content from vlc.

 

[Luke 42302]

18 hours ago, palight said:

Hi, 

I got the same problem and captured the first connection packets from minidlna and emby as servers with vlc 

Result for minidlna

Result for Emby

Let me know if you need other packets, I also captured during browsing of both server content from vlc.

 

Hi, yes I would say please send everything until it stops communicating with Emby Server. Thanks.