ESP-NOW appears to be NOT working on V2.4.0 and V2.4.1 Firmware?
-
Environment: UIFLOW2
Device: M5Dial V1.0 (not the newer V1.1 with the RTC)
Problem: communication between a Core2 and M5Dial using ESP-NOW with:
Version 2.4.0 and 2.4.1 of the Firmware to be used with UIFLOW2Greetings all,
It appears that at least on the M5Dial V1.0 that the ESP-NOW is not working (just seems dead) until I move to down to V2.3.9 of the firmware (which brings up other problems with formatting which I did find a solution to rid the b').
I think this issue MIGHT exist on the CORE2 but I ran out of time to verify because of a problem I created.
Any thoughts on a fix /workaround or I am the only one using the ESP-NOW?
Thanks-Brian
PS: TAB5 does not have ESP-NOW listed in UIFLOW2 which I would be a better suited solution.
Project Overview for the curious: using multiple M5Dials that are connected to a ENVIII for air temperature monitoring and a DS18B20 for floor temperature monitoring in each of the seven zones on the first floor of the house which is using radiant floor heating. The M5Dials will communicate using ESP-NOW to a CORE2 which is acting as a "base". When the temperatures falls below the set temperature the CORE2 will using a EXT I/O 2 to control a relay board with in turn will control the values that allow hot water to flow to each zone on the first floor of the house.
-
-
@bschwahn The Tab5 uses a ESP32-P4 which doesn't actually natively support wifi and therefore also not esp-now!
On the Tab5 there's also a ESP32-C6 co-processor which is handling the wifi.
I guess implementing Tab5 wifi/esp-now in uifow2 over the espressif wifi extension (esp_wifi_remote) might take some time and effort?
Not all esp32 variations support wifi. Check out the difference between the NanoC6 (wifi, zigbee, thread, matter) and the NanoH2 (no wifi, only zigbee, thread, matter).