HDHomeRun EXTEND problems

Reception, channel detection, network issues, CableCARD setup, etc.
FordGT90Concept
Posts: 2
Joined: Sat Oct 20, 2018 12:55 pm

HDHomeRun EXTEND problems

Postby FordGT90Concept » Sat Oct 20, 2018 1:24 pm

I have an open support ticket (#105335) since 10/10/2018. That ticket was opened for device 1054AECF. The behavior of that device caused the creation of this Emby support thread:
https://emby.media/community/index.php? ... -failures/

TL;DR: there were frequent issues, especially with Live TV. One of the users suggested turning off transcoding on the device which, within 15 minutes of doing so, it rebooted itself giving an application watchdog error:

Code: Select all

19700101-00:00:17 System: reset reason = application watchdog 19700101-00:00:17 System: E5592573 0000000E 004FDAF8 00441278 004484B0 00412F18 004F8A7C 004F8A50 19700101-00:00:17 System: 005246EC FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF 19700101-00:00:17 System: network link 100f 19700101-00:00:18 System: ip address obtained: 192.168.0.101 / 255.255.255.0 20181011-00:31:02 System: time changed from Thu Jan 1 00:00:36 1970 to Thu Oct 11 00:31:02 2018
At that point, I changed which HDHR EXTEND was primary to device 10581E00 (7 months old) which, at first impression, was working a lot better than 1054AECF. Then I discovered there was a failed recording on the 18th. At 6pm, it did an application watchdog reset for reasons unknown to me:

Code: Select all

19700101-00:00:20 System: reset reason = application watchdog 19700101-00:00:20 System: E5592573 0000000E 004FDAF8 00441278 004484B0 00412F18 004F8A7C 004F8A50 19700101-00:00:20 System: 005246EC FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF 19700101-00:00:20 System: network link 100f 19700101-00:00:22 System: ip address obtained: 192.168.0.102 / 255.255.255.0 20181018-23:01:04 System: time changed from Thu Jan 1 00:00:39 1970 to Thu Oct 18 23:01:04 2018 20181018-23:30:00 Tuner: tuner0 tuning 27.1 IPTV1-S (8vsb:557MHz-3) 20181018-23:30:01 Tuner: tuner0 streaming http to 192.168.0.128:55470 20181018-23:59:58 Tuner: tuner0 http stream ended (remote closed) 20181019-00:16:24 Tuner: tuner0 tuning 14.1 KMEG-DT (8vsb:623MHz-3) 20181019-00:16:25 Tuner: tuner0 streaming http to 192.168.0.128:56760 20181019-00:16:41 Tuner: tuner0 http stream ended (remote closed) 20181019-00:31:00 Tuner: tuner0 tuning 14.1 KMEG-DT (8vsb:623MHz-3) 20181019-00:31:00 Tuner: tuner0 streaming http to 192.168.0.128:57160 20181019-01:00:59 Tuner: tuner0 http stream ended (remote closed)
The recording should have happened at 00:00:00 according that log. Emby has record of the 27.1 event so I know my times are right. Emby claims to have tuned to 14.1 at 00:01 to 01:05 but it only generated a 20 KiB file in doing so (obviously inaccurate). The HDHR itself claims nothing happened at that time. Now I'm stuck between the two, wonder why it application watchdogged an hour before and why the HDHR has no record of it.

But wait, there's more! My third HDHR EXTEND also has an application watchdog:

Code: Select all

19700101-00:00:17 System: reset reason = application watchdog 19700101-00:00:17 System: E5592573 0000000E 004FDAF8 00441278 004484B0 00412F18 004F8A7C 004F8A50 19700101-00:00:17 System: 005246EC FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF 19700101-00:00:17 System: network link 100f 19700101-00:00:18 System: ip address obtained: 192.168.0.100 / 255.255.255.0 20181009-01:31:03 System: time changed from Thu Jan 1 00:00:35 1970 to Tue Oct 9 01:31:03 2018
It's too far back for me to have any records on.

11/6/2016 was the original purchase date for three.
10/16/2017 I paid for a UPS label to return one on RMA.
3/20/2018 one was pronounced dead and out of warranty by SiliconDust and I took the offer to buy a replacement at discount.

If I haven't lost count, these are my 3rd, 4th, and 5th HDHR EXTENDs and they all exhibit the same behavior that the first two were returned/discounted for.


The only thing I do that maybe most other people don't is use is the "heavy" transcode profile.

All three HDHR EXTENDs are running 20180817 firmware.

FordGT90Concept
Posts: 2
Joined: Sat Oct 20, 2018 12:55 pm

Re: HDHomeRun EXTEND problems

Postby FordGT90Concept » Tue Nov 13, 2018 8:52 pm

The newest one (192.168.0.102, Serial # 10581E00) just did it too half way through recording Magnum P.I. heavy profile:

Code: Select all

19700101-00:00:20 System: reset reason = application watchdog 19700101-00:00:20 System: E5592573 0000000E 004FDAF8 00441278 004484B0 00412F18 004F8A7C 004F8A50 19700101-00:00:20 System: 005246EC FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF 19700101-00:00:21 System: network link 100f 19700101-00:00:22 System: ip address obtained: 192.168.0.102 / 255.255.255.0 20181113-02:31:00 System: time changed from Thu Jan 1 00:00:39 1970 to Tue Nov 13 02:31:00 2018 20181113-03:00:00 Tuner: tuner0 tuning 14.1 KMEG-DT (8vsb:623MHz-3) 20181113-03:00:00 Tuner: tuner0 streaming http to 192.168.0.128:50898 20181113-03:00:00 Tuner: tuner1 tuning 4.1 KTIVNBC (8vsb:635MHz-1) 20181113-03:00:01 Tuner: tuner1 streaming http to 192.168.0.128:50899 20181113-03:00:01 HTTP: rejecting request from 192.168.0.128 - all tuners in use 20181113-03:59:59 Tuner: tuner1 http stream ended (remote closed) 20181113-03:59:59 Tuner: tuner0 http stream ended (remote closed) 20181113-23:10:15 Tuner: tuner0 tuning 14.1 KMEG-DT (8vsb:623MHz-3) 20181113-23:10:15 Tuner: tuner0 streaming http to 192.168.0.128:52128 20181114-00:58:46 Tuner: tuner0 http stream ended (remote closed) 20181114-01:00:09 Tuner: tuner0 tuning 14.1 KMEG-DT (8vsb:623MHz-3) 20181114-01:00:10 Tuner: tuner0 streaming http to 192.168.0.128:55057 20181114-01:59:59 Tuner: tuner0 http stream ended (remote closed) 20181114-02:00:05 Tuner: tuner0 tuning 44.1 KPTH-DT (8vsb:683MHz-3) 20181114-02:00:05 Tuner: tuner0 streaming http to 192.168.0.128:56761 20181114-02:00:05 Tuner: tuner1 tuning 4.2 KTIVCW (8vsb:635MHz-2) 20181114-02:00:06 Tuner: tuner1 streaming http to 192.168.0.128:56762 20181114-02:00:06 HTTP: rejecting request from 192.168.0.128 - all tuners in use 20181114-02:00:06 HTTP: rejecting request from 192.168.0.128 - all tuners in use 20181114-02:59:59 Tuner: tuner0 http stream ended (remote closed) 20181114-02:59:59 Tuner: tuner1 http stream ended (remote closed) 20181114-03:00:01 Tuner: tuner0 tuning 9.1 KCAU-TV (8vsb:189MHz-3) 20181114-03:00:01 Tuner: tuner0 streaming http to 192.168.0.128:58488 20181114-03:00:01 Tuner: tuner1 tuning 14.1 KMEG-DT (8vsb:623MHz-3) 20181114-03:00:02 Tuner: tuner1 streaming http to 192.168.0.128:58490 20181114-03:01:00 HTTP: rejecting request from 192.168.0.128 - all tuners in use
I need answers.

WashingtonMatt
Posts: 3
Joined: Mon May 15, 2017 10:24 pm

Re: HDHomeRun EXTEND problems

Postby WashingtonMatt » Fri Nov 16, 2018 5:24 pm

Replied to wrong thread, please delete.


Return to “HDHomeRun Hardware Setup & Troubleshooting”

Who is online

Users browsing this forum: No registered users and 4 guests