Jump to content


Photo

HDHomeRun on Windows Server 2016

HDHomeRun Server 2016

  • Please log in to reply
15 replies to this topic

#1 accarshop OFFLINE  

accarshop

    Member

  • Members
  • 22 posts
  • Local time: 08:59 AM

Posted 30 August 2018 - 08:30 PM

Has anyone had any luck getting Emby to detect tuners (HDHomeRun in my case) on Windows Server 2016?  Emby installs cleanly on 2016 and with the exception of Live TV tuner detection/access I haven't seen any Server 2016 specific issues.  When I try to detect the tuners it comes back after less than a minute that it can't find the tuners.  Manually adding them by type and IP doesn't work either.

 

In the attached log there are 2 captures. 

  • The first is debug turned on and trying to scan for the tuners.  It doesn't give you much.
  • The second is after manually adding a tuner by IP address and then attempting live playback.  Again, debug is on.

In searching the threads I see that I'm not the first to encounter this but didn't see a resolution.  Trying to diagnose this is a bit challenging as I'm not getting much to go on.  It isn't A/V or Firewall related.  Tried with both turned off.  The PC can see the tuners.  I installed the HDHomeRun setup program (20180817) and it sees the tuners and channels no problem.  I can launch a channel (have VLC installed) from the HDHomeRun Setup app and it opens and plays fine. 

 

One more confirmation Emby never talks to (locks) the tuner.  I set up 1 tuner by IP and opened 2 Emby life TV sessions.  Both sessions clocked like they were trying to connect.  While the sessions clocked I opened the HDHomeRun Setup program and attempted to stream a channel.  It worked.  The tuner wasn't committed to Emby. 

 

This 2016 server is my Media/NAS system and should be more than powerful enough to handle what I'll use Emby for.  That is if I can get past this tuner challenge.  From what I see with this I think Emby is likely the victim here.  Just how to prove it and identify what needs to be done to work around it.  Would be happy to test a diag runtime or run other tests to capture trace data.  Just let me know.

 

Any help is appreciated.

 

@

Attached Files


Edited by accarshop, 30 August 2018 - 11:14 PM.


#2 Doofus OFFLINE  

Doofus

    Advanced Member

  • Members
  • 12278 posts
  • Local time: 06:59 AM

Posted 31 August 2018 - 01:03 AM

I'm running server 2016 and I have 2 HDHR Primes. I had no problems setting them up.


  • CBers likes this

#3 accarshop OFFLINE  

accarshop

    Member

  • Members
  • 22 posts
  • Local time: 08:59 AM

Posted 31 August 2018 - 10:05 AM

D, thanks for the quick reply.  Good to know someone is using 2016 with Emby.  Now, just to understand what is hokey on my server. 

 

Could I trouble you to know what version of 2016 (1607, 1709, 1803,...), (desktop experience, core, ....) you are running, what version on HDHomeRun drivers, and if you saw anything in the attached logs that might allow you to make a suggestion(s).  

 

Thanks,

@


Edited by accarshop, 31 August 2018 - 10:37 AM.


#4 Doofus OFFLINE  

Doofus

    Advanced Member

  • Members
  • 12278 posts
  • Local time: 06:59 AM

Posted 31 August 2018 - 09:49 PM

Datacenter 1607, desktop experience

 

5b89efcf0acef_Snapshot_43.jpg

 

I haven't looked at the log. I imagine Luke may have grabbed it. I had no issues getting mine introduced.



#5 Doofus OFFLINE  

Doofus

    Advanced Member

  • Members
  • 12278 posts
  • Local time: 06:59 AM

Posted 31 August 2018 - 09:53 PM

Have you tried My HDHomerun, from the server machine?



#6 accarshop OFFLINE  

accarshop

    Member

  • Members
  • 22 posts
  • Local time: 08:59 AM

Posted 01 September 2018 - 10:24 AM

I'm on older hardware so stuck at 1607 (standard) myself.  Hadn't thought about my.hdhomerun.  The first time the page was loaded (Firefox) it took roughly 12 seconds to report the tuners.  Subsequent tests were 4 to 5 seconds.  While it was good to see it work I'm struck at the lag.  The server has been performing well.  I don't use GUI on it often but when I do I don't see this going to other sites.  Browsing to my.hdhomerun on my other systems is nearly instantaneous. 

 

One thought, when browsing for tuners in Emby it times out in less than 10 seconds.  With Firefox showing the initial report over 10 I'm wondering if it isn't timing out too quickly.  Do you by chance know if that value is exposed anywhere?

 

5b8aa3929f2eb_myhdhomerun.jpg


Edited by accarshop, 01 September 2018 - 10:35 AM.


#7 Doofus OFFLINE  

Doofus

    Advanced Member

  • Members
  • 12278 posts
  • Local time: 06:59 AM

Posted 01 September 2018 - 04:42 PM

Update your firmware. You're running on an old version.

 

Firmware update 

 

Changelog


  • CBers likes this

#8 accarshop OFFLINE  

accarshop

    Member

  • Members
  • 22 posts
  • Local time: 08:59 AM

Posted 03 September 2018 - 08:50 PM

Apologies for the delay.  Have been doing a bit of learning and rebuilding.  Should be done in the next few days and will update this post then.  In the meantime, thanks for the assistance.

 

Regarding the updating the HDHomerun firmware post.  Unfortunately that doesn't appear to be an option.  I've tried installing the latest HD Setup software on a couple different OS' to verify it wasn't a particular environment or OS that was preventing flashing the 2 HDHR3-US tuners I have.  No joy.  I've seen chatter on the SiliconDust forums that at one point they could be flashed.  Realistically, there isn't anything in the new firmware that applies to the old tuners so not really losing anything.

 

Cheers. 



#9 Doofus OFFLINE  

Doofus

    Advanced Member

  • Members
  • 12278 posts
  • Local time: 06:59 AM

Posted 03 September 2018 - 09:03 PM

Ah, you have an old model. That may be related to your issue.



#10 accarshop OFFLINE  

accarshop

    Member

  • Members
  • 22 posts
  • Local time: 08:59 AM

Posted 05 September 2018 - 11:20 PM

Will try to keep this brief.  I fall into the tl;dr crowd myself.

At the time of the original post my media server was built using Windows Server 2016 (1607) with Desktop Experience.  When I did the original build out on the server I had wanted to use 1709 but it didn't like my old hardware.  The reason I didn't want to use 1607 was there were a lot of reported issues relating to user profiles and authorities.  When I installed Emby on my server and was having trouble getting legacy HDHomeRun (HDHR3-US) tuners to work those 1607 issues kept ringing in the back of my head.  When I did some traces of Emby trying to talk to the tuners I became more concerned with them.

Since there isn't upgrade path from 1607 to 1709 or 1803 I thought I'd give 1803 (Feb 2018 package) a try.  I pulled down Windows Server 2016 (1803) and low and behold it installed clean and easy.

After setting up the server, restoring my accounts, shares, files and whatnot it was time to install Emby.  Once that was all done Emby could see the tuners and add them no problem but streams never played.  HDHomeRun Setup would report that a tuner was being used.  Turning off the firewall let the stream play.  Not a good idea to leave it that way.  :)  Doing a couple sniffs and enabling ports and traffic (UPNP) I could get it to work but it reduced the security of the server.  So, while spending money didn't appeal to me I dropped a buck twenty ($119) at Amazon for a new HDHR5-US 4 tuner.  It came in this afternoon.  Installation took seconds as did adding it to Emby.

It works nicely and just in time for AGT Live Finals.  :)

Will do some sniffs later and add to this post if I see anything but as of right now my recommendation is that if it works and is secure then don't fix it.  And if you are trying to run Emby on Windows Server 2016 1607 and/or using a legacy tuner I would recommend updating/upgrading accordingly.  It is cleaner, likely more secure, and just plain easier.

Happy days.



#11 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 138076 posts
  • Local time: 09:59 AM

Posted 06 September 2018 - 01:04 AM

Interesting, thanks for the info !



#12 Doofus OFFLINE  

Doofus

    Advanced Member

  • Members
  • 12278 posts
  • Local time: 06:59 AM

Posted 06 September 2018 - 01:42 AM

This looks to be the reason that I don't have 1803

 

https://docs.microso...arted-with-1803

 

5b90be2ac4845_Snapshot_47.jpg



#13 Doofus OFFLINE  

Doofus

    Advanced Member

  • Members
  • 12278 posts
  • Local time: 06:59 AM

Posted 06 September 2018 - 02:05 AM

I might switch back to windows 10, because of this.



#14 PenkethBoy OFFLINE  

PenkethBoy

    Advanced Member

  • Members
  • 3392 posts
  • Local time: 02:59 PM
  • LocationWarrington,UK

Posted 06 September 2018 - 09:15 AM

Or install the standard version of 2016 or is that core only as well?


Edited by PenkethBoy, 06 September 2018 - 09:17 AM.


#15 Doofus OFFLINE  

Doofus

    Advanced Member

  • Members
  • 12278 posts
  • Local time: 06:59 AM

Posted 06 September 2018 - 10:20 AM

I think because of 2019 they aren't wasting time on 2016.

#16 Doofus OFFLINE  

Doofus

    Advanced Member

  • Members
  • 12278 posts
  • Local time: 06:59 AM

Posted 06 September 2018 - 04:49 PM

Hmm...I'm getting board, again. Now maybe the time to take a run at Ubuntu, for the server.





Also tagged with one or more of these keywords: HDHomeRun, Server 2016

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users