-
Notifications
You must be signed in to change notification settings - Fork 41
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
M5Stack PoESP32 connected via ethernet stays connected to WiFi #631
Comments
Try to set the device to GL-S10. |
Same problem :(
|
I set the configuration as requested: Stil the device is connecting over Wi-Fi: Any clue what the fix has been in this issue?: #152 |
Hi, I think that was bug. It's strange, it should just work. I have one of those my own, just need to get it that sucker to flash ... a bit annoying it doesn't come with USB. P.S.: It'll have to wait a bit, need to order proper jumper cables first. |
No worries, thanks for looking into this! |
PROBLEM DESCRIPTION
A clear and concise description of what the problem is.
The device keeps connecting via WiFi, even though I've configured the device to make use of the ethernet interface.
This is the same problem as mentioned here: #152
But in that case a different esp32 is used (but same brand though)
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
TO REPRODUCE
Steps to reproduce the behavior:
Flashed the ESP, configured via WIFI and changed the network config to 'M5STACK PoESP32 Unit'
Afterwards I'm able to boot the device via Power-over-Ethernet, but the device keeps connecting over wifi.
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
I expected the device to be connected over the ethernet interface.
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
I tried to disable DHCP and add a static network config, but this didn't solve the issue.
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: