The Need for Further Investigation

Oct 13, 2025 by leolavanderia.com.br 138 views

Updating to 2025.2 "kills" Shelly if Bluetooth is enabled

The Problem: A Critical Issue with Shelly Relays and ESPHome

As we continue to push the boundaries of smart home automation, we often encounter unexpected issues that can hinder our progress. In this article, we will delve into a critical problem that has been reported by users of Shelly relays and ESPHome, a popular open-source home automation framework. The issue revolves around the update to 2025.2, which seems to "kill" Shelly relays when Bluetooth is enabled.

The Symptoms: A Reluctant Boot

Users who have attempted to update their Shelly relays from 2024.12 to 2025.2 have reported a peculiar issue. Despite having a minimal configuration that disables all other components, the relays fail to boot properly. However, if they manage to boot in safe mode, they can be pinged and updated via Over-the-Air (OTA) firmware updates. This suggests that the issue is not with the firmware itself but rather with the interaction between the 2025.2 update and the Bluetooth component.

The Culprit: esp32_ble_tracker

The component responsible for this issue is the esp32_ble_tracker, which is a part of the ESPHome framework. This component enables Bluetooth Low Energy (BLE) scanning on the ESP32 microcontroller, allowing it to detect and connect to nearby devices. However, in the case of Shelly relays, enabling this component seems to cause the device to malfunction, resulting in a reluctant boot.

Downgrading to 2024.12: A Temporary Fix

Fortunately, downgrading to 2024.12 has been reported to fix the issue completely. This suggests that the problem is specific to the 2025.2 update and not a hardware or configuration issue. However, this temporary fix may not be a viable solution for users who require the latest features and security patches.

The Need for Further Investigation

To resolve this issue, further investigation is required. Users who have experienced this problem are encouraged to provide serial logs, which can help identify the root cause of the issue. Additionally, developers can work together to reproduce the problem and develop a fix.

System Configuration and Specifications

To provide a better understanding of the issue, here are the system configuration and specifications:

ESPHome Version: 2025.2.x
Installation Type: Docker
Home Assistant Version: N/A
Platform: ESP32-IDF
Board: Shelly
Component Causing the Issue: esp32_ble_tracker

Minimal YAML Config

Here is a minimal YAML configuration that reproduces the issue:

# minimal config reproducing the issue

esp32:
  board: esp32doit-devkit-v1
  framework:
    type: esp-idf

i2c:
  sda: GPIO26
  scl: GPIO25

esphome:
  name: ${device_name}
  friendly_name: ${friendly_name}
  comment: ${comment}
  
wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
ota:
- platform: esphome
logger:
  logs:
    ble_gateway: INFO
api:

esp32_ble_tracker:

Conclusion

The issue with Shelly relays and ESPHome's 2025.2 update is a critical problem that requires immediate attention. By understanding the symptoms, culprit, and system configuration, we can work together to resolve this issue and ensure that our smart home automation systems continue to function smoothly.
Q&A: Updating to 2025.2 "kills" Shelly if Bluetooth is enabled

Frequently Asked Questions and Answers

In our previous article, we discussed a critical issue with Shelly relays and ESPHome's 2025.2 update. To provide further clarification and assistance, we have compiled a list of frequently asked questions and answers.

Q: What is the issue with Shelly relays and ESPHome's 2025.2 update?

A: The issue is that Shelly relays fail to boot properly when updating to 2025.2, especially when the esp32_ble_tracker component is enabled. This results in a reluctant boot, and the device may only boot in safe mode.

Q: What is the esp32_ble_tracker component?

A: The esp32_ble_tracker component is a part of the ESPHome framework that enables Bluetooth Low Energy (BLE) scanning on the ESP32 microcontroller. This allows the device to detect and connect to nearby devices.

Q: Why does enabling the esp32_ble_tracker component cause the issue?

A: The exact reason for this issue is not yet clear, but it is believed to be related to a conflict between the 2025.2 update and the Bluetooth component. Further investigation is required to determine the root cause.

Q: How can I fix the issue?

A: Downgrading to 2024.12 has been reported to fix the issue completely. However, this is only a temporary fix, and users who require the latest features and security patches may need to wait for a fix from the ESPHome developers.

Q: What system configuration and specifications are affected by this issue?

A: The issue has been reported on the following system configuration and specifications:

ESPHome Version: 2025.2.x
Installation Type: Docker
Home Assistant Version: N/A
Platform: ESP32-IDF
Board: Shelly
Component Causing the Issue: esp32_ble_tracker

Q: What is the minimal YAML configuration that reproduces the issue?

A: The minimal YAML configuration that reproduces the issue is as follows:

# minimal config reproducing the issue

esp32:
  board: esp32doit-devkit-v1
  framework:
    type: esp-idf

i2c:
  sda: GPIO26
  scl: GPIO25

esphome:
  name: ${device_name}
  friendly_name: ${friendly_name}
  comment: ${comment}
  
wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
ota:
- platform: esphome
logger:
  logs:
    ble_gateway: INFO
api:

esp32_ble_tracker:

Q: What can I do to help resolve this issue?

A: If you have experienced this issue, please provide serial logs to help identify the root cause. Additionally, developers can work together to reproduce the problem and develop a fix.

Q: Will this issue be fixed in a future update?

A: The ESPHome developers are working to resolve this issue, and a fix may be included in a future update. However, no official timeline has been announced.

Conclusion

We hope this Q&A article has provided further clarification and assistance in resolving the issue with Shelly relays and ESPHome's 2025.2 update. If you have any further questions or concerns, please don't hesitate to reach out.