Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Trying to change fixed position coords fails #930

Closed
prokrypt opened this issue Mar 24, 2024 · 4 comments · Fixed by #946
Closed

[Bug] Trying to change fixed position coords fails #930

prokrypt opened this issue Mar 24, 2024 · 4 comments · Fixed by #946

Comments

@prokrypt
Copy link
Contributor

prokrypt commented Mar 24, 2024

Similar problem as meshtastic/python#525 due to meshtastic/firmware#3403

Fixed position must be disabled (with a node reboot) and then re-enabled with the new coordinates or otherwise they won't stick.

Possible solution (don't know how the android app sets position) is to have it automagically disable fixed position before setting location and re-enabling? If that's not possible then maybe gray out the input boxes when fixed position has already been set.

@garthvh
Copy link
Member

garthvh commented Mar 24, 2024

You can't set a fixed position while fixed position is enabled anymore.

@jane1e
Copy link

jane1e commented Mar 24, 2024

why?

@prokrypt
Copy link
Contributor Author

prokrypt commented Mar 24, 2024

why?

Because someone complained about phone-provided location overwriting fixed position coordinates.
?!?

@joneyes
Copy link

joneyes commented Apr 14, 2024

why?

Because someone complained about phone-provided location overwriting fixed position coordinates. ?!?

The way around this would be to make provide phone location to mesh check box always visible (rather than only after device selection), that way you know the status before selecting the device

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants