Katoom Forever
New Member
- Joined
- Dec 23, 2018
- Messages
- 3
- Reaction score
- 1
I have been using Kodi and the SluGuy add-on to stream DSTV Now on my Firestick for the past 2 years, because the Firestick is not Google certified and Amazon does not offer a DSTV Now app for the Firestick. I have recenetly (last couple of days) found that I can no longer view the TV Shows (also known as catchup) content.
However, Live TV streams without any issues. The add-on previously played both Live TV and TV Shows content without any problems.
When attempting to play a video from TV Shows, the app simply displays a "rotating circle" icon for about 20 seconds, after which it disappears and nothing further happens.
I have installed KODI and the SluGuy add-on on my Win11 PC and experience the same problem, confirming that its not device specific.
If I use a Google certified Mediabox with the official DSTV Now app installed on it, I have no problem accessing TV Show (catchup) content.
Is anyone else perhaps experiecing the same issue when attempting to stream DSTV's TV Shows by means of Kodi and the SlyGuy add-on?
I have reported it to Matt Huismann, but he does not believe that the issue is add-on related. If other users are experieicing the same problem, I would appreciate your feedback so that I can escalate the concern.


However, Live TV streams without any issues. The add-on previously played both Live TV and TV Shows content without any problems.
When attempting to play a video from TV Shows, the app simply displays a "rotating circle" icon for about 20 seconds, after which it disappears and nothing further happens.
I have installed KODI and the SluGuy add-on on my Win11 PC and experience the same problem, confirming that its not device specific.
If I use a Google certified Mediabox with the official DSTV Now app installed on it, I have no problem accessing TV Show (catchup) content.
Is anyone else perhaps experiecing the same issue when attempting to stream DSTV's TV Shows by means of Kodi and the SlyGuy add-on?
I have reported it to Matt Huismann, but he does not believe that the issue is add-on related. If other users are experieicing the same problem, I would appreciate your feedback so that I can escalate the concern.

