TapHome

LED indicators

Overview of LED indicators on Core, their states and error states of IO modules.

Last updated:

The LED indicators on the TapHome Core and on IO modules show whether the device has started, whether it communicates on the TapHome bus, and whether it is connected to the local network and the cloud. On the Core, LED 1 reports the system boot and bus communication, LED 2 the local network and LED 3 the cloud connection. On an IO module, the LED shows that the module is powered and communicates with the Core control unit, or signals an error by blinking 1x, 2x or 3x or by staying off. Use the tables on this page to find the cause of a given LED state and what to check.

Status information

  • LED 1 LED 1:
    • Three blinks after power-on indicate system boot.
    • Otherwise, it indicates the communication status with other modules on the TapHome bus.
  • LED 2 LED 2:
    • The system is running.
    • Connection to the local network has been established.
  • LED 3 LED 3:
    • Connected to the cloud.
    • Remote access is available.

Error states

LED 2 (LAN)LED 3 (Internet)Description
OFFOFFThe system did not start
Fast blinkingOFFLAN cable is disconnected
BlinkingOFFThe device has not been assigned an IP address
ONBlinkingTapHome Core firmware is not running
ONOFFTapHome Core firmware cannot connect to the cloud
BlinkingBlinkingThe device has DNS configuration issues
Fast blinkingFast blinkingThe device cannot connect to the internet
ONONTapHome Core firmware is running and connected to the cloud

LED indicators on IO modules

Status information

LEDDescription
ONThe device is powered and communicates with the Core control unit.
✅ All good.
Regular blinkingThe configuration window in the iOS or Android app for this module is currently open.
✅ This is how you can identify the module you are configuring and name it for future use.

Error states

LEDDescriptionActions
1x
1x		The device is powered but receives invalid communication packets.❌ Check that the bus is properly connected.
❌ Check that terminals A and B are connected in the correct order.
❌ Check that a 100 Ohm termination resistor is placed at the end of the bus between A and B.
❌ Check that the device is connected to TapHome Bus conductors. Connecting TapHome to Modbus or another protocol will cause invalid packets, shown as 1 blink.
2x
2x		The device is powered and has valid communication with the Core control unit, but messages are not addressed to this module.✅ Everything is ready, but the module has not been scanned (Hardware → TapHome Bus → Find new devices).
3x
3x		The device is powered but does not receive any communication.❌ Check that the correct BUS terminal is enabled in Hardware → TapHome Bus → Terminals.
Off
Off		The device is not powered or is not functioning correctly.❌ Check that there is a voltage of 24VDC between the +24V and GND terminals. Tolerance is ±10%.

See also — Bus Analyzer, Backup, restore, factory reset.