Feature: ESPEasy-now layer #3301
Conversation
|
This PR fails the build because of this error: Might need a fix? |
|
Yep Case sensitive issue, which compiles well on Windows, but not on Linux. |
|
does this mean that we will be able to use one node (esp8266) as a sensor unit and another node as a display unit in places that don't have wifi? |
|
Yep and even completely self-organising. Currently the implementation tries to forward MQTT messages (of any size) to a node that's connected to a broker, but I am -as we speak- working on making it possible to send messages to any node in the mesh of nodes. Both ESP8266 and ESP32 can be used together and also ESP32 + ethernet to act as a gateway (that's how it is being tested right now) But there's still some stability issues in the self organizing routing which I'm working on. I want to make it completely network-agnostic and thus very resilient to network outages. Upto 6 hops of each 50m have been used in tests with 700+ bytes of payload (ESP-NOW packets can only hold 200 - 250 bytes of data), so the underlaying datastructure of splitting and merging packets does work well :) |
src/src/WebServer/WebServer.cpp
Outdated
| @@ -221,6 +221,9 @@ void WebServerInit() | |||
| webserver_init = true; | |||
|
|
|||
| // Prepare webserver pages | |||
|
|
|||
| // FIXME TD-er: The added String() wrapper is needed for the latest ESP32 core lib. | |||
| // See: https://github.com/espressif/arduino-esp32/issues/4374 | |||
| #ifdef WEBSERVER_ROOT | |||
| web_server.on("/", handle_root); | |||
There was a problem hiding this comment.
Shouldn't that "/" also have the F() macro, like the other strings?
There was a problem hiding this comment.
Probably, but I've had some issues not so long ago with the web_server.on calls with FlashStringHelper on ESP32.
So perhaps I missed this one?
There was a problem hiding this comment.
perhaps I missed this one?
That's the most likely cause 😉
Not a biggie, of course, just something I spotted.
| @@ -293,12 +293,12 @@ void WebTemplateParser::getWebPageTemplateVar(const String& varName) | |||
| if ((i == MENU_INDEX_RULES) && !Settings.UseRules) { // hide rules menu item | |||
| continue; | |||
| } | |||
| #ifndef FEATURE_NOTIFIER | |||
| #if FEATURE_NOTIFIER==0 | |||
There was a problem hiding this comment.
This could have been:
#if !FEATURE_NOTIFIER
but the end-result is the same 😃
There was a problem hiding this comment.
And that piece of code looks like it might still be wrong in the mega branch (#ifndef instead of #if !...)
There was a problem hiding this comment.
Tested that both ways and with and without Notifiers enabled, but it doesn't seem to make a difference, still works as intended (tab is shown or not, based on notifiers available or not), the code just looks a bit odd.
But you fixed it already so it will be corrected in due time 👍
Disabled any call to set TX power as it seems to seriously do some strange stuff, requiring to reflash the ESP to get it to connect again.
A communication layer using ESP-now extended to be used in ESPEasy.
For example the ESP-now packets only can have a 255 byte payload, so sending more means those have to be split and merged while processing packets from several different nodes.
ESP-now is quite fast, with typical round trip times of less than 4 msec.
It also does not need to be connected to WiFi.
As it can use a very small bandwidth channel and low bitrate, its reach is significant more compared to normal WiFi.
This is nowhere near complete, but it takes a lot of time to keep in sync, so by merging it I may speed up development.
It is still highly experimental and lots of code may change regarding ESPEasy-now.
What's working now:
Still in development:
Known issues: