djp952/pvr.hdhomerundvr

Unofficial Kodi HDHomeRun DVR PVR Client

pvr.hdhomerundvr's Issues

Support for darwin (iOS) Kodi platforms

There are still additional outstanding Apple-based Kodi platforms that could be supported by the PVR client:

Krypton:
darwin-ios
darwin-ios-arm64

Leia:
darwin-ios
darwin-ios-arm64
darwin-tvos

There appears to be no official Kodi builds for any darwin platforms earlier than Krypton, so Jarvis support isn't likely to be necessary.

Decide on final version for Kodi 16.1 Jarvis

Jarvis is getting a little long in the tooth at this point. My research into the downloads from here in GitHub indicates that it's still a rather popular platform, approximately 1/4 of everyone is still using Jarvis, which is unexpected.

So far there has only been one appreciable 'feature' that couldn't be implemented on Jarvis, and it was a fringe case option to disable reporting real-time streams (v1.2.8), otherwise everything still works pretty much the same, so I think this boils down to just drawing a line in the sand, per se, and deciding on a last version for Jarvis.

Perhaps when Leia is released formally bump Krypton and Leia up to version 1.3 or 2.0 and keep Jarvis on 1.2 as a 'maintenance' thing, only fixing bugs but not adding anything new?

Request

Please update the leia builds for latest pvr addon api.

Add logging verbosity slider

The standard logging verbosity has been pointed out to be a little excessive, and of course the new (1.2.8) 'verbose' logging is insane by design. Add a slider to the settings to allow for three levels of logging:

• Errors Only
• Standard (come up with a fancier name)
• Verbose (also come up with a fancier name)

Handle tuners without DeviceAuth strings better

Making this an issue since the resolution is non-trivial and may require some fundamental changes and perhaps a database schema update.

The problem is that a user has a PRIME tuner that is not exposing a DeviceAuth code via the JSON data. It's most likely a tuner issue as they indicated the CableCard status is showing as invalid, but the PVR doesn't handle this well.

The PVR makes an assumption in a great deal of places that there will be at least one valid DeviceAuth code available. If there are none, the backend HTTP query ends up sending in "DeviceAuth=", which of course fails.

The simplest solution would be to systemically eliminate tuners without a DeviceAuth code from the device discovery altogether. If there are no tuners with any DeviceAuth codes, it would behave as if there are no tuners at all, which seems reasonable. The user will be altered to that fact at startup with recent other changes made.

As part of this, I should also add something to completely block/eliminate any backend HTTP requests if there are no tuners. Right now it will still try (and fail), which is fine for the user but unnecessarily bangs against SiliconDust's servers with no possibility of success.

Move away from GCC / gnustl in Android builds

As of June 2018, use of GCC and gnustl is now officially deprecated for Android. At some point in the near future this needs to be switched over. Not sure at this time what that will do for older versions of Android that people are still using Kodi with.

crash on record from guide

everytime i try to select a program to record from the guide, kodi crashes.
i’m using zuki.pvr.hdhomerunpvr v1.2.8

logs at paste.osmc.tv/lefobefiha

Leia - DVR live streams halt when switching channels

Reported on SD forums and confirmed on nVidia Shield running PVR 1.3.4 on Leia Beta 2. When switching channels, the stream may appear to halt with "ActiveAE - large audio sync error" warnings in the Kodi log.

Not sure yet if this is PVR or Kodi, but it doesn't happen when streaming directly from the tuner, only when accessing live streams via the RECORD engine.

scrolling fwd/back on live tv hangs

while watching livetv, scrolling fwd/back eventually hangs kodi; i have to kill kodi from ssh/cli

Unexpected behavior when skipping forward on Live TV stream

From the SiliconDust forums:

The only problem I see so far is with pausing Live TV for several minutes and then trying to go past
the commercial with skipping forward. Something I use all the time.
I have my remote setup so that I can skip forward by several minutes when I hit the skip function several times.
However it only skips 10 seconds ahead even though I see it tries to go forward by showing "Seeking +03:00"
It looks like it does not know exactly how big the buffer is at that point. Skipping forwards works great on recordings, but there is definitely a problem for me with Live TV buffer.

This is probably something that can be improved; the client is currently limiting how far into the future Kodi can request on a seek operation. I believe with some tinkering I can improve this by letting Kodi ask for whatever it wants and let the RECORD engine handle it as best it can. I will also test reporting an infinite length to Kodi for Live TV streams, IIRC that caused a problem at some point which was why I started tracking the "seen" length instead.

The code has changed/improved a lot since the last time I played with this, so I think it's reasonable to mark this as a bug/defect and work on it from that perspective.

guide doesn't automatically update

i have to manually bounce kodi, then i’m good until the guide empties…

Add option to reset the database

It would be nice to add a way to completely reset the database through the Kodi UI. Such an operation would drop all the tables and rebuild them from scratch.

It's possible that the database could become corrupted and/or unusable for a number of reasons, this option would prevent users from needing to find where the database file actually is on their platform and deleting it manually.

Other than the inconvenience there should be no important consequences to resetting the database, all the data is volatile anyway. Things already retrieved by Kodi (EPG, for example) will have been copied into the Kodi PVR database(s) so the user shouldn't necessarily lose anything.

Failing to load stream for HDHomerun premium channels

Running LibreElec 8.2.5 on a Raspberry Pi 3 with zuki.pvr.hdhomerundvr-linux-armhf-krypton-1.3.2.6799. The addon worked fine while the new HDHomerun premium channels were in demo mode, however, after paying for the subscription the premium channels fail to load in Kodi.

Also running hdhomerun_record_linux_20180817 on a server where recording is done.

local EPG data blank after update to zuki 1.311.6972

new to github, let me know if this is not the proper place to post my issue/question... I have read the "known issues" and wiki here. also hours on google, hoping this is a simple mistake on my part...

I just updated to libreELEC 9.0 with Leia18 today with fresh install... along with zuki.pvr.hdhomerundvr-raspbian-armhf-leia-1.3.11.6972.zip

Currently my EPG data for local channels is completely blank, but premium hdhr channels display just fine. Everything else is working as expected.

If i switch to the libreELEC "PVR HDHomeRun Client", local and premium guide data displays just fine. I only lose the local EPG when using the zuki pvr.

I have gone through all settings many times and recently set all back to default and still no bueno. I have also tried clearing cached guide data to no avail.

I also checked my other libreELEC 8.2.5 install with kodi 17.6... when using zuki 1.39.6943, local and premium EPG works. i updated to version 1.3.11.6972 and lose local epg data. i revert back to zuki version 1.39.6943 and local epg data comes right back... I do not have access to older zuki leia builds as just updated today. Anything else I can try?

Future timers

Is it possible to add a timer for a show that will be upcoming? Perhaps months from now? Or to find keywords that may not exist yet?

For instance, there is a show that we regularly watch, but it is on hiatus right now. If I try and add a timer, it does a search of the EPG and if there's nothing like it available, it rejects it. I'm not sure if it stored away somewhere for when a show matching those parameters shows up, but if it does, I can't find it anywhere.

Thanks for your hard work...I love the HDHomerun device, but, man, do I hate their DVR software.

Recorded Show Progress

Is it possible to synchronize recorded show viewing progress across multiple playback devices? I use MySQL to centralize Kodi's libraries and viewing progress of library content. It would be great to have the same for recorded content as well.

Automatically enable broadcast discovery if RECORD engine only found that way

Given the prevalence of people that have the problem with HTTP discovery not finding their RECORD engine, I think it would be nicer to add some logic to fall back to broadcast automatically.

Here's my current plan:

• If HTTP discovery is ON and no RECORD engine was found, try a broadcast discovery
• If broadcast found a RECORD engine, auto-enable the broadcast setting and notify the user
• If broadcast did not find a RECORD engine, do nothing. Discard the broadcast discovery results and leave HTTP ON

I think this is a pretty good way to handle it, it should help the people that first install this thing and have to research out or ask why it's not working, while at the same time not interfering with the people that legitimately don't have a RECORD engine running -- they should see no difference at all.

Extended Channel Names Not Displayed In Kodi (18.0 - RC3)

Within the native HDHomeRun setup tool, the extended (real) proper-case channel names for scanned channels are displayed. Within Kodi (18.0 "Leia" - RC3) Only the truncated "Shortcut - All CAPS" channel names (abbreviations) are displayed.

My setup uses OTA guide data provision that's broadcast along with the channel data, and I'm based in the UK, using the Mendip Transmitter. I experience no such issues using any of the other HDHomeRun PVR add-ons available from the default Kodi Repo add-ons, but they don't provide recording functionality.

OSMC install error

Hi there,

This my first time trying this addon on my RPI3 running OSMC. On install, the kodi log shows the following errors

19:39:45.725 T:1457255168  NOTICE: AddOnLog: HDHomeRun DVR PVR Client: ADDON_Create: zuki.pvr.hdhomerundvr v1.3.4 loading
19:39:45.759 T:1457255168   ERROR: AddOnLog: HDHomeRun DVR PVR Client: ADDON_Create failed due to an exception: database disk image is malformed (11): database disk image is malformed
19:39:45.760 T:1457255168   ERROR: ADDON: Dll HDHomeRun DVR PVR Client - Client returned bad status (6) from Create and is not usable
19:39:47.832 T:1457255168   ERROR: UpdateAddons - failed to create add-on HDHomeRun DVR PVR Client, status = 6

I searched around and found no clues as to what this error means. I'm running OSMC Kodi 17.6 and I'm trying to install the zuki.pvr.hdhomerundvr-linux-armhf-krypton-1.3.4.6838.zip file when the error occurs. Thanks in advance for any help

Automatically rebuild database on error 11 "database disk image is malformed" in ADDON_Create

User has reported issue with SQLite error 11 "database disk image is malformed" happening in ADDON_Create. While working with user to resolve issue, this seems like something that can be auto-recovered from, or at least make an attempt. There is nothing critical in the PVR database that won't be automatically rebuilt if this error is detected during ADDON_Create.

• Manually trash a database file to verify behavior, and then add code to delete and rebuild the database in ADDON_Create. Only make one attempt, if there is something systemic going on don't want to put the user into an endless loop of hopelessness!

Leia PVR API 5.10.3

Please update Leia to pvr API 5.10.3

OSX version?

Any possibility you can release one for Kodi 17 running on OSX?

"Trigger recording discovery immediately after playback" setting isn't applied until restart

The "Trigger recording discovery immediately after playback" setting isn't being applied until a restart of Kodi. I tracked this down to a bug in the settings implementation -- the flag is instead being applied to "Use network broadcast for device discovery".

The bug is only triggered when the setting is changed, the correct value is loaded and applied during Kodi startup.

This will be fixed in version 1.2.8.

Support EDL files for Recorded TV

Support loading of EDL (Edit Decision List) files for Recorded TV. Files generated by ComSkip, for example.

Challenges:

• Need to parse the file; there are various formats from various vendors
• Need a way to associate the recording with the file. Comskip, for example, names the output file to match the input .MPG file name. That file name is not accessible from the PVR client, only the metadata provided by the HDHomeRun RECORD engine. The file name will have to match something available in the metadata.
• Tools might provide frame numbers, these need to be mapped into milliseconds for Kodi as well as what should be done (CUT, MUTE, SCENE, COMBREAK)
• Comskip itself provides an easy to parse .edl file that has the necessary millisecond data rather than frame rates, better choice than the .txt file.

Design:

• Add an option "Enable Edit Decision List (EDL) processing" (default: false)
• Add an option "EDL input file location", selectable from existing libraries. User will have to add a network share via Videos or Music first due to UI limitations.
• Add an option "EDL input file format", toggles for Comskip et al, supporting multiple formats automatically is probably not worth the effort
• Implement PVR "GetRecordingEDL" function
• GetRecordingEDL:
  -- uses available PVR_RECORDING to access metadata to generate file name to look for
  -- if file is found, load and parse based on selected file format
  -- populate PVR_EDL_ENTRY[]/count and return to Kodi

References:

• Kodi already supports this for Video library files, there should be reference code for all of the file formats supported by Kodi, likely to the same millisecond/action format expected by the PVR subsystem.

Android build target of Kodi 16.1

I installed kodi-16.1-zuki.pvr.hdhomerundvr-arm-1.3.3.6808.apk on my Android device running Android 4.4.2 (API level 19, kernel: Linux 3.10.33). After I enable the addon and then enable TV under Settings > TV, I get an error The PVR manager has been enabled without any enabled PVR add-on. Enable at least one add-on in order to use the PVR functionality.

The Kodi log mentions the following:

19:17:16 T:1791862648   ERROR: Unable to load /data/data/org.xbmc.kodi/cache/apk/assets/addons/pvr.hdhomerundvr/libhdhomerundvr.so, reason: dlopen failed: cannot locate symbol "srand" referenced by "libhdhomerundvr.so"...
19:17:16 T:1791862648 WARNING: bool PVR::CPVRClients::UpdateAndInitialiseClients(bool) - failed to create add-on HDHomeRun DVR PVR Client, status = 6
19:17:16 T:1791862648 WARNING: bool PVR::CPVRClients::UpdateAndInitialiseClients(bool) - failed to load the dll for add-on HDHomeRun DVR PVR Client, disabling it

What is the target for the build of the file I installed? Is it higher than 19?

Some HTTP requests are executed multiple times

The way that some HTTP requests are being satisfied via a SQLite custom function is causing them to be executed multiple times. This is due to SQLite re-evaluating the result when that column is listed as part of a WHERE clause. The prime examples are the device and lineup discoveries, but there are other instances like when adding a recording rule the episode query is executed multiple times.

I haven't found a good solution for this yet, SQLite seems really set on re-evaluating the result of a column sourced from a deterministic custom function.

Listing this as a bug since I can't fix it at the moment. It's not the end of the world, but it wastes time and bandwidth for no good reason.

Support for multiple HDHomeRun Prime tuners

I currently have multiple HDHomeRun Prime's (4) but when I go to record more than three shows during the same time period it deletes the last recording rule I created. I have 12 tuners available on my network yet it seems I can only access the tuner on one device.

Scheduled tasks should be cancellable

The internal task scheduler should incorporate and use a cancellation notification. Currently, only the 'extended guide' version of the guide discovery task really needs it, but it wouldn't hurt to incorporate into all of them.

The problem this aims to solve is that a background discovery task may be long-running and if it's active when the user attempts to close Kodi or otherwise unload the PVR manager there could be an appreciable delay. The internal scheduler will not stop until the active task has completed.

silicondust issue

attn. djp952

! silicondust is trying to get in touch about a guide data download issue

Please check in on the forums we the users love your work and want to continue using it.

" by nickk » Thu Jun 21, 2018 5:20 pm

Has anyone heard from djp952?

(If the problem isn't resolved in the near future we will have to block this plugin from downloading guide until it is resolved). "

HDHomeRunDVR: Difficulties with audio-only streams

Having an issue where the add-on is freezing Kodi when initiating a new stream from the tuner.

It will start on either TV or radio by playing a short amount of audio / video, which then freezes at that point. For radio, the station logo remains visible and the rotating CD in the music vis area (Aeon Madnox) will continue to spin, but there's no audio. also there is an insane amount of length of "played" time listed, like 9 hours or so, and there will also be an end time which shouldn't be present for a live stream (as if it's being treated like a regular audio track with a definite end).

Stopping the stream with the stop button causes Kodi to freeze. Discovery actions from the add-on still execute in the background upon playback stop, but nothing else is responsive.

Checking the log I see a lot of the following message being scattered throughout the log.

ERROR: PVR::CPVRTimerType::CreateFromAttributes: Unable to resolve timer type (0x1, 0xa, 795398121)

also seeing a lot of the following:

ERROR: CDVDAudio::AddPacketsRenderer - timeout adding data to renderer

It's my assumption that there is a problem with the way the add-on is caching the live stream, and potentially also not clearing the cache upon playback end. Once the crash happens for the first time, it's impossible to play anything through the add-on without the same behaviour occurring next time round. A restart / reboot does not cure the issue.

Clearing commoncache.db, simplecache.db and the video database seem to solve the issue, until the next time it happens.

I installed Zoltan's HDHomeRun PVR add-on and it works as expected with no freezing of either TV or radio stations, but as I mentioned in my other post, it has no DVR functionality.

Leia PVR API 5.9.0

Update Leia build for PVR API 5.9.0

Thanks

Not an issue -- just a thanks on behalf of our OSMC users for producing binaries.

We'd be happy to get this included in OSMC out of the box for Leia if you'd be interested.

Cheers

Sam

Kodi 17.4

I am running Kodi 17.4 on Windows 10x64. I just installed this addon. When I click on record or add timer I get an error and for me to check the logs. In my log I have.

16:59:49.476 T:9240 ERROR: CPVRTimerType::CreateFromAttributes unable to resolve timer type (0x1, 0xa, 235985751)
16:59:49.712 T:9240 ERROR: AddOnLog: HDHomeRun DVR PVR Client: AddTimer failed due to an unhandled exception: constraint failed (1299)
16:59:49.712 T:9240 ERROR: PVR - PVR::CPVRClient::AddTimer - addon 'zuki.pvr.hdhomerundvr:my.hdhomerun.com' returned an error: the command failed
16:59:49.712 T:9240 ERROR: PVR - PVR::CPVRClients::AddTimer - cannot add timer to client '235985751': the command failed

May be a 17.4 change that is making this happen

Cannot delete DateTimeOnly rule that overlaps with a Series rule

When a DateTimeOnly recording rule is added that overlaps with a Series rule, the timer type displayed in Kodi will be the "Record Series Episode" timer, which cannot be deleted. In order to delete the DateTimeOnly timer the Series rule needs to be deleted and then requires a rather brute force manipulation of the database.

To compound the issue, even after nuking the database, since the EPG entry has already been added, the user can go back and try to reschedule the same episode again with a new DateTimeOnly timer and it will fail because the episode information has been purged. This whole debacle needs to be fixed via a code change so the user can't get themselves into this bad state.

Ideally both timers would display for the user, but if they are destined to always be collapsed into one, the DateTimeOnly timer should take precedence so that it can be manipulated.

Changing channels causes audio to skip

This is a great plugin. Thanks.

I've noticed that when changing channels the audio may skip for a little and then stabilize. This issue seems identical what was described in this thread: https://forum.kodi.tv/showthread.php?tid=306231 .

Rewind / FF Live TV not working

If this is the wrong place to ask these questions, please point me to the appropriate location. As I suspect this is a configuration issue, not a bug.

I successfully installed the addon, and I was able to add a recording via the Kodi UI on my OSMC RPI3. I notice that in the addon feature summary, it says that I can rewind and fast-forward live tv, but I'm having a hard time getting that feature to work. Is there something special that needs to be done to enable this feature, or is it a hardware limitation? Pause works fine.

Thanks again.

Record Series Rule timer types shows up in EPG "Add Timer"

When an EPG element is right-clicked and "Add Timer" is selected, the non-EPG "Record Series Rule" timer type is exposed -- it should not appear in this context.

I tracked this down to a change made in Kodi 17.1 that was applied to solve a problem with the mythtv addon #11775 (xbmc/xbmc#11775). That change allows the first timer type detected by the dialog box to appear regardless of it being an EPG-based timer type.

I have submitted a pull request #12354 (xbmc/xbmc#12354) to the Kodi team to resolve the concern.

Marking this as 'wontfix' since it can't be resolved in the PVR client itself, this issue is to keep track of the concern only.

Linux builds require GCC 5 ABIs

The Linux builds (release 1.0.0) require the GCC 5 ABIs, specifically libstdc++.so.6.0.21. This is more current than many Linux systems will have available. Look into building the Linux libraries with gcc/g++ 4.9.x instead of 5.x.

Attempt to recover lost streams

Report from SD forums is that some devices (Amazon FireXXX in this case) can temporarily lose connection to the RECORD engine/tuners if DHCP changes their IP address. Look into a way to make at least one or two reasonable attempts to recover streams that stopped prematurely.

The trick here may be figuring out if the stream ended or if it was interrupted. A live stream that switched to recorded but was never seeked will still appear to be live to the PVR.

Provide an option to load/use extended guide data

It should be feasible to use the channel-specific guide data available from the online backend to feed the Kodi guide rather than just using the small bulk data. The channel specific requests are notably slower and would need to be done in a loop since only the start time can be provided, but it should be relatively easy to satisfy the Kodi guide requests realtime and not feed from the local database at all. The local database and the bulk guide data will still be required to provide the proper channel names and back up the existing queries that join against it.

I'm thinking this can be an option, "Use extended Electronic Program Guide (EPG) data", let the user decide if they want to take the time/network hit to get more guide data. Default will probably be OFF for this.

Initial tests show it's reasonable, but definitely not as fast as I would prefer. On the flip side, Kodi will be dealing with when to load the data and there doesn't need to be a scheduled task to handle it.

Error being logged by Android: database is locked

Android Jarvis (x86) is logging the "database is locked" error in GetChannels (pvr.cpp). Not sure if this is a defect in the Jarvis baseline or specific to android/android-x86 yet. Need to investigate, if the problem is something systemic with the updated SQLite (3.17.0) it will cause users an unending amount of annoying problems.

1.2.2 linux skip and ff/rw issue

Hi,
Let me say great work.

But since the latest update the skip and fast forward / rewind has not worked well on my libreelec kodi 17.3 boxes. In both recorded content and paused live content the skip will only do 10 seconds even when it was press multiple times and shows on the screen it would be skipping more. Fast forward seems to be only 2x even when 4x, 8x, 16x, or 32x are showing. The show time counts up quickly but when play is pressed it jumps back to a 2x time.

These were working well on the previous version. If you need more information or can't recreate the issue I let me know.

Live TV stopped working

Have been enjoying the app, great work! I have been running it on my shield with great success the last few months now. I recently adding a couple more shields around the house as well in the last week. Last night, in the middle of Thursday night football, it stopped streaming Live TV and now, I can't get it to work. Really weird. It will not stream live TV but will record programs. I am sure what happened? Thoughts?

Excessive DNS requests (over 200k per day)

While troubleshooting an unrelated issue, I discovered that every 5 minutes, my Kodi install is doing about 1000 DNS lookups for the A and AAAA records of api.hdhomerun.com.

My Kodi install is fairly basic. The only HDHR-related addon I use is the pvr.hdhomerundvr addon.

Any idea what's going on? Is there some DNS lookup that's happening per-channel every 5 minutes?

Currently this is resulting in over 200,000 DNS lookups per day from my Kodi install, looking for api.hdhomerun.com.

I appear to be using version 1.2.6 of pvr.hdhomerundvr on Kodi 15.2 on Ubuntu Linux.

Legacy devices causing phantom channel zero to appear in Kodi

When a legacy HDHomeRun device is detected via the my.hdhomerun.com HTTP API, and if the firmware of that device is new enough, it will be listed as a valid device in the database. When the channel lineup URL is queried, the string 'null' is returned from the backend. This causes a phantom channel 0 to be sent into Kodi, which causes some general havoc, especially with the EPG.

To fix this problem, devices returned from my.hdhomerun.com with the 'Legacy' flag set should be ignored. Also add protection into the lineup query to specifically look for JSON that contains just the string 'null' in case there are other conditions that may cause this in the future.

This issue will be marked as closed when version 1.0.5 has been tested and released.

Revisit options for increasing the amount of the guide data beyond 8 hours

Users have requested that more guide data beyond the provided maximum of ~8 hours be exposed. This enhancement was written off in the past as too time consuming due to the need to request each channel multiple times, but it should be revisited now that it has been specifically requested.

If the option can be made to work and the only "problem" is the amount of time/resources it takes to load, that is a decision that the end user can make; enable them to decide if it doesn't become too ridiculous to implement.

[Feature Request] Record TV (DVR feature) save video stream to local disk

@djp952 I like to make a feature suggestion, that is to add local recording functionality into this PVR client addon.

In summery; I would like to request the ability for this PVR client addons to perform local video recording / stream saving to files on the local file-system. That is, so enable local recording without an active HDHomeRun RECORD storage device on the local network or a subscription to the SiliconDust HDHomeRun DVR Service. Totally stand-alone local recordings done by the PVR client itself without any external PVR backend or DVR service what so ever.

From a user-experince point of view it would be great for an option have the ability to "record to local disk" inside this native HDHomeRun PVR client addon. In function for this, the PVR client addon would be able act a completly stand-alone DVR (Digital Video Recorder) on its own when used in Kodi (which I beleiev would be especially of interest to Kodi users running Android without having any NAS or PC to run a backend on). That is, for the PVR client addon itself to save individual video streams locally to a disk directory/folder on the local file-system. Preferably for the PVR client addon to even save as video files in MPEG-TS (.TS) format just like real stand-alone DVR devices.

This ability to do stand-alone recordings could also lead more DVRs stand-alone features which have dependency on recording, like the ability to "Pause" and "Rewind" Live TV for timeshifting if could add the possibility to continuously record a video streaming from a networked-attached HDHomeRun tuner to a series of temporary files in a look, again acting just like a read stand-alone DVRs (DVR boxes).

As you know, compaing to other PVR client addons for Kodi, all such recording functionality is normally located and dependent in an external PVR/DVR backend instead of the PVR client addon itself, (just as your PVR client addon is currently dependent on SiliconDuct's HDHomeRun DVR service as a PVR backend) but this addon is kind-of special and somewhat unique in that it connects to the (network-attached) TV-tuner directly, streaming directly from, so technically it could be changed so it would not actually have to go through a PVR backend at all which can bring such local recording functionality. And in addition it would be very nice to have the ability for the video files to be saved locally directly on an Android device (or more specicially local direct attached USB storage) instead of on the PVR/DVR backend or NAS.

PS: FYI; I have previously already made this request to your competing PVR client addon author @zcsizmadia here: kodi-pvr/pvr.hdhomerun#7 who initially said that he definitely planed to add this feature but later just closed the request without comment.

Stale episode discovery data is not being deleted from local database

There is a defect in the discovery logic that is causing stale episode data to remain in the local database when a seriesid still has a valid entry in the series table but no results were returned from the backend episode query.

This leads to a condition where a REPLACE INTO command does not overwrite the existing data in the episode table, leaving the affected row(s) in an unchanged state. When Kodi asks for Timer data, the stale data is queried and any flagged episodes are passed on as a valid timer with a state set to PVR_TIMER_STATE_COMPLETED.

The expected behavior is that these rows would be deleted from the episode table and nothing would be reported to Kodi for that seriesid.

Very slow loading of guide data

I just installed and enabled the plugin and it seems to be working but loading the guide data when i start kodi takes a long time. It's still loading and has been for 2-3 minutes and it's at 40%. I have the dvr service and two hdhr primes that work flawlessly in the hddvr app.

Enhance MSBUILD script

A lot of the manual steps documented in the README.md could be automated with special tasks in the MSBUILD script. It would be much easier to initialize the bash-based build environment this way rather than giving people a ton of manual steps to follow.

I also want to break up the build into separate tasks: windows, linux, raspbian, android, android-apk, osx, and 'all' (default being 'all'). Folks that clone the repository are typically interested in just one type of build, they shouldn't need to do all the setup and sit through long-running builds just to get the one they want.

Note that the 'windows' build will continue to be the primary/master build, and all other builds will need to depend on it to acquire the tmp/version.h file.