-
Notifications
You must be signed in to change notification settings - Fork 16
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
Welcome to ESP-Parking-Assistant Discussions! #32
Comments
Is that a v4 of the D1-Mini with a USB-C connection instead of a microUSB connection? From the photo, it looks as if it is. There is known issue with the board and I'm not sure if/when I'll be able to diagnose further and repair. See issue #31. In the interim, I recommend a D1 mini that uses a microUSB connection. |
Thank you for your quick response, the chip has a micro usb connector but I bought it from Amazon in Canada so not sure of version number. Maybe I’ll try to get on from US Amazon. Thanks for your trouble I’ll carry on and report back. |
Sorry if I assumed it had the USB-C port. I've just never seen a D1 Mini like that (square corners on the PCB vs. rounded or angled). This doesn't necessarily mean anything is "wrong" with your D1 Mini, but I've run into boards by some sellers that use lower cost components on the board (e.g. different voltage regulator, different USB-to-Serial chip, etc.). Occasionally, I'll get a hold of one that doesn't want to play nice... I even had a batch that wouldn't even flash. If you are going to try ordering new boards, I'd try a completely different seller and see if you can find one that more closely matches the one above. I know you said you were in Canada, but for comparison, here's the link to the D1 Minis I normally purchase from U.S. Amazon if it helps out for comparison purposes: Wemos D1 Mini And please let me know what you do find so I can update the info here and in the general documentation if needed. |
Just ordered from Amazon us will report back when received |
Just received my new d1 mini and rewired it into circuit and nothing has changed, " AP not found." Any further thoughts or do i have a router problem? |
I'm at a bit of a loss. There was an issue reported quite some time ago that was related to the WiFi/onboarding library that I'm using. Apparently, it has some issues with special characters in the SSID and password. Now, it looks like you only have an underscore and a dash, so I don't think that's an issue. But if you have special characters in the password, that could also be the cause. But you can easily verify if this is the case if you have the ability to spin up a secondary SSID on your network. If you can at least temporarily create a simple SSID and password that only consists of letters and numbers, then you can try joining the controller to this test SSID. If it joins, then we know its an issue with something in the SSID and/or password. FYI... I'm in the slow process of going back an updating many of these old projects, replacing the external onboarding library with one that I developed myself (and doesn't have the SSID/PW issues). Along the way, I'm making a number of other standard improvements, updating the libraries and boards to the latest versions, etc. This being one of my more popular projects, it is high on the list. But I can't say for sure when I'll get to it. If are able to determine that it is an issue with your SSID/PW, then the options are to use a different SSID, change and remove special characters from your existing WiFi or simply wait until I get around to an updated version. But if you are able to try joining a different WiFi network without any special characters in either the SSID or password, please let me know what you find. |
I have wled on my network and it connects fine, also the password for this
project is only lowercase letters and 4 numbers. I'll keep trying
different ideas and if I come up with any thoughts I will report back to
you .
thanks again
…On Tue, Jan 28, 2025 at 2:58 PM Resinchem ***@***.***> wrote:
I'm at a bit of a loss. There was an issue reported quite some time ago
that was related to the WiFi/onboarding library that I'm using. Apparently,
it has some issues with special characters in the SSID and password. Now,
it looks like you only have an underscore and a dash, so I don't *think*
that's an issue. But if you have special characters in the password, that
could also be the cause. But you can easily verify if this is the case if
you have the ability to spin up a secondary SSID on your network. If you
can at least temporarily create a simple SSID and password that only
consists of letters and numbers, then you can try joining the controller to
this test SSID. If it joins, then we know its an issue with something in
the SSID and/or password.
FYI... I'm in the slow process of going back an updating many of these old
projects, replacing the external onboarding library with one that I
developed myself (and doesn't have the SSID/PW issues). Along the way, I'm
making a number of other standard improvements, updating the libraries and
boards to the latest versions, etc. This being one of my more popular
projects, it is high on the list. But I can't say for sure when I'll get to
it. If are able to determine that it is an issue with your SSID/PW, then
the options are to use a different SSID, change and remove special
characters from your existing WiFi or simply wait until I get around to an
updated version.
But if you are able to try joining a different WiFi network without any
special characters in either the SSID or password, please let me know what
you find.
—
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BOXC4PHGITRLEW3E3GR6RP32NADR5AVCNFSM6AAAAABVYRJWRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRQGIZDSNBRGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I appreciate it. WLED is definitely using a different onboarding process (assuming that is the cause here). But I'm going to go ahead and close this issue for now as I know that there are a lot of successful installs based on what I've heard from others. So I do think it is something particular to your network/hardware/situation. If we eventually determine that it is truly a problem with the firmware, I'll reopen this issue or start a new one. |
Ok, thanks for the update.
…On Tue, Jan 28, 2025 at 6:28 PM Resinchem ***@***.***> wrote:
I appreciate it. WLED is definitely using a different onboarding process
(assuming that is the cause here). But I'm going to go ahead and close this
issue for now as I know that there are a lot of successful installs based
on what I've heard from others. So I do think it is something particular to
your network/hardware/situation. If we eventually determine that it is
truly a problem with the firmware, I'll reopen this issue or start a new
one.
—
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BOXC4PBB4VLPZNS6GGRPF4T2NA4EXAVCNFSM6AAAAABVYRJWRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRQGQ4TIOJSGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Discussed in #18
Originally posted by Resinchem May 14, 2023
Welcome!
Please use discussions for the following:
help since may be out of this discussion, but if you could direct me to areas or ideas as how I could fix this I would appreciate the help. Used d1 mini, ws2812b leds, logic level shifter, tf mini-s. Sending three pics if they help.
Thanks
Barry Jefferies
The text was updated successfully, but these errors were encountered: