Robert Hadow

### Back to Basics The Meshtastic project is complicated by its applicability to multiple hardware platforms. Contributors have made a decsion to exploit features in each platform, rather than assiduously...

@juergenRe The problem is more general. For example, I have a 20 argument meshtastic command that includes: ``` --set bluetooth.enabled true \ --set bluetooth.mode FIXED_PIN \ --set bluetooth.fixedPin 654321 \...

@juergenRe If I were the designer I would choose your option (a). All or nothing. What is my logic? A user may have deveoped a set of preferences, the new...

@juergenRe In all my wandering around this github repository, I have not seen a programming standards document. My background is in large systems development, but in the last century. Forgive...

@ianmcorvidae Hello Ian -- The online doccumentation makes two general assertions: (1) The default syntax for all preferences is `--set preference PREFERENCE` (2) remote admin works only with commands in...

I have not looked at the code, but I surmise that: (a) names are handled differently from other configuration attributes (b) they are referred to by various (apparently) equivalent names...

Hello @juergenRe -- If there is a **disabled** attribute, then there whould be a distinct **enabled** attribute. That's yet another bit to keep track of. I suggest going back to...

@juergenRe -- Consistency is important. How about using the same terminology as the GPS? _**NOT_PRESENT**_

On a regular basis, I've discovered that when an ESP32 node (Heltec V3) runs out of juice and quits, Owner and Owner-short revert to the default "Meshtastic abcd" and "abcd"....

@SubhaNAG2001 I tried your solution. In response to `--set ham false` "LocalConfig and LocalModuleConfig do not have attribute ham." According to https://meshtastic.org/docs/software/python/cli/ setting owner and owner-short automatically disables ham mode.