[eelton]

Thanks, wmcbrine. This is fantastic. The app works great for me, allowing me to control the TiVo from two different tablets running iRule.

 

[TonyBlunt]

One issue, whenever the Tivo is restarted I have to reboot the Mac as well for the remotes to take effect, is there an easier way to maintain connection?

 

[telemark]

I'll chime in some talking points...

It's possible to put a retry that would attempt to connect after a Tivo restart, assuming its IP didn't change.

A couple examples makes it debatable if this is the best way to handle it.

What if the Tivo wasn't restarted but was switched off? Shouldn't the proxy exit instead of hanging around? Then how to tell the difference?

Even if the Tivo's coming back, is it fair to the connected clients to accept commands that won't be sent out.

Haven't fully thought it through, but I'm guessing it would be cleaner to exit whenever a Tivo goes missing. Then either external or internal controls should restart it (if desired) to a state of waiting around for a good broadcast.

And disclaimer: my opinion doesn't matter, while wmcbrine's does.

 

[telemark]

This is the smallest patch I could find against 0.5, that will cause rproxy to exit when it gets a network error back from the Tivo.

If you set Lingon to "Always", rproxy should exit when the Tivo is back up, and Lingon will restart it.

Turning off the Tivo for an extended time might eventually cause undesirable behavior on the Mac, as described earlier but really depends on how Lingon is written.

# diff ~/rproxy0.5/rproxy.py /usr/local/bin/rproxy.py 
282,283c282,283
<     thread.start_new_thread(status_update, (tivo, listeners, target, verbose))
<     serve(queue, listeners, host_port)
---
>     thread.start_new_thread(serve, (queue, listeners, host_port))
>     status_update(tivo, listeners, target, verbose)

Edited: a second patch that reintroduced KeyboardInterrupt detection

 

[wmcbrine]

One issue, whenever the Tivo is restarted I have to reboot the Mac as well for the remotes to take effect, is there an easier way to maintain connection?

Haven't fully thought it through, but I'm guessing it would be cleaner to exit whenever a Tivo goes missing.

These both make sense to me, so, that's what I've done now.

http://wmcbrine.com/tivo/#rproxy

Reconnecting is the default, similar to how it works in Network Remote. This doesn't (yet) work if the TiVo changes IP. To instead get telemark's behavior -- exit on disconnect -- specify "-x" when starting.

This version also reports more info in verbose mode, and -- unless you specify the server port to use -- it will automatically try the next nine ports if 31339 is already bound. This makes it a little easier to proxy multiple TiVos from the same machine.

 

[tyd450]

test post

 

[Jacksteraz]

Do you think this program would run on a Raspberry pi or an NAS, for those of us that don't leave our computers on all the time?

 

[telemark]

Yes, as long as they have python available, which if they're running linux should be available.

 

[jonstrasser]

Hi
I'm a total newbie at TiVO but have been an irule user since it's inception.
Do I just run this program on my mac, then point the rule IP to my mac's ip? also, what port do I use?

 

[wmcbrine]

Do I just run this program on my mac, then point the rule IP to my mac's ip?

Yes.

also, what port do I use?

31339 is the default.

 

[wmcbrine]

Version 0.7 of rproxy is out now. This just adds support for Python 3.x.