Closed DavidFW1960 closed 5 years ago
Hi,
I couldn’t reproduce this issue.
Your config seems ok.
Please, could you try to wipe out the config settings using reset 5 command?
If that can't be done or don't solve your issue, please do a full flash erase with esptool.py as explained in the wiki and then flash with esptool.py the latest precompiled bin from development branch.
I did flash a precompiled firmware from dev ok but there is no precompiled 2.3.0 core and 2.4.2 and 2.5.0beta3 have been a disaster.
It's tricky flashing when you only have 9 seconds before it crashes.... I flashed 7 sonoffs yesterday and managed to get them all back to my previous build and they have all been quite stable since.
I am just downloading the zip from dev and extracting, editing platformio.ini and user config and recompiling firmware. I have done this 50 times with no issue...
I think there is something specific wrong with this firmware I am compiling...
Ok. So the issue is not in the original Tasmota. Is in your building environment.
The precompiled bins with core 2.3.0 are available for release only (6.4.1) check thehackbox.org page
The core 2.5.0 has been released 2 or 3 days ago and it is working great for me. Anyway, the selection of the core depends on your router brand. Some works better with 2.3.0 and others with 2.5.0
So what should I check in my building environment? It hasn't previously been an issue.
I might try the released core 2.5.0 - is that in the latest dev releases?
I just compiled my own with core 2.5.0 and it's not rebooting.... remains to be seen how stable it is with MQTT disconnects. I don't even know where to begin looking to find troubles in my building environment - it's just Visual Studio Code with PlatformIO IDE..
Good to know that now it is working for you. Closing this issue as it isn't a Tasmota bug.
For your building setup, you can try to delete all Tasmota files and also the core files and download them again. This I'm sure will solve your building setup issue because as you told me that you were downloading and copying, that could led to weird issues. In both, Tasmota and the core, some files were deleted and others renamed in the lasts versions, so, if you just overwrite files, the old files remain producing weird issues.
If you need further assistant on that, please just ask here or in the Tasmota Support Chat. Thanks
IMPORTANT NOTICE If you do not complete the template below it is likely that your issue will not be addressed. When providing information about your issue please be as extensive as possible so that it can be solved by as little as possible responses.
FAILURE TO COMPLETE THE REQUESTED INFORMATION WILL RESULT IN YOUR ISSUE BEING CLOSED
Describe the bug A clear and concise description of what the bug is. Last 2 dev builds, d509dcf and 78b2bd3 cause the sonoff (S22 and Sonoff SV) to go into a boot loop... every 8 seconds they reboot after an exception
Also, make sure these boxes are checked [x] before submitting your issue - Thank you!
status 0
:To Reproduce Steps to reproduce the behavior: Using this my_user_config.h
PlatformIO.ini
Expected behavior A clear and concise description of what you expected to happen. Every previous dev version has worked with this configuration. I also compiled the current firmware with a my_user_config.h file that I used successfully with version 6ee3d1a
Screenshots If applicable, add screenshots to help explain your problem. See below the console
Additional context Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)