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]: Position not sent #3273

Closed
todd-herbert opened this issue Feb 24, 2024 · 3 comments
Closed

[Bug]: Position not sent #3273

todd-herbert opened this issue Feb 24, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@todd-herbert
Copy link
Contributor

Category

Other

Hardware

Heltec Wireless Paper

Firmware Version

2.2.24.b2ea1e23

Description

  1. Erase flash

  2. Build and upload for Heltec Wireless Paper

  3. Disable smart position, decrease GPS broadcast interval to 10 seconds (for testing)

  4. Use fixed position
    Other nodes do not receive position, even manually requested from android app.
    Log indicates that position is not being send because precision is 0.
    Android app has no field for precision.

  5. Connect via serial, at client.meshtastic.org
    Channel Precision field, in position settings, is blank

  6. Set channel precision. Tested values 1 and 32

  7. Save settings
    device reboots

  8. Open positions settings
    Channel precision field is again blank

Relevant log output

INFO  | 06:28:04 70 [PositionModule] Sending pos@0:6 to mesh (wantReplies=0)
DEBUG | 06:28:04 70 [PositionModule] Skipping location send because precision is set to 0!
DEBUG | 06:28:04 70 [PositionModule] allocReply returned a nullptr
@todd-herbert todd-herbert added the bug Something isn't working label Feb 24, 2024
@jp-bennett
Copy link
Collaborator

jp-bennett commented Feb 24, 2024

We're working on adding client support. It's good to know that the web client isn't working as expected. I'll look into that. The Python client is working, using a command like:
meshtastic --ch-set module_settings.position_precision 16 --port /dev/ttyACM1 --ch-index 0

@todd-herbert
Copy link
Contributor Author

Thanks for taking the time to update. Sorry if it's just a case of jumping the gun, just wasn't sure if it needed to be brought to anyone's attention. It sounds like it's already well under control.

@jp-bennett
Copy link
Collaborator

I'm pretty sure the old default behavior will work again with PR #3278

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants