New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strange Total-Crash Failure after a couple of days/weeks ESP32 RF gateway #854
Comments
saw some similar problems here with a suggest for solution: |
Hello, Could you try to isolate the crash reason by deactivating the modules one by one please? Alternatively you could try to update the BME280 library (platformio.ini file): |
i will have a try with BME@2.0.9 i just compiled and uploaded the version to my NODEMCU board, which is also using the RF-Receiver/sender... i'll try to keep an eye on that and post feedback. |
This is just to target the defective module, not to ask for a permanent removing |
Thanks, i completely understand... i've updated my NodeMCU with RF and BME to BME-Lib2.0.9 and give it a try. If it dosn't work, i'll remove the BME from these board completely for testing. |
Updating to BME @2.0.8 seems not to fix.... BME@2.0.9 was not possible in a quickly manner since there are some changes in the initialization process that seems to require a bit of changes in OMG to open the I2C. Nevertheless, i removed the BME-Lib and the sensor completely from the board and give it a try for testing purpose. |
Hi, OMG in Version 0.9.5 development
Also for me the only way to unlock the esp is to use the Dattel technique, |
Today my device crashes again - this time only with RF-Send/Receive Modules.. so 14 days to crash this time... |
Thanks for the feedback. Did you checked your power supply voltage and stability? Also I found out that there is an issue with wifi manual setup and the v0.9.5, could you erase the flash, comment this line of code, and upload it. The issue is that the wifi.begin() function may be called too close to another wifi.begin resulting in a continuous reconnect loop |
@Albertowue did you get a serial monitor output (115200) to see what's going on. |
Hi @1technophile, thanks for your fast reply.. i just updated my sources to the latest development-sources, commented out your line, but didn't change the loglevel, since the device is running offsite only with power supply. As i mentioned earlier, if the device crashes, i only got rubbish on the serial and the rate changes magically to 74880 - so i assume that there is nothing more usefull coming in then. Will give it a try now... |
Hello @Dattel @Albertowue, I have done an update of the RCSwitch libraries,
to
and see if you get a better stability? |
sure... |
I just updated to the latest git sources and changed line 87 of platformio.ini as indicated. The system just crashed after 10 days of operation. |
I am using OMG with BLE discovery. I've tried the current code on several ESP32 and I recognized crashes after several days. |
Could you indicate what do you mean by the current code? |
Hmm, I don't understand how you can have a system crash after 10 days of operation if you took a change that was provided 2 days before your message :-) |
I am using the current dev-branch. Not the release. |
ok, there were several corrections made these last days, could you try the last dev? |
Excuse my bad English, I meant that before making the change you suggested it was blocked again. For now with your changes I have reached 12 days of operation and without blocks |
No problem, thanks for the feedback! |
I'm closing the issue if it reappears do not hesitate to comment here |
sorry, the problem isn't fixed... two devices reached lockdown-state a couple of days before - i didn't realized that so i can't say, how long they really last without crashing. |
@Dattel which version are you using? By lockdown state, you mean that it didn't restart itself? |
with "lockdown state" i mean, i have to reflash the device including "Erase UserData & Wifi settings".. i have two "locked down" devices:
I'm using the latest git-checkout from the 03.03.2021 with rcswitch#0e0d210 |
I reflashed both devices 2 day's ago - the NODEMCU Dev-Board lasts for 2 days and stucks again.... |
Hi,
i have a strange behaviour with OMG in Version 0.9.5 on a ESP8266 NodeMCU Board
espressif8266@2.6.2
My attached devices are:
-BME280
-RF-Sender
-RF-Receiver
I'm using my own prod_env.ini with the following compiler settings:
After a variable time period (days/weeks) the board hangs... If i try to capture some informations using the serial port in need to adjust the baudrate to 74880 and all i got is:
The only way to fix these issue-state is to flash a sample blink sketch with Arduino-IDE using the "Erase all Flash Content" and after that reflashing OMG. If i flash without "Erase all Flash Content", i can't leave these state of death.
I also have these issue with other ESP-01 based boards only with BME280 Sensors attached. But here the frequence of death is much less frequently.
Any Idea's how to fix that?? Or any clue, where i have to dig a bit deeper??
Thanks
D
The text was updated successfully, but these errors were encountered: