Mykhailo Lesyk

@caveman99 Still does not work: ``` meshtastic --version 1.3.35 ``` ``` meshtastic --info Connected to radio Owner: Meshtastic ea54 (ea54) My info: { "myNodeNum": 2747853396, "maxChannels": 8, "firmwareVersion": "1.3.42.2f74f9ca", "errorCode":...

> #response_container_BBPPID{font-family: initial; font-size:initial; color: initial;} I'll have a look tomorrow, looks like it's not even saved. Anyway the value is only read during device startup, so you should See...

> This has been modified to meshtastic --set device.serial_enabled = false I did execute this command, please see my listings.

> Device also reboots automatically after saving now as well in firmwares 1.3.41+ I did all kind of reboots I can imagine just to be sure :)

@caveman99 this issue is reproducible on many devices - can it be re-opened?

Sure, this can be (less priority) part of the project how to harden autonomous node which was stolen in order to save the entire network from compromising (i.e. disposable nodes)....

I currently play with just ESP32 by flashing firmware into it and learning parameters but real hardware is on the way. Regarding "connect over serial" - I thought `meshtastic --set...

Filed https://github.com/meshtastic/Meshtastic-device/issues/1713 just in case.

cc @thanksmister as some who has more info (was maintainer in the past).

As I mentioned just disabling bluetooth will disable usage of the end nodes. Just disable pairing while enable bluetooth running will be better. Regarding fixed pin - it will be...