[mythtv-users] Home Run doesn't operate with Myth

[Mike Bibbings]

On 30/08/16 10:18, GT wrote:
> On 15/08/16 10:03, GT wrote:
>> On 14/08/16 11:54, Jim Abernathy wrote:
>>>
>>>
>>>> To: mythtv-users at mythtv.org
>>>> From: GT at pl19.eu
>>>> Date: Sun, 14 Aug 2016 10:00:39 +0100
>>>> Subject: [mythtv-users] Home Run doesn't operate with Myth [may be
>>>> a    duplicate message]
>>>>
>>>>
>>>> My HD Home Run worked fine with previous generations of Ubuntu & Myth
>>>> but having upgraded to 16.04 - nada.
>>>>
>>>> The HD HR Config utility tunes stations OK.  VLC then displays TV OK.
>>>>
>>>> MythTV backend set-up finds loads of transmissions but the frontend
>>>> fails for live TV or recordings - it just sits there and sulks.
>>>>
>>>> Logically my simple mind says this has to be a Myth problem but I have
>>>> tried a range of configurations and none of them helps . . . ?
>>>>
>>>> All suggestions gratefully received!
>>>>
>>>
>> m/c is Revo Aspire R3610
>> Myth is V0.28-2-g15cf421
>> Tuner is HD-HR4-2DT (Home Run Connect)  Firmware updated to 2015 08 26
>
> Since then the system has been disassembled in order to fit an SSD.  
> At some stage during the rebuild process I DID have the HDHR running 
> again but not now.
>
> 1.    Power supply changed.
> 2.    Firmware downloaded and updated to 2015 08 26 (again).
> 3.    HDHR configuration gui installed and running.
> 4.    That config program finds TV transmissions which VLC displays.
> 5.    Myth B/E set-up: delete all tuners then install HDHR.
> 6.    Tuning process finds ~150 channels.
> 7.    Restart the m/c.
> 8.    Myth F/E live TV falls back immediately to the basic menu.
> 9.    System status show 6 tuners not recording (3 recs each).
> 7.    Unsurprisingly recordings on the HDHR also fail to capture the 
> transmission before timing out.
>
> In short the HDHR is ignoring the Myth F/E.  I am sure there is a 
> software switch or configuration option somewhere which is disabling 
> the HomeRun with MythTV.  Anyone know what might be the problem?
>
> GT
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

I don't have HDHR, but I note you have an SSD.

In step 7 how did you restart the m/c ? If it was a reboot you might 
have been hit with a problem of networking not being fully up when 
mythbackend starts, in which case it only listens on local addresses.

There is a  check you can run to see if this is the problem:

In a terminal run (probably best to check port 6543 as well):

sudo netstat -nlp|grep 6544
tcp        0      0 192.168.0.20:6544 0.0.0.0:*               
LISTEN      26862/mythbackend
tcp        0      0 127.0.0.1:6544 0.0.0.0:*               LISTEN      
26862/mythbackend
tcp6       0      0 fe80::922b:34ff:fe:6544 :::*                    
LISTEN      26862/mythbackend
tcp6       0      0 ::1:6544 :::*                    LISTEN      
26862/mythbackend
                 :::*                    LISTEN 26862/mythbackend

If you do not see the network IP (192.168.0.20 in my case)  try 
restarting mythbackend :

sudo systemctl stop mythtv-backend.service

followed by

sudo systemctl start mythtv-backend.service

and rerun

sudo netstat -nlp |grep 6544

On my systems I use /etc/network/interfaces to assign a static IP, 
rather than using DHCP Reservation on a Router (I found that using a 
Router assigned IP showed this problem, a static IP setup in 
/etc/network/interfaces does not).

As I said I do not have HDHR so may be completely off base on this.


Mike