I don't have this entirely narrowed down, but I've been able to replicate the issue easily with two Heltec v4 boards running the latest firmware (1.17.1).
Symptoms:
Given two boards, a Heltec v3 and a Heltec v4, I can communicate with either of them on public channels perfectly fine. They can talk to eachother too. I can also use my Heltec v3 to direct message other nodes, like my t1000. I send out an advert from my Heltec v4 as well as from my Heltec v3 and I get eachothers contacts just fine. However, when I try to send a direct message from my v4 to my v3, it shows as sent, but never delivers. The v3 never sees the message. When I try to send a message from my v3 (running with meshmonitor) to my v4, meshmonitor doesn't even make an attempt. It just says "Failed to send message" instantly after I press send. I tried reflashing my v4 with different firmware versions, even trying a different v4 board, all to no avail.
In short, neither of my v4 boards can do direct messages. My current suspicion is that there's something off with the adverts these are sending where it doesn't give a correct public key or id or something, and this is what causes meshmonitor to freak out when it tries to send a message.
I'd love any help with this I can get! Thanks!
I don't have this entirely narrowed down, but I've been able to replicate the issue easily with two Heltec v4 boards running the latest firmware (1.17.1).
Symptoms:
Given two boards, a Heltec v3 and a Heltec v4, I can communicate with either of them on public channels perfectly fine. They can talk to eachother too. I can also use my Heltec v3 to direct message other nodes, like my t1000. I send out an advert from my Heltec v4 as well as from my Heltec v3 and I get eachothers contacts just fine. However, when I try to send a direct message from my v4 to my v3, it shows as sent, but never delivers. The v3 never sees the message. When I try to send a message from my v3 (running with meshmonitor) to my v4, meshmonitor doesn't even make an attempt. It just says "Failed to send message" instantly after I press send. I tried reflashing my v4 with different firmware versions, even trying a different v4 board, all to no avail.
In short, neither of my v4 boards can do direct messages. My current suspicion is that there's something off with the adverts these are sending where it doesn't give a correct public key or id or something, and this is what causes meshmonitor to freak out when it tries to send a message.
I'd love any help with this I can get! Thanks!