I ended up buying a 4k firestick just for Tablo for one TV that a Roku Express wouldn’t handle the Tablo demands. So basically I’m saying a small extra cost upfront to cut the cord. I’ve had my Tablo for 16 months now and even with the teething pains I believe it is worth it. I’m thinking of also purchasing a Onn pro streaming box to when it is on sale.
You really need to put me on your beta test team. The new fast forward, while I can see potential, the preview screen is WAY too small. Please make it bigger.
Thanks for the response. Going to be out of town for a week or 2 so maybe when we return it’ll be fine. Pretty wishful thinking but there always a fire stick.
I also have a Roku stick I was using prior to buying this TV.
We’ll see!
It might also be interesting to hear from Tablo support on why some of us have not seen the “Connecting to Tablo” issue, since the upgrade. Clear details can sometimes be calming to users
I have tablo and Sling for recording. when I have the same recording on both I have watched on tablo. But now the table recording looks like sling on the fast forward and reverse, Both have crummy small slide shows. Plus now the tablo hangs up on reversals periodically. Roll back to the former fast forward and reverse.
Ever since the Tablo update that was pushed out this past Saturday 4/12/25 to our Rokus they can no longer connect to our Tablo. They were working fine during the day but in the evening they lost all connectivity. Firestick, Android, iOS and one of my Samsung TVs is working. I tried power cycling the Tablo, router, Rokus and TVs and nothing helped. They completely lost all connectivity to my Tablo Saturday evening. When will there be a fix for Roku? They were working fine with the new rollout for about a little over a week but now since Saturday evening neither of our two Rokus (Roku Premier and Roku Streaming Stick 4k) can connect to our Tablo. The streaming stick 4k was just purchased less then 3 weeks ago! How much longer will this take to fix?
Welp, I hit the “Connecting to Tablo” issue on my Roku Ultra tonight , but quickly discovered that I couldn’t connect from any device (i.e. phone, Firecube, firestick) in my house, so likely another Tablo specific issue. Reset didn’t reboot the Tablo, so had to power off by removing power. Everything is back up and running fine now.
Clearly not related to the current Roku app issue based on reporting I have seen, but initially very disconcerting.
I sure wish we could see logging and error messages. It would be so much easier to accurately report issues hit.
Do you have a timeline of when the connectivity issue between Roku and Gen4 Tablo (v 1.0.0) will be resolved. If this cannot be resolved soon, I will require a refund of my Gen4 Tablo and I will seek to purchase a used legacy Tablo, as it works perfectly.
On two of my three Roku devices where the Tablo app is not connecting, the old app was already on it and it just updated. After the update the app couldn’t connect. On the third, There was a Roku error message stating there wasn’t enough memory to update the app. I deleted some items, including the Tablo app and then rebooted the device. When I was able to install the app it wouldn’t connect.
Tablo worked great before the April app update. Support has given different suggestions:
Turn off caption
Send us your Roku info
Send us your Tablo ID
Oh it’s a known issue-be patient
We need to wait for Roku to fix
Join the community discussion for updates
I’m now a week past the return date of the product. Granted we don’t pay a monthly fee, be we all shelled out $100 for the device that’s now not compatible with Roku. It’s been a week. Either roll the update back or fix it.
There are 90 million active Roku accounts and only 80,000 Tablo accounts. Why are we waiting for Roku when Tablo created the issue? Seems logical this is on Tablo not Roku.
Tablo cannot push out an update. Roku does not allow that. Tablo submits the update to their app to Roku. Roku’s people look through the update and have to approve it. That takes some time that Tablo has no control over… Once Roku approves the update, Roku (not Tablo) makes the update available on their servers and it gets pushed out to Roku devices.
Tablo has little control over this schedule. At the same time, I understand why Roku would want to review these things before they go out, otherwise they risk pushing out some code that would cause problems or even damage Roku devices.
Dude, it is on Tablo to fix. They fixed the app and sent it to Roku to approve before putting on their system. Roku isn’t going to put an app on their system before putting it through whatever paces they have to.
How can anyone say Roku is to blame for having to review updates? This is a normal, standard process. Roku didn’t code the app. Is it possible that Tablo’s update was thoroughly and fully tested but Roku broke it? Who knows? Yes, there are minimum Roku platform requirements that probably have to be met by the Tablo devs.
Now, if Roku’s development platform is constantly changing and Tablo has to hit a moving target, then I can understand that - it’d be just about impossible. I just don’t think that’s what’s happening.
All I’m saying is that Roku likely has no blame in this.