You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The aioespnow module is now available in micropython-lib. However, it is unclear how users are intended to access the aioespnow module once v1.21.0 is released. There are two options:
Uncomment # require("aioespnow") in ports/esp32/boards/manifest.py so that aioespnow.py is frozen into esp32 firmware by default (as suggested in PR esp32: ESP-NOW support for ESP32 and ESP8266 #6515)
This should be done after updating the micropython-lib submodule reference in micropython from c113611 and before releasing v1.21.0.
This requires no changes to the existing documentation
OR
Update docs/library/espnow.html to indicate that the aioespnow modules should be installed with mip.
and remove the commented line in ports/esp32/boards/manifest.py.
I am seeking guidance and will submit a PR accordingly. Without action, the documentation will be incomplete/inconsistent with respect to use of aioespnow when v1.21.0 is released.
The text was updated successfully, but these errors were encountered:
Great - thanks. I'll submit a one-liner PR (which will fail commit checks till micropython-lib is updated) - unless you prefer to handle it yourself ;).
The
aioespnow
module is now available inmicropython-lib
. However, it is unclear how users are intended to access theaioespnow
module once v1.21.0 is released. There are two options:# require("aioespnow")
inports/esp32/boards/manifest.py
so that aioespnow.py is frozen into esp32 firmware by default (as suggested in PR esp32: ESP-NOW support for ESP32 and ESP8266 #6515)micropython-lib
submodule reference in micropython from c113611 and before releasing v1.21.0.OR
docs/library/espnow.html
to indicate that theaioespnow
modules should be installed withmip
.ports/esp32/boards/manifest.py
.I am seeking guidance and will submit a PR accordingly. Without action, the documentation will be incomplete/inconsistent with respect to use of
aioespnow
when v1.21.0 is released.The text was updated successfully, but these errors were encountered: