I don’t believe there are integrations for those other players so DLNA would be the go.
I don’t know what the URL and other settings would be, Google may help you find the setup instructions for each player.
understood, thank!
that’s what i was unsuccessfully trying before reaching out here…
Im affected with this too.
I have a NEDIS wireless DLNA capable player, which worked fine until now.
https://support.nedis.com/en-us/products/550673394#support
As it is not really common, I’m not able to find any related info.
I’m stuck also now, don’t know, how to make it work again… 
I hear you man
hopefully we will find a little more info as to how the new integration works.
maybe someone will have better luck\knowledge oh how to to make the magic happen soon…
meanwhile, other than KODI, can anyone recommend another windows-base-suitable-dlna-programs with good working integration for HA?
Actually I do not understand, why someone decides to turn the discovery off, when it worked fine for dozens of people…
Because it did not work fine for others. This was answered here:
Basically it’s my fault for raising the issue with discovery and Daikin. It was the straw that broke the camels back.
The beta release that removed it was even named after me.
Sorry.
To be fair I did offer just to remove discovery from my system:
If you had been on the beta version test program you would have had a chance to protest this.
i doubt anyone is blaming you…
just not really sure as to how this new integration communicates with DLNA compatible devices i have on my network (is that’s even an option now…?)
if anyone could clarify it some more - that would be great
Kind of you to say.
It comes down to discovery not always working well for everyone.
I did a bit of searching and the port foobar2000 media server uses by default is 56923. The URL will be the ip address of your PC.
right. No blaming from here too. I just now need a hand to get my device working again…
Have a look at the media server settings in your device to see if you can find the port number it is using.
My Vero4K Kodi box is using port 8080.
In the previous version it was possible to turn on autodiscovery for dlna as option under discovery setting in configuration.yaml. But if I read in this thread the new UI configuration doesn’t offer that option.
Why was it released at this stage when it doesn’t offer at least the same functionality?
This side effect was also not documented as a breaking change.
And most surprisingly the documentation of this integration doesn’t mentioning anything about a URL that you need to provide for each device and how you should get that.
Of course this is not how you should configure this at all in UI… you should be able to:
- pick from a list of devices that were autodiscovered
OR - all the autodiscovered devices are automatically created but turned off by default. And user can manually enable the devices that he needs. Similar as how some router integrations, like FritzBox, handle device discovery.
I really wonder how this unfinished component could have passed all quality control gateways in the release pipeline…
1 Like
This is all, I can find. No ports mentioned. So it gives me the feel like cracking a keylock with 5 digits. That will take a year to find the winning number…
It did have it initially but it was tuned off as I said above: New dlna intedration in 2021.10.1 - #2 by tom_l
I think removing the whole change from the release would then have been a much better decision.
And then rethink and redesign the solution for next month release…
i cant seem to make it works even for kodi - where the port, and ip are well known - and after making sure that it does work from a browser…
i think this new DLNA integration works differently
There’s a setting for DLNA control that must be turned on in Kodi.
ohh i know…
it works gr8 from other DLNA controllers i have on my network… just cant make it work with the new integration
@tom_l My suggestion would be to have a look at the Fritzbox router integration.
There all network devices are autodiscovered and for each device a device_tracker is created but they are turned off by default.
As a user I can pick the devices that I need and turn them on. The rest I can ignore.
The UI is not intended for entering an URL. That is just a kind of “lazy developer” solution. WIth that in mind the configuration could have been better kept in yaml.
You are telling the wrong person. I’m not a developer. Perhaps open a feature request quoting your solution to this:
1 Like
Basically, what happened now is: To make ones things work, other ones things got broken… Good job 
So as I’m already used to it, I will just sit and wait again, until it’s fixed. Luckily, there are more ways to play some music in my bedroom…
I’ve decided not to get frustrated anymore by broken integrations. It just is a part of the game, it seems…