Replies: 3 comments 4 replies
-
Teltec V3 ---> Heltec V3 "unknown encryption" error ---> "Unknown Public Key" error. I also noticed "Encrypted Send Failed" When I updated firmware 2.5.7 ---> 2.5.8 from updated node sending time. |
Beta Was this translation helpful? Give feedback.
-
yeah we need a button that does "Manually Send/Exchange/Refresh Keys" either to a targeted node, or the whole mesh (maybe a within x hop limit?). its causing frustrations having to manually delete nodes/nodedb and wait everytime we update fw on each node. At the least, each test send is causing lots of dead end TX's traffic on the band until the nodes sort it out |
Beta Was this translation helpful? Give feedback.
-
I went to Meshtastic phone app "setting" tab --- Security and copied the Public Key and Private Key. I updated the firmware with full erase. I copied back both the Private Key and the Public Key. It worked. I was able to send the direct message successfully. I felt this "key saving & restore" action was easier than "deleting from other nodes list" action. Maybe copying the Public Key and Private Key and putting these back to the same device can be done by the new phone app function? |
Beta Was this translation helpful? Give feedback.
-
Platform
ESP32
Description
I did "Full Erase and Install" firmware ver 2.5.7 to Lilygo T-LoRa T3-S3.
I sent direct messages from Teltec V3 and RAK 4631.
I got "no channel" error.
I sent direct message from Lilygo T-LoRa T3-S3 to other nodes, I got "unknown encryption" error.
I needed to delete Lilygo T-LoRa T3-S3 node information from other nodes to resolve this issue.
I used iOS iPhone app ver 2.5.9.
My request is some other way to resolve this issue without deleting node information from other nodes manually.
Beta Was this translation helpful? Give feedback.
All reactions