Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
troubleshooting:communication_errors [2023/11/13 01:31] – [Guided support] nedstroubleshooting:communication_errors [2023/11/14 15:39] (current) – nickk
Line 1: Line 1:
 ====== Troubleshooting communication errors ====== ====== Troubleshooting communication errors ======
 <btn type="success" size="xs" icon="fa fa-chevron-left">[[:Troubleshooting|Go back to all troubleshooting topics]]</btn>\\ <btn type="success" size="xs" icon="fa fa-chevron-left">[[:Troubleshooting|Go back to all troubleshooting topics]]</btn>\\
-<lead>Are you are receiving a "Communication error" message in the HDHomeRun app? This would indicate an issue on the network between the HDHomeRun tuner and the playback client running the HDHomeRun app. This page will help troubleshoot and correct common networking issues that can cause such communication errors.</lead>+<lead>Are you are receiving a "Communication error" message in the HDHomeRun app? This indicates a network bandwidth issue somewhere on your network. This page will help troubleshoot and correct common networking issues that can cause such communication errors.</lead>
  
 ===== Guided support ===== ===== Guided support =====
Line 7: Line 7:
 Most customers will want to open a support ticket with one of Silicondust's technical support specialists. We can help troubleshoot your specific set up and find solutions to fix the communication errors, and/or any other issues you might be having involving the HDHomeRun. Most customers will want to open a support ticket with one of Silicondust's technical support specialists. We can help troubleshoot your specific set up and find solutions to fix the communication errors, and/or any other issues you might be having involving the HDHomeRun.
  
-First, let's get some important diagnostic data that will help our technicians troubleshoot the issue:+==== Enable debug logs ==== 
 +<WRAP indent> 
 +Let's get some important diagnostic data that will help our technicians troubleshoot the issue:
  
-  - In a web browser go to http://hdhomerun.local \\ <wrap tip>NOTE: That address will go do the first HDHomeRun device found on your network. If you have more than one HDHomeRun device, use the "device ID" printed on the bottom of the unit instead of "hdhomerun" in the address. For example, if your device ID was 104FFFFF then you would go to http://104fffff.local</wrap> +  - Open the HDHomeRun app
-  - If it tells you that a firmware update is available, please [[update|install it]] +
-  - Click "System Menu" +
-  - Check the "Send diagnostic information" box (if this box is already checked, please un-check then re-check it) +
-  - Go back one page +
-  - Click "Channel Lineup" +
-  - Click on "Detect Channels" +
-  - After the scan finishes, open the HDHomeRun app+
   - Go into the app settings: the gear icon in the top right corner of the "Live/Recorded/Discover/Tasks" page   - Go into the app settings: the gear icon in the top right corner of the "Live/Recorded/Discover/Tasks" page
-  - Enable the option to "Send diagnostic information"+  - Enable the option to **"Send diagnostic information"**
   - Watch a problem channel for at least 10 minutes or until you receive the error message   - Watch a problem channel for at least 10 minutes or until you receive the error message
   - Open a support ticket here: **https://www.silicondust.com/support/trouble-ticket/**   - Open a support ticket here: **https://www.silicondust.com/support/trouble-ticket/**
-  - In your trouble ticket provide us the device ID of your HDHomeRun and we will check the logs. You can find the device ID on a label on the bottom of the HDHomeRun itself or on the http://hdhomerun.local page. +  - In your trouble ticket provide us the **device ID** of your HDHomeRun and we will check the logs. You can find the device ID on a label on the bottom of the HDHomeRun itself or on the http://hdhomerun.local page.
  
 +</WRAP>
 </WRAP> </WRAP>
  
 ===== Self-service troubleshooting ===== ===== Self-service troubleshooting =====
 <WRAP indent> <WRAP indent>
-==== TV signals are demanding ====+==== DVR record engine ====
 <WRAP indent> <WRAP indent>
-You might be asking why "only the HDHomeRun app isn't working", when your other internet streaming video apps appear to be fine. Over-the-air TV signals tend to be a lot more demanding for network bandwidth, and sensitive to network connection issues, compared to internet streaming services. Internet streaming services fully control their video streams, and can adapt them to drops in connections, different speeds, and can use more efficient video compression. Broadcast TV uses standards that were designed for over-the-air transmissions, with many transmissions still using older standards made back in the 1990s.+The optional HDHomeRun DVR record engine for PC/Mac requires that the PC/Mac be connected to your home network with enough network bandwidth available to handle many high-bitrate video streams. It is recommended that the PC/Mac be connected to the network via Ethernet and not WiFi when configured to be a HDHomeRun DVR record engine.
  
-This doesn't make broadcast video impossible, and most customers won't even notice a difference, but it is important to note that broadcast video is very different from internet streaming services.+To check if the HDHomeRun DVR record engine has been enabled on any PC/Mac computers launch the HDHomeRun app and go into Settings, Devices. Check for "HDHomeRun RECORD" entries to identify all HDHomeRun DVR record engines on your network. To disable the HDHomeRun record engine on a Windows PC run HDHomeRun Setup (if not present the Windows PC is not running the HDHomeRun DVR record engine). Go to the DVR tab and untick "Use this PC for recordings".
 </WRAP> </WRAP>
  
-==== Try a different network cable ====+==== Power line adapters ====
 <WRAP indent> <WRAP indent>
-Sometimes the issue is as simple as trying a different ethernet cable between the HDHomeRun and your router (or network switch). You will also want to try using a different ethernet port on the router, as it is possible for specific ports on a router to develop issues.+Power line network adapters can be a great way to connect your HDHomeRun unit to your router in another room, while not having to run actual Ethernet wire. However if the power line network adapters are struggling with interference or under-performing it can cause a reduction in network bandwidth resulting in a communication error. Temporarily connecting the HDHomeRun and player device without using the power line path can rule out a power line adapter issue.
 </WRAP> </WRAP>
  
-==== Checking for packet loss ====+==== WiFi ====
 <WRAP indent> <WRAP indent>
-Describe the HDHomeRun packet loss tool [[troubleshooting:network packet loss]] +While the HDHomeRun hardware will connect to your home network/router using an ethernet connection, all WiFi connections to playback devices will happen over your router's WiFi radio. Even if a WiFi connection had previously been "good enough", additional WiFi traffic (neighbor's WiFi, additional WiFi devices, etc) can impact the connection's performance. On paper an 802.11n (aka Wireless-N or WiFi 4) should be good enough for most HD-broadcasts, but if you have issues you should think about upgrading to at least 802.11ac (WiFi 5) or 802.11ax (WiFi 6).
-</WRAP>+
  
-==== Older routers and slow wifi ==== +802.11n/ac (WiFi 4/5) routers should be configured in "n only" or "performance" mode for the 2.4GHz network, and "ac only", "n/ac only", or "performance" mode for the 5GHz network. Backwards compatibility with a/b/g networks significantly degrades performance. All wireless devices connected to the network must support 11n or 11ac in order for this to work. 
-<WRAP indent> + 
-Notes about slow wifi +If the router has an option to set channel bandwidth, use the largest setting, typically 40MHz for 2.4GHz networks and 80 or 160MHz for 5GHz networks. 
-</WRAP>+ 
 +If the router supports operation in both the 2.4Ghz and 5GHz bands, try both. 5GHz is less congested and offers better performance in most circumstances, but does not go through walls and floors as well as 2.4GHz does. Bluetooth devices, many cordless phones, and other unlicensed wireless devices that operate on the 2.4GHz band can interfere with wireless networks, so avoid using them if at all possible. For cordless phones, use models that operate in the 900MHz or 1.9GHz band, not 2.4GHz.
  
-==== Mesh networks ==== +If the router permits limiting the network speed to something below its theoretical max, try utilizing that. For example, eather than the typical 108Mb/s max for 802.11n, try limiting it to 72 or 54Mb/s operation. While in theory this will limit the maximum performance of the network, in practice the network will operate more reliably at the lower speed, minimizing speed fluctuations that can cause packet loss.
-<WRAP indent> +
-Notes about mesh networks+
 </WRAP> </WRAP>
  
 ==== HDMI sticks ==== ==== HDMI sticks ====
 <WRAP indent> <WRAP indent>
-Notes about HDMI sticks and using an HDMI extender to get past the metal in the TV +If your playback device is connected to a TV set directly, such as an HDMI-stick-like device (Fire TV stick, Roku, etc), you may need to use a short HDMI extension cable. TV sets have a lot of electronics inside, and they also have a big metal shield inside of them, that can mess with the stability of the WiFi connection. Even getting just 3 or 6 inches away from the TV can often make a significant difference in getting around that.
-</WRAP> +
- +
-==== Power line adapter issues ==== +
-<WRAP indent> +
-Notes about powerline adapter issues+
 </WRAP> </WRAP>
  
-==== DVR storage ====+==== Packet loss detection tool ====
 <WRAP indent> <WRAP indent>
-Notes about DVR storage issues. Could be NAS/PC network connection, or USB drive is causing FLEX to reboot, etc.+Windows, Mac, and Linux users can use the hdhomerun_config tool to check for packet loss. See: **[[troubleshooting:network packet loss]]**
 </WRAP> </WRAP>
  
 </WRAP> </WRAP>
 {{tag>troubleshooting}} {{tag>troubleshooting}}
  • Last modified: 2023/11/13 01:31