We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From looking at the MQTT data and map of the global channel it looks like some nodes report their latitude, longitude and altitude as "0".
{"channelId":"LongSlow","gatewayId":"!a84c7038","packet":{"from":1230671069,"to":-1,"channel":177,"decoded":{"latitudeI":0,"longitudeI":0,"altitude":0,"batteryLevel":33,"time":1639753585},"id":1481766144,"rxTime":1639753583,"rxSnr":5.25,"hopLimit":1,"wantAck":false,"priority":"UNSET","rxRssi":-36}}
From looking at the code (https://github.com/meshtastic/Meshtastic-device/blob/6fc3c9c8689e754869097b797c6d9dfe101cc182/src/gps/GeoCoord.h#L85) it seems that those values get initialized as 0 and are sent like this later on.
The behaviour should be changed so that values that can't be determined do not default to 0 and are not reported / used at all.
The text was updated successfully, but these errors were encountered:
This would come from the backend. latitudeI and longitudeI are not in the device.
Sorry, something went wrong.
No branches or pull requests
From looking at the MQTT data and map of the global channel it looks like some nodes report their latitude, longitude and altitude as "0".
From looking at the code (https://github.com/meshtastic/Meshtastic-device/blob/6fc3c9c8689e754869097b797c6d9dfe101cc182/src/gps/GeoCoord.h#L85) it seems that those values get initialized as 0 and are sent like this later on.
The behaviour should be changed so that values that can't be determined do not default to 0 and are not reported / used at all.
The text was updated successfully, but these errors were encountered: