---
title: "Packet Parser Integration"
description: "Connect HTTP, TCP, UDP, FTP and MQTT devices to TapHome with Packet Parser: import a ready-made template or write your own script."
url: "https://taphome.com/en/compatibility/packet-parser-guide/"
language: en
lastmod: 2026-03-18
generator: hugo
ai:
  topics: ["packet-parser","http-integration","tcp-integration","udp-integration","ftp-integration","mqtt","custom-scripting","protocol-integration","rest-api"]
  questions: ["What is the TapHome Packet Parser?","Which protocols does the Packet Parser support?","How do I connect an HTTP REST API device to TapHome?","How do I use ready-made Packet Parser templates in TapHome?","How do I create a custom Packet Parser integration?","When should I use TCP vs UDP vs HTTP in Packet Parser?","Can I share my custom Packet Parser template with the community?","How does Packet Parser handle MQTT devices?"]
---

# Packet Parser Integration

## What is Packet Parser?

Packet Parser is TapHome's built-in interface for connecting third-party devices over TCP/IP. It supports multiple protocols, enabling integration with a wide range of smart devices via WiFi or LAN.

## Supported Protocols

- **HTTP** — REST API communication (GET/POST requests, status polling, webhooks). Ideal for devices with a REST API such as air conditioners, air recovery units, or smart appliances.
- **TCP** — Direct socket connection for real-time communication. Suitable for devices requiring a persistent connection or a custom binary protocol.
- **UDP** — Lightweight connectionless messages. Ideal for simple sensors where delivery reliability is not critical.
- **FTP** — Reading and writing files to/from a device. Suitable for devices that export data as files (logs, measurements).
- **MQTT** — Publish/subscribe protocol for IoT devices (Shelly, Sonoff/Tasmota, Zigbee2MQTT). Requires activation of the built-in MQTT Broker.

## Using Ready-Made Templates

The easiest way to add a device is to use a pre-built template. Templates define how data is sent and received — no scripting needed.

1. Go to **Settings → Hardware → Packet Parser**
2. Select **Download templates** to browse available configurations
3. Enter the device's IP address or mDNS name
4. Choose which devices to create and confirm

> [!TIP]
> Browse the available Packet Parser templates in the compatibility list below.

## Custom Integration

For devices without an existing template, you can create your own using TapHome's scripting language. Define how data is sent and received, then export your template to XML and share it with the community.

> [!NOTE]
> You will need the device's API documentation — endpoints, message formats, and authentication parameters.

## Documentation

### [Device Templates](https://taphome.com/en/docs/integration/packet-parser/templates/)

Download a ready-made template and connect a device without programming.

### [Manual Configuration](https://taphome.com/en/docs/integration/packet-parser/manual/)

Protocol functions — SENDHTTPREQUEST, SENDDATA, FTPDOWNLOAD, and more.

### [MQTT Broker](https://taphome.com/en/docs/integration/packet-parser/mqtt-broker/)

Activate the built-in MQTT Broker and connect Shelly, Zigbee2MQTT, or Tasmota devices.

### [Scripting Language](https://taphome.com/en/docs/integration/packet-parser/)

Complete reference — variables, functions, data types, and script examples.