MythTV backend won't scan HDHomerun Connect after firmware update

Forums › Home Theatre (including HTPC and EPG Collector) › MythTV backend won't scan HDHomerun Connect after firmware update

jfstoke

18 posts

Geek

#270465 10-May-2020 22:18

A couple of weeks ago I updated the firmware on my HDHomerun Connect Duo. About the same time, MythTV showed errors when recording scheduled programmes. When I tried watching live TV, it showed "Channel Unavailable". I presume that the two events are related.

Since the Windows and Android HDHomerun apps were both successfully accessing the device, I knew that the problem was unique to the MythTV application. I tried deleting the HDHomerun from the MythTV backend, and re-creating the configuration. No improvement. I tried deleting all the channels from the MythTV backend, and doing a channel scan. The scan completed in less than 5 seconds, finishing with the message "Failed to find any channels". For completeness, I tried running /usr/bin/mythhdhomerun_config from the Ubuntu command line. This time the scan took a decent length of time, and found all the local channels.

Something seems wrong with how the MythTV backend is addressing the HDHomerun, I'm out of ideas. Has anyone else found (and solved) a similar problem?

The MythTV scan screen has:

Desired Services: TV

Unencrypted only: [checked]

Test decryptability: [Unchecked]

Video source: Source 1

Input: [HDHOMERUN:1232C5AA-0] (MPEG2TS)

Scan type: Full Scan

Scan

I'm running Ubuntu 18.04.4 LTS, MythTV v29.1-13-g329c235, HDHomerun model: HDHR4-2DT, HDHomerun Device ID: 1232C5AA, HDHomerun firmware: 20200225.

fe31nz

1228 posts

Uber Geek

#2480859 10-May-2020 23:39

Is mythbackend actually seeing the HDHR tuners at boot? There has always been a problem with mythbackend and networked tuners where mythbackend gets started before the network connection is up and when it tries to connect to the network tuner(s) at boot time, it fails to connect and marks the tuners as unavailable. The test to see if that is the problem is simply to restart mythbackend well after the network is up:

sudo systemctl restart mythtv-backend

If the tuner works after that, you will need to install one of the fixes that gets systemd to wait until the network is really up before starting mythbackend. And as this is a race condition that can start affecting you at any time when something changes, if you do not already have a fix like that installed, I do recommend doing it anyway, even if it is not your current problem.

Here is a thread on the MythTV mailing list with my fix:

https://lists.gt.net/mythtv/users/625827

jfstoke

18 posts

Geek

#2481153 11-May-2020 13:16

fe31nz:

Is mythbackend actually seeing the HDHR tuners at boot?

Yes, it is. When I deleted and re-added the HDHR tuners, it found them immediately and reported the correct firmware version. I did also try stopping the backend and relaunching, and it didn't improve the situation.

fe31nz

1228 posts

Uber Geek

#2481600 11-May-2020 23:55

You could try increasing the timeout for the scan. There have been people with that problem recently on the MythTV mailing list, but I think they were all using v31, which has had updates to the scanning code. Anyway, if the scan stops on timeout, you normally seem to get no results at all - it does not seem to report the channels it has already scanned. However, I have not done a scan myself for a long time - I have been manually updating the channels so that I do not lose any recording rules to channel name changes.

jfstoke

18 posts

Geek

#2482774 13-May-2020 13:54

fe31nz:

You could try increasing the timeout for the scan.

I tried this, and it didn't help

fe31nz: I have been manually updating the channels so that I do not lose any recording rules to channel name changes.

Finally, I've made some progress. I tried defining a channel manually (Prime) and managed to get a signal... for Apna. I've obviously misinterpreted some parameters.