is this normal?
I have a T-Deck Plus with external 915 antenna. It sees 20+ nodes, many without padlock but also a bunch of green ones, up to some 50 km away, over the mountains from Santa Cruz into San Jose, Gilroy and Salinas...
But messages sent from Android app to #LongFast are never delivered, and from the device itself it shows up only on the phone app. It's also not receiving messages.
Default key of AQ== and US 20 LoRa LONG_FAST config, no MQTT, CLIENT
@jaythvv How many hops are showing for those nodes? Are any direct? Are most “unknown”? Sounds like you have the correct defaults. What’s your hop limit?
You’ll get weak incomplete packets that don’t show much info from distant or mobile nodes that are barely in reach.
I’m new to #meshtastic but live in a pretty active mesh in Austin. Our best practice is 3 hops but you can increase it to 4 … send a test message “<your node/user shirt name> here, ncan I get an ack?”
@jaythvv It’s OK in your case to increase the hop limit by one. Try that for a day or three. That will only help you get heard however.
Do you have a fixed node or is it a portable? Lora likes LOS so getting it higher is better. Roof mount or even in an attic can give better results than in the ground floor. (1/2)
Since I am on the edge of the mesh in the suburbs outside Austin, I have an attic node set to 3 hops, client, and my in-house fixed node which is set to 4 hops client mute.
If your local mesh has a web page describing best practices, also look at it and see if you are complying. (2/2)
@jaythvv Reset the NodeDB and recommend others to reset it also. The NodeDB is rebuilt from mesh so it shouldn't cause any harm to do so.
There was something between 2.4 to 2.5 firmware that broke something, then something and something. Dunno, haven't looked into it more. But resetting NodeDB fixed it for bunch of us in our small mesh.
Jay Thoden van Velzen ☁️🛡️
Bill Plein🌶
Bryan Haskin
Ossi OH8HUB