Skip to content
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

ESP8266/D1 Mini Wont Connect to WiFi, Resets to Default Settings #192

Closed
benlongjohn opened this issue Nov 13, 2018 · 44 comments
Closed

ESP8266/D1 Mini Wont Connect to WiFi, Resets to Default Settings #192

benlongjohn opened this issue Nov 13, 2018 · 44 comments

Comments

@benlongjohn
Copy link

After the release of 9.0, the program itself is broken. I am unable to connect to any WiFi network after scanning for a network and replacing the hardware credentials. After a "Save & Reboot", the module does not connect to the wifi network specified, but instead stays on the same ESP network and reverts all changed settings back to default. How can a brand new update be released with his kind of major bug?

@omersiar
Copy link
Collaborator

I can not reproduce this issue. Did you follow update procedure exactly?

@benlongjohn
Copy link
Author

The reader is causing me too many problems. Ill order a new one and retry. What is the best/most compatible reader to use with his software?

@omersiar
Copy link
Collaborator

MFRC522 or Wiegand based readers are best option for now.

@Nelson-Oliveira
Copy link

I dont know why, but im trying to flash on esp8266 nodemcu lua + RC522 since sunday, and im not having any luck... it has weird behavior.. when i flash 0.8.3 it shows as version 0.8.2... and i was having a hard time saving changes, it sometimes kept broadcasting insted of acting as a client, after some reboots and some re flashes it joined the network as client, i was able to save the other settings added a card but the mqtt wasnt working for some reason... today with the 0.9 release i thought it would be stable. i flashed 0.9 and i setup all settigngs hiting save in each tab and when all settings saved i hit the yellow area to save and reboot. It doesnt act as client. the only settings i can get saved are the client network settings, and it still acts as AP. and the hardware settings. it doesnt connect to the network and settings act weird. it always keeps the same admin password.
Am i missing something?? i also tried flashing on another nodemcu and acts the same.

@lb-ha
Copy link

lb-ha commented Nov 13, 2018

After upgrading to 0.9 following exactly the procedure you suggested to, i've the same issue exposed by benlongjohn. No wifi client connection (only AP mode) and no way to customize parameters (always reverted to default after restart). I've tried to completely delete flash memory of nodemcu and flash firmware again whit no success. Do you have any solutions? Thanks for your great work.

@teriall
Copy link

teriall commented Nov 14, 2018

Confirm, 0.9.0 can't save settings.
log from terminal:
[ INFO ] ESP RFID v0.9
Flash real id: 00164020
Flash real size: 4194304

Flash ide size: 4194304
Flash ide speed: 40000000
Flash ide mode: DIO
Flash Chip configuration ok.

[ WARN ] Failed to open config file
[ INFO ] ESP-RFID is running in Fallback AP Mode

@omersiar
Copy link
Collaborator

Sorry for the inconvenience, i do not have any suggestion other than using the version 0.8.1.

https://github.com/esprfid/esp-rfid/releases/tag/0.8.1

I am rolling back the releases after 0.8.1

@egebaek
Copy link

egebaek commented Nov 15, 2018

The same on Nodemcu cannot keep settings

@omersiar
Copy link
Collaborator

Can someone please test this enclosed firmware ? (Do not forget to unpack the .zip file and flash debug.bin)
debug.zip

@papaloewe
Copy link

Ver. 0.9.1 does not work an Wemos D1 mini board. Wifi settings are not saved.

@danicasti
Copy link

Ver. 0.9.1 does not work an NodeMcu V3 board. Wifi settings are not saved. :(

@tipsworld
Copy link

what vision of NodeMcu firmware works

@GryKyo
Copy link

GryKyo commented Dec 2, 2018

So I followed the steps in post 3 of #201 and get a very slick looking v9.0 but can not save SSID/PSK creds to a Wemos D1 mini. Same issue...

@ReneHezser
Copy link

Can someone please test this enclosed firmware ? (Do not forget to unpack the .zip file and flash debug.bin)
debug.zip

I tried that version on my NodeMCU, but it didn't work either :-( On every boot it just shows the same as in post #192 (comment)

@tipsworld
Copy link

tipsworld commented Dec 3, 2018 via email

@PathEtechManagement
Copy link

Can also confirm no wifi client with D1 mini also with debug.bin firmware.

@omersiar
Copy link
Collaborator

omersiar commented Dec 4, 2018

@kessack The only version currently supported is v0.8.1, sorry for the confusing releases lastly. I will remove confusing release now.

@Pako2
Copy link
Contributor

Pako2 commented Dec 26, 2018

I have not had the problem yet, everything worked for me normally.
But now, I've also stumbled upon it.
So I studied it, and I probably found the cause.
The problem is that the size of config.json has increased and the websocket is unable to transfer it.
This can even happen with previous versions as well. when multiple strings (such as passwords and the like) that have a slightly longer length are encountered.
I think the easiest solution will be to use POST request for config.json transfer, instead of websocket.
I think I could send a pull request.

@Pako2
Copy link
Contributor

Pako2 commented Dec 30, 2018

I released the experimental version of 0.9.3.
You can try it.

Pako

@ReneHezser
Copy link

ReneHezser commented Dec 30, 2018

@Pako2 your version 0.9.3 is working for me regarding the settings being stored.
I've configured RDM6300 as reader and connected my UART output pin to D4 on my NodeMCU (should be GPIO2). The onboard LED flashes on the Reader and the NodeMCU when a tag is detected. But no interaction in the UI :-( Could you give me a hint on how to connect a UART reader?
Update: I found the solution. Just connect the TX pin of the reader to the RX pin of the NodeMCU as you've mentioned in #181 (comment) . Thank you!

@Pako2
Copy link
Contributor

Pako2 commented Dec 31, 2018

@ReneHezser
Thank you for your test and your positive message.
I'm glad I could help.
BTW: A much better sensitivity than the RDM6300 has the Gwiot 7941E.
I recommend to try!

@ReneHezser
Copy link

ReneHezser commented Dec 31, 2018

Actually I have this one and am using a voltage regulator to connect it. Its range is more than 10cm.

@GryKyo
Copy link

GryKyo commented Dec 31, 2018

@Pako2 I had a brief attempt with your forked version yesterday. I am not very experienced but had an error (missing library) when I teied to build this using Platformio so then tried flash_write your generic.bin using esptool. No sign of serial output or wifi from my WemosD1?
Anything obvious wrong? Thx, Garry

Edit: Generic did flash OK, my bad!
Thanks for the working version...

@Pako2
Copy link
Contributor

Pako2 commented Dec 31, 2018

Here is version 0.9.4.

@tipsworld
Copy link

tipsworld commented Dec 31, 2018 via email

@omersiar
Copy link
Collaborator

Wow, thank you @Pako2.

@Rudi1947
Copy link

Rudi1947 commented Jan 8, 2019

@Pako2 👍 Thanks a lot! It is now working for me as well. Tomorrow I'll try to connect an MFRC522 reader. Has anybody experience on how long the connection cable between reader and node MCU can be made? In my case I need about 1.5 meters. By the way: the units for the relay toggle displayed at the pop up field should be milliseconds (not microseconds). This was a bit confusing for me.
Thanks to all contributors, great work!

Edit: I connected an MFRC522 reader today and it worked like a charm. I use a D1 mini.
Edit 2: Cable between Reader and Wemos D1 mini worked with a 2 m cable. Also, I could power the reader with the 3.3 V of the D1 mini.

@bib2
Copy link

bib2 commented Jan 9, 2019

I use the official hardware board from nardev with 0.9.1 installed. Can i simply flash your modded version with the esp-rfid webinterface onto my device? Will it keep all my settings?

@Pako2
Copy link
Contributor

Pako2 commented Jan 9, 2019

I have zero experience with official HW, so I do not have the courage to answer your question.
I think only the author of the project (or another user of the official HW) can provide explanations or experience.

@omersiar
Copy link
Collaborator

omersiar commented Jan 9, 2019

You can use both firmwares, only difference is that you have to manually configure hardware options for generic firmware.

@bib2
Copy link

bib2 commented Jan 9, 2019

I was on 0.8.2 formerly, not on 0.9.2...

I made a backup inside the webinterface, then i made an update with the webinterface-update-button to the modded 0.9.5 from Pako2. After that, i connected to the esp-wifi, restored my backup-file and my esp-rfid was back online again.

Is there a changelog, where i can see the changes since 0.8.1? The bug of the new versions started with 0.8.2 is fixed int his modded release? So no need to wait for a new official release or downgrade to 0.8.1?

@omersiar
Copy link
Collaborator

omersiar commented Jan 9, 2019

@omersiar
Copy link
Collaborator

Closing it for now.

@bburkett52
Copy link

I was having exactly the same problem where settings were not being saved. I discovered that my issue was caused by using the incorrect flash size in my flash utility. My device was 4M and utility was set for 1M.
All good now!

@JuculianD
Copy link

Hi, I can't get my Gwiot reader to work.
@Pako2 do you have some information about setting and firmware for me?

@Pako2
Copy link
Contributor

Pako2 commented Jul 2, 2019

@JuculianD:
What version of esp-rfid are you using?
What version of Gwiot reader do you use?
It is serial or wiegand?
How is it connected (GPIO numbers)?
If it is serial, it must be wired as follows (like RDM6300):
https://github.com/esprfid/esp-rfid/tree/dev#pin-layout

@JuculianD
Copy link

Hello, it is not the Wiegand Version, but the UART version!
I was using the latest version, pre release.

I connected it to RX.

@Pako2
Copy link
Contributor

Pako2 commented Jul 3, 2019

I'm sorry, but I don't know how I can help.
Everything seems to be fine.
Do you have an RDM6300 reader selected in the web interface?

@JuculianD
Copy link

Yes, I do... Can you maybe tell me exactly which version of esp RFID you used which worked? I have some other Gwiot readers here and will try to be sure it's no hardware defect.

@Pako2
Copy link
Contributor

Pako2 commented Jul 4, 2019

I use version 1.0.3.
I have no reason to change it, it works as I need it.
When a RFID tag is scanned by a reader, the red LED flashes once on the reader (even if it is an unknown tag). Does it work the same for you?

@JuculianD
Copy link

Yes, it blinks once, but I do not get any popup or information in the Webinterface

@Pako2
Copy link
Contributor

Pako2 commented Jul 8, 2019

What board are you using (eg NodeMCU, bare ESP12 module etc.)?
If it is a board equipped with a USB chip (eg NodeMCU), how do you power it? If you use USB power, it may be a problem that the USB chip blocks RX.

@JuculianD
Copy link

Oh, very good idea. I will give it a try. It is a wemos d1 Mini and I powered it with USB.

@JuculianD
Copy link

Hi Palo, I connected it with a external power supply and without USB, but it again did not work.

Wemos d1 Mini with the TX pin connected on RX on the wemos.

Gwiot 7941E V4.1 Serial...

Can someone please help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests