Improper trace path on single node with 2byte path

[fzd2vp4nmb-oss]

Hello,
I'm just trying to report what seems to be a bug when using meshcore-cli to run the trace command.
When I use the 2byte/3byte notation for the path, if I specify a single node, meshcore-cli splits those digits like it was couple of 1byte path.

For example meshcore-cli trace 0a27 gets split like a trace of 0a -> 27 and it goes in timeout
However if I provide a trace for 2 nodes in 2byte/3byte notation, it works fine: meshcore-cli trace 0a27,ab12 gets correctly 0a27 -> ab12
So to trace a single node I'm forced to use the 1byte notation for the path

Regards, Armando

[fdlamotte]

Yes, by default it assumes 1 byte hashes if it has no means to decide ... the idea was to stay retro-compatible with old scripts You could do "tr 0a27," or tr "0a27:2", I think it's in the help but feel free to reply if it is not clear enough ;)

…

On Thu Jun 11, 2026 at 3:30 PM AST, fzd2vp4nmb-oss wrote: fzd2vp4nmb-oss created an issue (meshcore-dev/meshcore-cli#62) Hello, I'm just trying to report what seems to be a bug when using meshcore-cli to run the trace command. When I use the 2byte/3byte notation for the path, if I specify a single node, meshcore-cli splits those digits like it was couple of 1byte path. For example **meshcore-cli trace 0a27** gets split like a trace of 0a -> 27 and it goes in timeout However if I provide a trace for 2 nodes in 2byte/3byte notation, it works fine: **meshcore-cli trace 0a27,ab12** gets correctly 0a27 -> ab12 So to trace a single node I'm force to use the 1byte notation for the path Regards, Armando