FYI; tomaszduda23, an independent developer is working on developing an initial port of ESPHome for nRF5 platform on Zephyr RTOS for nRF52 SoC series based nRF52840 SoC from Nordic Semiconductor (and in theory it should also lay the ground work for the newer nRF54 SoC series):
Summery for those unfamiliar with Nordic Semiconductor and their lines of microcontroller chips; Nordic Semi is a 40+ year-old company that has been making their ARM-based nRF5 family of ultra-low-power wireless MCU SoCs (nRF51, nRF52, and nRF53 series) since 2012 and those have become very popular among developers/manufacturers that make battery-powered devices, especially those requiring ultra low-power wireless communication on the 2.4 GHz ISM bands, like Bluetooth, Thread, and Zigbee. Nordic Semi also makes Wi-Fi SoCs but then we are no longer talking about ultra low-power devices.
Note that I have nothing to do with this project myself, I just stumbled in this project and wanted to spread this news because I got exited by the potential of this could not only bring more developers and thinkers that feel more familiar with the Nordic Semiconductor nRF5 platform to start using and contributing to ESPHome, so it should hopefully help the community grow even faster, but it could possibly make it easier to make running ultra low-power battery-operated devices running ESPHome, as well as add another type of radio MCU hardware for ESPHome that can support Thread/OpenThread and Zigbee.
PS: Off-topic That development effort might be indirectly interesting to another sub-project to follow for those who (like myself) have been asking for native Thread/OpenThread and Zigbee wireless support in ESPHome (and perhaps posted in the feature request tracker) since Nordic Semiconductor nRF52840 do not support WiFi but does support Thread and Zigbee protocols, (similar to the ESP32-H2), with nRF52840 and the newer nRF5340 being ideal for battery-powered devices:
Looks like tomaszduda23โs work on basic support for nRF52840 for ESPHome progressing very nicely and just yesterday he marked his pull request as ready for review and testing by devs/testers:
Btwy, also wanted to mention missed that @NateLust previous begun porting ESPHome to nRF52840:
Looks like @NateLust has not updated his forked esphome repository the last year and seems like the โzephyr-devโ branch there is latest:
There do not seem to be any new posts from @NateLust on this since he posted this zephyrESPHomeGuide in little over 1-year ago:
PS: Noted that @NateLust did also make more progress on Thread/OpenThread for ESPHome than any other have I seen so far(?).
This would be really amazing as it might allow for projects like b-parasite to using esphome instead of the custom firmware that is very difficult for new users to build and install!
PS: Also interesting and relevant is that the initial pull request for Zigbee support on nrf52 for ESPHome is now also getting close to being merged soon:
Will these changes natively support the BBC Micro:Bit, which I believe has a NRF51822 chip?
Asking as I have a few lying around, and this would probably revive that ecosystem significantly, breathing new life to sales and utilisation, and allow learners to adopt HomeAssistant into their home style once the novelty of flashing a LED has worn off.
It would possibly appeal to those that do not want dependency on Chinese technology such as the ESP ecosystem, but still want a flexible platform to deploy their projects.
That means that the next upcoming ESPHome release (scheduled for release as ESPHome 2026.1.0 in a couple of weeks from now or if that is delayed then in the 2026.2.0 release) will have have initial Zigbee end device support for the nRF52 platform.
Again, also be ware that both tomaszduda23 and luar123 also still have their previous work and pulls requests open that offer much more extensive and comprehensive Zigbee device types (which also have much more information and better overview of the project scopes), but I guess that if the two pull requests linked above are accepted and merged into ESPHome mainline then each of their comprehensive work (linked below) will be partially rewritten to align with the new agreed upon standard and formatting. See these for more background information:
PS: FYI, tomaszduda23 and luar123 are at least now more aligned and have agreed on how initial Zigbee config with platform/component abstraction should be handled/formatted at a high-level for ESPHome config to be platform-independent, and as such they both each submitted matching pull requests for initial bare-minimum Zigbee support on nRF52 and ESP32 respectively.
โThe zigbee component allows exposing supported ESPHome components over a Zigbee network to Home Assistant via Zigbee2MQTT or ZHA. Due to the limitations of the Zigbee protocol, only basic properties are exposed. Additional properties must be configured manually in Home Assistant. Each ESPHome entity consumes one Zigbee endpoint. Because of a limitation in Zigbee2MQTT, at least two endpoints are required. The maximum number of supported endpoints is eight.โ
So far in ESPHome 2026.1 they added initial support however it already features supports for sensor, binary sensor, and switch functions:
Switch support - Control ESPHome switches via Zigbee as binary output (#13083)
wipe_on_boot: once - Wipe network settings only on first boot, preserving connections after OTA updates
Framework version support - Configure nRF-SDK version with experimental support for SDK 2.9.2 and 3.2.0 (#12489)
Future
Zigbee support in ESPHome is currently available only on nRF52 platforms but there is an open PR to also add ESP32 support as well:
Also be ware that both tomaszduda23 and luar123 also still have their previous work and and side-development woth pulls requests open as drafts that offer much more extensive and comprehensive Zigbee device types (which also have much more information and better overview of the project scopes), but I guess that if the two pull requests linked above are accepted and merged into ESPHome mainline then each of their comprehensive work (linked below) will be partially rewritten to align with the new agreed upon standard and formatting. See these for more background information:
Thanks Hedda and nice that this is moving on.
The problem with nrf52 is that thereโs no documentation in practice. I donโt know what can I do with it and how. Normal gpio i/o, analog input and I2C are the only components that have been even mentioned.
Will there be the ability to tap into the BBC Micro:bit ecosystem using ESPHome? This would bring you a whole lot more opporrunities similar to when the ESP series were added to the Arduino ecosystem.