Network Preparation for a TapHome Installation

The TapHome Core talks to devices on the home network at the address stored in its configuration. When the router gives the Core or a device a different IP address — after a router replacement, a restart or a switch to DHCP — the integration stops working and the device reports an error. Before the installation, give the Core and every such device a fixed address: an IP reservation in the router, or an mDNS name if the device supports it. For the built-in MQTT broker, enter 127.0.0.1 in TapHome.

The basic rule: a fixed address#

Every device the Core talks to over the network, and the Core itself, needs an address that does not change:

• IP reservation in the router (DHCP reservation, in some routers “static DHCP” or “Address Reservation”) — the router always gives the device’s MAC address the same IP address. It works for every device; when a device is replaced, move the reservation to the new MAC address.
• mDNS name (for example shellyplus1-a8032ab12345.local) — the device announces it on the network itself and the name does not change with the IP address. It works only for devices that support mDNS. When you add a device in TapHome by scanning the network and the device announces an mDNS name, TapHome uses it on its own (IP Scanner).

When the router is replaced, enter the reservations in the new one too.

Address of the Core control unit#

The IP address, MAC address and mDNS name of the control unit are in the app under Settings → My location (rows IP Address, MAC address and mDNS name).

• We recommend an IP reservation in the router by the MAC address of the control unit.
• A static IP in the app (Settings → My location → Network settings, turn off Enable DHCP) works as well, but the address must lie outside the range the router hands out over DHCP — otherwise the router may give it to another device and the addresses collide. After the router is replaced by one with a different network, a Core with a static IP is unreachable until the setting is corrected. Steps → Network architecture.
• The mDNS name of the control unit is the location name without diacritics with the suffix .local (location “Family House” → Family-House.local). It changes when you rename the location.

Devices on the network#

Use a static IP set directly in the device only when the manufacturer requires it; it too must lie outside the router’s DHCP range.

Built-in MQTT broker#

The built-in MQTT broker listens on port 1883 (TCP) by default. It uses two different addresses:

• In TapHome (Packet Parser module with the MQTT protocol, broker IP address field) enter 127.0.0.1. It is the control unit’s address for itself and does not change even when the control unit’s IP address changes. Do not enter the control unit’s IP address here — once it changes, the module stops receiving messages.
• In the MQTT device (for example in the Shelly web interface) enter the control unit’s IP address with a reservation in the router. Use the control unit’s mDNS name only when the device manufacturer states that it resolves a .local name in the server address.

Some templates had the name taphome.mqtt.broker.local as the default broker address. The control unit does not know this name and the module does not connect — replace it with 127.0.0.1.

Ports and firewall#

Ports the firewall must allow for the app, the Core and the cloud → firewall settings.

Checklist before handover#

• The Core has an IP reservation in the router (or a static IP outside the DHCP range).
• Every Modbus TCP, HTTP and SIP device and every camera has an IP reservation or is entered in TapHome by its mDNS name.
• MQTT modules in TapHome have 127.0.0.1 as the broker address, MQTT devices have the control unit’s IP address with a reservation.
• You handed the list of reservations (MAC address, IP address, device) to the customer — they will need it when the router is replaced.
• After a router restart, all devices in TapHome report values without an error.

See also — Requirements for Third-Party Devices.