-
For whatever reason, My ESP32 seems to stop working randomly. Sometimes once a day, sometimes multiple time, sometimes it'll go a few days. I have to power cycle it to get it running again. Is this a Blerry issue? A Tasmota issue? A user issue!? I'm using a NodeMCU-type ESP32 Devkit board. Haven't had any similar problems with other uses of it with just Tasmota. A buddy that also started using Blerry has had similar issues. I'm running 7 InkBird TH2 sensors right now (problem started when I only had one a couple of weeks ago). |
Beta Was this translation helpful? Give feedback.
Replies: 61 comments 10 replies
-
I don't have time for a full response to this at the moment but can you try |
Beta Was this translation helpful? Give feedback.
-
Thanks, |
Beta Was this translation helpful? Give feedback.
-
My longer thought is that it's asking a lot of the radio to 1) deal with the regular wifi connection, 2) deal with BLE passive and active scans, then 3) do a scan of available networks. You could run into power supply issues or just random issues that cause the radio to seize. I have not been able to reproduce the issue on a dev-board myself. So, your update will be greatly appreciated! However, I did have an ESP32 plug (Wyze WLPP1CFH) that was showing similar behavior, uptimes of ~1 day. Turning SO57 off, and I hit 10 days before I restarted stuff for an unrelated reason. |
Beta Was this translation helpful? Give feedback.
-
I've asked a buddy that's having the same issue try the SO57 option. Will go a day or three and follow up (sooner if he or I see similar problems). |
Beta Was this translation helpful? Give feedback.
-
I have experienced this as well. I am using the TTGO T7 V1.5 ESP32 module and two Inkbird IBS-TH2 sensors. |
Beta Was this translation helpful? Give feedback.
-
I’m having the same problem. I have 4 Shelly 1 Plus with Tasmota32 solo1 BLE and thermostat either version 10.1.0.2 or 10.1.0.1. Most have only 1 sensor it is reading. They can go several days without issues and then require a reboot to start responding again. I’ll try the above option and report back if it’s not fixed. |
Beta Was this translation helpful? Give feedback.
-
The dev version of Tasmota lasted about 40 hours before the problem popped back up. My buddy had it pop up with SO57 0 on the latest release version shortly after making that change. I'll try a different controller with only one inkbird on it. I'll also use a different flashing tool than Chrome, but don't think that really matters. |
Beta Was this translation helpful? Give feedback.
-
Since you are using a development board, were you able to capture serial log data to see what's happening? Like I said, I have been unable to reproduce the issue locally. If we are to propose to the Tasmota devs that there is an issue somewhere, we need log data. |
Beta Was this translation helpful? Give feedback.
-
I'll set up a couple here on the latest dev build and dump them to a file. I'll do some dev boards of various ones with the same files on various sensor types. |
Beta Was this translation helpful? Give feedback.
-
I was not able to reproduce as well. of course with blerry they all have to monitor : |
Beta Was this translation helpful? Give feedback.
-
Pardon my lack of experience posting in github and the format. First log entry foundLogger: homeassistant.components.mqtt Disconnected from MQTT server 192.168.1.216:1883 (7) Second log entry foundLogger: paho.mqtt.client failed to receive on socket: [Errno 104] Connection reset by peer |
Beta Was this translation helpful? Give feedback.
-
I think the log we are talking about is from Tasmota. I was going to drop the log via syslog to a file. |
Beta Was this translation helpful? Give feedback.
-
@Brummy need to log from the device edit: whoops digi was faster than me :) |
Beta Was this translation helpful? Give feedback.
-
Thanks @devzwf and @digiblur |
Beta Was this translation helpful? Give feedback.
-
Just wanted to throw this in here. I've experienced the same issue with what i assume is the same device. Would additional logs be of use or a distraction? |
Beta Was this translation helpful? Give feedback.
-
I’m also trying it currently on several devices and no issues so far (though it went days without issues on the old version). The daily scheduled restart has kept them working so far. I disabled that to see if this fixes the root issue. |
Beta Was this translation helpful? Give feedback.
-
If you can, do an erase flash then flash latest dev. Jason2866 mentioned on a Tasmota issue that somehow some things that were screwing with BLE stability on old frameworks didn't get taken care of by an OTA and |
Beta Was this translation helpful? Give feedback.
-
I threw on this version on to one of my ESP32s with the standard Rule1 and Blerry:
I did erase the flash so it should have been a blank slate, will update if goes down. |
Beta Was this translation helpful? Give feedback.
-
Good timing, mine crashed last night after 48 hours. Trying it now. |
Beta Was this translation helpful? Give feedback.
-
Had a Shelly plus 1 crash with the new firmware. However I didn’t clear flash. |
Beta Was this translation helpful? Give feedback.
-
Newest Tasmota DEV firmware does not do anything for me, it is in this usual loop, displaying this every second: 15:21:05.282 WIF: Connect failed as AP cannot be reached |
Beta Was this translation helpful? Give feedback.
-
I erased the device and flashed the new FW above today and it became unresponsive after about one hour. |
Beta Was this translation helpful? Give feedback.
-
I am using a so called ESP-32 D1 mini as a MQTT gateway for some Xiaomi BLE sensors and I think I am facing the same issue after upgrading Tasmota from 9.5.0 to 10.1.0. The device is unresponsive (MQTT and HTTP) and the issue is solved after a power reset - however it reoccurs after 1-2 days. I will rollback to 9.5.0 but it would be good if someone will be able to understand and mitigate this issue. |
Beta Was this translation helpful? Give feedback.
-
So was it stable with 9.5.0? That might mean it was something in a recent version? |
Beta Was this translation helpful? Give feedback.
-
Yes, it was stable for a long time 9.5.0 as I don't recall ever resetting the device. Something to add, after reading this topic, I just pressed the reset button on the ESP-32 D1 mini and it recovered - I don't know if this is in any way different from a power reset. Something that I didn't state in the initial post is that I'm using the Tasmota32-bluetooth build. |
Beta Was this translation helpful? Give feedback.
-
The nightly reboot timer worked as a mitigation for the unresponsive/wifi dropping issue on my Shelly plus 1s. That is until just recently I had one of them go offline. I tried the latest dev version of Tasmota (11.0.0.4) doing an OTA upgrade from https://github.com/tasmota/install/blob/main/firmware/unofficial/tasmota32solo1-bluetooth.bin?raw=true and I think it fixed the problem as I haven’t had any issues so far without the reboot timer. |
Beta Was this translation helpful? Give feedback.
-
After firmware upgrade to 11.0.0.4(bluetooth) my ESP32-D0WDQ6 is working continuously for 48 hours |
Beta Was this translation helpful? Give feedback.
-
Same here on 11.0.0.3 no reboots since it upgraded 15days ago |
Beta Was this translation helpful? Give feedback.
-
Really glad to hear the latest Tasmota is stable without custom compiles! I am also working on a compatibility layer to use the new BLE driver that's being developed, and it is working great! |
Beta Was this translation helpful? Give feedback.
-
Hi! I'm quite new to using ESP devices... So, I have a ESP32-DevKit (ESP32-wroom-32) , with last Tasmota version 13.2.0(bluetooth). However, I got into the issue where my ESP began to restart without stop, 2-3 seconds after boot, restarted again.
|
Beta Was this translation helpful? Give feedback.
Please try with tasmota v11.x train
and not tasmota v13.x.x for your sanity