Can the Tablo firmware be updated so that a REST API is available on the Tablo tuner device that would allow 3rd party developers to query the tuner (on the local network) for just the over the air (OTA) channels picked up by the connected antenna. This would allow 3rd party developers the ability to create apps and interfaces (just for the OTA channels) outside of the main Tablo software? I imagine this would be a popular feature for 3rd party developers and help to create an eco system of apps that could use the device for viewing OTA channels locally and differently without burdening the main Tablo developers to create other UI interfaces that are in demand/requested. In light of the recent server outage, this could lead to alternative ways to view OTA channels when the Tablo services or the internet is down.
Why would you think using favorites has any affect on the need for internet?
I must say, my internet almost never goes down.
If it does, I unplug the antenna from the tablo and attach it to the tv to continue watching ota programming.
The antenna and Tablo device are in an optimal position to get the best signal strength and quality in my elderly mothers home, away from the TV. I don’t want to tell my elderly mother to go unscrew the coax from the Tablo tuner, run an extension coax from there using a coupler, then move the tv to find the tv tuner connection and connect the other end of the extension there, get the TV out of HDMI mode, then run a channel scan, and undo all this when everything is back to normal. Neither do I want her fiddling with another antenna and trying to find the optimal position each time for best signal quality and strength for each OTA channel. I can do that personally in my own home because I’m technically inclined, but I don’t expect my elderly mother or her elderly friends to do that.
A REST API for Tablo as a network TV tuner may help open up possibilities to view OTA channels by allowing other developers a chance to develop interfaces for it without bothering the Tablo developers or main Tablo interface. If there are any developers out there that are viewing this and agree, consider liking this topic and post in the hopes that it gives it more traction.
I think Tablo has around 10 employees. Asking for a developers API and the associated support burden (help desk, documentation, API toolkit, …) that entails is probably way beyond they can step up to.
I’m a developer myself and have much respect for all software engineers. I know the stresses it can bring and I know there are often undocumented challenges. For the last year, I have used AI extensively to generate (and fix) code in a number of code bases I oversee. What use to take months of development time from me, I can now often do in a day or less including testing when using the latest models. I have generated REST API’s with some of the latest reasoning models and it’s been great. It gets me 90-95% done with many tasks (sometimes done in one go) in minutes. Instead of having to start coding from scratch, I’m able to just review the generated code and ask the model to change and fix things where needed to meet my objective. It can also help generate documentation! I’m a big fan of its usage!
Maybe tablo uses AI and that could explain the roku app 1.0 release. Of course with the 0.9 release the guide data was consistent with the legacy guide - until 1.0. Now they have added 45 new FAST channels. I scheduled something to record on April 20th at 10:57 PM. If you go to library/all and the scheduled recording and then select failures you get the spinning wheel of death.
Lol…I was impacted by the 1.0 startup issue also if that’s what your referring to. I think it was fixed in short order relative to the implied size of the release, so I’m inclined to forgive and move on.
I’ve made many mistakes myself as a developer in the past. From my perspective, it’s part of growing as a dev and it’s the nature of the beast. I learn from my mistakes and move on. I don’t dwell on it even if others do. I’d rather focus on making my code better. I’ve learned (overtime) to overlook the sometimes harsh and unecessary feedback and focus on the constructive feedback.
I usually do some basic testing of the code I generate depending upon the impact I think it will have. If I think what I have generated can have a significant impact, then I do more extensive testing. After that, for programs that have an interface, I usually pass it on to a human peer who is a non-developer for further and more in depth testing for a while before finally releasing the release to production. Passing the code off to a non-developer for more extensive testing for a period of time frees me up to do more development or fix any bugs that were found in testing. And that cycle continues until no bugs are found and ready for release. I’ve learned to try not to squeeze in any last minute changes without adequate testing into a release to help minimize bugs making it’s way to production releases.
You got to be kidding. if you make changes to the contents and display of the guide and don’t verify that it is as reliable and consistent as the guide was before your changes I’m not sure I would classify that as development. I’ve fired more senior developers for less stupid mistakes.