SchedulesDirect account disabled

[BobPhoenix]

Was greeted with a Schedules Direct account disabled in system messages today. Checked and my account is still enabled on Schedules Direct and shows active for status. Assuming this is because of this: "SD_JSON:Server offline for maintenance". So will delete message and check again tomorrow when the message disappears from the SD site. Was curious if anyone else has the same problem?

[something fishy]

Yep same here.

[bigbill]

Me Too! Sent an email to the account listed in the message. No response. Still erroring out this morning:

Sun 5/22 6:52:53.281 [ConnRecvQueue@4216e9cc] Error communicating with server:java.net.SocketException: Socket Closed
Sun 5/22 6:52:53.281 [ConnRecvQueue@4216e9cc] Cleaning up c/s connection
Sun 5/22 6:52:53.281 [ConnRecvQueue@4216e9cc] NetworkManager CommunicationFailure : /192.168.1.XX:60027 type=1
Sun 5/22 6:52:53.281 [ConnRecvQueue@4216e9cc] MsgRecv thread is terminating for /192.168.1.XX:60027

Sun 5/22 6:27:50.118 [EPG@492fc6a7] ERROR Updating EPG Source Local Over the Air Broadcast - 921xx (sdepg)
Sun 5/22 6:27:50.118 [EPG@492fc6a7] ErrorText:expand called on Local Over the Air Broadcast - 921xx (sdepg) at Sun 5/22 6:27:49.459 expandedUntil=Sun 5/22 5:27:49.060 scannedUntil=Sat 8/16 23:12:55.807
EPG Expanding Local Over the Air Broadcast - 921xx (sdepg) at Sun 5/22 6:27:49.465

-Bill

[peternm22]

They are migrating their API from PHP to Python, they've run into a few snags by the looks of it: https://forums.schedulesdirect.org/v...ic.php?p=10535

[egeller]

Me three.

I have a trouble ticket opened with Schedules Direct. In fact, I found that SD contacted me a few hours before I discovered the issue and opened the ticket. Unfortunately, their email had gone to the spam folder.

The issue is Sage TV is sending invalid ProgramID values and that now error out and locks the account. ProgramIDs can only start with EP, SH, SP, or MV, followed by 12 (or perhaps up to 12) numbers. My data reportedly had ones with non-numeric values in the last 12 and DT in the first two positions. From the JSON call, SD can see it's coming from SageTV.

Robert Kulagowski, of SD, forwarded my information to the Sage TV developer who worked on the grabber. As of now, I have not been contacted for any further information.

If you've not done so already, you might want to open a ticket on SD to keep in the loop until this is resolved.

[dlj9999]

Thank you, egeller, for the ticket advice. I was getting the same error message this weekend.

[KeithAbbott]

Weird. Mine shows that it last updated at 3:02am this morning, and I count a full 18 days of EPG data in the program guide, with no system messages. Any idea why this would be impacting some people and not others?

Edit: It looks like SD reverted back to the PHP API, which may explain why my EPG is working properly.

[emveepee]

There was a change of API that talk place on Friday. If SageTV isn't handling the md5 of duplicated shows properly or adding tokens to artwork accounts can be disabled for 24 hours.

The server is also have issues.

Martin

[EnterNoEscape]

There are a lot of new rules that SageTV was not playing by when things were first implemented (and SD was ok with at the time). I am attempting to sort things out, but it will be a slow process. In the testing phase, I largely uncovered bugs on the SD side of things and didn't start to learn of these other things being a problem unless after go live.

When I agreed to continue this maintenance, I wasn't expecting earth moving changes to be needed to the code base. As I continue to get emails about issues caused by SageTV, I'm realizing that the best path is to just cut features and maybe fix them to work the way SD would prefer them to work in the far future. To be clear, the features that would be cut are all related to getting images for shows, so it wouldn't break the EPG's core functionality, but it would get us back in the good graces with SD.

[AlphaCrew]

Oh this is not sounding good, I hope it can all be sorted out.

Thanks EnterNoEscape for all your hard work.

[TGsell]

Guys - for what it's worth - I was having an SD issue on my WMC machines as well broght to light by your posts. There was also a JSON issue posted on the SD site (likely due to your tickets) . Anyway, it's back working as of this AM. Perhaps SS is working for you on Sage again? I still have my 14 days of Guide on Sage so as far as I can tell I never lost Guide info.

[TGsell]

Mean SD working for you.....

[emveepee]

Since they temporarily reverted to the old API it should be working as before.

Martin

[rmeden]

We (SD) have been fighting high Amazon bandwidth costs.

Analysis has shown some apps have re-downloading the same artwork and there is also illegal sharing of artwork links (probably sharing guide data as well... tons or artwork downloads from IPs that didn't download data). We're trying to crack down on it to reduce costs, holding down membership prices.

Devs were informed of the changes, and it only effects image downloads. Sounds like SageTV mis-interpreted the message, or returned a misleading message to users. *ACCOUNTS* were ever disabled, just the downloading of new images. Guide data probably continued.

I run the account side of things... I know entire accounts were never disabled.

RobertE
SchedulesDirect

[randyth]

Thanks so much for the update @rmeden. I appreciate the explanation.