saahbs

Results 6 comments of saahbs

As of 2.2.24 to which I downgraded, the fixed position is stored in location: which is NOT nodeDB AFAICT, see: ``` $> meshtastic --export-config ... location: alt: 30 lat: 37.310116...

Interesting, perhaps with 2.3.x one needs to specify fixed_position true and ALL of lat/lon/alt at ONCE for it to take effect. I did ``--export-config`` from 2.2.24, which had ``fixed_position: true``...

moar debugging on 2.3.1: ``` > /meshtastic --setlat 0 --setlon 0 --setalt 0 --set position.fixed_position false Connected to radio Fixing altitude at 0 meters Fixing latitude at 0.0 degrees Fixing...

This does work: ``` > /meshtastic --setlat 1 --setlon 2 --setalt 3 --set position.fixed_position true Connected to radio Fixing altitude at 3 meters Fixing latitude at 1.0 degrees Fixing longitude...

Lets try setting lat/lon/alt without passing set: ``` > meshtastic --setlat 4 --setlon 5 --setalt 6 Connected to radio Fixing altitude at 6 meters Fixing latitude at 4.0 degrees Fixing...