-
Notifications
You must be signed in to change notification settings - Fork 308
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
Additional "device_id" field in config.json #45
Comments
I tend to think this calls for an additional setting ( My 0.01c 😄 |
@jpmens This is what I wanted to do, an additional
@hoalex an Does it sound good to both of you? |
👍 |
Sounds perfect 👍 Thanks for looking into it! |
This will land in 1.3.0! The new |
Released! |
* HTTP 302 and 304 Support Add support for http redirection (302) and http not modified (304) to reduce the load the server. server.redirect(“url”, “location”, exclude-ip) will respond with 302 to redirect the browser to a different url, this is useful for backward compatibility and to redirect call to CDN when not no AP mode. server.serveStatic has a new optional parameter to get the Last-Modified date for all files serve for this location, when the browser request have the same If-Modified-Since header value, the server respond with 304 code instead of serving the file. * First round of performance improvements. * Merge remote-tracking branch 'me-no-dev/master' into performance # Conflicts: # src/WebHandlerImpl.h # src/WebHandlers.cpp * use of sprintf * Remove sections not related. * Fix a bug to serve a file in directory (e.g. serverStatic("/", SPIFFS, "/index.html");
Hi there,
I think it would be great if Homie could optionally publish its MQTT messages under
devices/name
instead ofdevices/device id
. That way, multiple ESP8266s would be easier to distinguish, as one could simply name them -- for example -- "kitchen", "living room" and so on in configuration mode and then access them by that name via MQTT.I guess that the current approach was chosen mainly to avoid naming conflicts, therefore I suggest using an optional statement in the
setup()
block à la:What do you think? :-)
The text was updated successfully, but these errors were encountered: