Add more bytes to bots "path:" #67

New Issue

2026-10-05T01:55:51+02:00

adam commented

2026-10-05 01:55:51 +02:00

Would it be possible to have the path the bot send back to show more than one byte? Firmware .14 has options for 2 and 3 byte paths.

View or change this node's advert path hash size
Usage:

get path.hash.mode
set path.hash.mode
Parameters:

value: Path hash size (0-2)
0: 1 Byte hash size (256 unique ids)[64 max flood]
1: 2 Byte hash size (65,536 unique ids)[32 max flood]
2: 3 Byte hash size (16,777,216 unique ids)[21 max flood]
3: DO NOT USE (Reserved)

Would it be possible to have the path the bot send back to show more than one byte? Firmware .14 has options for 2 and 3 byte paths. ------------------------------------------------------ View or change this node's advert path hash size Usage: get path.hash.mode set path.hash.mode <value> Parameters: value: Path hash size (0-2) 0: 1 Byte hash size (256 unique ids)[64 max flood] 1: 2 Byte hash size (65,536 unique ids)[32 max flood] 2: 3 Byte hash size (16,777,216 unique ids)[21 max flood] 3: DO NOT USE (Reserved)

adam closed this issue

2026-10-05 01:55:51 +02:00

adam commented

2026-10-05 01:55:52 +02:00

Hm, so you're meaning to toggle the radio's path mode, send a message, then toggle it back? I've had a similar request for byte width per room, and the short answer is that it's a pain in the butt, and probably doubly so for bots, but if it's something folks want, I can try to work on that.

The big downside is that it's going to dramatically increase send time as we are adding two additional round-trip transactions to mutate the radio's configuration on top of message send.

Hm, so you're meaning to toggle the radio's path mode, send a message, then toggle it back? I've had a similar request for byte width per room, and the short answer is that it's a pain in the butt, and probably doubly so for bots, but if it's something folks want, I can try to work on that. The big downside is that it's going to dramatically increase send time as we are adding two additional round-trip transactions to mutate the radio's configuration on top of message send.

adam commented

2026-10-05 01:55:53 +02:00

I would generally just say to change the setting globally, which will include bots and can be done from the settings. I'm assuming the goal is providing some kind of bot that always sends a multibyte path identifier for testing?

I'm not sure if I'm up for the level of plumbing this would take for something that's hopefully a temporary issue as the mesh converts. I'll think on it, though.

I would generally just say to change the setting globally, which will include bots and can be done from the settings. I'm assuming the goal is providing some kind of bot that always sends a multibyte path identifier for testing? I'm not sure if I'm up for the level of plumbing this would take for something that's hopefully a temporary issue as the mesh converts. I'll think on it, though.

adam commented

2026-10-05 01:55:53 +02:00

So, the bots ARE able to know the width of an arriving message by looking at path_bytes_per_hop; when running 1.14, multi-byte messages will arrive just fine so they can be read/analyzed. That, combined with the global hop width config which is available in settings, mean that I'm not going to introduce message-width toggling right now; that's adding more/slow/hairy radio ops that clog things up in terms of send velocity that I don't think is going to be relevant in the long term. Sorry!

So, the bots ARE able to know the width of an arriving message by looking at `path_bytes_per_hop`; when running 1.14, multi-byte messages will arrive just fine so they can be read/analyzed. That, combined with the global hop width config which is available in settings, mean that I'm not going to introduce message-width toggling right now; that's adding more/slow/hairy radio ops that clog things up in terms of send velocity that I don't think is going to be relevant in the long term. Sorry!

adam commented

2026-10-05 01:55:54 +02:00

Sorry for the late reply. I just wanted to see 4 digits of a path. It only sometimes works I found out. I left it on #test in the bay area.. and sometimes it started showing 4 digits, then it would not. I don't know

Sorry for the late reply. I just wanted to see 4 digits of a path. It only sometimes works I found out. I left it on #test in the bay area.. and sometimes it started showing 4 digits, then it would not. I don't know

adam commented

2026-10-05 01:55:55 +02:00

I would expect that to be because only some clients are sending multibyte paths right now

I would expect that to be because only some clients are sending multibyte paths right now

adam commented

2026-10-05 01:55:55 +02:00

That makes sense.

That makes sense.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#67