I'm running Channels 4.9.0 on my Google TV. After sitting unused, I get the screen saying that it can't connect to the tuner. This happens every morning and many times during the day. I have to force quit the app then it will work. Getting tired of this. Any thoughts on what's going on? This started happening just recently. A week or so perhaps. It was perfectly reliable before that.
Next time this happens, try to connect to the HDHomerun 4k directly through their app, OR with a browser directly to whatever IP address it's on in your network. This might help narrow it down. IF it's still dead that way, then it's something with the tuner itself.
1 Like
Give some more details. Is the client wifi or wired? Are other clients having an issue?
Could be your WiFi access point or router if it's connected via WiFi.
Could also be your HDHR 4k tuner IP address is changing if you didn't set a reserved DHCP IP address for it.
The HDHomerun app connects just fine and Channels will work after force-quitting. I'm using wired Ethernet, and the address is reserved in DHCP. Since nobody else seems to be reporting this issue, I'm starting to think it is the router. I installed some minor updates recently (OpenWRT) and one of them must have affected it somehow. There's a major update available that I'm about to install. I'll see how it works later or tomorrow. Thanks for your responses.
1 Like
Updating the router didn't help. The issue continues and is getting very annoying.
I've deleted the app on the TV and reinstalled.
I've updated the HDHomerun firmware and powered off and on.
IP addresses are fixed and stable, and it's all hardwired Ethernet.
I'm trying to remove it from the channels server and re-add but can't find a way to do that.
It still looks like an app issue. When was 4.9.0 released?
Could be Power Supply
have you tried a different client like appletv, iOS device, another android TV/phone etc? Does it exhibit the same issue?
Have you tried using the HDHR official app and tried to repro the issue and will it never fail if you put it through the same tests?
Expand on this. What is your definition of unused? Does that mean that you are leaving the Channels app open at the main screen or are you leaving the HDHR live channel playing and eventually it times out? What about other content? When it is in this state will pre-recorded content play? Will TVE play?
Have you emailed support about this issue and submitted logs when it is in the broken state?
Are you using an external Google device connected to the TV via HDMI or are you using the Channels client on the embedded TV OS? If its the latter you should look into an external device instead of using the embedded OS.
Something I’ve noticed about built in TV Ethernet ports is they are an afterthought and generally stink. Not saying this is the issue, but I thought id throw in my 2 cents.
Most everything stinks on embedded TV software due to it being underpowered poorly designed. Best thing I ever did was to connect an AppleTV to my brand new top of the line Sony TV. The only thing I use the OS on the TV is to get to HDMI1.
1 Like
Make sure to provide your HDHR tuner with a Reserved DHCP IP address from your router.
Otherwise its IP address changes, or doesn't get a DHCP IP address and uses an APIPA (Automatic Private IP Addressing) IP address (169.254.x.x)
Unfortunately, there is no way to set a "Static IP address" on a consumer HDHR tuner.
There are curl commands you can use to remove an HDHR tuner IP address if you manually set it.
Otherwise, just make sure it has a fixed, stable IP address and do a Scan Network from Channels Sources in the web UI.
If your HDHR is getting a 169.x.x.x ip then it is having issues communicating with your dhcp server. The 169 address is an autoconfig address which is pretty much unusable. Could be a bad switch or a bad hdhr or some other networking issue
Could always check the HDHR System log for troubleshooting.
But sounds like his router isn't giving the HDHR tuner a Reserved DHCP IP address.
A long time ago, the HDHR Prime had an issue with its networking stack and would lose the DHCP Reserved IP and use an APIPA IP, but I don't see that's a problem with the newer HDHR units.
1 Like
YAY! I fixed the issue.
Slampman was on the right track. I had recently upgraded the network adapter on the Server and had left the old one enabled. That was causing it to, for some reason, assign an autoconfig address that it was reporting to the TV app. I disabled the unused nic and rebooted. Channels Server was now reporting the correct address and the app is happy again. So am I. Whew. Thanks all for your helps.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.