SchedulesDirect: request that a Jellyfin developer contact me

[robo45h]

I am hoping for a quick solution to this one.  Part of the reason we use Schedules Direct is simplicity in not having to download xml files and have it automated.

By definition this already does not have a quick solution. This is a flaw that disabled live TV programming and DVR recording of live TV -- important key functionality of Jellyfin -- and it should have been fixed within days if not hours. Now, it's free software, so hard to complain. Luckily once enough people had posted on hints to a workaround, I'm tech savvy enough to have implemented it, but i was offline for quite awhile. And during the brief time, my brother tried for only the second time to use the system. It failed him.

[terpfan1980]

Still no news on this?!

[theguymadmax]

A merged PR has been made to address this issue. It should be available in the next bugfix release, though there's no timeline for when that will occur.

[bobsey]

Hello.

Is anyone else still having issues with SchedulesDirect connectivity with Jellyfin? I am on 10.10.5, and got SchedulesDirect to unblock my account. This worked for a few days, but I am getting the following error again:

"Request to https://json.schedulesdirect.org/20141201/token failed with response "{\"response\":\"JSON_ACCOUNT_ACCESS_DISABLED\",\"code\":4005,\"serverID\":\"20141201.web\",\"message\":\"Access to account via JSON has been disabled. If you are running Jellyfin, upgrade to v10.10.5 or higher. Otherwise, please contact Schedules Direct support: service@schedulesdirect.org for more information or create a support ticket:"

Thanks.

[theguymadmax]

The last bug fix didn't fully resolve the issue. One of the developers is currently working on a solution, but it's still in the early stages.

[onemorejeff]

I just read where this "account disabled to JSON" issue is still going on 10.10.5 I am currently using the service with about 30 channels without problems. However, I did make changes to my lineup a couple days ago that resulted in refreshing the guide about 5 times in a 24 hours period and I got locked out of the JSON EPG for a day. It came back and is still running. I am rather new to all this and do not want to cause Schedules Direct any problems. I don't know if I should stop using it for a while until another fix is implemented or just leave it to run as is?

2/8/25 - I did get verification logs from SchedulesDirect that listed some of the expired tokens that have been discussed here. I'm back to pulling XML from them with a XMLTV grabber. Again, I'm a noob and hope this might help another noob.

[twich1226]

10.10.6 just dropped, I see a PR for SD image pre-fetching but I don't believe that is the issue. Anyone have any idea if we can get EPG direct SD>Jellyfin again or should we still be doing it manually?

[theguymadmax]

10.10.6 just dropped, I see a PR for SD image pre-fetching but I don't believe that is the issue. Anyone have any idea if we can get EPG direct SD>Jellyfin again or should we still be doing it manually?

I don't understand your statement. Could you clarify what you mean and post any error messages in your logs. Might be best to start a new thread.

[twich1226]

10.10.6 just dropped, I see a PR for SD image pre-fetching but I don't believe that is the issue. Anyone have any idea if we can get EPG direct SD>Jellyfin again or should we still be doing it manually?

I don't understand your statement. Could you clarify what you mean and post any error messages in your logs. Might be best to start a new thread.

Sorry if I was unclear, I was just asking if we are safe to start using Jellyfin to import the EPG from schedules direct directly again or not. I have been using the manual XML method to pull from SD because of the aforementioned failures.

Sounds like I should continue with the XML for now until the additional issue you mentioned is resolved.

[williamthrilliam]

Oh it's not resolved yet?