Emby with HDHomeRun - no video data - until HDHomeRun software tunes in

[Michaeldjcox 1]

Ultimately this is going to be one for SiliconDust but I thought I would post here because it is related to how Emby tunes to channels.

 

I've owned an HDHomeRun Quattro for a couple of weeks now happily using it with Emby.

 

But I started to notice that when I wake up in the morning and try to tune in it cannot. 

 

HDHomeRun log will say something like:

20200118-22:39:47 Tuner: tuner0 tuning 101 BBC ONE HD (tt8qam256:674MHz-17540)
20200118-22:39:52 HTTP: rejecting request from 192.168.1.201 - no video data

(my signal strength is 94% and signal and symbol quality 100%)

 

I find I cannot tune to any channel. The device is effectively broken until I power it off and on (and Emby then has to be restarted too before it works)

 

However (and this is the interesting bit) Emby tunes as an http request.

 

If fire up "HDHomeRun Config" on linux I can tune into that channel.

20200118-22:41:56 Tuner: tuner0 streaming rtp to 192.168.1.119:45270
20200118-22:42:17 Tuner: tuner0 rtp stream ended (stop request)

But even more interesting is it tunes using rtp but once it has I can now tune from Emby again:

20200118-22:42:33 Tuner: tuner0 tuning 101 BBC ONE HD (tt8qam256:674MHz-17540)
20200118-22:42:33 Tuner: tuner0 streaming http to 192.168.1.201:36562
20200118-22:42:49 Tuner: tuner0 http stream ended (remote closed)

Anybody seen this? 

 

I'll log a trouble ticket with Silicon dust but I'm wondering - is it possible to work around this from Emby. Can Emby made to use rtp rather than http which seems to be flawed. 

Edited January 18, 2020 by Michaeldjcox

[Luke 37057]

Hi, that's really a strange one. We use their http api due to how so simple it is.

[Michaeldjcox 1]

Well I logged a support ticket.

 

They asked me to turn diagnostics on and to re-detect channels.

 

The result was it failed to find any channels (previously I had 192).

 

I tried numerous times and tried restarted the device to no avail.

 

They asked to me to return the device. 

 

Overnight I left it unplugged and in the morning turned it on and its behaving normally again able to tune and play and no re-occurrence of the http issue. 

 

So I guess the device is suspect and although I still feel my issue was more of a bug than broken hardware I'll have to replace it and see if I still have issues. 

Edited January 19, 2020 by Michaeldjcox