@jcaron unfortunately, there is any method with the stdin and I haven't found any way to interact directly with the telnet server. My previous implementation used the UART, but then I realized that I was able to read from Telnet, but no way to type anything. Also, the telnet connection was quite slow and unreliable for some reason (time out when login/password). With stdin it works much better, but not typing anything will block the application forever.

@livius Thank you i will try immediately

Thanks. If I set os.dupterm(None), I get a telnet login on WLAN which works OK ('Login succeeded!), but no REPL '>>>' on WLAN (or UART0) as might be expected. micropython.org indicates dupterm requires a stream_object. I have tried the obvious wlan and server instances without success. What is the relevant object here?

@misterlisty Do you want to implement that in Python or C? For python, you can use for instance sys.stdin.read(1) to get single characters from whatever is sent to the device.

thanks, must say the documentation needs improvement.

@robert-hh Thanks for the snippet. I can confirm that it seems to be a problem with my windows machine. I can now connect to the LoPy in STA mode via telnet and ftp (with my linux machine). Thanks for all the suggestions!

@lebucur The Lopy warms up a little bit when running. Can you estimate how worm it get's. It's normal that it gets a little bit warmer than environmental temperature, so it feels warm, but you should still be able to touch it without without any pain. Is it the deviec in total or a specific component?

It happens when it's connected to my router. I tried first with a static IP adress but I read there are some problems with that (because of DNS), so I use address reservation for DHCP clients in order to have it connected to a specific IP address.