Page 2 of 5 FirstFirst 1234 ... LastLast
Results 11 to 20 of 42

Thread: HDHR3-US Issue

  1. #11
    Join Date
    May 2006
    Location
    Canada
    Posts
    29,167
    How old is the firmware on your devices?

    Quote Originally Posted by sub View Post
    If you open this in your browser, does it list the channels?
    http://192.168.1.82/lineup.xml?show=found
    That doesn't work on legacy devices


    Martin

  2. #12
    Join Date
    Jul 2019
    Location
    Texas, USA
    Posts
    18
    page not found 404

  3. #13
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    91,181
    Quote Originally Posted by mvallevand View Post
    That doesn't work on legacy devices
    I wasn't sure if his was a legacy device or not. Mine has the same case shape and style, but does have the lineup.xml.

  4. #14
    Join Date
    Jul 2019
    Location
    Texas, USA
    Posts
    18
    Firmware is version 20170930. It seems to be the latest according to SiliconDust for this device.

  5. #15
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    91,181
    Bee do you have the "C:\Program Files\Silicondust\HDHomeRun" directory with software in it?

  6. #16
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    91,181
    or "apt-get install hdhomerun-config" on non-windows platforms.

  7. #17
    Join Date
    Jul 2019
    Location
    Texas, USA
    Posts
    18
    I've got both Win10 and Linux versions.

  8. #18
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    91,181
    I think what is happening is that it's initially trying to scan using the modern approach with lineup.xml, but after that fails, it's looking for the device again, but not correctly detecting that it's a legacy device, so not falling back to the legacy scan.

    I'm checking why that recheck isn't seeing the device as a legacy device.

  9. #19
    Join Date
    May 2006
    Location
    Canada
    Posts
    29,167
    Quote Originally Posted by sub View Post
    I wasn't sure if his was a legacy device or not. Mine has the same case shape and style, but does have the lineup.xml.
    The json tells you

    "Legacy": 1,

    Martin

  10. #20
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    91,181
    The app does two types of scan for device discovery, one that uses the SiliconDust url, and one that uses a UDP broadcast, which results in these types of messages:

    2019-07-17 15:19:28.404 [DEBUG][6] HDHOMERUN_TAG_DEVICE_TYPE: 1
    2019-07-17 15:19:28.404 [DEBUG][6] HDHOMERUN_TAG_DEVICE_ID: 103BE535
    2019-07-17 15:19:28.404 [DEBUG][6] HDHOMERUN_TAG_DEVICE_AUTH_STR
    2019-07-17 15:19:28.404 [DEBUG][6] HDHOMERUN_TAG_TUNER_COUNT: 2
    2019-07-17 15:19:28.404 [DEBUG][6] HDHOMERUN_TAG_BASE_URL: http://192.168.1.81:80
    2019-07-17 15:19:28.404 [DEBUG][6] ...
    2019-07-17 15:19:28.404 [DEBUG][6] HDHOMERUN_TAG_DEVICE_TYPE: 1
    2019-07-17 15:19:28.404 [DEBUG][6] HDHOMERUN_TAG_DEVICE_ID: 1032BCF0
    2019-07-17 15:19:28.404 [DEBUG][6] HDHOMERUN_TAG_DEVICE_AUTH_STR
    2019-07-17 15:19:28.404 [DEBUG][6] HDHOMERUN_TAG_TUNER_COUNT: 2
    2019-07-17 15:19:28.404 [DEBUG][6] HDHOMERUN_TAG_BASE_URL: http://192.168.1.82:80
    I think it's somewhere in that second type of scan where things are getting confused, and not realising it's a legacy device.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •