Replies: 2 comments 1 reply
-
|
@poncz90 Unfortunately I do not have a lot of context to the problem you are describing. I wouldn't expect the access point interface to be any different. I do not know what the "socket" way means, so if you could share some example code that does and does not work it would be helpful. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I have the same issue with an ESP32-WROOM. I managed to get it working with version Microdot <2.0. This is the code import network
ap = network.WLAN(network.AP_IF)
ap.config(essid='OOD') # Nom du réseau WIFI
ap.active(1) # Activation du réseau WIFI
while ap.active() == False:
pass
print('Connection successful')
print(ap.ifconfig())
from microdot import Microdot
app = Microdot()
@app.route('/')
async def index(request):
return 'Hello, world!'
app.run(debug = True, port=80) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have an issue with using microdot when raspberry pico w serves as an access point. When using basic microdot code from microdot introduction I have valid response when my pico is connected to wifi network, but when pico serves as access point it does not respond. Do you have any solution for this? (Pico responses works when I use the "socket" way)
Beta Was this translation helpful? Give feedback.
All reactions