You shouldn't run pyTiVo as a service and the other way at the same time. I would recommend getting it running as a manually launched program first, since service versions can be more complicated to get going.

Try using 255.255.255.255 as the beacon setting.

 

I believe you do not need the "beacon=" line.

Under [server] for my PyTivo.conf config file, I have:

tivo_username= (use your tivo.com login)
tivo_password= (use your tivo.com password)
tivo_mak = (your tivo Media Access Key
ffmpeg = (your ffmpeg folder)
temp= (your temporary cache folder)
togo_path= (your folder to where to download)
port= 9032

 

I believe you do not need the "beacon=" line.

Under [server] for my PyTivo.conf config file, I have:

ffmpeg = (your ffmpeg folder)

That should be:

ffmpeg = (<your ffmpeg folder>\ffmpeg.exe)

It needs to be the fully qualified file name. His looks correct.

 

Thanks for all your replies.

I tried leaving beacon empty and setting it to 255.255.255.255. Neither worked.

Any other ideas?

This is quite frustrating.

Ed

 

What version of pyTivo are you using? What is your network configuration? Have you tried running NOT as a service?

 

What version of pyTivo are you using? What is your network configuration? Have you tried running NOT as a service?

Hi,

I don't see anything that tells me what the version is. I just installed it a couple of weeks ago and picked the latest version but it was not the McBrine fork; it appeared there was an even more recent fork (forget the name) and took it.

The network is fairly simple. One Win7 desktop, one Win7 notebook, one Win8 notebook and two tivos. All on 192.168.1.x

Just shut down the service and ran pyTivo.py as a console app. No difference.

Here's a bit more background info.

Two of the PC's are running pyTivo. The Win8 notebook has the new version mentioned above. The Win7 desktop has a version that's a year of two old using the McBrine fork (I think?). Both are running as a service. Neither works!

It's the Win8 version I've been focusing on so far.

I just tried running the console app on the Desktop and it caused that version to work! In the console, just after the "Scanning for Tivos" line it reports that it found both Tivos, and boom, it worked. And still works after killing the console! Strange.

As I reported in my first post, the console on the Win8 machine does not report finding any Tivos except occasionally. And when it does find them, it works.

Thanks,

Ed

UPDATE: It seemed the Win7 machine would stay connected when the service kept running and the pyTivo console was closed. This was NOT correct. After a period of time the Tivo stops seeing the pyTivo shares. So it seems I have to keep the console app running.

Running the console app on the Win8 machine does not usually work; but does on occasion.

Something is wrong with BOTH of my pyTivo installatios. Why???

Thanks,

Ed

 

Hi,

I'm still having this problem and it's on both of my Tivos and from both of my PC's.

I now find that on the Win7 PC I can connect consistently by launching pyTivo.py.

As I understand it, this should NOT be necessary as the service is always running. Restarting the service does not help nor does re-booting the PC.

Any ideas would be greatly appreciated.

Ed