This guide covers common issues with the WTH and how to fix them. Work through the section that matches your symptom. If a problem persists after trying the solutions below, contact LF Audio support.
Sensors and Readings
Sensors are wired, not paired: plug one in and its channel appears on the dashboard. A channel drops off when its sensor stops reporting.
| Issue | Likely cause | What to do |
|---|---|---|
| Dashboard shows "No sensors connected" | No sensor is plugged in, or none is reporting a valid reading yet | Connect at least one WTH Infrared Sensor or Thermocouple Temperature Probe. Give it a few seconds to be detected. If the channel still does not appear, reseat the connector and check the cable for damage. See Sensors and Probes. |
| A channel shows "--" instead of a temperature | The sensor is unplugged, an infrared sensor is not aimed at a surface, or a probe has come loose | Reseat the connector. For an infrared channel, aim the sensor at a solid surface within its range. For a contact probe, make sure the plug is fully seated in the probe jack and the tip is on the surface you are monitoring. The tile returns once a valid reading resumes. |
| An infrared reading looks wrong or jumps around | The sensor is aimed past its target, at a moving part, or at a reflective or shiny surface | Re-aim the WTH Infrared Sensor squarely at the hot surface (for example the motor or voice-coil area of a subwoofer) and secure the cable so it cannot drift. An infrared channel shows the current temperature. The max on the tile shows the highest recent reading. |
| A probe reads far colder or hotter than expected | Loose plug, poor surface contact, or the tip is touching the wrong point | Reseat the plug in the probe jack and secure the tip flat against the surface or terminal you want to monitor. A probe that is dangling in open air reads the surrounding temperature, not the part. |
Every channel shows its recent minimum and maximum on the second line of its tile. Tap any tile to open its "TEMPERATURE HISTORY" graph and see its recent readings.
Temperature Alarms
The hub has one global over-temperature threshold that applies to every channel. When a channel meets or exceeds it, that tile recolors to a warning state and the status dot in the top-right corner of the "TEMPERATURES" home screen turns to its warning state.
| Issue | Likely cause | What to do |
|---|---|---|
| A tile and the status dot have entered the warning state | That channel has reached or passed the over-temp threshold (default 110°F) | This is the hub doing its job: something you are monitoring is running hot. Check the part that channel is watching and improve cooling or reduce load. The warning clears on its own once the temperature drops back below the threshold. |
| Tiles enter the warning state too early or too late | The threshold does not match this build | Change the single global Over-temp threshold (adjustable from 70°F to 200°F) in Settings > Channels. See Menus and Settings for the full setting reference. |
| A tile starts shifting color before it is over the limit | Severity tint is enabled | This is intentional. Severity tint gradually ramps a channel's color as it approaches the threshold so you get an early visual warning. Turn it off in Settings > Display if you prefer a plain tile until the limit is reached. |
The over-temp alarm is visual only. The hub has no buzzer and no switched output, so there is no beep and nothing is turned on or off when a channel goes over. Watch the screen, a paired wireless display, or the LF Audio app to catch a warning.
Display and Touch
| Issue | Likely cause | What to do |
|---|---|---|
| The screen is dark but the hub seems powered | The display has gone to sleep to save power | Tap the screen or short-press the front button to wake it. Adjust how long the hub waits with Sleep after (10 to 240 seconds) in Settings > Display, or turn Sleep when idle off entirely. |
| The screen is dim and hard to read | Brightness is set low | Raise Brightness (5% to 100%) in Settings > Display. |
| Taps land in the wrong place or feel off | The touchscreen calibration has drifted | Recalibrate. Open Settings > Display > Calibrate Touch and tap each of the nine targets. If the touch is too far off to reach that menu, press and hold anywhere on the screen for about 10 seconds to trigger the same nine-point calibration directly. |
| You tap Confirm (or Forget) and nothing happens | That button ignores a tap right after the box opens. This is on Reset Settings, Force OTA Update and Forget Phones. | Wait a moment. Then tap it again. This stops a quick double tap from acting by mistake. |
Pairing and the App
The hub connects to your phone over Bluetooth using the LF Audio app, and it links to LF Audio wireless displays such as the RTC, WDD-LITE, and BassWatch over its own wireless link.
| Issue | Likely cause | What to do |
|---|---|---|
| A wireless display will not pair | The hub is not in pairing mode, or the two units are too far apart | Put the hub into pairing mode by triple-pressing the front button, or tap Pair New Display on the Devices tab. The screen shows "Pairing Mode" and "Searching for display...", and the pairing light flashes while it searches. Make sure the display is also in its pairing mode and is close by, then wait for "Paired!" See First Boot and Pairing. |
| Pairing starts but never completes | Interference or distance | Move the two devices closer, keep them away from large metal panels, and confirm the external antenna is screwed on. Try again from the Devices tab. |
| The app will not find or connect to the hub | Bluetooth is off, or the phone is out of range | Turn on Bluetooth and location permission for the app, keep the phone near the hub, and look for the device named "LF_WTH" in the app. If a phone just disconnected, wait a few seconds. On firmware 4.20 or newer, the hub shows up again on its own. |
| The app asks for a PIN | Bluetooth pairing needs the 6-digit code | Enter the 6-digit PIN shown on the hub: Settings > System tab > BT PIN. If it is rejected, close and reopen the app and try again. See App Getting Started. |
| Your phone cannot pair with the hub. Forgetting the hub on the phone did not help. | The hub still keeps an old pairing for that phone | Use Forget Phones on the hub: Settings > System tab > Forget Phones, right under BT PIN. Then forget the hub on each phone. Pair again in the app with the BT PIN. It needs hub firmware 4.20 or newer. See Menus and Settings and Forget Phones. |
| Forget Phones says "Checking the hub. Try again soon." | The hub is still starting up | Wait a few seconds. Then tap Forget Phones again. |
| Forget Phones says "Update the hub first." | Part of the hub has older firmware | Update the hub. Then check that Firmware and Sensor board on the System tab both show 4.20 or newer. See Firmware Updates. |
| A phone paired again by itself right after "No phones are paired now" | A phone with the LF Audio app may reconnect by itself. On Android, the app remembers the BT PIN. | This is normal. Forget Phones is for a phone that cannot pair. It does not keep out someone who knows the BT PIN. |
| Forget Phones is missing from the Advanced menu of your RTC, WDD-LITE or BassWatch | The hub or the display needs newer firmware. Or the display was paired long ago and has no secure link. | Update the hub to 4.20 or newer. Update the display too. If the row is still missing, pair the display again: on the display, choose Advanced > Forget Base, then pair it with the hub again. See Forget Phones. |
| A display that was paired and working has stopped showing live temperatures | The display is out of range or obstructed, the hub lost power, or the two are running older firmware | Confirm the hub is powered and check the Signal rating for that display on the Devices tab. Move the two closer together, keep them clear of large metal panels, and confirm the antenna is attached on both. If a display keeps ending up disconnected and only comes back after you forget and re-pair it, update both the hub and the display to the latest firmware. See Firmware Updates. |
A display that drops off and will not reconnect until you re-pair it is worth an update on both ends. A fault that could leave a paired display permanently stuck reconnecting to the hub, surviving a restart, was corrected in a hub firmware update, and the matching displays received the same correction. Displays left on a live graph or analysis view were the most affected. Once both the hub and the display are current, forgetting and re-pairing should no longer be needed to recover a link.
Power
| Issue | Likely cause | What to do |
|---|---|---|
| The hub will not turn on at all | No supply voltage, a blown fuse, or reversed wiring | Confirm the +12V lead has 9V to 18V DC and that your inline fuse on that lead is intact. Check the three-position power connector: +12V, remote turn-on, and ground each land on the correct terminal. The hub is reverse-polarity protected, so swapped power and ground will not damage it, but it will not run until the wiring is corrected. |
| The hub stays off with the system on | The remote turn-on wire is not switching | Wire the remote turn-on terminal to your head unit's remote or accessory output so the hub powers up and down with the system. Verify that wire goes high when the system is on. |
| The hub powers off unexpectedly | Loose power connector or a marginal fuse | Reseat the pluggable power connector, check for a nearly-open fuse, and confirm the +12V source is solid under load. |
Resetting the Hub
There are three different reset actions. Pick the smallest one that solves your problem so you keep as much of your setup as possible.
- Reset Settings (Settings > System) restores the display and interface settings and restarts the hub. It keeps your paired displays and your setup, so use this first when the interface is misbehaving.
- Clear all paired displays: press and hold the front button. This forgets every wireless display at once but leaves your other settings alone. Use it before moving the hub to a new setup.
- Forget one display: on the Devices tab, use the per-display Forget button to remove a single wireless display without touching the others.
None of these removes the phones paired to the hub. To remove phones, use Forget Phones on the System tab. See Forget Phones.
Long-pressing the front button clears all paired displays and restarts the hub. You will need to pair each display again afterward, as described in First Boot and Pairing.
Still Need Help
If none of the steps above resolve the issue, we are here to help.
- Reach the team through Contact Us with your hub's firmware version and a short description of what you see on screen.
- For repair or replacement, review Warranty and Returns.