-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Web Workflow: no circuitpython.local (Pico W, 9.0.1) #9124
Comments
I've seen similar behavior on |
I think this is because you are initializing the mdns.Server yourself. Right now, circuitpython.local is only added if the workflow starts the server: https://github.com/adafruit/circuitpython/blob/main/ports/raspberrypi/common-hal/mdns/Server.c#L70-L76 |
I think this is the web workflow case. My understanding is that (Running the code above I don't think will show its own device, but running on a separate device should catch any MDNS Maybe @studiostephe can chime in on their original observations from Discord. From my own observations, it can be difficult to connect to |
My observations match anecdata's above: a blank code.py, Web Workflow has started because its accessible via cpy-xxxxxx, but circuitpython.local never loads |
It is totally possible that MDNS on pico w isn't as reliable as ESP. What OS are you running and what browser? (To know what is doing the mdns lookup for the browser.) |
This is Safari on MacOS |
To remove the browser from the equation: Running web workflow on:
A separate ESP32-S3 scanning MDNS in CircuitPython (code above) continually shows:
For comparison, later (to get past the 2-minute? MDNS cache) running web workflow on:
(the redirect comes after a couple of seconds, the final page comes after a couple more seconds) |
(Some previous observations on MDNS / raspberrypi here.) |
@anecdata I've retested with With an empty CIRCUITPY_WIFI_SSID = "xxxxxxxxxx"
CIRCUITPY_WIFI_PASSWORD = "xxxxxxxxxx"
CIRCUITPY_WEB_API_PASSWORD= "jk" I can access the web workflow through my browser (Firefox on Debian Bookworm) using either
It appears that #10027 has resolved this issue. Closing. |
CircuitPython version
Code/REPL
Behavior
code.py output:
Starting mDNS server...
Finding mDNS hosts from 10.0.1.55...
circuitpython.local
socket_resolve_host() returned -2
OSError: (-2, 'Name or service not known')
Description
The Pico W joins the network without issue, and can be accessed via IP or individual hostname (cpy-xxxxxx.local), but not via circuitpython.local
Access via circuitpython.local is important for when the device's REPL is not physically accessible via USB (device installed somewhere deep), and the IP is not known or knowable in advance (not my network)
Additional information
No response
The text was updated successfully, but these errors were encountered: