ESP-Now support for ESP32 (and ESP8266)

[glenn20]

New ESPNow images uploaded: v1.19.1-espnow-6-g44f65965b

I've uploaded a new set of images with a fixup for the broken callback support in my latest images.

Great, I wait for the fix. Need to use the ESPNow object passed to the callback as I do not have access to the global object, like you show in your code example

My espnow-g20-v1.19.1 branch is now updated with a fix for the callback api. Updated docs at: Callback Methods. I've also added tests for the callback apis so hopefully I won't overlook breaking these apis again .

Explanation: After migrating the recv() and irecv() methods from the C module (_espnow) to the python module (espnow.py) it was no longer possible to readily support the specific .irq() api requested by Damien in the C module. I have moved the .irq() method to the espnow.py module and renamed the low-level callback setting method in the C module to on_recv(). espnow.py:ESPNow.irq() creates a callback wrapper to match the requested api and invokes the low-level on_recv() method to set the callback (see espnow.py for the details).

In case it's not obvious, the incoming message is read out of the buffers before invoking the .irq() callbacks and the message is passed as an argument. For on_recv() callbacks, the incoming message is NOT automatically read out of the buffers before invoking the callback. This is useful if you just want to use the callback to signal your app that data is available or if you want more control over how the msg is read.

[mekanixms]

Good stuff, I will test tomorrow!!

[mekanixms]

New ESPNow images uploaded: v1.19.1-espnow-6-g44f65965b
I've uploaded a new set of images with a fixup for the broken callback support in my latest images.

Works great, just tested!

Will come back if I notice anything to report

[davef]

ESP-Now and WiFi

I noticed that in your latest 1.19 docs that calls to e.init() and e.deinit() appear to have gone away. Are they included in the e.active(True) and e.active(False) calls now?

Thanks,
Dave

[davef]

ESP-Now and Wifi

Latest 19.1 firmware-esp32-GENERIC.bin and example 2

Code: Select all

e.add_peer(peer, None, None, network.AP_IF) #  register peer on AP_IF
TypeError: can't convert NoneType to int

Had to do:

Code: Select all

e.add_peer(peer, ifidx=network.AP_IF) #  register peer on AP_IF

Also, it chokes on:

Code: Select all

#w1.config(hidden=True)              # AP_IF operates on same channel as STA_

with the error:

Code: Select all

OSError: Wifi Invalid Mode

Any hints on how to call my send_alarm() and send_csv() methods so that they go to the hotspot?

[glenn20]

ESP-Now and WiFi

I noticed that in your latest 1.19 docs that calls to e.init() and e.deinit() appear to have gone away. Are they included in the e.active(True) and e.active(False) calls now?

Thanks,
Dave

Hi Dave,

Yes - this was part of the api changes requested in the initial review of the PR on github by @dpgeorge. Note that there is currently an init() and deinit() method in the espnow.py wrapper module to support backward compatbility for existing users.

[davef]

Thank you.

Ignore the question at the end of my last post. I previously made a ESP-Now/WiFi setup where I completely shut-down ESP-Now and fired-up a WiFi connect. This crude approach left me thinking that somehow I had to direct my data to w0. I will just trying sending that data as I do on a normal WiFi connection.

[davef]

Hi Glenn,

Using Example 1 as a basis I found that when you send something via uMail is just works.

Thanks for all the effort you put in, improving and maintaining this useful feature.

Dave

[davef]

I have a working link on ESPNow/WiFi but would like to verify the behaviour I see. The local unit is as per Example 1.

I noticed that the remote unit needs to be connected to the WiFi network even though the traffic only goes over the e0 interface.

Is the remote really connected to the my hotspot/router to enable traffic over the e0 interface? Seems to suggest that I can't run a bunch of ESP32s ESPNow-only sensors and interface them to a ESPNow/WiFi gateway.

I must be missing something important.

Thanks,
Dave

[glenn20]

Hi Dave,

I must have lost track of some of your messages. Which is Example 1? Can you point me to some code?

I can confirm however that you should NOT need to be connected to an access point to send espnow messges from that interface. You just have to set the network STA interface to network.WLAN(network.STA_IF).active(True) and also set the espnow object to e.active(True) (or e.init() as per the original api).

I can confirm that I am running a bunch of espnow-only sensor devices and interface them through an espnow-wifi bridge to an mqtt service.

I have a working link on ESPNow/WiFi but would like to verify the behaviour I see. The local unit is as per Example 1.

I noticed that the remote unit needs to be connected to the WiFi network even though the traffic only goes over the e0 interface.

Is the remote really connected to the my hotspot/router to enable traffic over the e0 interface? Seems to suggest that I can't run a bunch of ESP32s ESPNow-only sensors and interface them to a ESPNow/WiFi gateway.

I must be missing something important.

Thanks,
Dave