Compatible Devices by Protocol

Browse TapHome compatible devices organized by communication protocol.

TapHome supports multiple communication protocols for device integration. Browse devices by their connection method below.

Modbus RTU (53)

The most common wired protocol for HVAC integration with TapHome. Devices connect over RS-485 serial bus — either directly from a built-in Modbus interface, or through a manufacturer-specific gateway that bridges proprietary buses like Daikin P1P2, Samsung R1/R2, or Viessmann LON. TapHome Core's RS-485 port supports daisy-chaining multiple Modbus RTU devices on a single bus.

Modbus TCP (32)

Devices connect to TapHome over standard Ethernet or Wi-Fi using Modbus TCP on port 502, with no RS-485 wiring required. This protocol is used by NIBE S-Series heat pumps, Atrea ventilation units, and solar inverters — all with a built-in network interface. Some devices that only support Modbus RTU can also reach TapHome via a third-party RS-485-to-Ethernet bridge.

HTTP (33)

Wi-Fi devices with an HTTP API connect to TapHome over the local network — no cloud account, no gateway hardware, no wired connection required. TapHome polls the device's local HTTP endpoint for status and sends commands directly. Devices are discovered by mDNS hostname, making the setup resilient to DHCP address changes.

MQTT (17)

MQTT is used for devices that push data on events rather than responding to polls — particularly battery-powered sensors that sleep between transmissions and protocol gateways that publish bus status in real time. TapHome subscribes to device-specific MQTT topics, receiving updates as they happen without continuous polling. An MQTT broker (e.g. Mosquitto) running on the local network is required.

Data (PP) (7)

RS485 (0)

Coming soon

DALI (0)

Coming soon

Wiegand (0)

Coming soon