My tablo was working fine until I decided to do the update just before the Super Bowl (HUGE MISTAKE). Did the update and now the Tablo is constantly dropping off the network. Roku app keeps asking to search for it over and over again. The only way to fix it is to unplug the ROKU and the Tablo and plug them back in. Then it can find the Tablo.
Once I am in a channel it works fine but if I come out I have to rinse and repeat. This all started with the new firmware 2.2.18
Every since the update my Tablo is constantly stopping and buffering. Iāve tried restarting everything and it will work for awhile, and then it will start acting up again. Very annoying.
It is connected using the RJ45 connector (so hardline).
I need this resolved ASAP. My dad is a senior citizen with Alzheimers and I canāt explain to him how to unplug and replug in the Tablo every time he wants to watch Tablo.
It wont matter, it was the Firmware upgrade. I spoke to Tablo tech support and they gave me instructions on how to revert back to 2.2.16 and when I did that everything started working again normally.
There is something wrong with their 2.2.18 firmware for sure.
The trouble shooting steps did not work. Rebooting the tablo and the entire network only gets the Tablo to work for a few minutes before the problem comes back.
The only way I was able to get it to work was to go back to the old Firmware.
HI, I Have the same problem. Roku app keeps loading and loading. You must fix it with a new version of a firmware rapidly. In the meantime I would like to downgrade to version 2.2.16. Do you have the procedure to do that?
Thank
Iām having the same issues AFTER the 2.2.18 upgrade. Yes, Iāve followed all troubleshooting tips but nothing helped. No, Iām not opening a Support case because they will blame everything on earth but wonāt admit itās a firmware issue. Iām currently only using my Tablo 4-tuner device for recording, automatically move everything to Plex overnight and watch it from there.
Would be nice though if the Tablo folks could stop the blame-anything-else-game and start looking into what in 2.2.18 along with Roku version 8 is causing this issue.
sodaman-2k, just because your working setup also has roku v8 and 2.2.18 does not mean that we must look elsewhere for the root-cause of the problem. Complex tech stuff is rarely simple āeither/orā like that.
When hunting complex technical problems we should look everywhere including at things we think are āimpossibleā - not excluding anything, not assuming anything .
Until the root-cause of a complex/elusive technical issue is identified, trust nothing without empirical demonstration of its correctness plus empirical demonstration of the falsity of its opposite. Turns out this approach can apply nicely in determining the truth or falsity of assertions & assumptions outside the technology area too.
Engineers sometimes refer to āthe dreaded third binary resultā. For example, we design a test and we are 100% sure that the device-under-test will indicate a result of ā0ā or ā1ā. And indeed 0 or 1 is the test result, 99.99% of the times we run the test. But 0.01% of the time, the result is ā42ā.