DLNA Digital Media Renderer
dlna_dmr
The DLNA Digital Media Renderer integration allows you to control a DLNA Digital Media Renderer, such as DLNA enabled TVs or radios.
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
media_player | Media player (as switches) | Only TVs and receivers get a TV tile; other players show as power and play switches; Needs its own HomeKit Bridge in accessory mode |
What people report
DLNA renderers work locally but quirks in device XML or HTTP handling cause failures. Hegel and some speakers needed library fixes.
- Works1
- Partly works2
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Panasonic Viera 42AS650 | Works Local | Fixed by async_upnp_client upgrade so media playsSaved copyDescription: Upgrade to async_upnp_client==0.14.6, fixing the issue with Panasonic Viera (42AS650) where it does not accept media to be played. Related issue (if applicable): fixes #20749 ## Checklist: - [x] The code change is tested and works locally. - [x] Local tests pass with `tox`. Your PR cannot be merged unless tests pass - [x] There is no commented out code in this PR. If the code communicates with devices, web services, or third-party tools: - [x] New dependencies have been added to the `REQUIREMENTS` variable ([example][ex-requir]). - [x] New dependencies are only imported inside … Excerpt saved from GitHub on 2026-10-23. | PR #22223 · 2019-03 | |
| DLNA renderer speaker | Partly works Local | Local media and TTS failed; speaker HEAD request got HTTP 500Saved copyThe problem If I try TTS or playing a local media file on a DLNA compatible renderer, it doesn't work and shows an error in the log: [code] Right before the `Resource not found` error above, the HA logs show that there's a HEAD request coming in from the speaker and that fails with an HTTP 500 error. I also saw somewhere someone hinting that DLNA renderers might send a HEAD request before sending the GET one. There are several reports around the net about this or related DLNA problems, dating back to 2022: - #81162 - #111078 - Media Cast / DLNA not working with Samsung TVs or Smart Monitors - … Excerpt saved from GitHub on 2026-10-23. | Issue #139580 · 2025-03 | |
| Hegel H190 amp | Partly works Local | Unavailable after firmware upgrade due to empty QPlay XML; library patch proposedSaved copyThe problem Hi guys! Yesterday I upgraded my amp firmware to a recently version (Hegel H190 - was at 5107.29, upgraded to 5117.31) DMR integration is no more working on HA (amp is shown as "unavailable") I tried to delete and re-configure the DMR integration but this didn't fix the problem. The weird thing is, other dmr apps (such as BubbleUpnp) are still working correcly. Looking at log, I can find: `Failed connecting to recently alive device at http:// :38400/description.xml: UpnpXmlParseError('no element found: line 1, column 0')` Comparing the two decription.xml versions (the one that … Excerpt saved from GitHub on 2026-10-23. | Issue #67788 · 2022-03 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local push
Talks to the device on your network, and the device tells Home Assistant the moment something changes.
Found automatically over
- SSDP/UPnP
Details
| Installs (analytics) | 156,200 (22.04%) |
|---|---|
| Added in | Home Assistant 0.76 |
| Set up in the UI | Yes |
| Maintainers | @chishm |
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
