[Bug]: No channel while trying to send DM #6079
Replies: 15 comments 23 replies
-
| I have a similar issue using Station G2. Also tried deleting the nodes to refresh the key. Any ideas? |
Beta Was this translation helpful? Give feedback.
-
| This comes directly from the firmware here firmware/src/mesh/ReliableRouter.cpp Line 111 in 7eb7727 |
Beta Was this translation helpful? Give feedback.
-
| Hello Garth, I appreciate your reply. Can you expand on it a little? Is there a work around? Regards |
Beta Was this translation helpful? Give feedback.
-
| Hello, Open channel works normally. I just now flashed two Heltec E-paper units with InkHUD_2.5.20_firmware.factory.bin One of them sends and receives from other nodes on the mesh and on my desk normally. Older nodes with this behavior are on the latest Flasher Beta. All settings are default and look identical on both units. Any idea whats happening? |
Beta Was this translation helpful? Give feedback.
-
| I have also been seeing the instantaneous slash-cloud response to a DM attempt. It has only happened to me on a few occasions for a handful of msg target nodes (out of several dozen) and in each case, I believe the problem went away in a few hours without any intentional action to fix it, maybe sooner. My most recent example was sending from a Lillygo-TLora-v2.1-1.6. I am running 2.5.23 Alpha fw. DMs to other nodes works normally, where normal is a slash-cloud response takes a second or more to show. I don't think what I'm seeing is a duty-cycle-exceeded issue because my nodes are lightly loaded. |
Beta Was this translation helpful? Give feedback.
-
| Having same issue...do I just give the radio time to sync into the network? Super frustrating that I am getting a no channel after I flashed it. Makes me really hesitant to add more nodes, as there are separated by 10s of miles. |
Beta Was this translation helpful? Give feedback.
-
| It was working before I flashed it with a software update. Will it “heal” itself? Or forever it will be without the proper pki key? On Apr 21, 2025, at 10:25 AM, Garth Vander Houwen ***@***.***> wrote: If you are getting a no channel error the PKI key has not been exchanged with the node you are trying to DM, or that node has rolled out of the nodedb. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***> |
Beta Was this translation helpful? Give feedback.
-
| I have the same " no channel " crap !! The nodes I used to talk to don't work anymore, tried all the usual fixes but some of them still don't talk !? Is there a new and easy fix for this ? |
Beta Was this translation helpful? Give feedback.
-
| Hi Jonathan That worked for some of them but the stations I’m trying to reconnect with are all 20km away ! They are discreetly deployed so that makes it harder to go there and play radio ! Doh ! So I’d need to delete nodes on both sides and wait till they reappear in my node list before I can try a DM again and maybe they will shake hands ! ThanksColin On 29 Jun 2025, at 10:30, Jonathan Huff ***@***.***> wrote: Remove each other from your node lists and then try to DM them again. I had two devices that wouldn't talk. I deleted node 1 from node 2's list of DMs and removed node 2 from node 1's list of DMs and then tried messaging them again. That fixed it. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***> |
Beta Was this translation helpful? Give feedback.
-
| Yous are the guys with the brains here ! Not me ! lol Yeah did notice the trace route still works tho & yeah I do use for testing but nice to message and get a response message back from the ones that have stopped working Is there a Bluetooth repeater that could be used on our nodes ? As the range is sometimes not good and lots of houses here in oz have metal roofs if node is on roof then sometimes a problem to connect On 29 Jun 2025, at 10:52, Jonathan Huff ***@***.***> wrote: Yes! This is VERY frustrating and problematic functionality for the nodes to cling to the old key despite there being a new one. We really need to get this fixed with a way to pick up the new key without needing physical access to delete them from both sides. How can you tell the remote to do that when your DMs can't be delivered because of this problem? AARGH —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***> |
Beta Was this translation helpful? Give feedback.
-
| Nothing has worked for me. About to reflash everything On Jun 28, 2025, at 7:52 PM, Jonathan Huff ***@***.***> wrote: Yes! This is VERY frustrating and problematic functionality for the nodes to cling to the old key despite there being a new one. We really need to get this fixed with a way to pick up the new key without needing physical access to delete them from both sides. How can you tell the remote to do that when your DMs can't be delivered because of this problem? AARGH —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***> |
Beta Was this translation helpful? Give feedback.
-
| Same issue, needed to completely reset both devices and delete the app and reinstall. Very problematic for reconnecting to other mesh devices particularly if remote |
Beta Was this translation helpful? Give feedback.
-
| Hopefully someone will know ? So on my RF50 xio seeed I can't get it to come up with DFU so that it programs (using chrome on win11 ) I also have a 1000e tracker think I ordered the wrong one mines is a lorawan can it be re flashed to work Meshtastic ?? |
Beta Was this translation helpful? Give feedback.
-
| Same with 2.7.3 |
Beta Was this translation helpful? Give feedback.
-
| Still happening with 2.7.3 with DMs. Channels and traceroute both work fine. This key issue should either resolve automatically, or be fixable from only one end. Maybe with a prompt after a no-channel error. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Contact Details
Dandcodes
What happened?
I have a friend I DM with frequently, my application was saying I was connected to my Heltec Meshtastic device. Anytime I send a DM the cloud icon shows up, but quickly turns to a cloud with an X through it, and after clicking on it the error says "no channel" which isn't a very helpful as it doesn't describe how I can fix the potential issue.
App Version
2.5.16
Phone
Pixel 6 Android 15
Device
Heltec v3
Firmware
2.5.20
Relevant log output
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions