Hi everyone,
Yesterday I updated our chirpstack from version 4.5 to 4.8.1.
I noticed that the value of the “rxInfo[0].location.altitude” property is the same as the value of the longitude.
I was able to verify that the messages on the MQTT server have the correct location values.
Does anyone else have the same situation?
I haven’t yet tried building the system from source and debugging, but looking at line 87 in the below it seems like this could be a simple typo in the backend code.
use std::collections::hash_map::DefaultHasher;
use std::collections::HashMap;
use std::hash::{Hash, Hasher};
use std::str::FromStr;
use std::time::Duration;
use anyhow::{Context, Result};
use chrono::{DateTime, Local, Utc};
use tracing::{error, info, span, trace, warn, Instrument, Level};
use crate::gateway::backend as gateway_backend;
use crate::helpers::errors::PrintFullError;
use crate::storage::{error::Error, fields, gateway, metrics};
use crate::{config, region};
use chirpstack_api::{common, gw};
use lrwn::EUI64;
pub struct Stats {
gateway_id: EUI64,
stats: gw::GatewayStats,
This file has been truncated. show original
I’ll raise it as an issue so that it can be looked at, and hopefully corrected in a subsequent release.
2 Likes
Hey,
We upgraded to ChirpStack version 4.8.1 recently and have seen the same issue.
The gateway logs indicate it is sending the correct value so it does seem like a ChirpStack issue.
1 Like
abaena
July 11, 2024, 10:55am
4
It is definitively a bug, as @matteogales says at the line 87 of the file he shared. Must be “altitude” and not “longitude”. Open a new Issue in the Chirpstack repo, as it’s a bug and needs to be solved.
2 Likes
This was kindly fixed this morning by offizium-berndstorath (Bernd Storath) · GitHub , with his pull request merged into the master branch by Orne.
opened 08:51PM - 10 Jul 24 UTC
closed 08:01AM - 11 Jul 24 UTC
As described in the below topic on the ChirpStack forum, there appears to be an … issue with the altitude being reported for gateways in version 4.8.1 of ChirpStack (I have not noticed this issue in previous versions).
https://forum.chirpstack.io/t/rxinfo-altitude/21467
I'm not sure if this is helpful (or indeed correct; apologies I have not built and debugged the code, but I am happy to test any potential fixes) this could be down to line 87 in the below file.
https://github.com/chirpstack/chirpstack/blob/v4.8.1/chirpstack/src/uplink/stats.rs
It was really great to see open source software development working in this really efficient manner.
1 Like
system
Closed
October 9, 2024, 8:31pm
6
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.