search

Xylopyrographer / STAC

A Roland Smart Tally Atom Client
Other
3 stars 0 forks source link

mDNS Responder #36

Closed mqshaw closed 1 year ago

mqshaw commented 3 years ago

When setting up the STAC for the first time we have to remember the custom IP Address for the STAC once connected to the WiFi access point. http://192.168.6.14

Instead, what about using an mDNS responder to use a simple, easy to remember hostname for the STAC such as http://stac.local/

Here is an example tutorial that we can use as a baseline. https://techtutorialsx.com/2020/04/17/esp32-mdns-address-resolution/

Xylopyrographer commented 3 years ago

Super idea!

Xylopyrographer commented 3 years ago

With that, might also be able in include OTA firmware updates. Which would be cool.

Here's the sketch I used to test OTA for the STAC. (Had to add the .txt extension to keep GitHub happy 🙄.)

AtomOTAWebUpdater.ino.txt

mqshaw commented 3 years ago

Your example code looks great.

One question, the mDNS example code i uploaded uses an asynchronous Web Server, your example does not. I am assuming that the main benefit of using an Asynchronous web server is its ability to handle multiple connections at a time, which is not something that we want.

I guess the main thing now is to figure out how to make a WiFi Access point, with mDNS and OTA update capability.

Xylopyrographer commented 3 years ago

Thanks. Was kind of anti-climatic when I ran it. It just...worked 😄!

Agree that working through the various libraries and feature set of each will take a bit of noodling. We definitely want only one connection at a time to the STAC.

I've got a few things going on between now and mid next week. I can start to poke around after that.

Something else for you. I'm monitoring the arduino-esp32 Issues on GitHub. A thread came up about the log_X() functions. A person there noted: "you can toggle core logging off/on (IF ITS compiled in !) using:

Serial.setDebugOutput(true | false);"

Haven't tested that to know if they meant "turn off the entire log_X() functionality" or "turn off just the log_X() stuff that originates in the libraries" or if you can turn it off in one part of the code and then turn it back on in another...

Regardless, might be of use if you're running a debug version at service tomorrow.

mqshaw commented 3 years ago

I posted the log from my debug trace on Sunday night here #35.

Xylopyrographer commented 1 year ago

Implemented in version 2.1 👍