Hello All I am sorry if this has been asked already but I have noticed with the alpha 2.5.0 that when I try to direct message I get a “no channel” message next to the message.
I confirmed that we all have the same channel and Lora wise using the standard channel 20.
Curious if anyone can assist with this error. I suspect it’s limited to certain devices that have the issue but I have a couple that noticed this error on.
I have seen the same behavior on my t-beam and heltec v.3 units. I couldn’t get DM to work between units running 2.5.0 and I couldn’t get remote administration to work either (same NO_CHANNEL error). However, the nodes appear with the green padlock and normal messages in any of the channels (including admin) work fine.
EDIT: I deleted the nodes from the list and let it repopulate, and now everything works as designed. It seems that changing keys can mess things up until there is a chance for keys to be exchanged again. If you have this problem, delete the nodes from the list and wait a little bit.
Hi.Thanks. Do you mean NodeDB reset? Or something else? (I am on Android)
A NodeDB restart does it for sure, but if you want something more selective just go to the specific nodes in the nodes list and erase those that are running 2.5.
OK. But there is only in Android the option, when clicking on the short name coloured icon, “Remove”… is that it? (There are also Ignore, Traceroute, Request Position, and Direct message…)
That is correct. Just remove them and they will repopulate with the correct keys
I’ll try it next time my encounter it doesn’t happen all the time. Thank you