Coming from Investigating ESP32 WiFi connectivity behavior, we are investigating and discussing mDNS support for Pycom MicroPython here.
This would be cool and I was thinking about that as well. However, I haven’t been able to see anything at
espressif.local out of the box. May we missed some switch – research+outcome welcome! But I’m also hesitant: While having no proof for that, I am questioning if a superfast cycle like you’ve outlined with
will be able to let mdns or similar technologies enough breath to converge. Everything I can tell you from my experiments is that reaching the device using the regular
espressif hostname through a standard Fritz DNSDHCP is not reliable at all regarding quick turnaround times which I believe are essential for plug & play operations.
However, as soon as the device will be in maintenance mode, we will be happy to use just everything from the comfort zone the ESP32 might be able to offer us. I’ve somewhere read something about someone trying to do some DLNA stuff on the ESP32 – maybe with MicroPython already. Finding this again might give us some direction to follow.
Thanks for your interest, I would be happy to have you with us close to this specific topic (ongoing), especially reviewing the first important iterations of the respective implementation.
It’s been this thread (without any solution fitting our current problem) on the MicroPython forum:
Interesting enough, it’s Daniel Campora who is answering back then. So, maybe we could use that to ask him on the Pycom forum these days.
We want to a) look at MicroPython in general but also currently more important to us b) at the Pycom implementation specifically.
It looks like it has been on someones wishlist already:
First, as I learned
I would like to retract that statement:
hard-coding IPs, or scanning ports sucks
- ESP8266 seems to have it already, right?
Why can’t I just ping this widget?
At least, it’s not a builtin on Pycom’s MicroPython:
make repl >>> import network >>> dir(network) ['__class__', '__name__', 'Bluetooth', 'LTE', 'LoRa', 'Server', 'Sigfox', 'WLAN']
@vinz is already using the MicroDNSSrv  at the Hiverize Datalogger for FiPy . I am wondering if this might also help us for device discovery in any way? Probably not.
 GitHub - jczic/MicroDNSSrv: A micro DNS server for MicroPython to simply respond to A queries on multi-domains with or without wildcards (used on Pycom modules & ESP32)
 FiPy/webserver.py at workshop-20190528 · Hiverize/FiPy · GitHub
Two more things for today:
GitHub - nickovs/slimDNS: Simple, Lightweight Implementation of Multicast DNS
slimDNS: a pure Python mDNS implementation - MicroPython Forum
mDNS capability by goatchurchprime · Pull Request #14 · peterhinch/micropython-mqtt · GitHub
mDNS capability · Issue #11 · peterhinch/micropython-mqtt · GitHub
- See also: Telnet to esp32 · Issue #191 · micropython/micropython-esp32 · GitHub
If I’m not counting wrong here, the issue at [ESP32] DHCP Hostname not working correctly · Issue #4748 · micropython/micropython · GitHub seems to reflect that well.
So, we will be happy to check out mDNS capability by goatchurchprime · Pull Request #14 · peterhinch/micropython-mqtt · GitHub within one of the next iterations on the datalogger code.
Thanks again for bringing this up, @roh.
There have been some news about this within the development of Genuine MicroPython coming from the Roadmap for next release (v1.11 -> v2.0?) · Issue #4821 · micropython/micropython · GitHub.