Cannot toggle is_unmessagable from Python CLI YAML-based configuration

[ndoo]

Cannot toggle is_unmessagable from Python CLI.

It is not available from --set or other arguments.

[porkcube]

--set-is-unmessageable [true|false] works for me, maybe your cli is out of date? i think it was added in 2.7.x

[ndoo]

Thank you, how about support from --export/--configure? I’ll update the issue to reflect that

[porkcube]

yeah that would be great, but does seem like --set-is-unmessageable is missing from --help / -h output and should be added there as well (I had never actually checked before, originally saw it mentioned in #python in discord and never thought to see if it was in the help 😬)

[ianmcorvidae]

It's in --help, that's all automatic.

  --set-is-unmessageable SET_IS_UNMESSAGEABLE, --set-is-unmessagable SET_IS_UNMESSAGEABLE
                        Set if a node is messageable or not

export and configure of course still valid concerns, but just clarifying that bit

[ndoo]

Thank you, yes it worked well, just reusing this issue and renaming it, though if you like I can close this and open a new one.

…

On Fri, Oct 10, 2025 at 00:46 Ian McEwen ***@***.***> wrote: *ianmcorvidae* left a comment (meshtastic/python#835) <#835 (comment)> It's in --help, that's all automatic. --set-is-unmessageable SET_IS_UNMESSAGEABLE, --set-is-unmessagable SET_IS_UNMESSAGEABLE Set if a node is messageable or not export and configure of course still valid concerns, but just clarifying that bit — Reply to this email directly, view it on GitHub <#835 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACAFADQ6JCTPG7UTINLP7L3W2GOVAVCNFSM6AAAAACIUVITSGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOBWGY3TINBSGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[porkcube]

It's in --help, that's all automatic.

  --set-is-unmessageable SET_IS_UNMESSAGEABLE, --set-is-unmessagable SET_IS_UNMESSAGEABLE
                        Set if a node is messageable or not

export and configure of course still valid concerns, but just clarifying that bit

Ah you're right! The linux-native node I checked on was running an older version (2.5.12).

[juergenRe]

Import/export of is-unmessagable now possible, see PR #867