Separate names with a comma.
Discussion in 'TiVo Underground' started by Omikron, Apr 30, 2008.
Of potential interest to users and developers of remote control apps: Remote Proxy.
The Aspect and CC buttons now pull down menus with all the options for each, instead of cycling through. The "Aspect" label has been shortened to "Aspt." to fit. The keyboard shortcuts still cycle as before.
On startup, the TiVo selector is now always displayed (unless an address is given on the command line), even when only a single TiVo is found; and the entry box is included after the list of TiVos, so you can always enter an address that's not on the list. These changes can help in some cases where the TiVos' announcements aren't making it through the network, or for connecting to things (like rproxy without Zeroconf) that aren't announcing.
Ports other than 31339 can now be specified, on the command line, in the entry window, etc. (via colon notation, e.g. "188.8.131.52:5678"), and are now recognized via Zeroconf. Although no TiVos use ports other than 31339, this feature can be useful with rproxy (q.v.). When no port is given, 31339 is the default.
For Tivos proxied via rproxy (and assuming that the proxy is announcing via Zeroconf), the entry for the original TiVo is now automatically removed from the list of TiVos available to connect to at startup (since you can't connect to it anyway).
The Mac app bundle now uses the default Python (2.7) instead of 2.6. This is necessary to get the benefits of ttk, but it drops support for OS X 10.6 in the resulting app. (You can still use the non-app version.) Let me know if this is an issue.
Thanks for the update, wmcbrine! I'm liking the new "splash of color" on some of the buttons
I am using the Mac app bundle and it's working fine. I've only got one TiVo and have never had an issue with its announcement not making it through the network. I wanted to avoid that new confirmatory click every time I launched the app, so I manually edited line #94 in the "Network Remote.pyw" file (inside Contents/Resources,) inserting my TiVo's IP address (and then also made sure my TiVo's IP address wouldn't change from that.)
Thanks again, for your work on this very useful app, and all the great assistance and explanation you provide.
Huh... I'd have thought that would break the app signing, and OS X would therefore refuse to run it, but disturbingly, it doesn't.
Edit: It does at least say "a sealed resource is missing or invalid", but only if I inspect it. I guess it would only be blocked on first run. Ugh.
Just some workarounds for problems with rproxy, and a new icon for the OS X app.
has anyone noticed problems with the telnet on a mini after the update that changed the timeout to 4 hours?
I can telnet in, but every command I try said command not recognized.
I recently got an Android phone and have been playing around with Tasker. Has anyone tried using Tasker to control their Tivo?
It seems like it SHOULD work using a tasker-enabled Telnet client, but for some reason none of the telnet clients I have tried seem to be able to "see" my Tivo. However, the Tivo app and other "Tivo remote" apps seem to work fine. Does anyone have any tips on accessing my Tivo via an android telnet client?
My initial thought for a task would be to automatically enable parental controls at a certain time (6:00 AM) so if my kids get up and turn on TV they'd be enabled even if I was up really late with them disabled. But there are endless possibilities for things to do with tasker:
- one-button enabling/disabling of parental controls
- if it's a weekday and my commute is longer than "X" minutes, tune to the local news when I wake up.
- If a twitter account announces a police chase, tune to a news channel and begin recording.
- etc, etc
Surely I can't be the first to think of using Tasker and Tivo. Has anyone been successful getting them to work together? (or even just telnetting commands from an android phone?)
^^ I like where your head's at. Some great ideas there. Couple IFTTT.com with Tasker and TiVo and you've got yourself a winning combination right there!
I know nothing about Tasker, but note that the remote service is on port 31339, not 23 (the standard telnet port). It doesn't really use the telnet protocol, either, although telnet clients generally work.
I was using 31339, but I'm still having problems. I've been in touch with the guy who wrote the tasker "Send/Expect" plugin, and he said he's going to try it himself. If I get it working, I'll post it here.
I have been using port 31339 to control my TiVo since series 3, I can't believe in Roamio Series 5, this is still not fixed in TiVo land.
The issue is, this port just stops working (no response, no control) once you enter into a "promo" menu. The most common "promo" menu are the charmin coupon or app in TiVo Central.
If using port 31339 is the only way you are controlling your TiVo and you enter this menu, this is a big deal, especially if you are on the 3rd floor and your TiVo is in the basement viewed through a distribution system. The box either needs to be rebooted or if you still have a remote, pressing LiveTV will also allow the the port to work again.
I have tried bringing this to the attention of tech support, but they have no
idea what I am talking about. Any else know of a work around or know who and how to request TiVo finally fix this?
What actual remote program are you using? I'm using a 31339 app, and I don't have this problem on Series 4 on 20.4.1 and can navigate Charmin and the Fall preview apps.
Thanks for the response.
I have tried my own programming and I have tried one from Crestron. Both have the same issue. Once I navigate into a level or two deep into the Charmin menu, I can no longer use port 31339. I tried to close the connection the port and then open it again, but as long as I am in the Charmin menu, I lose control. Of coarse I just tried it now and there is no "promo" Charmin menu, so I can't tell you how deep I get before loosing the port.
Added a "Back" button, an "Mcr." (Macros) button (including Clock and SPS30), and a "Vid." (Video mode) button to allow direct video mode setting. Keyboard shortcuts are now bound to all buttons in Tkinter (as they had already been in Gtk), eliminating the problem of clicking on a button and losing keyboard shortcuts. Plus new zeroconf, and new icon (again).
Thanks for the update! Thhe shortcut were a problem for me a while back.
one question, is it possible to incorporate a custom skip ?
like skip ahead X minutes via a macro. kmttg has this type of feature
Not with the "Crestron" protocol.
Well, with a macro, sure -- you can do anything with a macro. You could make one that was just ['ADVANCE', 'ADVANCE', 'ADVANCE', 'ADVANCE']. But to me, it seems just as easy to hit the equals key four times... I can already skip faster that way than with the real remote.
I'm not sure if this is generally known, but I got access to a THR-22 (DirecTV TiVo) the other day, and the port 31339 remote interface works there. I got a weird name for the TiVo in my network remote (and there seems to be no way to set the name), but otherwise it worked fine.
Great remote, love the simplicity!
1) I like how the "c" button toggles closed caption on/off. Can the button on the remote also do the same? Seems like extra work to click button, then select on off.
2) Is there an android app for this? I know there are others, but it'd e great to have a single interface between platforms.
That's how it worked before 0.29. The problem is, since 0.25 -- prior to that, this button was a true toggle, which sent a sequence of keys to navigate the Info menu -- I use the direct CC codes, IRCODE CC_ON and IRCODE CC_OFF. But the remote program has no way to determine what caption state the TiVo is in; so, to make this work as a toggle, I arbitrarily assumed a state at startup (off), and alternated the command sent, based on that state. Half the time, that starting assumption would be wrong, requiring an extra press to get the desired result (although the caption status syncs up after the first press). And you'd basically have to wait for a caption to appear (or not appear) to even know that you weren't in the right state yet.
That was always a kludge. Although the shortcut key still works that way (since I don't want to assign two shortcut keys to caption control), the pull-down menu button now allows you to choose the new caption status directly, regardless of the current status, or the remote program's ignorance thereof. This is how it should work.
There's no Android version of my remote, no. There are a number of Android apps that use the Crestron interface, which are worth checking out -- although they're limited compared to the official TiVo app, they also lack some of its problems. I'd just do a search for "tivo" on the Play store to find them. But offhand, I know of RCX and DVR Commander, and an older one that's not on the store anymore. (Edit: As I think of it, I'm not sure DVR Commander doesn't use the iPad interface instead of Crestron. Anyway, it's an alternative to check out.)
You could have a toggle if you had the code for the function with simply math.
IRCODE_CC_on = 1,
IRCODE_CC_off = -1,
if CC_Toggle = -1 sends "IRCODE CC_ON"
if CC_Toggle=1 sends "IRCODE CC_OFF"
then codes CC_Toggle = CC_Toggle * -1