---
title: "One ESP32 can bring old Tasmota devices into Apple Home"
locale: "en"
url: "https://irz.fr/en/articles/tasmoshelf-tasmota-apple-home-en"
markdown_url: "https://irz.fr/en/articles/tasmoshelf-tasmota-apple-home-en.md"
category: "tech"
tags: ["Tasmota", "smart home", "Matter", "local-first"]
published_at: "2026-08-13T22:46:00.000Z"
author: "Manon Girard"
translation: "https://irz.fr/fr/articles/tasmoshelf-tasmota-apple-home-fr.md"
---

# One ESP32 can bring old Tasmota devices into Apple Home

TasmoShelf controls Tasmota devices directly over the local network. Recent ESP32 hardware can join Apple Home through Matter, while one ESP32 can bridge older ESP8266 devices.

There is a particular kind of smart home that works perfectly as long as you agree to maintain one more little server in a corner somewhere.

TasmoShelf tries to remove that layer for devices running Tasmota. The iOS and Android app talks directly to them over the local network through Tasmota’s HTTP interface. There is no required account, cloud service or MQTT broker.[1](https://tasmoshelf.app/)

That is useful for switching a plug. It becomes more interesting when the hardware starts spanning several generations.

> Tasmota → Apple Home
> **The path depends on the microcontroller**
> - With Tasmota 13 or later, the device can speak Matter directly.: ESP32
> - The older chip cannot take that direct path.: ESP8266
> - A single ESP32 running Tasmota can bridge older devices.: 1 ESP32
> - Once paired, Siri, scenes and automations run over the local network.: Apple Home
> Source: TasmoShelf documentation. Tasmota remains uncertified Matter firmware.

TasmoShelf reads the chip and firmware version of each device and tells the user whether it can pair directly, needs an update or needs a bridge.[1](https://tasmoshelf.app/) Its documentation says ESP32 devices on Tasmota 13 or later can expose Matter themselves. Older ESP8266 hardware, which cannot take that route, can sit behind an ESP32 running Tasmota.[1](https://tasmoshelf.app/)

The key detail is that the phone app does not become the permanent server. It helps configure the fleet, exposes the pairing code and remains useful for diagnostics. Once a device is in Apple Home, scenes and Siri do not need TasmoShelf sitting in the middle.[1](https://tasmoshelf.app/)

Tasmota has long documented other routes into HomeKit, including Homebridge and MQTT-based plugins.[2](https://tasmota.github.io/docs/Homebridge/) TasmoShelf is therefore not inventing interoperability. It is reducing the number of moving pieces for one specific setup.

The same local-first logic appears elsewhere in the app. Timers are stored and executed by the devices themselves. Backups retrieve each device’s own configuration. Energy readings and commands stay on the local network.[1](https://tasmoshelf.app/)

There is an important caveat. Tasmota is free firmware, and its Matter implementation does not go through the closed certification programme in the same way as a commercial accessory. TasmoShelf warns that Apple may therefore label the accessory uncertified during setup.[1](https://tasmoshelf.app/)

The broader idea is more interesting than one app. Instead of modernizing a working plug by replacing it, TasmoShelf first asks what the old hardware can already do, then adds only the bridge it actually needs.

## References

1. [TasmoShelf, official website](https://tasmoshelf.app/)
2. [Tasmota, Homebridge documentation](https://tasmota.github.io/docs/Homebridge/)