---
title: "Bus Analyzer"
description: "Bus Analyzer in Settings → Hardware → TapHome Bus shows module communication errors and unexpected resets, and finds new devices fast."
url: "https://taphome.com/en/docs/setup/bus-analyzer/"
language: en
lastmod: 2026-10-08
generator: hugo
ai:
  topics: ["bus-analyzer","diagnostics","communication-errors","module-monitoring","device-discovery"]
  questions: ["Where do I find the Bus Analyzer in TapHome?","What do the color indicators (red, green, gray) mean in the Bus Analyzer?","How do I diagnose communication errors on the TapHome bus?","What does it mean when the module uptime is shown in red or green?","How to quickly search for new devices using the Bus Analyzer?","How do I reset error statistics in the Bus Analyzer?","When should I use the Bus Analyzer to diagnose TapHome issues?"]
---

# Bus Analyzer

Diagnostic tool for TapHome bus with communication error monitoring and quick new device discovery.

Last updated: 2026-10-08

For better diagnostics of the TapHome bus, use **Bus analyzer** in **Settings → Hardware → TapHome Bus**.

⚠️ **Warning:** The bus analyzer uses extensive communication with modules, which may slow down normal operation. After properly closing the bus analyzer or the TapHome application, the analyzer will no longer be active.

## Overview
![busanalyzer.png](https://taphome.com/documentation/setup/busanalyzer.png)

1. Refresh error statistics  
1. If there are errors on the bus, they will be displayed here.  
1. Modules that have never communicated have no statistics.  
1. Information about the physical bus to which the module is currently connected.  

## Error indicators
- If communication with a module is faulty – the module does not respond – the information is displayed in **red**.
![noresponsered.png](https://taphome.com/documentation/setup/noresponsered.png)
- If there were communication problems, but the module now responds correctly, the errors are displayed in **green**.
![noresponsegreen.png](https://taphome.com/documentation/setup/noresponsegreen.png)
- If there is unexpected information related to a module – for example an unexpected reset – it is displayed next to the module name in **red**.
![devicewatchdogflag.png](https://taphome.com/documentation/setup/devicewatchdogflag.png)
- If the module uptime is more than **30 seconds**, but less than **2 minutes**, it is displayed in **green**.
![uptimegreen.png](https://taphome.com/documentation/setup/uptimegreen.png)
- If the module uptime is less than **30 seconds**, it is displayed in **red**.
![uptimered.png](https://taphome.com/documentation/setup/uptimered.png)

After **two minutes** from startup, the uptime is displayed in **gray**.

## Actions

### Refresh error statistics
Clicking the **Refresh error statistics** button clears all module communication errors from memory and starts gathering new statistics. This can be used after identifying problems to focus only on new errors that appear on the bus after this step. If the statistics are not reset, every time the bus analyzer is started, errors from communications prior to its start will also be displayed.

### Pause and Resume
It is possible to **Pause** the bus analyzer and check the current state without changes. To do this, click the button. To **refresh the live view**, use the **Refresh** button.

### **Quick search for new devices**

The bus analyzer enables a quick search for new devices. When started, only one cycle of searching for new devices is performed – in normal mode, three cycles are performed.

**See also** — [LED indicators](https://taphome.com/en/docs/setup/led-indications/), [Serial Bus Topology](https://taphome.com/en/docs/wiring/serial-bus-topology/), [Device log](https://taphome.com/en/docs/configuration/device-log/).

## Troubleshooting

Common issues related to this topic:

- [TapHome bus: measure Bus A and Bus B](https://taphome.com/en/troubleshooting/wiring/taphome-bus-voltage-a-b/) — Modules on the TapHome bus drop out, the bus analyzer shows errors or push buttons react late. A multimeter check of Bus A and Bus B against GND at the Core and at the modules shows a loose terminal, an unconnected wire or a faulty module.
- [EXT sensor after replacement](https://taphome.com/en/troubleshooting/hardware/ext-sensor-not-communicating-after-replacement/) — Replaced external sensor (temperature, humidity, CO2) still not communicating with the module

[View all troubleshooting articles](https://taphome.com/en/troubleshooting/)