(OLD) Unofficial Kodi PVR Client for HDHomeRun DVR subscribers

[djp952]

Welcome to the new thread! The old one was getting out of hand ... 30 pages long!
(Original thread: viewtopic.php?f=88&t=64143)

zuki.pvr.hdhomerundvr is an open-source Kodi PVR Client add-on supporting the SiliconDust HDHomeRun DVR services. This is different than the official Kodi HDHomeRun PVR Client -- this client exclusively works with the DVR services; you must be a subscriber in order to access all this add-on has to offer.

Requirements:

• Kodi 16 "Jarvis", Kodi 17 "Krypton", or Kodi 18 "Leia"
• An active SiliconDust HDHomeRun DVR subscription (https://www.silicondust.com/dvr-service)
• An HDHomeRun recording engine instance on your local network

Supported Kodi Platforms:

• Microsoft Windows / Windows Store *
• GNU Linux i686 / x86_64 / ARMv7 / ARMv8 (ARM64)
• Android x86 / ARMv7 / ARMv8 (ARM64) **
• Raspbian for Raspberry Pi 2 / Raspberry Pi 3
• Apple OSX x86_64
• Universal Windows Platform ***

* Windows Store is available for Kodi 17 "Krypton" only
** Android ARMv8 clients are available for Kodi 17 "Krypton" and Kodi 18 "Leia" only
*** Universal Windows Platform is available for Kodi 18 "Leia" only

Features:

• Live TV streaming and time-shifting **
• Full Electronic Program Guide (EPG) data
• Recorded TV playback and deletion
• Timers and Timer Rules (Record Series, Record Once)
• Channel Groups (HD Channels, SD Channels, Favorite Channels)
• HDHomeRun Premium TV (demo and subscription)

** Streaming of DRM channels is not supported and will be filtered out by the PVR Client

All documentation and downloads for the PVR client are located on GitHub. Please feel free to leave comments and suggestions regarding documentation, keeping that up to date is far more of a challenge than keeping the code up to date. Here are a few direct links to get you started, I suggest thumbing through the other documentation pages as time allows:

Main Documentation Page:
https://github.com/djp952/pvr.hdhomerundvr/wiki

Download Pages:
Kodi 16 "Jarvis" : https://github.com/djp952/pvr.hdhomerun ... odi-Jarvis
Kodi 17 "Krypton" : https://github.com/djp952/pvr.hdhomerun ... di-Krypton
Kodi 18 "Leia" : https://github.com/djp952/pvr.hdhomerun ... -Kodi-Leia

How-To Page:
https://github.com/djp952/pvr.hdhomerundvr/wiki/How-To

Known Issues and Limitations Page:
https://github.com/djp952/pvr.hdhomerun ... imitations

As of December 2018 there have been more than 30 releases of the client, many of which were driven exclusively by bug reports and feature requests from here on the SiliconDust forums; if there is something not working right or something you think it could do better, please say so! Without feedback, there would be no versions for Android, no access to the full Electronic Program Guide, and there would definitely be a lot more defects in there. All feedback, positive or negative, is quite welcome.

I'd also like to thank our host here, SiliconDust, not only for allowing us to use their forums but for creating HDHomeRun and the HDHomeRun DVR solution in the first place. I've been using HDHomeRun devices since 2008 and have never looked back. None of this would be possible without their hard work.

NOTE: As a rule, I do not accept donations. I deeply appreciate the offer, but it's reward enough for me to have so many people getting use out of the project. I've got a day job; this is a hobby

[djp952]

Version 1.3.13 (2019.02.12)

• Update SQLite database engine to version 3.27.1
• Update cURL library to version 7.64.0
• Log detected stream properties (real-time, seekable, etc) for diagnostic purposes
• Detect and report dropped streams if data transfer rate falls to zero
• Fix bug that caused a dropped stream to be waited on infinitely for more data to become available
• (Leia) Log unexpected zero length reads that occur on in-progress streams as errors
• (Leia) Accurately set the media type (MIME type) stream indicator as reported by the DVR engine
• (Leia) Fix bug preventing Kodi from calling into SetRecordingLastPlayedPosition()

Downloads:
Kodi 16 "Jarvis" : https://github.com/djp952/pvr.hdhomerun ... odi-Jarvis
Kodi 17 "Krypton" : https://github.com/djp952/pvr.hdhomerun ... di-Krypton
Kodi 18 "Leia" : https://github.com/djp952/pvr.hdhomerun ... -Kodi-Leia

Release History:
https://github.com/djp952/pvr.hdhomerun ... se-History

[cvonk]

I am trying to get this promising add-on to work under the Windows version of Kodi. When trying to record TV, I run into "unexpected error". The debug log is shown below.

21:07:15.857 T:14736 NOTICE: EPG::CEpgContainer::Start - EPG thread started
21:07:18.560 T:14960 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_startup_task: initiated startup discovery task
21:07:18.875 T:14960 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_startup_task: scheduling periodic device discovery to initiate in 300 seconds
21:07:18.875 T:14960 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_startup_task: scheduling periodic lineup discovery to initiate in 600 seconds
21:07:18.875 T:14960 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_startup_task: scheduling periodic recording discovery to initiate in 600 seconds
21:07:18.875 T:14960 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_startup_task: scheduling periodic guide discovery to initiate in 3600 seconds
21:07:18.875 T:14960 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_startup_task: scheduling periodic recording rule discovery to initiate in 7200 seconds
21:07:18.875 T:14960 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_startup_task: scheduling periodic recording rule episode discovery to initiate in 7200 seconds
21:08:17.122 T:21284 ERROR: CPVRTimerType::CreateFromAttributes unable to resolve timer type (0x1, 0xa, 235985751)
21:08:44.791 T:21284 ERROR: AddOnLog: HDHomeRun DVR PVR Client: AddTimer failed due to an unhandled exception: constraint failed (1299)
21:08:44.791 T:21284 ERROR: PVR - PVR::CPVRClient::AddTimer - addon 'zuki.pvr.hdhomerundvr:my.hdhomerun.com' returned an error: the command failed
21:08:44.791 T:21284 ERROR: PVR - PVR::CPVRClients::AddTimer - cannot add timer to client '235985751': the command failed
21:10:46.364 T:21284 ERROR: CPVRTimerType::CreateFromAttributes unable to resolve timer type (0x1, 0xa, 235985751)
21:11:21.863 T:21284 ERROR: AddOnLog: HDHomeRun DVR PVR Client: AddTimer failed due to an unhandled exception: constraint failed (1299)
21:11:21.863 T:21284 ERROR: PVR - PVR::CPVRClient::AddTimer - addon 'zuki.pvr.hdhomerundvr:my.hdhomerun.com' returned an error: the command failed
21:11:21.863 T:21284 ERROR: PVR - PVR::CPVRClients::AddTimer - cannot add timer to client '235985751': the command failed
21:11:31.619 T:21284 ERROR: CPVRTimerType::CreateFromAttributes unable to resolve timer type (0x1, 0xa, 235985751)
21:12:04.491 T:21284 NOTICE: VideoPlayer: Opening: pvr://channels/tv/All channels/pvr.hdhomerundvr_36865.pvr
21:12:04.492 T:21284 WARNING: CDVDMessageQueue(player)::Put MSGQ_NOT_INITIALIZED
21:12:04.515 T:21284 ERROR: DXVA::CProcessorHD::IsFormatSupported: Unsupported format 105 for 1.
21:12:04.516 T:15792 NOTICE: Creating InputStream
21:12:04.523 T:15792 ERROR: AddOnLog: HDHomeRun DVR PVR Client: OpenLiveStream failed due to an unhandled exception: unable to determine the URL for specified channel
21:12:04.524 T:15792 ERROR: CVideoPlayer::OpenInputStream - error opening [pvr://channels/tv/All channels/pvr.hdhomerundvr_36865.pvr]
21:12:04.524 T:15792 NOTICE: CVideoPlayer::OnExit()
21:12:10.389 T:21284 ERROR: CPVRTimerType::CreateFromAttributes unable to resolve timer type (0x1, 0xa, 235985751)
21:12:10.479 T:21284 ERROR: AddOnLog: HDHomeRun DVR PVR Client: AddTimer failed due to an unhandled exception: constraint failed (1299)
21:12:10.479 T:21284 ERROR: PVR - PVR::CPVRClient::AddTimer - addon 'zuki.pvr.hdhomerundvr:my.hdhomerun.com' returned an error: the command failed
21:12:10.479 T:21284 ERROR: PVR - PVR::CPVRClients::AddTimer - cannot add timer to client '235985751': the command failed
21:12:19.073 T:14960 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_devices_task: initiated local network device discovery
21:12:19.209 T:14960 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_devices_task: scheduling next device discovery to initiate in 300 seconds
21:12:22.865 T:21284 ERROR: CPVRTimerType::CreateFromAttributes unable to resolve timer type (0x1, 0xa, 235985751)
21:12:22.960 T:21284 ERROR: AddOnLog: HDHomeRun DVR PVR Client: AddTimer failed due to an unhandled exception: constraint failed (1299)
21:12:22.960 T:21284 ERROR: PVR - PVR::CPVRClient::AddTimer - addon 'zuki.pvr.hdhomerundvr:my.hdhomerun.com' returned an error: the command failed
21:12:22.960 T:21284 ERROR: PVR - PVR::CPVRClients::AddTimer - cannot add timer to client '235985751': the command failed
21:14:00.331 T:21284 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: ADDON_SetSetting: setting prepend_channel_numbers changed to true -- trigger channel update
21:14:00.331 T:21284 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: ADDON_SetSetting: setting use_episode_number_as_title changed to true -- trigger recording update
21:14:00.331 T:21284 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: ADDON_SetSetting: setting use_direct_tuning changed to true
21:17:18.935 T:14960 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_recordings_task: initiated local storage device recording discovery
21:17:18.935 T:14960 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_recordings_task: scheduling next recording discovery to initiate in 600 seconds
21:17:19.436 T:14960 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_lineups_task: initiated local tuner device lineup discovery
21:17:19.465 T:14960 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_lineups_task: scheduling next lineup discovery to initiate in 600 seconds
21:17:19.965 T:14960 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_devices_task: initiated local network device discovery
21:17:20.154 T:14960 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_devices_task: scheduling next device discovery to initiate in 300 seconds
21:18:17.827 T:21284 ERROR: CPVRTimerType::CreateFromAttributes unable to resolve timer type (0x1, 0xa, 235985751)
21:19:09.711 T:21284 ERROR: Previous line repeats 1 times.
21:19:09.712 T:21284 ERROR: AddOnLog: HDHomeRun DVR PVR Client: AddTimer failed due to an unhandled exception: constraint failed (1299)
21:19:09.712 T:21284 ERROR: PVR - PVR::CPVRClient::AddTimer - addon 'zuki.pvr.hdhomerundvr:my.hdhomerun.com' returned an error: the command failed
21:19:09.712 T:21284 ERROR: PVR - PVR::CPVRClients::AddTimer - cannot add timer to client '235985751': the command failed
21:22:20.395 T:14960 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_devices_task: initiated local network device discovery
21:22:20.539 T:14960 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_devices_task: scheduling next device discovery to initiate in 300 seconds
21:23:03.085 T:21284 NOTICE: Log level changed to "LOG_LEVEL_DEBUG_FREEMEM"

Can somebody please shed some light on this?

[RockerC]

Already posted here viewtopic.php?f=88&t=64143&p=300283#p300283 so this is just a copy, but as I thought this might not be noticed I'll break netiquette and cross-post hoping that you and forum moderator exuse that bad bad posting behavior just this once.

Hmmm... it's kinda Kodi development and it's kinda 3rd party at the same time I guess. Let me ping TVJunkie198 on a PM and see what he thinks is the most appropriate forum to start the new thread.

I think that the Kodi.tv community forums at https://forum.kodi.tv has the most appropriate (sub)forum for discussing all and any PVR client addons for Kodi, official and unofficial, original branch and distinct forks of existing PVR client addons. I'm sure that that the Kodi team's forum moderators could even create your own new seperate sub-sub-forums there too if that is what you wanted, so that even each distinct PVR client addon gets its own sub-sub-forum there:

https://forum.kodi.tv/forumdisplay.php?fid=250

That would also be the best place for team Kodi to get feedback on what additions that they need to make to Kodi's own PVR API and to Kodi's core/GUI to make it better suited for a broader range of DVR services or new features and functions requested by PVR client addon developers and end-users.

PS: Remember that SiliconDust is also a sponsor of kodi.tv and have already collaborated with the Kodi development team so I would hope that they would start to monitor activity in the existing HDHomeRun sub-forum there for PVR client addons any any subsequent sub-sub-forums as well

[RockerC]

Quote to continue from other thread viewtopic.php?f=88&t=64143&p=299871&hil ... se#p299871

I kinda did things my own way and didn't follow their guidelines/rules (at all) and I've gone so far as to compile in my own versions of some libraries they use in Kodi (SQLite, cURL). It could be made to work within their guidelines, of course, but they would need to at least change how they build SQLite and tweak their cURL implementation to work right with the HDHomeRun RECORD engine. So there's that on the technical side.

I read in bits an pieces on kodi.tv that that the Kodi developerment team currently have plans to first move to an abstracted DB layer, like with example an ORM and ODBC, and then later they will also refactor Kodi's database schema. So now rather than later might be the right time to give them input on that first part as that might be what you would want to use to use the database differently, (while the second part if probably a couple of years away before users will see it). However as for tweaking cURL you would probabably be better of submitting a request for change directly upstream to the cURL project instead of to Kodi as I know they prefer to use vanilla libraries whenever possible, which is why Kodi developers themselves are for example active contributors to many different projects upstream from them, like FFmpeg and many more.

Wanted follow-up on this FYI to also let you know that the Kodi development have now publushed the new ODB (ORM) work-in-progress that they are working on and it has its own public feature branch in their XBMC repo for Kodi on GitHub here:

https://github.com/xbmc/xbmc/tree/feature_odb

I found the link just now as it was posted a couple of days ago in this other discussion about a new DB Structure for all libraries in Kodi, and in that thread there is in additon a lot of discussion on ideas future database schemas and db structures to fit broad features and be more flexible that the Kodi DB has been in the past:

https://forum.kodi.tv/showthread.php?tid=200911

Again, as I mentioned in the quoted post above, their goal is to first implement an ORM (ODB in this case) to abstract the choice of databases used, and then later once that been merged into mainline they will move on to the much larger job of adopting a new DB schema.

[RockerC]

** Streaming of DRM channels is not supported and will be filtered out by the PVR Client

FYI, just in case you did not know it already, the upcoming Kodi v18 (codename: Leia) will technically have the possibility to support DRM chains (protected streams) "InputStream" (input stream) addons using the new InputStream API which PVR client addons has the ability to use as well and to a part has to move to anyway:

http://kodi.wiki/view/Kodi_v18_(Leia)_changelog

This change to move to "InputStream" (input stream) addons for PVR client addons described here:

https://forum.kodi.tv/showthread.php?tid=259830

As I understand the main "InputStream" (input stream) addon that can be modified to support such this is this "Acaptive InputStream" addon by peak3d (who is also the lead developer behind the new DRM support additions in Kodi v18):

https://github.com/peak3d/inputstream.adaptive

As a proof-of-concept they have already shown that is can be used with play protected video streams from Netflix in Kodi without breaking the DRM stream, as mentioned here:

http://www.phoronix.com/scan.php?page=n ... ix-Support

While it might still be be very hard to add support for DRM protected streams from HDHomeRun in your PVR client addon, this at least should give you (or others) the underlying framwork needed to add such support in the future is you/they wanted to.

[djp952]

I am trying to get this promising add-on to work under the Windows version of Kodi. When trying to record TV, I run into "unexpected error". The debug log is shown below.

Looks like you have a couple problems happening here:

Code: Select all

21:12:04.523 T:15792   ERROR: AddOnLog: HDHomeRun DVR PVR Client: OpenLiveStream failed due to an unhandled exception: unable to determine the URL for specified channel

Code: Select all

21:12:10.479 T:21284   ERROR: AddOnLog: HDHomeRun DVR PVR Client: AddTimer failed due to an unhandled exception: constraint failed (1299)

The first one indicates that the client wasn't able to generate a URL for the channel to request it from the RECORD engine. The most common reason for this would be that no RECORD engine was discovered, or there isn't one available on the network. There are 2 options under 'Advanced' that might help you out with this one.

• If you are certain the RECORD engine is working and on the network, you can turn on the "Use network broadcast for device discovery". This bypasses going to my.hdhomerun.com to get the device list and just pokes around on the network.
• If you have no RECORD engine or it's still not being discovered, you can enable the "Stream Live TV channels directly from tuner device(s)" option. This breaks timeshifting/seek of Live TV, but uses the tuners directly bypassing the missing RECORD engine.

The second error is a bit of a head-scratcher, there is little to no referential integrity in the database, so the only thing I believe could be causing this particular message is a duplicate primary key, which is odd since the only place that they come from is the backend service. I'll have to look into this one later tonight, perhaps there has been a schema change or something on the back end. First time I've heard of this - you get an official new bug award!

Let me know if the advanced options help your Live TV problem; we can play around in the web browser and check the discovery results by hand if need be!

[djp952]

cvonk, can you assist me with figuring out why you are getting errors adding timers? I can't duplicate that concern here yet.

- What program/series are you trying to add a timer for (If I have that program I can try same one)?
- How are you adding the timer (from the EPG, from pressing the REC button in the player, from "Timer Rules" UI, etc.)
- If you are presented with a choice, what kind of timer are you trying to add ("Record Series", "Record Once")?

edit: Nevermind! I think I found it. I'm betting you have no Recording Rules at all (or perhaps aren't a DVR service subscriber?) - the error is telling me that I'm trying to insert a NULL into the database where NULLs aren't allowed I am not protecting against the backend returning no results. If this is the case, the error is a false positive and isn't really hurting anything, but I will clean that up for the next release regardless. Let me know if my assumption is correct.

I'm also adding a fallback mechanism to automatically switch to a direct tuner stream if generation of the stream URL for the storage/RECORD engine fails for any reason. I'm debating on adding a banner notice, but it's probably left as a silent failure only visible in the Kodi log; that would get really annoying really fast for people having problems.

[fab4272]

Just noticed on my Win10 rig, when in the EPG, if there is no fan art for the TV show, the TV network logo shows. On my Android rig, no TV logo is shown. Fan art pops up, but if there is none from the HDhomerun then no TV logo.

[djp952]

Just noticed on my Win10 rig, when in the EPG, if there is no fan art for the TV show, the TV network logo shows. On my Android rig, no TV logo is shown. Fan art pops up, but if there is none from the HDhomerun then no TV logo.

You might try a clear data in the Kodi PVR & Live TV settings, I've had this happen to me from time to time as well. In my case I think it's because I fire up and crash Kodi like a billion times, but it definitely fixes things like this for me. Note that the entire EPG will need to reload afterwards, when they say clear data they mean it!

For what it's worth, I just give Kodi the URLs supplied in the data, it takes care of getting and displaying the actual images. It's just a hand-off from the back end to Kodi for these.

[djp952]

I have a new, albeit minor, release out there for you guys:

Version 1.2.1 (2017.08.02)

• Add "Disable Channel", "Add to Favorite Channels" and "Remove from Favorite Channels" Client Actions to channel context menus
• Adapt to new backend discovery URLs (api.hdhomerun.com)
• Fall back to using a direct tuner stream for Live TV if a storage engine has not been discovered on the network
• Add "List discovered devices" PVR Client Specific setting

The new channel context menu items are accessible from the "Channels" area in Kodi only -- right-click on the channel and select Client Actions. Disable turns the channel off on all tuners - you must use the tuner web user interface to turn them back on! Add to Favorite Channels and Remove from Favorite Channels do what you'd expect, and again it sets/clears that for all tuners. There isn't a way to dynamically add/remove these menu options so I can't differentiate between channels that already are or are not favorites and show just the option that is appropriate.

The discovery URL change shouldn't make any real difference to anyone, the old URLs were set to redirect automatically. I just noticed on another thread out here that the URLs have changed so I updated them to keep pace with the backend.

The Live TV fall back mechanism is for when the storage engine hasn't been discovered for some reason, or flat out doesn't exist. If I can't generate the URL for the channel because of the missing engine it will just automatically (and silently) switch to using a tuner directly. I opted to keep it silent because I know some folks are using this client as a straight replacement for the regular Kodi one (no DVR subscription or no RECORD engine running)

The "List discovered devices" setting (PVR & Live TV / Client Specific / Client Specific settings) pops up a rudimentary dialog box that simply lists the devices that the client has discovered. This should be easier than asking people to go type in all those URLs just to see if the client knows about all the things you expect it to know about. It just provides the device "Friendly Name" and the Device ID if it's a tuner.

If none of these items are of interest to you, there is no reason to upgrade from 1.2.0; there were no changes to any core functionality (not on purpose, anyway )

Downloads:
https://github.com/djp952/pvr.hdhomerun ... /Downloads

There is also an updated Leia (Windows only) build out there to handle a PVR API change that was made by Team Kodi recently, be advised that the current Kodi Leia 32-bit Windows build seems rather broken right now and just crashes, but the 64-bit one is working fine for me: https://github.com/djp952/pvr.hdhomerun ... leia-1.2.1

[NYPlayer]

Working great on Shield.

[djp952]

NOTE: I'm seeing a problem with guide data today (8/2), the backend doesn't seem to be returning data from the past in the same way it used to, which trips up the guide loader since it thinks there is nothing more to load and it stops. You may or may not run into this problem if your guide is generally up to date already.

I'll ask on the development forum if this is a permanent change or a temporary thing. If it's permanent an adjustment can be made to deal with it.

(Always on the day you release something completely unrelated! LOL)

edit: disallowing data older than 8 hours in the past seems to clear it up, if I don't hear back from somebody about the API tonight I'll just go ahead and build a 1.2.2 with just that change. I'd like to know what the expectation is for back data so we don't have to change it again, but there are plenty of version numbers left to use -8 hours seems reasonable to me.

[djp952]

Two builds in one day, I think that's a first?

Version 1.2.2 (2017.08.02)

• Fix EPG update being aborted prematurely when requesting guide data from the past

This is a recommended update as you will lose EPG functionality if Kodi ever tries to fill in guide gaps that occur in the past.

The problem that occurred is that the backend API no longer allows EPG data requests for the past and returns a blank listing for the channel. The client was programmed to interpret a blank listing as "no more data" and stops the update process for that channel. This change adjusts how a blank channel listing is interpreted -- if the requested time is in the past it is fast-forwarded to the current time and continues rather than aborting.

>> Many thanks to SiliconDust's NickK for his very timely support answering my questions <<

Downloads:
https://github.com/djp952/pvr.hdhomerun ... /Downloads

As with v1.2.1, there is also an updated Leia (Windows only) build out there to handle a PVR API change that was made by Team Kodi recently, be advised that the current Kodi Leia 32-bit Windows build seems rather broken right now and just crashes, but the 64-bit one is working fine for me: https://github.com/djp952/pvr.hdhomerun ... leia-1.2.2

[fab4272]

You might try a clear data in the Kodi PVR & Live TV settings, I've had this happen to me from time to time as well. In my case I think it's because I fire up and crash Kodi like a billion times, but it definitely fixes things like this for me. Note that the entire EPG will need to reload afterwards, when they say clear data they mean it!

For what it's worth, I just give Kodi the URLs supplied in the data, it takes care of getting and displaying the actual images. It's just a hand-off from the back end to Kodi for these.

I've tried to clear the data. Same result. No channel logo's in Kodi from the HDHomerun backend. You mention giving Kodi the URL's? How do you do that?