as @nilephant hinted at previously, its probably best to wait for the Developer to weigh in at this point. youre not the only one with the issue since yesterday.
Thanks, I did remove the radio feed, rebuilt it, but it still has my channels as .1 I think I will try removing both the radio and video feed part of the environment and see if it will re do my channel numbers.
Here is what my environments looks like and it is working
You also need to reload the m3u in the dvr and probably need to delete and recreate the guide database for the channels to show correct
Yup, that's how mine looks like too. I checked on the http://172.16.5.33:8080 and I see both the playlist and epg data, that's how I know that It recreated the channels with the same .1
for example:
#EXTM3U #EXTINF:-1, channel-id="mlb-nym" channel-number="777.1" tvg-id="mlb-nym" tvg-name="NYM" tvg-logo="http://172.16.5.33:8080/images/channel-logos/nym.png", New York Mets http://172.16.5.33:8080/playlist/NYM
That did it, going back to 1.8.3 did the trick. Have to remember not to update.
Same...
I just rolled back from matty8199/channels-baseball:latest to matty8199/channels-baseball:1.8.8 and it seems to be working again...
2 Likes
yeah this is definitely broken for some reason now.
1.8.8 worked here too. Thanks!
1 Like
i've tried 1.8.8 and 1.8.3, neither work. i'm getting "could not fetch playlist"
refresh your guide?
Yeah all fails. Manually going to ip:8088/m3u(epg) fails as well
The default of the container is 8080. Did you change it to 8088? Perhaps try a different port
Yes, rolling back to 1.8.3 worked for me as well
1 Like
another successful rollback to 1.8.3 here.
anyone having luck with Big Inning though?
1 Like
Yeah sorry I change the port
have you tried refreshing or clearing credentials yet? I had to after rolling back yesterday. this is what did the trick for me: