-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider support for simpler mDNS configuration #15
Comments
Either #1 or #2 have the advantage of not requiring library upgrades. #2 has the advantage of being more universally discoverable, so I would vote for that (good suggestion, James!) #3 also works if it is just the ESP library being a bit of a subset. Please note that the ESP8266 represents a huge percentage of commercial (as well as maker) devices (eg, tuya.com) so we should make sure it is directly supported somehow. For example, all our forthcoming IoT devices use ESP chipsets to date. |
I did run into several libraries without proper sub-type support (i.e. bonjour), but was able to work around it or find a different library in all cases. In my opinion:
|
Here's the results of my initial survey of the landscape:
I think 2 is the best approach to support since that gets us support for ESP8266 and ESP32. I think it's also an easier target for modifying the WiFi101 library. Based on how most of the examples with the other boards tell the user to print out the IP address on a serial port I think it's reasonable to say that users of these boards should use Add Thing by URL with the IP address they're already getting. |
I'm fine with that. Do we want to support |
I think we should view _http._tcp with a txt record webthing=true to be just an alternate way of specifying the _webthing subtype and keep both supported. |
Agreed. |
At least one embedded mDNS library doesn't support subtypes. We should consider one of three approaches:
webthing=true
Do any of these approaches sound reasonable? Is there a good alternative I haven't covered?
The text was updated successfully, but these errors were encountered: