-
Notifications
You must be signed in to change notification settings - Fork 639
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
No Wifi connection to AI-Thinker AI Light after updating flash to 1.90 using web interface #190
Comments
AP mode is not working either? The only reason for this is that something went terribly wrong with the update... Without wireless access to the bulb I'm afraid the only way is wired... |
Original comment by BrentK (Bitbucket: brentk01, GitHub: Unknown): AP mode does not come up. I tried flashing a second bulb in the same manner with the same result - not available on wifi or as AP |
It could be the firmware being stuck with some other task. Latest version had a problem with MQTT that might cause an endless connnect-disconnect loop, meanwhile the web interface becomes irresponsive... |
Original comment by BrentK (Bitbucket: brentk01, GitHub: Unknown): The lights are configured to get a static IP address based on their MAC address from the DHCP server on my DD-WRT router. I checked in the router and it no longer sees them come up as a DHCP client after I delete previously existing the DHCP lease and it doesn't show up as an active client in the router. Also unable to ping the address. Not currently home so unable to try any other tools, but it definitely looks like it is not starting up properly after being flashed. |
Original comment by BrentK (Bitbucket: brentk01, GitHub: Unknown): Just tried scanning with Fing as suggested - Light not found and not available as AP. So definitely totally unresponsive after flash. |
Original comment by Daniel Silva (Bitbucket: dreamfalcon, GitHub: dreamfalcon): Same problem here after upgrading from 1.8.3 to 1.9.1 using the web interface. |
Try erasing flash and reflash using DOUT flash mode and 8Mbit flash size. |
Original comment by Daniel Silva (Bitbucket: dreamfalcon, GitHub: dreamfalcon): How to erase? I flashed all the files with 8Mbit and 32Mbit in DIO. |
Original comment by Daniel Silva (Bitbucket: dreamfalcon, GitHub: dreamfalcon): Tried DOUT and 8Mbit. but same problem. |
Since you have it wired, can you access the debug log via serial and copy it here (open a serial connection at 115200 baud)? |
Original comment by Daniel Silva (Bitbucket: dreamfalcon, GitHub: dreamfalcon): Apparently does not disconnect, but tried opening the page and never loads.
|
Original comment by Daniel Silva (Bitbucket: dreamfalcon, GitHub: dreamfalcon): And a reboot after some time:
|
I can't see anything specially relevant in the log. Tonight I will test it with one of the AiLights I have (both running 1.9.1 without problems, thou). If you don't mind: don't remove the wires, just in case I need a tester :) |
Original comment by Daniel Silva (Bitbucket: dreamfalcon, GitHub: dreamfalcon): No problem. |
Ok, I managed to reproduce the issue with one of the bulbs. The bulb crashes on boot in the ticker callback created in the lightUpdate method of the light.ino module. Ultimately this callback performed a debugSend_P where another bug was executing the UDP code when it shouldn't... I've fixed both problems by 1) using a flag on the Embedis save callback and checking whether I should commit the changes in the module loop and 2) fixing the compile checks in the debug.ino module. @dreamfalcon do you have the chance to test the code using the latests changes in the dev branch? Hopefully you light bulb will be back to life. Unfortunately, @brentk01 , the chances to recover your bulb without wiring it are very low... Next thing I'll do is to add some boot check to go into a save mode (TBD) if the device enters such a tight crash loop... (see #196) |
Original comment by Daniel Silva (Bitbucket: dreamfalcon, GitHub: dreamfalcon): Appears to be working, the webpage opens. |
Original comment by BrentK (Bitbucket: brentk01, GitHub: Unknown): I'll have a go at reflashing the light without the broken pad when I get home from work tonight. |
Original comment by BrentK (Bitbucket: brentk01, GitHub: Unknown): I'm not sure if I'm doing something wrong - but I'm unable to compile the dev branch code using Arduino 1.8.3. I get the error listed below:
|
Original comment by BrentK (Bitbucket: brentk01, GitHub: Unknown): Just tried to compile the master branch and I get the same error. Version 1.8.3 which I was using previously compiles fine. |
Original comment by Daniel Silva (Bitbucket: dreamfalcon, GitHub: dreamfalcon): The bin file |
Original comment by Daniel Silva (Bitbucket: dreamfalcon, GitHub: dreamfalcon): |
You have not updated the my9291 library to version 2.0.0, the API has changed. |
I'm closing this ticket. Version 1.9.2 is out with this fix an a couple off addons I hope will be useful for future issues like this one:
I hope that this two together could help in an issue like this one. |
Originally reported by: BrentK (Bitbucket: brentk01, GitHub: Unknown)
I just updated one of my AI-Thinker AI Lights to version 1.90 (from 1.83) using the built in web interface - updated to the latest .bin file from downloads.
The AI light no longer connects to my Wifi and does not go into AP mode so I am unable to access it at all.
Should my Wifi credentials still be saved after a flash?
Unfortunately, on this particular light, I broke the pad off the TX pin so cannot reflash via Arduino.
Is there any way out of this situation other than trying to solder a wire directly to the TX pin on the ESP8266 chip?
The text was updated successfully, but these errors were encountered: