Cannot enter fixed position unless device already has a position set

meshtastic / Meshtastic-Android

Android application for Meshtastic

https://meshtastic.org

GNU General Public License v3.0

693 stars 200 forks source link

Cannot enter fixed position unless device already has a position set #862

Closed erayd closed 7 months ago

erayd commented 7 months ago

If the device does not already have coordinates saved, then the coordinate fields for "fixed position" location are disabled and cannot be edited. This means that it is impossible to remotely provision the location on a non-GPS device, unless that device has first obtained its location from a paired phone etc.

App version: 2.2.23 Firmware version: 2.2.21.7f7c5cb Device: Heltec V3

Screenshot_20240219_172811_Meshtastic

andrekir commented 7 months ago

it is not possible to set the position for remote nodes

erayd commented 7 months ago

@andrekir Thanks for the speedy response 🙂. Out of curiosity, why not?

andrekir commented 7 months ago

to set the coordinates you send a position packet from yourself to yourself. firmware allows that over the API (Bluetooth, TCP/IP, Serial) but not over LoRa, otherwise nodes would be vulnerable to anyone changing their position (and time).

haplm commented 6 months ago

This unfortunately doesn't work over serial or TCP/IP either (from a computer). The node resets, but nothing happens. I'm using

meshtastic --setlat 51.0 --setlon 14.4

And of course fixed position is true as well.

basementbuilder17 commented 6 months ago

This unfortunately doesn't work over serial or TCP/IP either (from a computer). The node resets, but nothing happens. I'm using

meshtastic --setlat 51.0 --setlon 14.4

And of course fixed position is true as well.

i found that if you are connected to the device using BLE at the same time as Serial (USB), the location will not update. Was very confusing/frustrating because it responded as if it was working in python. Eventually I deactivated the bluetooth from my phone and the commands worked. Also found you needed to disable fixed position, set the position, then enable it again. hope this helps someone else!

haplm commented 6 months ago

Yes, I have also found out that disabling the fixed position is an absolute must. Without it, it won't report position even if pushed by phone. IMO the whole "Fixed position" thing is completely broken and should be reworked.

Few more notes:

Contrary to iOS, macOS and web, Android client can connect and push position also over IP!
Android generally has much more advanced options compared to iOS/macOS/web
As long as Fixed Position is enabled and lat/long is set, Android client shows the set position, but it doesn't get reported to the map (or to other nodes)
Fixed position needs to be disabled to get position reported. I'm not sure what re-enabling it would do

basementbuilder17 commented 6 months ago

Yes, I have also found out that disabling the fixed position is an absolute must. Without it, it won't report position even if pushed by phone. IMO the whole "Fixed position" thing is completely broken and should be reworked.

Few more notes:

Contrary to iOS, macOS and web, Android client can connect and push position also over IP!

Android generally has much more advanced options compared to iOS/macOS/web

As long as Fixed Position is enabled and lat/long is set, Android client shows the set position, but it doesn't get reported to the map (or to other nodes)

Fixed position needs to be disabled to get position reported. I'm not sure what re-enabling it would do

agreed i am new to this and the hardest part of setup was properly setting a correct, fixed location. definitely felt buggy. unfortunately no access to android, but i was able to get a good procedure going with the iOS app + CLI.