Setting up ESP NOW with "peerInfo.encrypt = true;" Force to have a working WiFi connection to a router. (AEGHB-934)

[fableman73]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate
• Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
• Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?

always

Expected behavior

I expect the encrypt to work without a WIFI router.

Actual behavior (suspected bug)

No data is transmitted or received over the ESP NOW

Error logs or terminal output

Using ESP32

If I enter a valid wifi network then it works.
If I enters an invalid WiFI network it fails to setup and work.

(If I run without encrypted data I can make it work without a wifi network.)

It's like the SEP NOW encrypted force to have a working WiFi else it will not work.

Steps to reproduce the behavior

Implementing encrypted functions without a wifi router.

Project release version

Latest

System architecture

other (details in Additional context)

Operating system

Linux

Operating system version

ESP32

Shell

other (details in Additional context)

Additional context

No response

[lhespress]

@fableman73 What do you mean change peer->encrypt=false to peer->encrypt=true or espnow_add_peer has LMK, it must connect with a router?

[fableman73]

Yes. As soon as you using encrypt in ESP NOW it will not be able to work correctly if you not connecting to a WiFi same time
, adding peer is ok and everything but the communication fails.

[fableman73]

Anyone manage to use encrypt messages between devices using ESP NOW without a connected WiFi router?