Hi @HougeDK — this is a harmless defensive warning that you can safely ignore. Here's what it means:

What's happening

Meshtastic node numbers (nodeNum) are 32-bit unsigned integers, with a maximum valid value of 0xFFFFFFFF (~4.3 billion). The value 6.027320115239811e+76 is astronomically larger than that — it's what JavaScript produces when a hex string longer than 8 characters (e.g. a 32-byte PKI public key, which is 64 hex chars) is accidentally parsed as a node number via parseInt(hexString, 16).

When a packet arrives where the decoded nodeNum falls outside the valid range, MeshMonitor logs this warning and treats the result as "no such node" (null) rather than passing the invalid value to the database — which would crash on PostgreSQL/MySQL backends with a bigint out-of-range error.

Why it happens

This is almost certainly triggered by a node on your mesh that is using PKI encryption (public/private keys). In certain edge cases, the public key hex value can end up getting decoded in a context that expects an 8-char node ID. The guard catches it cleanly.

What to do

Nothing — the warning is the fix working correctly. The packet is rejected and processing continues normally. If you're seeing it very frequently (dozens per minute), feel free to share more context (firmware versions of your nodes, whether you're using PKI-encrypted DMs, etc.) and we can investigate whether there's a more specific root cause.

Generated by Claude Code

Uh oh!

[SUPPORT] NodesRepository.getNode #3677

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions