---
title: "Connect several Cores over MQTT: discovery, device attributes, manual mode and availability"
description: "Idea: link TapHome Cores over MQTT so devices of one Core appear on another with name, icon and zone, manual mode and availability."
url: "https://taphome.com/en/ideas/cores-over-mqtt/"
language: en
lastmod: 2026-11-10
generator: hugo
---

# Connect several Cores over MQTT: discovery, device attributes, manual mode and availability

Cores on one site would share devices through an MQTT broker as if they were local: the other Core finds them with their name, icon, zone and category, controls them, sees their manual mode with its end time and knows when a Core is offline.

- Status: Gathering interest — We collect use cases and votes before we decide.
- Type: Feature
- 0 interested
- Topics: [Integrations and protocols](https://taphome.com/en/ideas/topics/integrations-protocols/)
- Last updated: 2026-11-10


![Core B publishes the status, configuration, values and operation mode of its devices to an MQTT broker, Core A shows the same devices, and commands from Core A travel back to Core B through the broker.](https://taphome.com/images/ideas/51ff7a35fa47cb10c2a6d8357e989c55dd6d0efba6b02aeb9c758f52b3d753ee.svg)

## Why and how you would use it

A site with more than one building often ends up with more than one Core: the TapHome bus runs over copper only, so a workshop, a garage or a second house gets its own Core, connected to the main one over the local network. Today the two Cores share devices over Modbus TCP, register by register. Each shared device is set up again on the other Core, and its name, icon, zone, category and manual mode stay behind.

*Two Cores. One connected place.* — [interactive illustration](https://taphome.com/en/ideas/cores-over-mqtt/)


Take a family house and a workshop across the yard. The workshop Core runs the hall light, the sockets, the gate and a meter. To see and switch them in the house, someone adds each device to the house Core by hand, from a list of registers. When the workshop light is switched to manual mode, the house does not know, and a third building means another interface and another list of registers.

All Cores of a site would use one MQTT broker. Each Core would publish its devices under its own name, so every Core can see the others and tell where a device comes from.

| | Today | With this idea |
|---|---|---|
| Adding a device | Register by register | Found automatically |
| Name, icon, zone | Set again by hand | Taken over |
| Manual mode | Not shown | Shown with end time |
| Another Core | New list of registers | Found on the broker |

## What will be possible

The idea would make devices of another Core feel like local ones. Nothing below is scheduled.

- **Exposing devices over MQTT.** On the Core that has the devices, you would choose which devices to publish, set the broker and a name for the Core. Each device would be announced with its attributes, its values and its operation mode.
- **Finding the devices automatically.** The other Core would read the announcements, list the Cores and devices it found with their icon, zone and category, and let you choose which ones to add and whether to keep their zones or map them to local ones.
- **Control in both directions.** A switch on one Core would send a command to the Core that owns the device. That Core would carry it out and publish the new value, and only then would the first Core show the new state. A change made on the spot, such as a wall switch, would come back right away.
- **Manual mode with its end time.** When a device is switched to manual mode on its own Core, the other Core would show it with the time the manual mode ends, and could ask to return it to automatic mode. The Core that owns the device would decide.
- **Availability.** If a Core or the network between the buildings goes down, the broker would announce it. The other Core would mark the devices as unavailable since a given time, keep the last value greyed out, and smart rules would skip them. The Core with the devices keeps running its own modules and smart rules.
- **Changes without broken rules.** A device would keep a stable identity, so renaming it or moving it to another zone would not break smart rules on the other Core. A name changed locally would win, and a new device would be offered, not added silently.

## What will not be possible

- **A bus over the network.** TapHome modules would still connect to their own Core over the bus. The idea links Cores, not modules.
- **One project for all Cores.** Each Core would keep its own configuration, users and smart rules. Shared devices are added on each Core that needs them.
- **Linking without a broker.** The Cores would need an MQTT broker they can all reach, for example the one built into a Core or a broker on the site network.
- **Control when the link is down.** A Core cannot switch a device of another Core while the connection is lost. It shows the device as unavailable instead.
- **Every MQTT device out there.** The topics would be made for TapHome Cores. Third-party MQTT devices keep using the Packet Parser.

## How to solve it today

- **Share devices over Modbus TCP.** One Core exposes the devices over Modbus TCP and the other reads them register by register, with a validity register for each value, see [Connecting multiple Cores](https://taphome.com/en/docs/configuration/multiple-cores/).
- **Use the TapHome API.** A Core can read and control devices of another Core through the local [TapHome API](https://taphome.com/en/docs/expose-devices/taphome-api/) with a Packet Parser script.
- **Set the attributes again.** Names, icons, zones and categories are set on the reading Core by hand, and the manual mode of the other Core is not shown there.
- **Plan the network between buildings.** The second Core connects over an ordinary LAN, over fiber where it is already laid, see [Devices in another building](https://taphome.com/en/docs/wiring/remote-buildings/).
- **Avoid the Integration Protocol for this.** It is made for third-party control systems and transfers only a fixed set of device types, without icons, zones or the operation mode.

## Learn more

- [Message log for Packet Parser and MQTT](https://taphome.com/en/ideas/packet-parser-message-log/), a separate idea about seeing what an MQTT module sent and received.
- [MQTT broker](https://taphome.com/en/docs/integration/packet-parser/mqtt-broker/) and [Connecting multiple Cores](https://taphome.com/en/docs/configuration/multiple-cores/) documentation.

Do you run a site with several Cores, and which of them would you link first? Vote for this idea and follow it for updates.

**Vote · Follow:** Anyone can vote. Sign in with your TapHome account to follow ideas, answer polls, comment and suggest your own.

- [Connect several Cores over MQTT: discovery, device attributes, manual mode and availability](https://taphome.com/en/ideas/cores-over-mqtt/)
- [Suggest an idea](https://taphome.com/en/ideas/#suggest)

