Idea: When in install by Network - Attempt to resolve target on network BEFORE compilation starts.

[nathan-curtis]

Describe the enhancement

Have you ever put together a complicated sketch - and deployed it to a device and found after a loooong compile it fails because the builder couldn't resolve mDNS?

Use cases

All Network Deployments

Visual examples

No visual necessary - infrastructure layer - Resolve mDNS as a preflight check to the compiler IF in network deploy mode and fail if resolution fails.

Anything else?

All problems are name resolution problems until proven otherwise. That build sure takes a long time if we don't need it because we cant write to the target. We don't attempt to connect to write to a bad com port - why do we wait until the write to check?

[nagyrobi]

It actually does some check in advance from what I could see.

[nathan-curtis]

I just watched it fail twice in a row with a custom voice build on 2025.10.0, Evidence says otherwise, Im trying to figure out if its ACTUALLY failing mDNS or a bogus message now... I kicked the specific device off the network and made it reregister itself then edited the build file to verify that the hostname matched what the device thought it was registering in Unifi... (It did) Waiting on third recompile... Will let you know -VPEs are long builds.

[nathan-curtis]

It is uploading but I noted an IMMEDIATE difference in the Info screen. Previously it was failing out could not find THIS time it connected via IPV6 Addr. So, on my end it WAS obviously some kind of horked mDNS issue. But I'm at a loss to tell you why when my mDNS was busted it compiled then failed and when I fixed it the third time it compiled then succeeded - connecting to the devices ipv6 address.