This is standard wired Ethernet with the playback on wireless firestick and android tv devices. I do not know how to test the network portion.
Where is your channels server in this mix? Are you using tuner sharing? If not does the problem happen when you view a live channel and the channels server is not involved?
Server is connected to the main hub in the office. I THINK I am using tuner sharing but could be mistaken but I cannot find where I set this. WE do not use other apps to view live tv as the appeal of channels is the time shifting. I do have HDHR app installed but these events usually happen after hours of tv being on so it may be hard to catch.
While looking for the tuner sharing I saw this:
Experimental Remote Live TV Segmenter
Test experimental remote Live TV Segmenter. This may fix some uncommon issues with remote Live TV streaming.
Any idea what this is or if I am experiencing the problem this might fix?
EDIT I found tuner sharing setting and turned it off to see if that helps
Look at the [SNR] Statistics for any drops in the snq, seq, bps and pps
2024/10/05 11:00:46.929928 [SNR] Statistics for ch15.1 KADN HD: ss=100% snq=100% seq=99%,7%-100% bps=6609230,1682976-14472992 pps=566,155-1239
2024/10/05 12:28:43.317552 [SNR] Statistics for ch3.1 KATC-HD: ss=98%,92%-100% snq=99%,0%-100% seq=99%,0%-100% bps=6818851,2445504-11929728 pps=583,213-1021
2024/10/05 12:30:04.683638 [SNR] Statistics for ch22.3 BuzzrTV: ss=77%,69%-82% snq=91%,0%-100% seq=84%,0%-100% bps=4416475,1765696-5008320 pps=378,151-429 sigerr=21%
2024/10/05 15:02:43.263791 [SNR] Statistics for ch3.1 KATC-HD: ss=94%,92%-96% snq=99%,70%-100% seq=99%,0%-100% bps=6770138,2465056-12316256 pps=579,218-1054
2024/10/05 16:36:44.006095 [SNR] Statistics for ch10.1 KLFY-HD: ss=78%-79% snq=99%,96%-100% seq=99%,15%-100% bps=9749098,2597408-14582784 pps=834,228-1246
2024/10/06 13:57:15.167339 [SNR] Statistics for ch10.1 KLFY-HD: ss=78%-79% snq=99%,0%-100% seq=99%,0%-100% bps=9851835,0-14645952 pps=843,0-1254
ss=Signal Strength
snq=Signal Quality
seq=Symbol Quality
bps=Bits per second
pps=Packets per second
The numbers in the log are avg_value, minimun_value-maximum_value that were sampled.
I dont think my suggestion of the network holds water after @chDVRuser grepped those errors. Snq and seq are trashed.
@Dinki are you positive the exact same issue happens with BOTH your HDHR's? If that is true then the issue has to be upstream of the HDHR's (connectors, coax, antenna). If it is happening on ONLY 1 HDHR then it is probably a bad unit.
He could also run the network packet loss test from the server pc to one of the HDHR's to see if it's a network issue.
https://info.hdhomerun.com/info/troubleshooting:network_packet_loss#troubleshooting_network_packet_loss
You should see a series of dots. "n" indicates network packet loss. "t" indicates a reception error. "s" is informational. While saving the stream, a single period . will be displayed every second. Additionally, as of the 20080609 release, the hdhomerun_config will detect reception and network errors, replacing the . with an alternative character to indicate the problem.
Example output:
............n...............................n..........ts..........
-- Video statistics --
46998 packets received, 0 overflow errors, 2 network errors, 1 transport errors, 1 sequence errors
But wouldnt he see neterr in the logs though if it were network?
I guess a question for the devs. What does their error mean "no data was received for 6s"
- That the http connection to the HDHR disconnected
- That the http connection to the HDHR is still established, but...
a) there is no transport stream
b) the transport doesn't contain a PCR
c) the transport doesn't contain a PMT
d) the transport doesn't contain PIDs
e) the transport doesn't contain any video or audio
Can you explain this a bit? What should SNQ and SEQ values be? I see some 0% values but also 100% as well
Yes this happens on multiple HDHR which makes me want to eliminate the devices as the problem. How likely would it be to have two fail at the same time? Seems unlikely.
SNQ should be 100%, minimum is 50%
SEQ should be 100%, anything lower indicates a problem with the received broadcast signal
Thanks to you both for the continued troubleshooting. I just pulled the antenna line from the amp and have fed it directly into the HDHR Connect. I'll keep a lookout on the numbers and see if I can isolate the signal problems. Crossing my finger that maybe it's the amp. I have thought about moving the tuners from the closet into my office but life is easier not doing that so I haven't yet.
Well that didn't take long. Had a failure with the amp out of the loop. Going to watch using the HDHR app and see if I can get the same sort of error using the app.
It means that we have a timer that is started each time we read from the HTTP (TCP) connection and absolutely no bytes were read in 6 seconds after we tried to start reading.
1 Like
What is "the main hub in the office" ? Is it a switch?
Can you draw a diagram of the network connections.
---------- --------------------------
| | | |->[Router?]
[HDHR Connect]->| Switch |->| main hub in the office |->[Channels DVR Server]
[HDHR Quatro]->| | | |
---------- --------------------------
|------------Closet------| |--------Office Office?
antenna in -> amp (not on) -> HDHR Connect and Quatro
HDHRs -> switch -> Ubiquiti Router -> Channels server
I've been watching a variety of channels for hours now using HDHR app with no hiccups.
Are you comparing the same channel from the same HDHR using both the HDHR app and the Channels client app at the same time? (noticed that was the reply on the SD forum)
I did not see the reply until you mentioned it. Thanks for the heads up. I will try this tomorrow.
You would want to enable tuner sharing on the Channels client app to make sure it's getting the stream from the Channels Server. That would use two tuners on the HDHR, one for the HDHR app and one for the Channels Server sharing to the Channels client.
Or better yet, and easier, record the same channel from the same HDHR that you're watching with the HDHR app.
I've set it with channel sharing and have HDHR app on one tv and the other using channels. It's been running for about 5 hours now with no hiccups of course. That's really the thing, it's hard to judge when it will happen so I'd have to set recordings all day long.
I haven't had problems with 10.1 and all the Ch10 channels until recently.
The HDHomeRun Config(Tech) test showed signal quality and symbol quality were bad.
I have rabbit ears in the attic 20 ft up from ground level, it's always been perfect until recently for Ch.10
The Ch.10 channels are VHF which can be problematic, you can find complaints on CH 10 on the web.
On the rabbit ears, VHF are the ears, UHF is the circle.
I tried another rabbitear which is inside and about 10' up and it worked fine connected directly to a TV.
Worked fine for Ch10's and others.
BUT:
So I changed my rabbit ears to a new one, which is only about 15' Up in the attic.
All is fine now.
I did slightly re-aim.
I think the antenna was the problem!!!