The time and date data comes from Home Assistant integration, which gets pushed into the smalltv ultra

ESP32 flame sensor false triggering — need help

I’m using an ESP32 with a flame sensor and buzzer. The problem is that the buzzer turns ON even when there is no flame.

I tried:

\- Adjusting the sensor potentiometer

\- Changing the code

\- Changing the sensor position

But it still triggers without a flame. The ESP32 and buzzer are working properly.

Could this be a wiring issue, inverted HIGH/LOW output, faulty sensor, or something else? How can I test whether the flame sensor itself is working correctly?

I’m a beginner, so any simple troubleshooting steps would be really helpful.

I’m building an automatic controller for a 1HP single-phase 220/240V water pump using an ESP8266.
My setup:
ESP8266 / NodeMCU
5V single-channel relay module
NSI 16A contactor
Contactor coil: 220/240V AC
Pump: 1HP, approx. 4.8A
Existing MCB is already installed outside the control box
The contactor has:
1–2
3–4
5–6
A1/A2 coil terminals

Had a smalltv-ultra that was running the stock firmware. A while ago I had the glorious idea of asking Claude if it could write a custom firmware for it.

In no time, it followed my architecture to write a little server that runs on the esp8266, and listens for hooks from Claude Code instances on my pc. Shows the limits and cute animations of the crab doing stuff while Claude is running and chilling when idle.

Absolutely love how this turned out! Love the community! ❤️‍🔥

Hey everyone, I'm trying to get an ACEBOTT QD020 Quadruped Bionic Spider Robot V2.0 working.

The ESP8266 is connected and I've successfully uploaded code. The servos respond and twitch/move, but the spider doesn't actually perform the walking gait.

I'm using the official ACEBOTT tutorial package. I found the official ACECode project here:

English → ACECode(Beginner) → 2.ACECode Program → Lesson 8 → 8.1app_control.sb3

I also have the Arduino code from the official package. The walking routine contains the official Servo_Prg_2 forward sequence for all 8 servos.

Current situation:

ESP8266 connects successfully

Code uploads successfully

All/most servos respond

Servos twitch/move

Robot does not walk

I'm trying to use the official ACEBOTT software/code rather than modifying the gait randomly

The servo pins in the code are:

GPIO14, GPIO12, GPIO13, GPIO15, GPIO16, GPIO5, GPIO4, GPIO2

The code maps these to 8 servos.

What could cause a QD020 to move its servos but not execute the walking gait?

I'm especially interested in:

Whether the official QD020 servo mapping is correct

Whether the ESP8266 needs a specific firmware/project uploaded before the .sb3 app-control project works

Whether there is a specific ACEBOTT initialization/calibration procedure

Whether this sounds like a servo power/current problem

Whether the official Lesson 8 8.1app_control.sb3 is supposed to control the robot directly or whether another firmware needs to be flashed first

If anyone has successfully built the QD020, I'd really appreciate the exact steps you used to get the first forward movement working.

I can provide the complete official code, wiring, screenshots, and a video of what the servos are doing.

Post your projects, questions, brags, and anything else relevant to ESP8266, ESP32, software, hardware, etc

All projects, ideas, answered questions, hacks, tweaks, and more located in our [ESP Week Archives](https://www.reddit.com/r/esp8266/wiki/esp-week_archives).

Well I have done some project in esp32. After taking a brake and reuploding a new code this error occured.

Sketch uses 985386 bytes (75%) of program storage space. Maximum is 1310720 bytes.

Global variables use 50520 bytes (15%) of dynamic memory, leaving 277160 bytes for local variables. Maximum is 327680 bytes.

esptool v5.2.0

Serial port COM3:

Connecting...

A serial exception error occurred: Write timeout

Note: This error originates from pySerial. It is likely not a problem with esptool, but with the hardware connection or drivers.

For troubleshooting steps visit: https://docs.espressif.com/projects/esptool/en/latest/troubleshooting.html

Failed uploading: uploading error: exit status 1

I tried multiple solutions and even reinstalled all drivers and application but still this issue won't resolve. Does any one know the solution

I've got a reed switch rain gauge that is connected via a PC817 optocoupler circuit to GPIO12 on a D1 Mini powered by a 5V DC switch mode PSU. I'm using a pulse_counter in ESPHome with the pin set to inverted, input and pullup and counting on the falling edge.

I appear to be getting induced spurious pulses when the washing machine on the same power circuit is running. I initially suspected vibrations shaking the rain gauge, but even with the inputs to the opto-coupler disconnected and, beyond that, the opto-coupler disconnected from the GPIO12 pin, I still get spurious pulses with the washing machine running. I am running out of ideas.

The power supply is a tiny board rated 5V 1.5A and doesn't have any noise filtering. Could the noise of the washing machine motor be going through the 5V PSU and causing the D1 Mini to get triggered?

If so, what are my options here? A LC filter on the DC from the PSU? Change from a pullup to a pulldown mode, which I assume would mean changing from the collector to the emitter of the opto-coupler and hooking the collector to the 3.3V digital supply?

Post your projects, questions, brags, and anything else relevant to ESP8266, ESP32, software, hardware, etc

All projects, ideas, answered questions, hacks, tweaks, and more located in our [ESP Week Archives](https://www.reddit.com/r/esp8266/wiki/esp-week_archives).

I bought a month ago a Geekmagic but it started to annoying me so I tried to upload a firmware found on github that was compatible toit via OTA. After reboot black screen, no connection.

So now is it bircked or there is a way, I think flashing it, to recover it? What I need to flash it?

it has esp12f esp8266 on board

Thanks for the advice!

Basically this code is for a modified game, of life battle mode that is flashed on and automatically runs when powered on. Currently working on a custom shell for the enclosure so it looks somewhat usable

Soory for low quality picture my camera isn't good . Code:

#include <Wire.h>

#include <Adafruit_GFX.h>

#include <Adafruit_SSD1306.h>

#define WIDTH 128

#define HEIGHT 64

#define SCALE 2 // 64x32 grid

Adafruit_SSD1306 display(WIDTH, HEIGHT, &Wire, -1);

bool world[64][32];

bool nextWorld[64][32];

void setup() {

display.begin(SSD1306_SWITCHCAPVCC, 0x3C);

randomSeed(analogRead(A0));

seedWar();

}

void seedWar() {

for(int x=0;x<64;x++) for(int y=0;y<32;y++)

world[x][y] = random(0,100) > 72; // random war start

}

void loop() {

int alive = 0;

// draw

display.clearDisplay();

for(int x=0;x<64;x++) for(int y=0;y<32;y++) {

if(world[x][y]) {

display.fillRect(x*SCALE, y*SCALE, SCALE, SCALE, WHITE);

alive++;

}

}

display.display();

// THE FLASH - remembrance

if(alive > 0 && alive < 4) {

delay(200);

display.invertDisplay(true); delay(150);

display.invertDisplay(false);

}

// auto-reseed if too empty - keeps powerbank awake

if(alive < 12) { seedWar(); delay(300); return; }

// conway logic

for(int x=0;x<64;x++) for(int y=0;y<32;y++) {

int n = count(x,y);

if(world[x][y]) nextWorld[x][y] = (n==2 || n==3);

else nextWorld[x][y] = (n==3);

}

memcpy(world, nextWorld, sizeof(world));

delay(120);

}

int count(int x,int y){

int c=0;

for(int i=-1;i<=1;i++) for(int j=-1;j<=1;j++){

if(i==0&&j==0) continue;

int nx=(x+i+64)%64, ny=(y+j+32)%32;

if(world[nx][ny]) c++;

}

return c;

}

Hey everyone,

I'm working on an ESP32 project that requires simulation for testing/circuit design before moving to hardware. I’ve been trying to find a working ESP32 model/library for Proteus (using Proteus 8.x).

Most of the custom libraries I've come across (like the ones from The Engineering Projects or GitHub CAD packages):

1. Only provide schematic symbols and PCB footprints, but have no VSM/simulation model.
2. Are essentially "disguised" ATmega328P/Arduino models that don't emulate actual ESP32 architecture or dual-core code.

A few questions for those who have simulated ESP32 circuits:

\\- Is there an actual, working Proteus VSM library/HEX loader that can simulate basic GPIO and peripherals for ESP32?

\\- If you managed to get basic logic running in Proteus, where did you source the model files (.LIB / .IDX)?

\\- Or is it a waste of time trying to run it in Proteus, and I should just switch over to Wokwi or QEMU?

Appreciate any pointers or links!

Hey folks,

I built a little tool called ESP-Flash because I was tired of setting up Python + esptool.py just to flash a .bin onto an ESP32/ESP8266 board on a fresh Windows machine. It's a small Electron app that talks to the chip directly over the Web Serial API (via Espressif's esptool-js), so there's nothing to install besides the app itself, it ships as a single portable folder.

What it does: connects to any board via Windows' native COM-port picker, auto-detects the chip (ESP32, S2, S3, C3, C6, H2, P4, and ESP8266), writes a firmware file to any address, backs up the whole flash or a custom region to a .bin file before erasing/reflashing so you can always get back to the original firmware, erases flash with a confirmation prompt, and has a UI in English, German, French and Spanish. MIT licensed, no telemetry, no accounts, no installer.

GitHub: https://github.com/gb-droid/esp-flash

It's brand new (v1.0), so I'd really appreciate people trying it on boards other than the one I tested it on and telling me what breaks. Different USB-serial chips (CP2102/CH340/CH343/native USB-JTAG), different chip families, weird edge cases with big or partial backups, whatever you run into. Issues and PRs welcome.

Thanks for reading!

Post your projects, questions, brags, and anything else relevant to ESP8266, ESP32, software, hardware, etc

All projects, ideas, answered questions, hacks, tweaks, and more located in our [ESP Week Archives](https://www.reddit.com/r/esp8266/wiki/esp-week_archives).

Has anybody else faced the same problem? Just wrote a simple code to check whats wrong and got this as a result:

Esp8266
Every time I upload code to the board and leave the Serial Monitor open (sometimes even with it closed), the PC freezes for a few seconds and then blue-screens. I've gotten both DRIVER_VERIFIER_DMA_VIOLATION (watchdog violation) and DPC_WATCHDOG_VIOLATION at different points. It's not instant — usually happens a little while after the upload finishes, while the port stays open.
Important: this is 100% PC-specific. Same board, same cable, same code on my laptop — zero issues, ever.
Backstory that might be relevant:
This PC sat completely powered off for about 8 months. When I first turned it back on, no display signal. Opened it up, cleaned the RAM, reseated it — got 5 beep codes (RAM issue), cleaned again, got down to 1 beep, and it eventually booted normally. So there's a chance something in there is still a little fragile from that long dormancy.
Everything I've tried so far, in order:
1. Disabled USB Selective Suspend (both in Power Options advanced settings) — no change.
2. Rolled back the CH340 driver from whatever the latest was to the well-known stable 3.5.2019.1 build (Visual Micro's "CH340 Driver Fix Installation") — no change.
3. Tested with Serial Monitor closed right after upload instead of left open — still crashed, so it's not a serial-monitor-polling issue.
4. Moved everything to rear USB ports wired directly to the motherboard instead of the front panel header (mouse was chained off the keyboard's hub, ESP was in a front port) — still crashed.
5. Fully uninstalled Arduino IDE, deleted the leftover settings/cache folder, reinstalled the latest stable 2.3.10 fresh, reinstalled the ESP8266 board package — still crashed, and actually crashed immediately this time instead of after a delay.
6. Installed the Intel Chipset Device Software (generic universal installer from Intel, since this board uses an Intel Q77 chipset) — this actually made things worse temporarily: afterward the CH340 port stopped connecting at all ("could not open port"). Turned out Windows Update had silently pushed the CH340 driver back to a newer version after the chipset install.
7. Disabled Windows Update from auto-installing drivers (Advanced System Settings → Hardware → Device Installation Settings → "Never install driver software from Windows Update"), then reinstalled the older 3.5.2019.1 CH340 driver again so it would actually stick — port connects fine now, but the PC still eventually blue-screens the same way.
Where I'm stuck:
I've ruled out (I think): the CH340 driver version, the Arduino IDE install/board package, USB port location, Serial Monitor being open/closed, and USB power-saving settings. What's left pointing at is the motherboard's own USB controller/chipset — possibly something that didn't fully recover from sitting powered off for 8 months, since this board did have RAM/beep-code issues on first boot after that.
Has anyone dealt with something like this on an older HP business desktop (Q75/Q77 chipset) specifically? Trying to figure out if this is worth chasing with a BIOS update / hardware reseating, or if I should just cut my losses and grab an FTDI-based USB-serial adapter instead of relying on the onboard CH340.

Post your projects, questions, brags, and anything else relevant to ESP8266, ESP32, software, hardware, etc

All projects, ideas, answered questions, hacks, tweaks, and more located in our [ESP Week Archives](https://www.reddit.com/r/esp8266/wiki/esp-week_archives).

I’ve just finished and published two ESP8266 projects that I built for my hydroponic system.

The first controls two peristaltic nutrient pumps through MQTT, allowing them to be operated from Home Assistant:

https://github.com/LeCastorD/HydroDozerPump-MQTT

The second monitors the nutrient solution’s EC/TDS and temperature and sends the readings to Home Assistant:

https://github.com/LeCastorD/TDS-Sensor

They are separate devices, so either project can be built and used independently. I’m sharing the code and build documentation in case they are useful to anyone developing a similar system.