Unofficial Kodi HDHomeRun DVR PVR Client

[djp952]

We had a power outage yesterday while Kodi and my HT computer were running. The link between Kodi and the storage location for the PVR seems to be broken now. That is, when I go to recorded TV in Kodi, there is no recorded TV, and when Koki records something, it appears to be "lost". That is, Kodi normally populates the program after a few minutes or so in the storage location. This does not occur, and also the fast forward or back no longer works. (You can pause live TV for a while, but you can't go back or forward.)

I installed the latest version of HD Homerun software. Did not help.

HD Homerun is storing on my Unraid NAS. I do not know if that is an issue or not.

Anyone have any ideas as to how I can debug this?

Thank you.

Sounds like the addon can't find the RECORD engine. When that happens, you lose Recorded TV and the ability to time-shift Live TV since it falls back to using a tuner directly. You may also see some pauses before playback of Live TV if it thinks there is a RECORD engine out there but can't contact it.

If you look in the Kodi log, you should see the discovery list from the addon:

Code: Select all

2020-02-27 23:44:19.537 T:27836  NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_devices: initiated local network device discovery (method: broadcast)
2020-02-27 23:44:20.204 T:27836  NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_devices: discovered: HDHomeRun PRIME 131EB7F7 (DVR authorized)
2020-02-27 23:44:20.204 T:27836  NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_devices: discovered: HDHomeRun PRIME 131ED0E0 (DVR authorized)
2020-02-27 23:44:20.204 T:27836  NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_devices: discovered: HDHomeRun RECORD E500A92F-F58F-F8CE-F5B8-2D10C224C933

I'm guessing that if you have "method: broadcast" on the first line (default), you won't see any entries for RECORD. If that says "method: http", the cloud service can report a non-existent RECORD device for up to 24 hours on you.

If there is no RECORD available, there's the trouble. Perhaps try rebooting the NAS to restart the service? There also should be a log file in the root of your HDHomeRun share, if you don't see one for today that is also an indication that RECORD isn't running.

How about the actual HDHomeRun app? If you run that (Windows/Android/etc), are you able to see your RECORD engine that way?

Any chance that an OS update may have been applied on the HT computer when power came back on, or perhaps a firewall setting was temporarily disabled and came back on? I recently found Windows 10 had changed my network from "Private" to "Public" for no reason, which alters the firewall rules on that OS. Wasn't able to re-install RECORD from HDHomeRun Setup since it couldn't find the NAS. Addon still worked, though.

[ctviggen]

Thank you for all that info. If anyone is using HD homerun and Unraid (as a NAS), I figured it out.

I used a docker called binhex-minidlna on the unraid NAS. That was not running after reboot of the unraid server, and was not set to startup upon reboot. So, I ran it and also set it to start automatically after reboot.

That still did not fix the problem. I had to run the HD homerun program on my Windows 10 computer and reinstall HD homerun onto my NAS. I'm not sure why I had to do this, but this worked.

I can now see all my old recordings in Kodi.

I'm hoping for the next time this happens (which is admittedly rare) that everything will work again upon both my HT computer and my unraid NAS being rebooted. (Reminder to self: start the NAS first, probably.)

[signcarver]

did you do anything to make sure the hdhomerun record engine restarts... "officially" the only nas that restarts the record service are the wd myclouds... unofficially qnap, synology, and asustor packages are maintained by demonrik that should start themselves on reboot. Also many people do their own things to make sure the service starts on other devices (but can vary by NAS/linux/bsd build but the issue most have in setting such up is properly pointing to the config file and/or making sure whatever path is up prior to starting).

[djp952]

News on the macOS issue ... they got it! I tested it myself on Catalina, everything is perfect again.

It's going to take Team Kodi a couple/few days to get it finalized and to re-issue the Leia .DMG files that were Notarized to allow for this (and other) third-party binary addons to load again. If anyone is newly installing or reinstalling Kodi Leia on macOS, please either wait a bit if you can, or use a Nightly Kodi build.

I feel a little bad; I did make one somewhat ill-tempered set of comments about this out of frustration, but they totally pulled it off THANK YOU TEAM KODI.

[djp952]

OK macOS gang, you should be good to go now with the release of Leia 18.6 today. I tried it on my mac, and the addon loads just fine again, no tricks or 'Nightly' builds needed anymore. I don't know if they are going to go back and re-notarize the other 18.x .DMG files or not, but hopefully Leia 18.6 is super stable and there would be no reason to go backwards anyway

[jarrah]

OK macOS gang, you should be good to go now with the release of Leia 18.6 today. I tried it on my mac, and the addon loads just fine again, no tricks or 'Nightly' builds needed anymore. I don't know if they are going to go back and re-notarize the other 18.x .DMG files or not, but hopefully Leia 18.6 is super stable and there would be no reason to go backwards anyway

Fantastic news indeed! Thank you very much, I shall try it out this evening.

[djp952]

I apologize on the delay for this. I've run into a problem with UWP builds that are likely of my own doing from messing around with the certificate stores while trying to "fix" macOS. For now, those builds have been omitted. I'll rebuild my dev/build machine this weekend, I'm sure that will take care of it

Looks like v3.2.1 will be a very small release; just some dependency updates to stay current and one new setting for bzz to help with custom channel logos. I did add a new "Interface" settings category to get the "General" category under control a bit -- feedback good/bad on this is of course welcome, I just thought that "General" became too big for it's own good ...

Version 3.2.1~beta1 (March 5, 2020)

• Update cURL library to version 7.69.0
• Update libhdhomerun library to version 20200303
• Add "Disable backend channel logo images" option
• Add new "Interface" settings category and move options that change how data is displayed from "General" to "Interface"

If this build properly handles the channel logos request and cURL 7.69 doesn't mess anything up, I'll fix up my environment to get UWP working again, update that to Kodi 18.6 and shoot for making this formal next week. NOTE: Kodi seems to have dropped support for UWP 32-bit, so that will probably disappear as well. Shouldn't affect XBox One users, but users that want to use it on Win10 as 32-bit may be out of luck moving forward. Can't blame Kodi too much, Microsoft themselves seem to have given up on UWP.

Please do let me know if there is anything going wrong for you or I've managed to forget about past promises/requests. I'm happy to send this out as-is, but if anything else can be squeezed in to make the update more significant, I'm on board with that too. Enjoy!

Download link - Leia Only - No UWP .APPX files are available at this time (OneDrive):
https://1drv.ms/u/s!AgEGEEVzGNq-jIsxUJk ... A?e=S6dcc7

[bzz]

... Looks like v3.2.1 will be a very small release; just some dependency updates to stay current and one new setting for bzz to help with custom channel logos. I did add a new "Interface" settings category to get the "General" category under control a bit -- feedback good/bad on this is of course welcome, I just thought that "General" became too big for it's own good ...

Thank you @djp952! The new channel logo option works like a charm. The ability to control the channel logos so they compliment the Kodi skin really improves the look of things.

Custom Channel Logos


Silicon Dust Channel Logos

[djp952]

Turns out UWP was broken by Microsoft with the Feb. 2020 cumulative update; rolling that back fixed the build UWP is available on Leia, but it's now x64 only, Kodi doesn't appear to be supporting 32-bit UWP anymore.

Version 3.2.1 (March 6, 2020)

• Update cURL library to version 7.69.0
• Update libhdhomerun library to version 20200303
• Add "Disable backend channel logo images" option
• Add new "Interface" settings category and move options that change how data is displayed from "General" to "Interface"

Downloads:

• Kodi 18 "Leia" : https://github.com/djp952/pvr.hdhomerun ... -Kodi-Leia
• Kodi 19 "Matrix" : https://github.com/djp952/pvr.hdhomerun ... odi-Matrix

There honestly isn't much here. A couple COTS updates, and one new option, but no expected changes in behavior. v3.2.x has been extremely stable, I don't want to jeopardize that with any ill-conceived changes Auto-update is also live for both Leia and Matrix.

Please let me know if you run into any problems, OK?

[sillywabbit]

I’m running into this issue on a Nexus 7 tablet (2013 version) update to Marshmellow running Kodi Leia 18.5.

I can successfully install the latest Android zip file for ARM. The channel and guide all work. However, upon selecting a channel there is no video or sound. The play arrow appears in the lower left corner and the time is moving (as if the channel is playing but there’s no video or sound).

Any thoughts?

Thank you.

[djp952]

I’m running into this issue on a Nexus 7 tablet (2013 version) update to Marshmellow running Kodi Leia 18.5.

I can successfully install the latest Android zip file for ARM. The channel and guide all work. However, upon selecting a channel there is no video or sound. The play arrow appears in the lower left corner and the time is moving (as if the channel is playing but there’s no video or sound).

Any thoughts?

Thank you.

IIRC, this is common on newer Kodis and the Nexus 7. I think the "solution" is to disable hardware acceleration in Kodi, but of course that may lead to a poorly functioning device too.

If you copy/access one of the recorded .MPG files outside of the PVR, like from the "Videos" library, do you get the same results? It's very likely a systemic thing with MPEG-TS files, or the actual stream encoding within as opposed to a PVR issue. The PVR is kind of a dumb middle-man between the HDHomeRun devices and Kodi, it just takes whatever it gets and hands it off, it doesn't do any decoding or rendering on it's own.

You may also have better luck with Kodi 17.3 Krypton on that device, but I can't be certain of that. It could be a big waste of your time side-loading that just to find the same problem exists.

Have you checked the Kodi forums? There are similar, if not dated at this point, problems noted with Nexus 7. Turning off HW acceleration appears to be the primary "solution" (again quotes because it's not really a solution, it's a workaround at best)

[EddieP]

I notice a setting for EDL ... I have EDL for all my HdHomeRun recordings but it seems it does not work not skipping commercials ?

[Ken.F]

I notice a setting for EDL ... I have EDL for all my HdHomeRun recordings but it seems it does not work not skipping commercials ?

Commercial skipping works good but it needs to be set up correctly. Check out the third post in the EDL/Comskip discussion thread here: viewtopic.php?f=88&t=72172

[EddieP]

I notice a setting for EDL ... I have EDL for all my HdHomeRun recordings but it seems it does not work not skipping commercials ?

Commercial skipping works good but it needs to be set up correctly. Check out the third post in the EDL/Comskip discussion thread here: viewtopic.php?f=88&t=72172

Thanks ken adding the share as a source worked.

[jbinkley60]

I don't know that this is a PVR problem but I figured I would start here given the errors I am seeing in my logs. The short version is that on one of my Windows 10 PCs I can't get HDHomeRun to start within Kodi. It works fine installed natively on Windows 10. But if I run it under Kodi on the same machine I get the No Channels Found on Any Device error message. Port 9777 is open on the Windows firewall and shutting down the firewall doesn't make a difference. Here's the log snippets of what I am seeing.

2020-03-13 16:43:24.652 T:13908 NOTICE: ES: Starting UDP Event server on port 9777
2020-03-13 16:43:24.652 T:13908 NOTICE: UDP: Listening on port 9777 (ipv6 : false)
2020-03-13 16:43:24.731 T:13792 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: ADDON_Create: zuki.pvr.hdhomerundvr v3.2.1 loaded
2020-03-13 16:43:24.732 T:13792 NOTICE: PVR Manager: Starting
2020-03-13 16:43:24.788 T:13864 WARNING: CPythonInvoker(5): Script invoked without an addon. Adding all addon modules installed to python path as fallback. This behaviour will be removed in future version.
2020-03-13 16:43:24.990 T:13948 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: wait_for_network_task: IPv4 network connectivity detected
2020-03-13 16:43:24.990 T:13948 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_devices: initiated local network device discovery (method: broadcast)
2020-03-13 16:43:25.212 T:13848 NOTICE: Skin Helper Backgrounds --> BackgroundsUpdater - started
2020-03-13 16:43:25.736 T:13948 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_devices: discovered: HDHomeRun CONNECT QUATRO 1070F4CE (DVR authorized)
2020-03-13 16:43:25.736 T:13948 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_devices: discovered: HDHomeRun CONNECT QUATRO 10757A98 (DVR authorized)
2020-03-13 16:43:25.736 T:13948 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_devices: discovered: HDHomeRun RECORD 0F77610F-1E34-4247-9915-7D8865CAB7CB
2020-03-13 16:43:25.740 T:13948 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_lineups: initiated local tuner device lineup discovery
2020-03-13 16:43:25.779 T:13948 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_recordingrules: initiated recording rule discovery
2020-03-13 16:43:25.916 T:13948 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_episodes: initiated recording rule episode discovery
2020-03-13 16:43:26.075 T:14088 NOTICE: Skin Helper Service --> WebService - start helper webservice on port 52307
2020-03-13 16:43:26.076 T:13852 NOTICE: Skin Helper Service --> Skin Helper Service version 1.1.3 started
2020-03-13 16:43:26.264 T:13976 NOTICE: Kodi version: 18
2020-03-13 16:43:26.905 T:13948 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_recordings: initiated local storage device recording discovery
2020-03-13 16:43:27.114 T:13948 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: update_listings_task: listing discovery skipped; data is less than 18 hours old
2020-03-13 16:43:27.114 T:13948 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: update_listings_task: triggering channel update
2020-03-13 16:43:27.114 T:13948 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: update_listings_task: execute electronic program guide update
2020-03-13 16:43:27.563 T:13948 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: update_listings_task: triggering timer update
2020-03-13 16:43:27.563 T:13948 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: update_listings_task: scheduling next listing update to initiate in 86841 seconds
2020-03-13 16:43:27.693 T:13952 NOTICE: PVR Manager: Started
2020-03-13 16:43:27.921 T:13808 NOTICE: EPG thread started
2020-03-13 16:43:27.936 T:14608 ERROR: PVR::CEpgTagStateChange::Deliver: Unable to obtain EPG for client 795398121 and channel 40964! Unable to deliver state change for tag '30143163'!
2020-03-13 16:43:27.936 T:14608 ERROR: PVR::CEpgTagStateChange::Deliver: Unable to obtain EPG for client 795398121 and channel 40964! Unable to deliver state change for tag '-497709541'!
2020-03-13 16:43:27.936 T:14608 ERROR: PVR::CEpgTagStateChange::Deliver: Unable to obtain EPG for client 795398121 and channel 40964! Unable to deliver state change for tag '675062331'!
2020-03-13 16:43:27.936 T:14608 ERROR: PVR::CEpgTagStateChange::Deliver: Unable to obtain EPG for client 795398121 and channel 40964! Unable to deliver state change for tag '325208923'!
2020-03-13 16:43:27.936 T:14608 ERROR: PVR::CEpgTagStateChange::Deliver: Unable to obtain EPG for client 795398121 and channel 40964! Unable to deliver state change for tag '-624313413'!

These continue on for quite a bit and then I finally get the following:

2020-03-13 16:43:45.078 T:16844 WARNING: XFILE::CFileFactory::CreateLoader - unsupported protocol(script) in script://script.hdhomerun.view/-poster.jpg
2020-03-13 16:43:45.078 T:16844 WARNING: XFILE::CFileFactory::CreateLoader - unsupported protocol(script) in script://script.hdhomerun.view/-poster.png
2020-03-13 16:43:45.078 T:16844 WARNING: XFILE::CFileFactory::CreateLoader - unsupported protocol(script) in script://script.hdhomerun.view/-banner.jpg
2020-03-13 16:43:45.078 T:16844 WARNING: XFILE::CFileFactory::CreateLoader - unsupported protocol(script) in script://script.hdhomerun.view/-banner.png
2020-03-13 16:43:46.488 T:3952 NOTICE: script.hdhomerun.view: Version: 2019.9.15
2020-03-13 16:43:50.799 T:3952 ERROR: EXCEPTION: Index out of range
2020-03-13 16:43:50.800 T:3952 ERROR:

I've searched the Internet for the error message but can't really find anything which matches the problem I am seeing. All of my other Kodi instances work fine but none of them are under Windows (i.e. LibreElec, OSMC etc..)

Thanks,

Jeff