flash sonoff basic r2 after connect to wifi net, is impossible to see online #2931
Comments
|
I installed ESP_Easy_mega-20200222_normal_ESP8285_1M.bin on a couple Sonoff Basic R2's without issue. So if this bin does not work for you then more information would be helpful. Flash again and connect using AP mode. After you enter the credentials, and before the reboot, go to the Tools=>Advanced=>Serial Log Level and set the serial log to debug. Submit (save). The serial log will provide messages that may explain the problem. So launch your favorite serial terminal, reboot, and review all the messages from ESPEasy. BTW, whenever problems occur from a firmware update it is wise to flash with the blank_1MB.bin file to clear out the Flash memory (removes old settings). Then flash the Mega Release.
|
|
The last nightly build has the There is a difference between flashing mode (dout/dio/etc) and the build settings. Do you see the node connecting to the WiFi? |
TD-er
added
Category: Stabiliy
hi, sure i always perfomr a blank_1MB.bin flash to eresa esp before flashing any fw my sonoff is a sonoff basic and on pcb si written R2 v1.0 2017-10-11 anyway with XXX_normall_ESP8266_1M.bin the issue was that after flash, when i connect using AP mode to my internal newtwork,, after reboot i'm not able to see the sonoff on my network. now i flash again with |
no, unfortunatly, after connecting to AP mode: 192.168.4.1 selecting my network SSID and enterin the password, the sonoff reboots and i can't see on my network
no, i wait many minutes but i can't see it inside my network EDIT: sorry, i add a note, when i connect to AP mode, the esp reboot and ESP_0 net disappear, and as i wrote it's no possible to have any IP inside my netword of this sonoff. |
|
i have also try to flash: in this case, after flashin appear ESP_Easy_0 network, i connect to that AP , i give credentianl of my network, it show the countdown, but after that sonoff remain connected at ESP_Easy_0 latest attempts was done using: nothing difference on behaviour except name of SSID that is now become ESP_Easy |
I made a bad assumption on which ESP chip was in your Sonoff Basic. Currently sold Sonoff Basics use ESP8285 (internal Flash). Older versions used ESP8266 (external Flash chip).
Unfortunately it does not appear that you can enable the log using serial commands. As a workaround, try this: reload the working firmware, set the log level to debug, save, and confirm the log is running. Then load the new firmware (without blank bin file). With a bit of luck the old Tool settings will still exists and provide a working serial log. @TD-er, |
|
i try also this: flash ESP_Easy_mega-20181023_dev_ESP8266PUYA_1024_VCC.bin |
|
env:normal_ESP8266_1M is using the regular platform, so it should have the "latest" SDK 22x settings. These are the current settings for the used SDK 2.2.x builds: ESPEasy/platformio_core_defs.ini Lines 113 to 132 in 4e7cb1e These "new" settings are now the default since you last tested them: ESPEasy/platformio_esp82xx_base.ini Lines 7 to 11 in cde4c93 So if the regular builds do not work and builds of about a week or a month ago also do not work, then we have another issue. Also the settings do not seem to be saved, so I guess it has nothing to do with the WiFi but more with the way how flash is being saved. |
You won't see the serial log from the browser. You need to use a serial terminal communication program (puTTY, Arduino Terminal, etc.) and connect the serial port via USB. First confirm the serial log is working when the "good" bin (ESP_Easy_mega-20181023_dev_ESP8266PUYA_1024_VCC) is running. After you see it working you can load the new firmware. Also, the Expressif startup messages will appear on the serial port at reboot even with serial log disabled. Post the messages that appear. They will confirm that boot was successful. With your serial terminal connected, enter this command in the terminal window: It will report some useful setting info, like this example:
Let's not give up on that yet and wait for more feedback. BTW, too bad that the various log levels cannot be set via serial terminal.
|
|
Keep in mind this is a Sonoff Basic R2 so runs at mains voltage. Hooking it to USB while plugged in can be dangerous. |
|
Good reminder about mains voltage. The serial terminal uses the USB port just like the flashing tool. The 3.3V power will come from USB. Never connect Mains power when USB is connected. Otherwise prepare an updated will for the surviving family members.
|
i well know, but better underline :-) |
|
Better to underline than to undertake.... |
i used putty with this is the log of fw with PUYA i can't write "settings" inside the command propt because it's not allow to write nothing. what's the next steps? EDIT: this log is simply generated only connecting to AP, giving my network credentials, activate the serial log inside tools=>advanced=> serial log as debug |
So far so good.
Your PuTTY settings seem valid, but I suggest setting Flow Control to None. Maybe the "settings" command did not exist in your old bin version? Here are some other commands to try out to help confirm that you can fully communicate with the device (each command must be followed by [Enter]). If you do not have success then try the Serial Monitor feature that is provided in the ESP.Easy.Flasher.exe program (included in the ESPEasy firmware zip bundle). After you are able to communicate, load the new firmware (do not use the blank bin).
|
these are commands for ESP with puya |
|
|
now i flashed directly: ESP_Easy_mega-20200204_normal_ESP8266_1M.bin the serial log was setted to "info" |
|
From reviewing your logs I believe you have a WiFi library compatibility issue that is related to the hardware. I experienced that last week on a Sonoff Basic that was the exact same vintage as your hardware. @TD-er:
|
after many trial i succeed on having for a while the web page using a reboot inside serial monitor. |
Just more symptoms of the WiFi library issue I mentioned. So far it seems to involve Sonoff Basic V1 modules made 2-3 years ago. But the sample size is very small (one of mine and maybe this one of yours). So consider my conclusion to be a gut feeling. I think you'll need @TD-er to assist with this. If the latest Mega release does not have the special WiFi library then a custom build will be needed to test things out.
|
|
I created 2 different 1M test builds, based on different SDK builds. They both are based on the current HEAD of the mega branch. |
Thanks. Fingers are crossed. Place your bets now.
|
|
I think his network may have gotten one of those very swiftly rolled out security patches which we have not yet implemented in ESPEasy. |
hi TD-er i do not think that is related to my home network because i have for example nodemcu, wemoss and ESP12 breadbord where i use espeasy and i do not find issue. anyway i'm testing the two versions p.s. but i would like to update the fw from a sonoff like this, what i have to do, if i would like to use OTA? |
|
i flashed first this: then i tested normal_ESP8266_1M_SDK22x_191122 what i notice is that with 2018 version of PUYA when i connected to AP Easy_0 and give my credentials after countdown the web page show me the internal IP address that was given to sonoff |
|
@megamarco833: @TD-er : Note: This version was for 4MB Flash, not 1MB. BTW, I didn't try out your two new 1MB test builds. The Sonoff node is in-use and not a good time to take it offline.
|
|
Hmm not sure if Tasmota source code will help here .... ;) |
|
"Introduction" in attached document can be worth to read anyway. Maybe this is the case. |
|
That's a useful paper. As it states the resistor is often included in the micro controller, I wonder if that may be a difference in silicon revisions of the ESPs. I guess adding a 100k (or more) resistor to those boards is a bit hard for most users, so we should look into ways of forcing a RF calibration after the crystal frequency has stabilized. |
|
I looked into several more papers and I don't think we need to wait for the crystal to stabilize for several seconds as it typically takes a number of ticks to get stable. I'm currently making a test build with changes in "autoreconnect" setting (that's something that was different at Tasmota) and setting the WiFi sleep mode after each change of wifi mode (STA/AP/off) |
|
@megamarco833 Can you try this test build: #3473 (comment) |
of course! results: no issue, the AP network "Esp_Easy" is visible, i can connect and after rebooting i can see my sonoff connected at my internal net. i see that web GUI is responding well and fast. only two comments, inside log i see: but practically i not see any issue. second, i think it's a test build so it should be "normal" i see that the plugins included are few, for example switch input pcf8574 is missing.... |
|
If you can try other builds, please be my guest :) |
i'm glad to do this for you!
yes, correct, this device was working only on the 2018 version that i told you, other version had the issue that i described when i open this issue |
|
Great! |
|
as i report i test successfully on sonoff R1: now, do you want that i'll test : ESP_Easy_mega_20210201_normal_alt_wifi_ESP8266_1M.bin or ESP_Easy_mega_20210201_normal_ESP8266_1M.bin ? |
|
if the |
|
i test right now |
|
Great! Well I could not have done it without the endless effort of testers and colaboration in trying to find the many causes :) I will perform some tests with ESP32 and if those turn out to be working I will merge it and in 1 or 2 days make a new nightly build. |
|
Nice job :) |
|
TD-er - thank you for all your commitment. For me, the last 3 weeks have been a real pleasure, with several people working in different ways to solve the same problem. It is a success that we have solved the problem defined for 10 months.
|
Make that close to 3 years already... |
|
Fantastic! This bug has been a hair puller for a long time, so it's great to see there are solutions. @TD-er: My satanic Sonoff Basic R2 demands the Xtal resistor hardware hack to make it work. Is this the final solution or is another firmware patch being created that avoids the mod? Either way I'm good.
|
|
@thomastech For now this is the solution we will go for. For now, just see what the response will be among users and how wide spread "your case" is among users. |
|
Roger that. It's not clear to me how the ESPEasy firmware fix will be implemented going forward. For example, will it be in all builds or will there be special "Sonoff Basic R2" builds that have it? If it's in all builds, does the user need to enable an option that turns it on? -Thomas |
|
The fix as is done now, is done for all, so maybe later I will add a checkbox for it as it may cause a delay and extra power consumption at boot, which is bad for battery operation. |
|
Hi all, Or will it be avaliable in the next official ESPEasy release? Thanks in advance |
|
You can try this test build I made 2 days ago: |
|
@TD-er: Thanks for your quick response. I think I have a major WIFI problem with the Wemos D1 pro (The ones with ceramic antennas): Until then, many thanks for your support and your amazing work around espeasy! |
|
Most of those Wemos boards with a ceramic antenna also have an IPEX connector for an external antenna. Maybe good to check if there is even one placed, or maybe only connected to the IPEX connector? |
|
ESPEasy_ESP82xx_mega-20210114-63-g1b2c1b05.zip Seems to work. |
|
thanks for testing/reporting. |
Add photo with installed resistor pls. |
|
AFAIK, the Sonoff Basic (R2) WiFi issues have been solved some time ago, so I assume this one can be closed. |
Checklist
i have some sonoff basic R2 V1 and i try to flash with new version of espeasy.
i used DOUT
and i succeeed. i see the ESP_Easy net, i connect to it ad i give my password and SSID of internal net.
when ESP reboot it's impossible to ping and open the sonoff on the internal net and ESP_Easy net desappear.
I try to use fw:
ESP_Easy_mega-20200204_normal_ESP8266_1M_VCC
ESP_Easy_mega-20200204_normal_ESP8266_1M
ESP_Easy_mega-20200204_normal_sdk3_ESP8266_1M
all same issue: after connecting ESP_Easy net and give internal SSID and password, is impossible to see on internal net the sonoff and ESP_Easy net desapper
the only way of became it working is using old version of EspEasy where there was PUYAversion:
ESP_Easy_mega-20181023_dev_ESP8266PUYA_1024_VCC.bin
in this case no problems
how it can be solved?
thanks
The text was updated successfully, but these errors were encountered: