[Issue]: Duplicate DLNA entries #3602

New issue

Closed

opened 2025-12-21 22:27:37 +01:00 by backuprepo · 1 comment

backuprepo commented

2025-12-21 22:27:37 +01:00

Owner

Originally created by @rmburg on GitHub (Feb 13, 2022).

Please describe your bug

One of the smart TVs in our network is discovered as a new DLNA device on every scan, leading to this device being listed multiple times in the device list.
See the attached screenshot and log excerpt.

Jellyfin Version

10.7.7

if other:

No response

Environment

- OS: Ubuntu Server
- Virtualization: Docker
- Clients: Browser, presumably others
- Browser: Firefox
- FFmpeg Version:
- Playback Method:
- Hardware Acceleration: none
- Plugins: none
- Reverse Proxy: none
- Base URL: none
- Networking: host
- Storage: local

Jellyfin logs

[2022-02-13 00:59:28.437 +00:00] [INF] [98] Emby.Dlna.DlnaManager: No matching device profile found. The default will need to be used.
FriendlyName:Fernseher Schlafzimmer
Manufacturer:SmartTV
ManufacturerUrl:http://www.smarttv.com
ModelDescription:#CAP#
mac=18300cf994a2
macWifi=3032350c0286
macEthernet=18300cf994a2
ip=192.168.178.113
region=4
country=CZE
model_name=43A519EEVS
tv_version=V0000.01.00L.L1103
language=eng
transport_protocol=1140
emanual=0
network_wakeup=1
voice=1
cap=0
mqttport=36669

ModelName:Renderer
ModelNumber:1.0
ModelUrl:http://www.smarttv.com
SerialNumber:

[2022-02-13 00:59:28.437 +00:00] [INF] [98] Emby.Dlna.Main.DlnaEntryPoint: DLNA Session created for "Fernseher Schlafzimmer" - "Renderer"

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

Code of Conduct

I agree to follow this project's Code of Conduct

Originally created by @rmburg on GitHub (Feb 13, 2022). ### Please describe your bug One of the smart TVs in our network is discovered as a new DLNA device on every scan, leading to this device being listed multiple times in the device list. See the attached screenshot and log excerpt. ### Jellyfin Version 10.7.7 ### if other: _No response_ ### Environment ```markdown - OS: Ubuntu Server - Virtualization: Docker - Clients: Browser, presumably others - Browser: Firefox - FFmpeg Version: - Playback Method: - Hardware Acceleration: none - Plugins: none - Reverse Proxy: none - Base URL: none - Networking: host - Storage: local ``` ### Jellyfin logs ```shell [2022-02-13 00:59:28.437 +00:00] [INF] [98] Emby.Dlna.DlnaManager: No matching device profile found. The default will need to be used. FriendlyName:Fernseher Schlafzimmer Manufacturer:SmartTV ManufacturerUrl:http://www.smarttv.com ModelDescription:#CAP# mac=18300cf994a2 macWifi=3032350c0286 macEthernet=18300cf994a2 ip=192.168.178.113 region=4 country=CZE model_name=43A519EEVS tv_version=V0000.01.00L.L1103 language=eng transport_protocol=1140 emanual=0 network_wakeup=1 voice=1 cap=0 mqttport=36669 ModelName:Renderer ModelNumber:1.0 ModelUrl:http://www.smarttv.com SerialNumber: [2022-02-13 00:59:28.437 +00:00] [INF] [98] Emby.Dlna.Main.DlnaEntryPoint: DLNA Session created for "Fernseher Schlafzimmer" - "Renderer" ``` ### FFmpeg logs _No response_ ### Please attach any browser or client logs here _No response_ ### Please attach any screenshots here ![screenshot](https://user-images.githubusercontent.com/42248344/153770018-4540040b-da68-4d15-9dad-e44f7ab98b11.png) ### Code of Conduct - [X] I agree to follow this project's Code of Conduct

backuprepo

2025-12-21 22:27:37 +01:00

closed this issue
added the
stale

bug
labels

backuprepo commented

2025-12-21 22:27:42 +01:00

Author

Owner

@jellyfin-bot commented on GitHub (Jun 14, 2022):

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.

If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.

This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.

@jellyfin-bot commented on GitHub (Jun 14, 2022): This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments. If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label. This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on [Matrix or Social Media](https://docs.jellyfin.org/general/getting-help.html).

backuprepo referenced this issue

2025-12-22 07:29:06 +01:00

[PR #3602] [MERGED] Fix username case change #9448

backuprepo referenced this issue

2025-12-22 07:37:39 +01:00

[PR #4113] [CLOSED] Fix chromecast behind reverse proxy #9710