Nodes No Reply, Why?

When listed nodes don’t answer

Nodes can appear in your list but not answer for both social and technical reasons.reddit+1

Node is unmanned: Many home or router nodes are left running only to relay and are not actively monitored.[reddit]
User chooses not to chat: Some operators intentionally ignore DMs or primary-channel chatter and use Meshtastic only for private groups or emergency use.[reddit]
Delayed responses: People may be driving, at work, or away from their phone and see your message hours later (or miss it entirely if notifications are off).[reddit]

You are at the fringe of coverage: Your node can “hear” small nodeinfo/telemetry packets, but your larger chat messages cannot reliably make it back through weak links.[reddit]
Very poor RSSI / SNR: If signals are around or below the sensitivity limit, discovery packets may sneak through but bi‑directional messaging fails.[reddit]
Antenna / placement mismatch: Other nodes might have higher‑gain antennas or better placement (high up, outdoors) so you see them, but they cannot decode your weaker transmissions.facebook+1

Channel or key mismatch: You may see a node’s broadcasts on a shared channel, but if your primary/DM channel keys differ they cannot decrypt or reply to you.[github]
Too many or too few hops: Aggressive hop or routing settings can mean your messages never reach certain nodes even though their nodeinfo is relayed to you.facebook+1
Node role differences: Routers or CLIENT_MUTE nodes may relay traffic but the owner never reads primary‑channel messages at all.[meshtastic]

App database issues: Some app builds have had bugs where DMs exist on the node but do not show up properly in the app until the DB is reset.[github]
Node database/key history: If a node was reflashed and got a new key but your app still has the old identity stored, your conversations can look broken or one‑way until the node data is reset and keys are aligned.github+1