Kodi's configuration tends to refer to DLNA as UPnP (DLNA is a UPnP A/V derivative). This post describes the (easy) process I followed to configure an OSMC box to act as a DLNA server, allowing playback on the Roku. Thankfully, there wasn't actually a need to do so, as those existing boxes are the key: Kodi can be configured to expose its media library to other players via DLNA. There are solutions (such as Plex) which could be used to provide DLNA support, but I didn't really want to have to stand up an additional service just so that the Roku could play content from a source that our existing media boxes handle fine. Roku's store includes a channel ( Roku Media Player) which allows playback of local content, but playback of LAN hosted media relies on DLNA, meaning that my simple HTTP server isn't compatible on it's own. The problem, though, is that the Roku is (understandably) very much focused on playing remote streams and I've got a local media collection that I'd like to access. It's been a good few years since I last played with a Roku (we had one to help with monitoring and testing a few jobs back), but the interface feels as accessible as it did then.įor those not familiar: Roku use the term 'channels' to refer to what might more colloquially be referred to as apps and their store contains a wide range of possible channels providing access to OTT content: everything from Amazon Prime Video to Rakuten TV.

However, I've been gifted a Roku 3810EU and wanted to play around with using that a bit.

This collection is exposed to Kodi via http, requiring nothing more special than a web-server (my NAS) with directory listings enabled. We're primarily a Kodi household, with OSMC on Raspberry Pis playing content from a modest, and locally hosted collection of digital media.

Add a upnp player to kodi