- Wed Jul 19, 2017 4:01 am
#68337
Here's the situation: Got an ESP running as webserver with several modules including OTA (and mDNS) but my ability to find the device via a ".local" url is not consistent.
If the Arduino IDE is open, I can see and program it via wifi and then access the http sever with my browser via the ".local" address. If the IDE is closed I can't after a short time.
If I run the zeroconf browser on my phone, I can see and access it via the ".local" Uri ( on my PC only not on Android phone - i do know why I can't on the phone). If the app is closed closed, i can't.
My PC is running linux mint and i have installed avahi. But when using:
I will only see the "_arduino.tcp" service/device in avahi ONLY if the IDE is open or the zeroconf browser is open.
Have I missed something about how mDNS should work? Does some deamon need to be running somewhere in the network (my router or on my computer) querying the network for mDNS services?
Is it an anounce type topology or query type topology?
Please can someone she'd some light.
If the Arduino IDE is open, I can see and program it via wifi and then access the http sever with my browser via the ".local" address. If the IDE is closed I can't after a short time.
If I run the zeroconf browser on my phone, I can see and access it via the ".local" Uri ( on my PC only not on Android phone - i do know why I can't on the phone). If the app is closed closed, i can't.
My PC is running linux mint and i have installed avahi. But when using:
Code: Select all
avahi-browse -atI will only see the "_arduino.tcp" service/device in avahi ONLY if the IDE is open or the zeroconf browser is open.
Have I missed something about how mDNS should work? Does some deamon need to be running somewhere in the network (my router or on my computer) querying the network for mDNS services?
Is it an anounce type topology or query type topology?
Please can someone she'd some light.
