1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

PyTivo server appears grayed out in HDUI

Discussion in 'TiVo Home Media Features & TiVoToGo' started by Eccles, Dec 18, 2012.

  1. Eccles

    Eccles Mostly harmless

    350
    0
    Dec 27, 2001
    Austin, TX
    I've just bought a new Premiere, and I notice that my PyTivo server appears grayed out and with an orange exclamation point icon in My Shows if I use the HDUI.

    If I switch to the SDUI, it appears bright and with a PC icon, just as it does on my TiVo HD.

    Regardless of which UI I use, I can access the PyTivo server, browse, and download content just fine, so obviously there's nothing actually wrong, but that display mode would suggest that not everything is quite right.

    Has anyone else noticed this behavior? Is this something that has been addressed in a newer version of PyTivo? I haven't updated mine in several months, on the basis of "if it ain't broke, don't fix it."
     
  2. Eccles

    Eccles Mostly harmless

    350
    0
    Dec 27, 2001
    Austin, TX
    Thanks for that - I did search for "exclamation point" but only in the subjects. Per that thread, I've tried setting Zeroconf to True and restarting PyTivo, but still I see ! and a grayed-out name. I guess it's time I updated my PyTivo.
     
  3. wmcbrine

    wmcbrine Ziphead

    10,364
    22
    Aug 2, 2003
    You should, but it's unlikely to help. :) Zeroconf is on by default already. This is the relevant part: "This would also apply if your Zeroconf packets weren't getting through, for whatever reason (a lot of people seem to have trouble with this)." Zeroconf relies on multicast. Apparently, a lot of (crappy) routers have problems with it. You may have an option in the router's menus to allow it.
     
  4. Eccles

    Eccles Mostly harmless

    350
    0
    Dec 27, 2001
    Austin, TX
    I'm not sure how the router would figure into it, since the PyTivo PC and the TiVo are both on the same LAN segment and thus traffic between them doesn't pass through the router.

    Perhaps the assumption is that the router is also the wireless access point, but that's not the case here - I have a separate AP that does no packet filtering.

    Still, it's an avenue I may need to explore, since it's still not working even after upgrading to the latest wmcbrine git. I did try changing the "beacon" setting from 192.168.0.255 to 192.168.0.115 - the explicit address of my Premiere - but it made no difference.
     
  5. wmcbrine

    wmcbrine Ziphead

    10,364
    22
    Aug 2, 2003
    The "beacon" keyword is for the old-style beacon; it has no effect on Zeroconf.
     
  6. Eccles

    Eccles Mostly harmless

    350
    0
    Dec 27, 2001
    Austin, TX
    Understood. I've put it back to .255 for the sake of consistency. One thing I notice is that while my HD makes only one GET call when the server is restarted, the Premiere repeats its GET two, three, or even four times. It's as though it's not getting the answer it was expecting, so it asks again. Is that possible/likely?

    For the record, here's my pytivo.conf:
    Code:
    [Media Server]
    type = video
    path = \\tower\media
    
    [Offloads]
    type = video
    path = \\tower\media\TiVo Recordings
    
    [_tivo_SD]
    
    [_tivo_HD]
    video_br = 20Mi
    height = 1080
    width = 1920
    
    [Server]
    tivo_password = xxxxxxxx
    tivo_mak = 9999999999
    ffmpeg_wait = 20
    ffmpeg_pram = -threads 3
    zeroconf = true
    beacon = 192.168.0.255
    togo_path = c:\users\jon\downloads\media\Tivo Recordings\
    debug = true
    tivo_username = me@example.com
    port = 9032
    
    and here's the log from the latest run:
    Code:
    INFO:pyTivo:Last modified: Mon Dec 17 01:58:08 2012
    INFO:pyTivo:Python: 2.6.1
    INFO:pyTivo:System: Windows-post2008Server-6.1.7601-SP1
    INFO:pyTivo.beacon:Announcing shares...
    INFO:pyTivo.beacon:Registering: Media Server
    INFO:pyTivo.beacon:Registering: Offloads
    INFO:pyTivo.beacon:Scanning for TiVos...
    INFO:pyTivo:pyTivo is ready.
    INFO:pyTivo:192.168.0.111 [19/Dec/2012 09:26:15] "GET /TiVoConnect?Command=QueryContainer&Container=%2F HTTP/1.0" 200 -
    INFO:pyTivo:192.168.0.115 [19/Dec/2012 09:26:15] "GET /TiVoConnect?Command=QueryContainer&Container=%2F&DoGenres=1 HTTP/1.0" 200 -
    INFO:pyTivo:192.168.0.115 [19/Dec/2012 09:26:15] "GET /TiVoConnect?Command=QueryContainer&Container=%2F&DoGenres=1 HTTP/1.0" 200 -
    INFO:pyTivo:192.168.0.115 [19/Dec/2012 09:26:15] "GET /TiVoConnect?Command=QueryContainer&Container=%2F&DoGenres=1 HTTP/1.0" 200 -
    INFO:pyTivo:192.168.0.115 [19/Dec/2012 09:26:16] "GET /TiVoConnect?Command=QueryContainer&Container=%2F&DoGenres=1 HTTP/1.0" 200 -
    INFO:pyTivo:192.168.0.115 [19/Dec/2012 09:29:15] "GET /TiVoConnect?Command=QueryContainer&Container=%2F&DoGenres=1 HTTP/1.0" 200 -
    INFO:pyTivo.beacon:Unregistering: Media Server Offloads
    
    That last log entry intrigues me, but it doesn't appear until the server has been running for several minutes, so I doubt it would be causing the ! from the start.
     
  7. larrs

    larrs Movie Fan-Addict

    1,011
    0
    May 2, 2005
    DFW
    I had the same thing happen to me when I upgraded to wmcbrine's latest pyTivo. It went away after about 4 or 5 reboots of the computer that is my pyTivo server.
     

Share This Page