Ben Meadors
Ben Meadors
Closing this per your message @lewisxhe. Thanks for the contribution
Looks like it's choking on some mqtt messages. Not entirely sure yet, but I wonder if it could be older versioned message protobufs coming through the public MQTT server. Here's...
Closing. No longer needed for debugging
**ch-set** Appears to work with the latest fix. My testing: ``` ch-set psk 0x1a1a1a1a2b2b2b2b1a1a1a1a2b2b2b2b1a1a1a1a2b2b2b2b1a1a1a1a2b2b2b2b --ch-index 0 ch-set psk random --ch-index 0 ch-set psk none --ch-index 0 ch-set channel_num 46 ch-index...
Almost all of the channel methods work now. Some of them bark with this, but it doesn't appear to affect the results: ``` meshtastic --ch-add 2ndLife ERROR file:stream_interface.py __reader line:171...
I believe 31536000 was the arbitrarily large value chosen from the discourse group originally, which I think is equal to one year. The maximum value or an entirely new "always...
> In the 11200 Spec there's this definition : #define PIN_VBAT WB_A0 (WB_A0 being 36) - The actual voltage divider of the baseboard is connected to AIN0 so that seems...
meshtastic --factory-reset has been working reliably for me on the latest builds. Closing for now
Discussion around this has come up before; my suggestion would be avoid tying it to a router, since some users might want the bluetooth to remain available on a router....
Phone could be a tertiary source as well?