Channel guide no longer populating in Kodi.

[apazrjon]

Been using the add on for a couple years now. It's been awesome with my HdHomerun Record subscription. Unfortunately, the channel guide no longer populates and shows no data in Kodi. The guide is blank.

I've tried reinstalling the addon with no luck. I am on Kodi Omega stable release using a Shield TV. Any help or suggestions would be awesoME!

Thank you for your time on this addon too!

[djp952]

Hi! Sorry you're having problems!

I'm not seeing anything on this end, I'm still getting 14 days worth of data downloaded (also on Omega), so it's unlikely to be an unexpected change to the data, which has happened before :)

Let's check the easy stuff first, can you go into Settings / PVR & Live TV / General -> Client specific settings? (I think the settings need to be on 'Expert' to see this) From there, there are a couple diagnostic things we can look at.

"List discovered devices" will generate a message similar to this. Make sure you have at least one tuner that says "DVR authorized" after it and see what your listings count is. The number should be pretty high but it depends on how many channels you have:

There is also a "List recent error messages" item. This list goes away when you restart Kodi, but the addon tries to keep track of the last 10 errors it's recorded. Kind of a shortcut to looking in the Kodi log :) You'll probably just see this, but it's worth a look:

If this all looks OK, are you able to post a Kodi log file for me to look at? I can give you an e-mail address to use or you can probably just post it here.

One other thing you can try easily is in that same Client specific settings there is a "Trigger guide listing discovery", this will try to kick off an EPG update. If that doesn't work after a few minutes, check "List recent error messages" again, we might get something in there.

There is also a slim chance that the addon is OK and Kodi isn't, that can usually be fixed by simply doing a Clear Data on PVR & Live TV. You WILL lose any custom channel groups you may have made, but all the other data is in the addon so it will simply reload. You don't lose your timers or rules or anything, it's actually quite safe.

[apazrjon]

I really am not sure what is going on now, lol! Thank you so much for taking the time to help!

My HDHomeRun seems to be working just fine as a standalone with the HDHomeRun app. I am getting all my channels and channel guide data just fine within the HDHomeRun app. I can record from within the native app too.

I will say this started to happen when my Shield TV updated Kodi automatically this week. So, I even sideloaded the last Nexus version of Kodi and reinstalled the appropriate add on. I was still having the issue! Next, I factory reset my Shield and reinstalled everything fresh. I thought maybe there was some residual files from the old Kodi, and a complete fresh start might help. Nope.

I tried some of the "easy" troubleshooting you advised. I think I got you the info you requested.

1. Under "List Discovered Devices", I see my HD Homerun Prime with "record" next to it. I see 135 available channels, but no available listings

2. My "List Recent Error Messages" has nothing listed in it. Even after I "Trigger guide listing discovery", nothing really happens at all. It doesn't seem like it is doing anything, and it doesn't cause an error in the "List Recent Error Messages".

What kind of Kodi log do you need? Is there a difference between a debugging log and a regular log? Do you want the log for just the PVR component?

Again man, thank you so much for helping and keeping this add on alive!

[noticons]

I'm having this problem as well. I'm happy to send you a log if it helps figure out what to do. I've done all the steps you listed. I was getting EPG lists a while ago, but it stopped working a few months back. One difference I have is that it does not say, DVR Authorized in my "list devices" section. But I am able to stream from the device without a problem, of course.

If this all looks OK, are you able to post a Kodi log file for me to look at? I can give you an e-mail address to use or you can probably just post it here.

One other thing you can try easily is in that same Client specific settings there is a "Trigger guide listing discovery", this will try to kick off an EPG update. If that doesn't work after a few minutes, check "List recent error messages" again, we might get something in there.

There is also a slim chance that the addon is OK and Kodi isn't, that can usually be fixed by simply doing a Clear Data on PVR & Live TV. You WILL lose any custom channel groups you may have made, but all the other data is in the addon so it will simply reload. You don't lose your timers or rules or anything, it's actually quite safe.

[djp952]

Hi guys, sorry was away for a few days there.

@apazrjon, I think the problem is that your tuner isn't coming up as 'DVR authorized', that will prevent the addon from even trying to go out to get the EPG data since it needs to be associated with an authorized account :( @noticons, same thing?

I noted a couple days ago on the SiliconDust forums at least one user that had a problem with their account and SD fixed it, perhaps you guys are in the same boat? I'm afraid there isn't a great deal I can do about it personally, but I think we've definitely hit the root cause for both of you guys.

If it helps, you can mimic the steps that the addon takes in a web browser? This way you have something very specific you can point to for SD to check it out?

First, hit this url: https://api.hdhomerun.com/discover. You should get back a list of your devices like this one:

[
    {
        "DeviceID": "131EB7F7",
        "LocalIP": "192.168.0.160",
        "ConditionalAccess": 1,
        "BaseURL": "http://192.168.0.160",
        "DiscoverURL": "http://192.168.0.160/discover.json",
        "LineupURL": "http://192.168.0.160/lineup.json"
    },
    {
        "DeviceID": "131ED0E0",
        "LocalIP": "192.168.0.161",
        "ConditionalAccess": 1,
        "BaseURL": "http://192.168.0.161",
        "DiscoverURL": "http://192.168.0.161/discover.json",
        "LineupURL": "http://192.168.0.161/lineup.json"
    },
    {
        "StorageID": "E500A92F-F58F-F8CE-F5B8-2D10C224C933",
        "LocalIP": "192.168.0.220:50000",
        "BaseURL": "http://192.168.0.220:50000",
        "DiscoverURL": "http://192.168.0.220:50000/discover.json",
        "StorageURL": "http://192.168.0.220:50000/recorded_files.json"
    }
]

Pick a tuner device and copy/paste the "DiscoverURL" into the browser and you get back stuff we need like the DeviceAuth string (I've Xed mine out below) ...

{
    "FriendlyName": "HDHomeRun PRIME",
    "ModelNumber": "HDHR3-CC",
    "FirmwareName": "hdhomerun3_cablecard",
    "FirmwareVersion": "20230713",
    "DeviceID": "131EB7F7",
    "DeviceAuth": "XXXXXXXXXXXXXXXXX",
    "BaseURL": "http://192.168.0.160",
    "LineupURL": "http://192.168.0.160/lineup.json",
    "TunerCount": 3,
    "ConditionalAccess": 1
}

Now you can check your account by adding a copy of the DeviceAuth at the end of this URL. Don't include the quote marks, just the characters inside:

https://api.hdhomerun.com/api/account?DeviceAuth=

What you get back from this needs to say "DvrActive":1 in here, that's what populates that in the addon and allows for EPG to be loaded:

{
    "AccountEmail": "XXXXXXXXXXXXX",
    "AccountDeviceIDs": [
        "131EB7F7",
        "131ED0E0"
    ],
    "DvrActive": 1,
    "AccountState": "Active"
}

Again, I'm afraid there won't be much more I can directly do if this is why it's not working. I'm very certain SiliconDust will be able to help you out if something has gone awry with the DVR account, though.

Please be sure to let me know if you ARE seeing "DvrActive":1 in the account information or if what you're getting back looks nothing like what I posted above, OK?

Oh, right, logs -- I don't think we need them, but if you do want to pass along a Kodi log, you don't need to enable debugging first or anything like that, and you can send them over to me at djp952 AT gmail DOT com. Just please tell me in the subject why you're sending it to me so I don't delete it accidentally!!

I hope both of your accounts are A) the problem and B) very easy to get fixed. Well, I mean, I don't hope your accounts have problems - lol - you know what I meant :)

[noticons]

That's great. Thank you. I did try to follow the steps. I think part of the problem is that my network isn't setup for 192.168.255, etc. I am getting proper information from the https://api.hdhomerun.com/discover link, but the local IPs are all 192.168 base. I use 172.16. I suppose I need to contact SD?

[noticons]

Is there a way to program the addon to just go for specific IPs rather than using the api which seems to direct by 192.168 by default?

[noticons]

I should add that when I go through the discover process, but instead of just using the discoverURL from the first step by replacing it with the correct IP, I'm able to get further along, but when I get to the final step by adding the DeviceAuth string, it does correctly state the deviceID, but doesn't have the section on
"DvrActive": 1,
"AccountState": "Active"
I'm waiting on a callback from SiliconDust to see what the word is. I have an active subscription, but on my account page with siliconedust, it says it isn't associated. Plus, when I look at the DeviceAuth page, it has an old AccountEmail. I can see why it would be worthless to supply a specific IP to the addon at this point, since there seems to be some inability of communicating between my HDhomerun FLEX DUO and the online API.

[djp952]

Well, I may have misled you a little on the IPs :) The addon actually uses a UDP broadcast to find the tuners, the web API isn't used, so I think you're OK there. If it finds them on 172.16, that's what it will use. I was just trying to walk you through (essentially) what the addon does so you could see what it sees.

Not having "DvrActive":1 is definitely going to stop the addon from trying to go get guide data. I hope SiliconDust gets it sorted out for you ASAP!

There is another feature I forgot about we can use if SD comes back and says it all looks OK on their end, the addon has a way to create a .ZIP file will all the discovery data it gathered that we can generate if we need to. I kinda forget where it puts that or if it prompts you for a location, let's hope SD works it all out so I don't have to look that up! LOL.

Good luck, do let me know if SD wants any information that's hard to provide and we can help get it. I think "Kodi" is maybe a bad word over there now for some reason, but they always come through!

[djp952]

If it helps, here is a link to the SD forum thread I saw where somebody had a similar problem ...

https://forum.silicondust.com/forum/viewtopic.php?t=79541

[noticons]

Well, I may have misled you a little on the IPs :) The addon actually uses a UDP broadcast to find the tuners, the web API isn't used, so I think you're OK there. If it finds them on 172.16, that's what it will use. I was just trying to walk you through (essentially) what the addon does so you could see what it sees.

That's great! Makes a lot of sense. I was wondering how I could stream from the unit though the API was obviously misdirected. If the API is still getting the incorrect local IP, I'm curious how this will all work out, but I will definitely let you know. I've reached out to SD, and I'll probably get a response tomorrow, I think.
I've previously generated the zip as a test. I didn't think of looking through there to see if it had discovered the lineup, etc., though inactive. I'll regenerate it tomorrow and see what it reads.

[noticons]

Alright, update. It turns out that somehow I had deactivated (I never did it personally, lol.) my HDhomerun. So it had to be reactivated. And boom, it all worked perfectly afterward. I just had to ask them to reactivate it and the addon immediately populated after the fact. Using the API directions that you gave were helpful, since it showed that the unit wasn't DVRactive. I asked them to check that. Interestingly, the IP address information in the API is still wrong, but it doesn't matter. That's the UDP broadcast you mentioned?