Seeed Studio IoT Button V2 errors

[Primer-Merc]

Hardware/Software:
Seeed Studio IoT Button V2 ( Button V2 for short )
Home Assistant Core 2025.12.0
HA Supervisor 2025.12.2
HA Operating System 16.3
ESPHome Device Builder 2025.11.4
ESPHome Firmware: 2025.11.3
Microsoft Edge Version 142.0.3595.94 ( for Web Flashing )

1. Button V2 will not flash the V2 firmware https://gadgets.seeed.cc/ webpage unless the battery is removed and the boot button is pushed. ERROR "Failed to download manifest"
2. Button V2 will flash with the V1 firmware https://gadgets.seeed.cc/ with the battery installed as expected. Boot button not always required.
3. Neither firmware functions correctly, or performs as expected.

Expectation is - On button push, the Button V2 wakes up, connects to Wi-Fi, sends payload, confirms payload is sent with LED lights, waits for return data (if any), returns to sleep mode.

4. Button V2 can be flashed with the V2 firmware/yaml , inside the ESPHome builder. This does not fix the issues.

Issues.

When flashed with the V2 or V1 firmware using (1) or (2) or (4) without any edits other that the Wifi settings and the device name, the user button will not work. The virtual buttons inside ESPHome will temporarily send a payload to the Button V2 , and the LED's will light accordingly. However, once the Button V2 goes to sleep, that no longer works. The Button V2 never comes out of sleep. Button pushes, plugging in to charge, nothing will awaken the device.

Removing all light sleep and deep sleep code from the Yaml will allow the Button V2 to function, except virtual button #3.

All Button V2 ( 3 TOTAL ) were received from China on 12/4/2025. All have PCB dates markings v2.0 4/24/2025 , and were purchased directly from Seeed Studio website.

Would love some advice on this. I followed all instructions from official sources, and used CHAT Gpt for trouble shooting to determine that the sleep settings were causing most of the problems.

The attached yaml is the most functional one I have to date, and it is still broken. The battery does not report correctly, and the virtual button #3 does not work. And of course the device never sleeps.

iot-button-1.yaml

[github-actions]

👋 @Primer-Merc

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.

[Primer-Merc]

Should anyone else come across this, apparently ESPHome cannot use the same input button to serve 2 purposes. The IOT user button cannot be the input that wakes the ESP32C6 and then later be a normal binary switch. I had to switch to Arduino and create my own firmware largely based on the zigbee sketch. I have included my sketch as a ZIP attachment. Anyone who wants to use this sketch will need to pay attention to the necessary " include files" , and setup your own MQTT server and Wi-fi details.

#include "connections3.h" // Your WiFi/MQTT Details

This sketch took about 7 hours to complete. The user button will wake the ESP32C6, connect to Wi-FI and MQTT , confirm those connections, then send a binary "switch on" payload.

Make sure to include these lines in your connections.h , or whatever you decide to name it. These names are custom to my scheme.

// MQTT Client ID
const char* client_id = "iot_button_3";

// Topic Base for Button 3
#define MQTT_TOPIC_BASE "iot/button3/"

button_v2.zip

[Primer-Merc]

I will leave this open until either someone from tech/ or user, has a better idea.

[limengdu]

@Primer-Merc If you want to fully leverage the button functionality an IoT Button should offer, ESPHome isn't your preferred platform. In that case, we recommend giving our plugin a try. https://github.com/limengdu/Seeed-Homeassistant-Discovery
You can flash the firmware compatible with this plugin onto your IoT Button on this page. https://limengdu.github.io/Seeed-Homeassistant-Discovery/flasher/
This plugin enables deep sleep for buttons, ensuring extended battery life. Physical changes can be triggered directly without requiring a click to wake up. All current limitations are due to constraints within ESPHome.

[Primer-Merc]

@limengdu So far the .ino I posted has been working exceptionally well. I did need to make a few very small tweaks to the voltage factor line. 1.36 seems to be a very close representation of the actual battery voltage.

" const float VOLTAGE_CORRECTION_FACTOR = 1.36; // FINAL CONFIRMED FACTOR FOR 4.20V "

With that change, I consider the firmware now final. No more weird sleep issues that need multiple click to send a payload.

I have my sleep timer set to 2 minutes, but that could be shortened if battery life was a major problem.

"const uint32_t INACTIVITY_TIMEOUT = 2 * 60 * 1000; // 2 minutes inactivity timeout (ms)"

I will be saving that link you provided though. I quickly looked through it and It seems very interesting.

And I do you ESP home with several sensors, So I may test your plugin with the additional IOT Button I purchased that's not in use.

Thanks for the reply !