I checked them this morning and observed the following:
Sub Channels 7-5 to 7-11 show No Programming available in guide but does play channel.
Sub Channels 25-7 to 25-9 does show programming in guide but does not play channel.
Per Rabbit Ears these are the MPEG-4 channels in my area.
Thanks again. Now we know there is at least one other MPEG4 station that Tablo’s Apple TV app can’t play. @Lkny will have to wait for @TabloTV to figure out why.
Well this is all I can come up with for an excuse, I mean explanation. Remember that I’m really lazy about stuff.
Who wants a list of all MPEG4 stations in the US? In no particular order for some reason.
Ok so here’s a better answer to the NBC reception problem. Remember I’m really lazy.
[quote=“Lkny, post:1, topic:44291, full:true”]
NYC market, updated firmware to 2.2.56, Apple TV, tvOS 26.2
I have this problem too on my Apple TVs and phones. My Roku works fine though.
Hey Pete, I have an open ticket with the good folks at Tablo. I had uploaded some data to them from the Apple TV app and understand they’re working on a fix or at the very least identifying the problem. I emailed them this afternoon for an update but haven’t heard back.
Same issue. Can record live TV but get “playback failed, cannot decode” when attempting live TV. I want to say it’s been like this for about a month now. Quite frustrating.
Esp. last night. Seems like there was an issue with either Tablo servers or my connection to them. Tablo eventually went to offline mode, but there was no ability in the interface to choose to record a live feed, and I could not watch one because of that error. Extremely annoying.
@Lkny did you try this?
Yes, I had actually changed my ZIP Code sometime ago to try and reach some stations that my regular ZIP Code wasn’t receiving. While that change in ZIP Code did help pull in the additional stations, I decided to change it back to see if it would have any impact on my ‘playback failed’ error. Unfortunately, it did not.
Thanks but now I’m confused… The zip code change should not affect any stations your antenna got. It’s really to effect the guide data. And overlay the databases.
I’m able to scan and lock TV stations over 100 miles away during Tropo/weather events without changing the zip.
Yeah, I don’t know, all I know is with a Manhattan ZIP Code I did not pull in any MeTV stations but with a Brooklyn ZIP Code. I definitely pulled in all 4 MeTV stations. Might it have been something else and coincidental that pulled in the stations that had nothing to do with the ZIP Code change? Possibly, but that’s above my pay grade, I’m afraid.
UPDATE 1/7/26 Tablo Customer Service seems to have resolved this issue. Both stations. are now playable.
I just happened to be trying it out tonight and was pleased to see that both stations are playable.… I’d love to hear from Customer Support what exactly the problem turned out to be but I will write them a separate email to see if they can clarify
Customer Support, thanks.
Explain what this is supposed to do? I shouldn’t have to blow up my guide data to be able to watch live TV.
@TabloTV are we going to see a fix for this issue any time soon?
Okie dokie…
Sunday January 11, 2026 4:30 am CST.
Anytime the servers are not available you can get an error message.
The Content Infrastructure server is otherwise not available every night during the Guide Update.
Perhaps the Tablo Gen4-2 initiates the update but the result is the same. Error message during the update nightly.
With luck, the downtime is brief. I’ve seen it finish in under 5 minutes and I’ve seen it run for 12 hours.
When you change zip code and rescan/save you are overlaying your database info with a complete new set of guide info.
Tablo Gen4 was unusable during the evening hours with the spinner and error messages. Couldn’t watch OTA or FAST using Fire Stick 4k G2.
It did appear to record the NFL games.
Monday January 12, 2026 4:30 am CST
Android mobile won’t connect. LGTV indicates overnight Guide Update finished.
Had to uninstall and reinstall Android mobile app after reboot of the Tablo Gen4.
@TabloSupport Is this accurate?
