Replies: 22 comments 27 replies
-
|
Even though I am not having any problems with being blocked lately, I would probably be willing to contribute again. SD functionality was integrated into SageTV at some point after it went open source; before that, it was a plugin. Is it time to think about moving it back into a plugin, for ease of maintainability? What are the pros and cons of keeping it integrated versus making it a plugin? |
Beta Was this translation helpful? Give feedback.
-
|
Ken always thankful for your efforts. I’m willing toBeta test any of your pre-releases and I do support your Patreon site. TomSent from my iPhoneOn Apr 10, 2026, at 9:03 AM, Ken Birch ***@***.***> wrote:
There have been a number of issues raised by users and SD that are still causing users to be blocked. I am tiered of the wack-a-mole approach to fixing these and it is not resolving these issues properly.
I am willing to do a rewrite of the error handling in this code but am looking for support in two ways.
Testers. The approach of me making changes and they go directly into a production release with only my testing is not a good one to get good results. I need a few users who are willing to test on either a test system or their prod system (risk) and provide feedback with potential for a few iterations prior to a production release.
Financial support. I plan to utilise AI to improve my chances of success in this project but there is a cost to this in addition to my efforts. I am hoping to see some users support me in this way (and thanks to those who already have).
If I get some good support on the above I will dig into this and hopefully provide a more solid solution to the SD solution.
Ken
@jusjoken
If you wish to support my efforts....
Patreon - https://www.patreon.com/user?u=58035567
Paypal - us at jusjoken.com (remove spaces and use @ instead of at)
Etransfer - us at jusjoken.com (remove spaces and use @ instead of at)
Zelle - us at jusjoken.com (remove spaces and use @ instead of at)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hmmmm, not seeing the level of interest that I would have expected. Especially considering EPG is arguably one of the most important functions in SageTV, without it you're looking at the equivalent of a 1980s VCR minus the flashing 12:00. |
Beta Was this translation helpful? Give feedback.
-
|
I'm no longer having any issues either, but always willing to send Ken some more money.... |
Beta Was this translation helpful? Give feedback.
-
|
I just now saw this topic... (this forum is a real chore to spot new postings). I'm willing to be a beta tester and have a couple of test systems in addition to my production boxes. I'm not worried about getting temporarily locked out of SD, since any lockouts have always been resolved well before the Guide's 21 days have elapsed. Thanks for your willingness to tackle this. |
Beta Was this translation helpful? Give feedback.
-
|
I can try doing some testing on my test server, especially if you alert SD to keep watch for lockouts & fixing them quickly. |
Beta Was this translation helpful? Give feedback.
-
|
Always willing to throw in a few bucks and even set up a test system if it helps. I'm not aware of any problems with the EPG at this point on my SageTV server, but I don't check the logs much either when things seem to be working fine. |
Beta Was this translation helpful? Give feedback.
-
|
I can help with testing as well. I was blocked again a couple of weeks ago with a "Token not presented" error. |
Beta Was this translation helpful? Give feedback.
-
|
I have posted a TEST JAR at the following link.... Updated May 8th 2026 with new test version This has fixes for the full set of errors that the SD API requires and hopefully now handles them the way the SD API expects. It also fixes errors we have seen occasionally where image requests are made under a generic user agent rather than the SageTV one that SD expects. There was also an issue discovered that I have seen randomly in the past where it is saying the user has debug_sd_support set to true but it is really false...that should also be fixed now. Those who wish to test I would appreciate you running this for a few weeks and report back any issues. If you reply here and let me know here (or in email to me) your SD account name then I will advise Robert at SD that you are testing. If the testing goes well I will build a release. Ken@jusjoken |
Beta Was this translation helpful? Give feedback.
-
|
Installed today on my server and EPG update worked fine. Will keep you advised. thanks for your work!
From: Ken Birch
Sent: Wednesday, May 6, 2026 8:02 PM
To: OpenSageTV/Community
Cc: TGsell1 ; Comment
Subject: Re: [OpenSageTV/Community] SD Issues - Round 2 - Error handling (Discussion #320)
I have posted a TEST JAR at the following link....
Sage Test Jar 9.2.16.1055
This has fixes for the full set of errors that the SD API requires and hopefully now handles them the way the SD API expects. It also fixes errors we have seen occasionally where image requests are made under a generic user agent rather than the SageTV one that SD expects. There was also an issue discovered that I have seen randomly in the past where it is saying the user has debug_sd_support set to true but it is really false...that should also be fixed now.
Those who wish to test I would appreciate you running this for a few weeks and report back any issues. If you reply here and let me know here (or in email to me) your SD account name then I will advise Robert at SD that you are testing.
If the testing goes well I will build a release.
Ken
@jusjoken
If you wish to support my efforts....
Patreon - https://www.patreon.com/user?u=58035567
Paypal - us at jusjoken.com (remove spaces and use @ instead of at)
Etransfer - us at jusjoken.com (remove spaces and use @ instead of at)
Zelle - us at jusjoken.com (remove spaces and use @ instead of at)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Will any of these updates asdress an issue Ive found with program names and descriptions being entirely corrupt? Initially used SageTV 9.2.2, but even after the updates above, shutting down then removing sdmd5prog and sdmd5sched and restarting and forcing an EPG update from the WEB server I still see the same errors e.g. (should be "Billy Connolly: 30 Greated Moments" I think) Im using Freeview in the UK so probably differant to most users. |
Beta Was this translation helpful? Give feedback.
-
|
Patched 3 systems (which had been running v9.2.16.1048) with Sage Test Jar 9.2.16.1056 yesterday (5/9/2026). All 3 use the SageTv service with HD200s and PlaceShifter. None are using the Client. 1st system initially burped: immediately upon restarting the Sage service with 9.2.16.1056, it logged a system message: "Schedules Direct Authentication Error. The saved user name and/or password are invalid..." I re-entered user/pass 3 times without success. Next, stopped the server service, reverted Sage.jar to v9.2.16.1048, and restarted the service without any issues. Finally, I stopped the Sage service, put Sage.jar v9.2.16.1056 in place and restarted the service; no failure this time. Manually forced an SD update on each system, which are running without issues so far. |
Beta Was this translation helpful? Give feedback.
-
|
New TEST JAR version 9.2.16.1059 posted... Added handling for SD server outages as a recent outage showed users they had an authentication error when it was a posted SD outage. It should now provide proper logging of the error and raise a system message to inform the user. Ken |
Beta Was this translation helpful? Give feedback.
-
|
Status: Patched my systems to 9.2.16.1059. Manually forced a SD update. All up and running without incident. Sure wish we had some sort of a test bench that would allow us to exercise/induce all the error conditions. I say this because I've historically had almost no SD lockouts; probably due to my Sage usage habits. This might make me a poor beta tester. |
Beta Was this translation helpful? Give feedback.
-
|
SD started blocking me again and Robert pointed me to you and I found this thread :-) THANK YOU for continuing the work on SageTV. I updated my Patreon to you. It's well worth it. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Jusjoken - Thanks as always for all of these contributions. Will keep the Patreon support going. If you run into a specific spend need (AI credits or cloud test VPS etc) let the community know. We will pitch in - I certainly will do. Separately, has anyone else discovered SchedulesDirect is currently down again? I don't want to bother Robert by email if others are already in touch and the community has an idea when he will be back online. My guide data is good until 6/5 and then my wife will be asking questions. Very much hoping he is back online by then. I can't reach their website via my main network or a backup. I was about to road-test the new jar when I thought I might be blocked and but tested my own (and 3rd party) connectivity to the website so anyone else see this too? |
Beta Was this translation helpful? Give feedback.
-
|
I get EPG Service Offline errors and their website is down too. It updated successfully yesterday. Being Saturday night, they may be doing some maintenance. If it doesn't update tomorrow night, I'll probably log a call. |
Beta Was this translation helpful? Give feedback.
-
|
I have updated to the lastest (test) version and am getting updates -- I
updated today and am good thru 6/10.
davidk
Human life is more precious than any ideology or doctrine.
-- Thich Nhat Hanh
---
…On 5/24/2026 7:44 AM, LoisGNS wrote:
I can't reach the website either, and got the same message. I'll try
again tomorrow too. I have guide data through 6/9, so hopefully it's
just a hiccup. I'm actually still on 9.2.15, and should probably dig
up the official jar for 9.2.16.
—
Reply to this email directly, view it on GitHub
<#320 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMC2CANY5F4DNWY4A26O24L44LOBXAVCNFSM6AAAAACXT76OEGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTOMBUGAYDCNY>.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I discovered that I was blocked this morning by Schedules Direct. I am on 9.2.16.1048. I am now updating to the latest beta. I also joined the Patreon as "Erv Ge;ller." Robert of SD responded to my request of what he is seeing said As I do not understand all the issues, I need to ask a simple question (to me, at least). Is what Robert sees something handled in the new beta? |
Beta Was this translation helpful? Give feedback.
-
|
@justjoken I have been blocked this morning at 9:52am. Running with test jar V9.2.16.1055, installed on May 6 which is exactly one month ago. Maybe the token expired and retrieving a new one failed? I have attached the zip file with the sagetv_0.txt log file. |
Beta Was this translation helpful? Give feedback.
-
|
Got blocked after about 6 months on .1048 You were blocked because the application was still making requests without sending a token, and you were still using a "Java" user agent. ...followed by a bunch more jpgs Updated to .1059 Does this jar apply to the client as well? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Test Jar in inital post for convenience....
Test version 9.2.16.1059
There have been a number of issues raised by users and SD that are still causing users to be blocked. I am tiered of the wack-a-mole approach to fixing these and it is not resolving these issues properly.
I am willing to do a rewrite of the error handling in this code but am looking for support in two ways.
If I get some good support on the above I will dig into this and hopefully provide a more solid solution to the SD solution.
Ken
@jusjoken
If you wish to support my efforts....
Patreon - https://www.patreon.com/user?u=58035567
Paypal - us at jusjoken.com (remove spaces and use @ instead of at)
Etransfer - us at jusjoken.com (remove spaces and use @ instead of at)
Zelle - us at jusjoken.com (remove spaces and use @ instead of at)
Beta Was this translation helpful? Give feedback.
All reactions