Let me know if there's any logs or other diagnostic data I can provide on this, @gopher.ny
I'd really like to wrap up a few things on my new Shelly Device Manager app, but it relies on mDNS to discover new Shelly devices quickly. I have a work-around where it just fires off a sequential subnet scan for everything on /24 looking for devices that respond to the /shelly endpoint, but that's slow since anything more than 1 address per second causes Hubitat to complain about too many inflight async HTTP request.
I'm wondering if maybe some sort of internal app or the built-in Shelly integration is somehow interfering with getting mDNS for _http._tcp properly.
