I’ve had the plenty of success running the amplipi with DLNA as the stream. I was working with the Home Assistant Universal Media Player and when the stream is set to Spotify, I’m able to grab the song name and title, and see the coverart in Home Assistant. However, with the DLNA stream active, I notice the only thing I see on the amplipi interface is “DLNA.” Is it possible for the DLNA process to accept and use the metadata in the same way? I can access this from my music server’s api separately and bring that into Home Assistant, but it would be much more straightforward if the amplipi was the source for all of this information. Or is this already possible and my DLNA server isn’t sending it properly?
DLNA is definitely something we added initial support for and have kinda left by the wayside since then. It’s very likely metadata other than playing/paused status is broken or never was implemented. We’ll check it out and get back to you.
That said, we are currently in the process of a UI redesign so that we can add file browsing support. That will allow us to add DLNA “Player” ability to AmpliPi instead of just “Renderer”. That will hopefully streamline your setup by allowing AmpliPi to directly control what it plays from your music server. We’ve added the DLNA Player addition to this GitHub issue: Feature: DLNA Player · Issue #273 · micro-nova/AmpliPi · GitHub
What I’m trying to do (and did a bit so far with the HA Media Player), was to create a tablet view that I can use in each room through HA. I can control the mute state, input, etc per room. Then on my phone, I can use spotify, a client for my DLNA server, bluetooth, etc. I’m trying to use the API aspect of the amplipi and not introduce another GUI, so the more I can get from the amplipi into HA, the better. That’s the goal at least!
We will try to test the dlna integration with your setup and get back to you on this. It is rather likely that our DLNA metadata parser is failing to handle something.
EDIT: We still haven’t been able to test this yet. Hopefully this week?
Is the expectation that this is working in 0.3.0? I’m still not seeing metadata when using DLNA via JRiver. i’m not sure how to verify that JRiver is really publishing the metadata, but before I investigated that, I thought I’d check if the DLNA metadata updates are wrapped up into 0.3.0. Thanks!
Just wanted to bump this ask again. I’m not getting any metadata via DLNA. I can use another DLNA renderer on my network and see metadata in there, so I’m pretty sure it’s being exposed correctly from JRiver. Thanks!
So sorry for the huge delay in this, at some point metadata on the DLNA stream definitely got broken. I’ve been working on this the last couple days and I’m almost done with a fix that should be out in 0.3.0!
No worries. I tried to read through the github issue and thought it was resolved, so I was trying to figure out why it wasn’t working for me on 0.3.0-beta3 Thanks!