in order to support deploying multiple ECLSS nodes on the same LAN, it would be nice to support some mechanism for assigning names to an individual node. in particular, this should do the following:
[ ] change the device's soft-AP SSID, so that you don't have a bunch of configuration access points which are all named "ECLSS"
[ ] change the device's mDNS domain (maybe a subdomain, so you can have e.g. bedroom.eclss.local and office.eclss.local and so on?)
[ ] add the name as a metrics label for prometheus
not totally sure how this ought to be configured. you could maybe set a name in the web UI and have the node store it in NVS flash, but this has the disadvantage that the device will still have a generic name initially and doesn't nicely solve the problem of deconflicting SSIDs for the configuration access point. maybe the default name could also be overridden via a build-time config?
in order to support deploying multiple ECLSS nodes on the same LAN, it would be nice to support some mechanism for assigning names to an individual node. in particular, this should do the following:
bedroom.eclss.localandoffice.eclss.localand so on?)not totally sure how this ought to be configured. you could maybe set a name in the web UI and have the node store it in NVS flash, but this has the disadvantage that the device will still have a generic name initially and doesn't nicely solve the problem of deconflicting SSIDs for the configuration access point. maybe the default name could also be overridden via a build-time config?