No stable WIFI connection w/ FW 7.0.0 & 6.6.0 #507
Comments
|
According to sources it will not send anything after " -> Connection restored!", just will go to sleep. Does it make any sense? |
|
@pppedrillo, can confirm, saw exactly this in the code and thought about changing the behavior such that after a successful "rescue" the data are sent.
Changing the code in that manner would solve the issue of not uploading data. But not the issue of loosing wifi connection. |
peterschrott
changed the title
What the wemos module do you have? can it be dodgy? I have 7.0 on 2 of mine ispindels and they send data to ubidots pretty well. |
I have ordered this d1 mini: https://www.reichelt.de/d1-mini-esp8266-v3-0-d1-mini-p253978.html. Haven't noticed anything wrong so far. As said, with fw v6.5.1 it all works just fine. Wifi seems awake and its sends out data right away. Saving WIFI settings w/ 6.5.1: On wakeup w/ 6.5.1: |
|
Oke, after half almost a day of debugging I am even more confused. By adding some debug infos in the source code of 7.0.0 I found out, that the wifi status ( So I wanted to add the same debug infos to v 6.5.1 to, because the pre-compiled version worked just fine for me. I checked out the source by the tag So I tried all previous version pre-compiled and self-compiled (macOS 11.2.3): Whenever I compile the bin myself this wifi connection issue pops up, regardless the version. The issue also appears from pre-compiled 6.6.0. I have a vague hypothesis now: I see, that from version 6.6.0 the compilation is done with GitHub Actions. I assume before it was done on @universam1 machine. So, maybe there was some older version of a dependencies laying around on his machine which was then bundled. With the GH Actions its always a clean setup, as it was on my machine now. 🤷 Side note: version <= 6.5.1 did not compile on my machine: Here I am asking myself, how fw releases could have been built. |
|
@peterschrott I have espesssif 8266 v.2.6.2 (not the latest 3.0.0) if it matters Have you tried a clean build (I believe so, but just in case) ? |
peterschrott
changed the title
|
UPD all good with espesssif 8266 v 3.0.0 (the latest) as well |
|
@pppedrillo, yes I also did a clean build, deleting the mentioned directories. Also global pio caches. I checkout the tag 6.5.1 ( I am not sure what espesssif is. The version of the d1 mini? Is it relevant for compiling? |
|
@peterschrott espesssif 8266 is a platform which is using for build ispindel image. |
|
@pppedrillo oke, as I found out, it was broken for older versions too. Thats why I got confused and was wondering how those old releases could have been built. Espressif is nothing I need to worry about when I build the fw on my machine? The way of building I described above is just fine, or does it need some more config or parameters? Still, I can fix the compilation error for the old versions but still get this weird wifi behavior with my builds, the same as with pre-builds >= 6.6.0. I made a clean build of the current master with some additional logging regarding wifi status in I still don't think its about my d1 mini, as the old precompiled versions work find. Software... 😪 |
Right, very confusing. May be it was guarded out by preprocessor with #if / #ifdef or such....
Here you are. It is indeed sending data only once on start.
|
|
I have the same problem, Ispindel sends the data only the first time, and later nothing. That problem is from V6.6.0 |
|
@pppedrillo thanks for the logs. This is whats happens on my iSpindel. I have done a clean-clean build by using Vagrant with a clean Ubuntu 20.04 LTS, fresh checkout of the source, and fresh install of platformio (quite similar, what on Github Actions happens). @pppedrillo can you actually confirm, that you don't see this issue (data are uploaded) with the pre-build 7.0.0? |
|
@peterschrott I don't see this issue even with 7.0.0 built myself, it uploads data to Ubidots pretty well. No such issues like with your image. Here is my log for couple of wakeups.
Thus all of this sounds like you have something in your setup which produces "not-so-good" image. You mentioned Ubuntu, have you tried to build on Windows? May be it is tolchain tricks eg linux VS windows.... I am using Windows box for all these exercises and all looks well so far. |
|
@pppedrillo thanks for the info & the logs. Locally I work with macOS. For the clean build I used Ubuntu to be analog with the Github Actions. Now I build the firmware on Windows 10 (quite clean, fresh python and such). Unfortunately I encounter the same issues with my builds as before. In locally build v 6.5.1 and in v 7.0.0 I get that wifi issue on each wakeup. So I still don't have a trace why the pre-builds > 6.5.1 do not properly work on my iSpindel. @zfeges reported the same issue. Maybe @pppedrillo you could provide me you locally build v 7.0.0 (and if its not too much to ask also 6.5.1). Thanks! |
|
And I'm not the only one who has the same problem ... I know a dozen other people with the same problem. |
@pppedrillo, can't open: 403. Sorry. |
|
https://www.dosyaupload.com/8e8j |
And it started only after update to 7.0.0? |
|
Yes, after update and adding again configuration data... ispindel send data only first time. If I restart ispindel - nothing... when I go in management mode and exit... ispindel again send first time and after that 0... |
|
@zfeges Have you tried to wipe wemos before flashing the image? eg
|
|
@zfeges didn't you say, that pre-build version 6.6.0 also did not work out for you? Maybe you can "confirm" my findings below and try the build of v7.0.0 from @pppedrillo? @pppedrillo thanks a lot! You could always use https://wetransfer.com/ – which I used sending you my bin. No mail needed you can just create a link. I have have tried your builds, and surprise: Both of them work like charm. To sum it up: And it must be about the build itself or the build environment. Especially since pre-build bins >= 6.6.0 are using Github Actions. This is the only significant change I can see in this repo. Unfortunately I am not deep enough in building firmware and the build tools. E.g. how about dependencies are handled. I also had the python or platformio version in mind. I am using Python 3.9.5 and pio 5.1.1. But it got even more interesting: The "error" is different now – it says Initially i flashed v 6.5.1 and then upgraded to 7.0.0 without wiping. Maybe I did not run into that My conclusion so far: The |
|
@pppedrillo found it! 🎉 The persistence of wifi has changed in It recommends to always use After adding this in my Side question: Where do I define the version of that dependency? Is it somehow tied up with platformio? |
@peterschrott You can just delete .pio folder in your project folder, it will re-download all the dep libs.
This error and the rest of mess (d1 was just not connected anymore – but still had the SSID somewhere– after the sleep) usually happens if you skip N1 "flash blank 1MB image x4 times (from 0x0 , 0x100000, 0x200000 and 0x300000 ) (I assume you have 4MB module)" and start directly from N2 (internal:// nodemcu, blank) https://arduino-esp8266.readthedocs.io/en/latest/esp8266wifi/generic-class.html#persistent Please note, what if you have 4MB module, the last file flashing (from 0x300000) will end up with error. This is ok.
In case you don't have/can not generate blank file yourself, I attached a good one.
Good catch, Funny enough, I have just wifi.begin and it works for me without problem. I have seen "ERROR no Wifi credentials", but it was gone after full wiping as described above.
Yes. Should be in platformio.ini in root folder of your project. lib_deps = |
|
This time I was doing the wipe before flashing. So the "real" issue came out. I am using
I was more talking about, that on every
|
I did not try on a blank wemos, it is my friend and he had a problem that his wemos did not save his data after entering. |
|
PR (#513) is merged into master. And will be available in the next fw release. -> Therefore closing this issue. |
|
@peterschrott For what it worth, I just noticed the logs you posted here have token for your API as well as ssid and psk password to your wifi network. Just in case you may want to remove it. |
|
@pppedrillo thanks, was a late night post. I edited the post, its still visible in the history, i ll revoke my ubidots token. |
I'm submitting a ...
Did you follow the general troubleshooting steps first:
Report
After updating the firmware of my iSpindel from 6.5.1 to 7.0.0 the d1 mini does not connect to my WIFI properly.
On the initial configuration of the wifi it seems to connect (see logs below).
On the wakups for reporting to ubidots somehow the connection is lost and it's restored. But the data are not sent do ubidots and on the next cycle it's restoring the connection again.
I flashed the old 6.5.1 version again and wifi worked like charm. I also changed SSID & PW of my network -> no fix here.
Console Logs
On saving WIFI preferences in web ui:
When waking up to report to ubidots:
Steps to Reproduce (for bugs)
Your Environment
The text was updated successfully, but these errors were encountered: