Crash after a day

Question

Crash after a day

MeisterQ opened this issue 6 years ago · comments

Andreas commented 6 years ago

I always get a crash of my ESP32 after a day.

I cant watch it via Serial, because its not connected to my PC directly.

If i open a Serialport when its connected, the ESP is always restarting.

Im controlling the ESP via Node-Red and sending a "unlock" each 15 minutes to 2 devices.

The ESP is not responding anymore untill im resetting the device.

paul · Answer 1 · Mon Feb 04 2019 06:45:59 GMT+0800 (China Standard Time)

Are you using the latest version 1.20?

Andreas · Answer 2 · Mon Feb 04 2019 15:36:31 GMT+0800 (China Standard Time)

Are you using the latest version 1.20?

Yes.

You can close that topic.

I used a pre-release-OS of my FritzBox!7590 that made the ESP crash. After updating to a newer OS its working.

paul · Answer 3 · Tue Feb 05 2019 04:56:20 GMT+0800 (China Standard Time)

Do you know what the fritzbox was doing to cause the ESP to crash? It would be good to understand if there is something that could be changed in the ESP code to prevent the crash.

Andreas · Answer 4 · Tue Feb 05 2019 05:27:47 GMT+0800 (China Standard Time)

I have no clue. Mostly it happend at the nighttime. So i guess it was only busy with DSL and WiFI

Peter Becker · Answer 5 · Sun Feb 24 2019 21:18:35 GMT+0800 (China Standard Time)

Can you pls try this release: https://github.com/Floyddotnet/esp32_mqtt_eq3/releases/tag/v1.20-dev

Features are the same as v1.20 but used the newest SDK release with some bugfixes. Maybe this error is solved upstream.

Andreas · Answer 6 · Tue Feb 26 2019 02:15:44 GMT+0800 (China Standard Time)

Can you pls try this release: https://github.com/Floyddotnet/esp32_mqtt_eq3/releases/tag/v1.20-dev

Features are the same as v1.20 but used the newest SDK release with some bugfixes. Maybe this error is solved upstream.

What kind of bugfixes?

Peter Becker · Answer 7 · Tue Feb 26 2019 03:13:21 GMT+0800 (China Standard Time)

For example:
espressif/esp32-wifi-lib@da0fa33
espressif/esp32-wifi-lib@0c5f3d4
espressif/esp32-wifi-lib@630ff82

Fix issue which causes an ESP32 in station mode to disconnect from certain APs which announce two SSIDs.
Fix occasional failure of esp_restart() or esp_wifi_stop() in Wi-Fi/BT coexist mode.
Fix BT hardware coexistence problems where disabling previously active Bluetooth controller causes WiFi to not operate correctly
Fix occasional watchdog timeout in WiFi when software coexistence is enabled
Fix issue where BT may stop receiving data if software coexistence is enabled
Fix WiFi memory leak
.....

Andreas · Answer 8 · Wed Feb 27 2019 22:42:30 GMT+0800 (China Standard Time)

For example:
espressif/esp32-wifi-lib@da0fa33
espressif/esp32-wifi-lib@0c5f3d4
espressif/esp32-wifi-lib@630ff82

* Fix issue which causes an ESP32 in station mode to disconnect from certain APs which announce two SSIDs.

* Fix occasional failure of esp_restart() or esp_wifi_stop() in Wi-Fi/BT coexist mode.

* Fix BT hardware coexistence problems where disabling previously active Bluetooth controller causes WiFi to not operate correctly

* Fix occasional watchdog timeout in WiFi when software coexistence is enabled

* **Fix issue where BT may stop receiving data if software coexistence is enabled**

* **Fix WiFi memory leak**
  .....

Hey,

after uploading your files, my ESP wont connect to wifi anymore, but tells me, its connected to MQTT.

Im not receiving any data from my valves, also i cannot send anything.

Im watching via serial while publishing commands to the esp

Peter Becker · Answer 9 · Wed Feb 27 2019 23:06:39 GMT+0800 (China Standard Time)

This is strange. All my unit tests complete with this version. Can you please create an issue https://github.com/Floyddotnet/esp32_mqtt_eq3/issues and upload the serial output? With configuration do you use for MQTT? With or without username, password?

paul · Answer 10 · Thu Feb 28 2019 06:13:32 GMT+0800 (China Standard Time)

I merged and gave this a try on my test esp. Looks good. Many thanks.
There is an issue with previous config when using the new mqtt client however. I used a simple x.x.x.x ip address for mqtt url but the new client needs to know which protocol. For TCP MQTT the url needs to change to mqtt://x.x.x.x and for websocket wss://x.x.x.x. I will implement a default modifier to apply mqtt:// to any url not including a protocol identifier. This should allow upgrade to this new version without the need to reconfigure.

Peter Becker · Answer 11 · Thu Feb 28 2019 06:56:30 GMT+0800 (China Standard Time)

Thanks, i restore the support for the simple ip oder host mqtt urls with this pull request: #17

Peter Becker · Answer 12 · Thu Feb 28 2019 07:03:27 GMT+0800 (China Standard Time)

Btw, @MeisterQ report an issue: Floyddotnet#2 (Im always getting response with "TRV not available" when i send 2 commands for 2 devices.)

I can starting to investigate this issue at the weekend but if you want you can also take a look at this. Your are more conform with the bluetooth code and maybe you can findout this faster then i. :-)

smarthome-w · Answer 13 · Sat Sep 21 2019 03:22:17 GMT+0800 (China Standard Time)

Thank you for very good project.
I want to bump this topic. I've installed latest 1.42-beta from repo and my ESP32 crashes randomly. It only reboots (not so bad, I use mqtt with known configuration, it works after restart) or crashes (very bad) and I have to restart it manually.
I am quite new in ESP32 topic, so can you just write in README.md how to debug ESP32 and your software to understand the nature of the problem and give you feedback? Thanks in advice.

paul · Answer 14 · Sat Sep 21 2019 03:50:26 GMT+0800 (China Standard Time)

The first step would be to run the ESP with the serial monitor connected. That should give you some clue as to what is happening when it crashes or reboots.