EPG123 shows schedule Direct Account expires

[cadprofessor]

Greetings,
I am Using EPG 1.7.1.4. I renewed my Schedule Direct Account for 2 more months today. The EPG123 configuration windows is not showing the new expire date. Is there something I should do to see if the Schedule Direct will send the new expire date to EPG123.

Thank you.

[StinkyImp]

If you look in your trace.log file you should see your Schedules Direct expiration date. If you're using the tray icon you can right-click and select "View Log File". That will tell you what expiration date Schedules Direct recognizes (or simply login to your SD account).

[3/19/2022 12:07:00 AM] ===============================================================================
[3/19/2022 12:07:00 AM] Beginning epg123 update execution. version 1.7.1.4
[3/19/2022 12:07:00 AM] ===============================================================================
[3/19/2022 12:07:00 AM] *** Windows 7 Professional, 64-bit [Version: 6.1.7601.23798] ***
[3/19/2022 12:07:00 AM] *** Windows Media Center [Version: 6.1.7600.16385] is installed. ***
[3/19/2022 12:07:00 AM] [ INFO] Beginning EPG123 update execution. 2022-03-19 07:07:00Z
[3/19/2022 12:07:00 AM] [ INFO] DaysToDownload: 14 , TheTVDBNumbers : True , PrefixEpisodeTitle: False , PrefixEpisodeDescription : False , AppendEpisodeDesc: False , OADOverride : True , SeasonEventImages : True , TMDbCoverArt: True , IncludeSDLogos : True , AutoAddNew: True , CreateXmltv: False , ModernMediaUiPlusSupport: False
[3/19/2022 12:07:01 AM] [ INFO] Token request successful. serverID: 20141201.web , datetime: 2022-03-19T07:06:49Z
[3/19/2022 12:07:02 AM] [ INFO] Status request successful. account expires: 2023-02-12T14:47:08Z , lineups: 1/4 , lastDataUpdate: 2022-03-18T04:31:13Z

[cadprofessor]

Here is the log. [3/19/2022 11:13:34 AM] [ INFO] Status request successful. account expires: 2022-03-19T13:45:05Z , Do I need to run the software again from the task scheduler? I update my account at 10:40am. My Schedule Direct account now shows expire date of May 19 2022.

I think I just saw the issue. Log shows ....lastDataUpdate: 2022-03-18T04:31:13Z
Thanks.

[garyan2]

I believe this due to epg123 using a still valid token from before you renewed your membership. I wouldn't worry about it until tomorrow. After epg123 gets a new token, then the new expiry date should be shown.

Sent from my SM-G965U using Tapatalk

[cadprofessor]

Thanks...I just ran it again from the task scheduler shows: Will check it again tomorrow.
2:09:26 PM] [ INFO] Status request successful. account expires: 2022-03-19T13:45:05Z , lineups: 1/4 , lastDataUpdate: 2022-03-18T04:31:13Z
[3/19/2022 2:09:26 PM] [ INFO] system status: Online , message: No known issues.
[3/19/2022 2:09:26 PM] [WARNG] Your Schedules Direct account expires in 00 days -04 hours -24 minutes.

[garyan2]

Considering how close you are to your expiration. You can force a new token by editing the registry HKLM\SOFTWARE\GaRyan2\epg123. Delete the "token" string and then open the configuration GUI. You will get a new token and should be able to see the expiration date move out 2 months.

[cadprofessor]

That worked. Thanks so much.

[Space]

...
[3/19/2022 2:09:26 PM] [WARNG] Your Schedules Direct account expires in 00 days -04 hours -24 minutes.

Perhaps it should tell you that the account expired 4 hours and 24 minutes ago instead of negative days/hours/minutes.

Also, it appears you are saying that if you already have a token, it will not be able to tell if your expiration date has been updated (subscription renewed). Is this something that can be fixed in EPG123? Do you need to get a new token in order for it to see the new expiration date?

Does it make sense to retain a token (reuse a token) if the subscription has expired? Perhaps only retain the token for reuse if the subscription is in effect?

I don't know the details of how it works, so just throwing out some ideas that may not make much sense...

I feel that if your subscription expires, EPG123 should be able to gracefully handle it. It should not allow you do things that might make the SD server block your IP (by connecting to it too many times while the subscription is expired), but it should also recognize that you have subsequently renewed your subscription and do what is required to get a new token (if that is what is needed) so you don't have to wait for the old token to expire.

These two things may be in conflict... If someone is using EPG123 to constantly connect to the SD server to get a new token, only to find out the subscription is still expired, EPG123 will probably want to rate limit that to a certain extent.

[garyan2]

There is nothing wrong with what it is doing now. I would rather the gui show the old expire date than dump a perfectly good token and risk failing getting a new one.

The expiration date is only for display and has no impact to downloading data from SD.

I didn't expect a snapshot of the user status to be tied to the token and this only became apparent once I started caching the token. Before 1.7.x.x, the configuration would always request a new token.

Sent from my SM-G965U using Tapatalk