I have started using the new bridge and found that two gateways that work fine send an ack after transmission:
The other 5 gateways are running on resin.io but these gateways do not reply with a ack.
So, data is sent by LoRaAppserver but not handled by the multi packet forwarder that runs on resin.io.
I might not have mentioned it in the documentation, but the ACK feature is only available for packet-forwarder versions using the v2 protocol. The protocol-version of your gateway is printed in the LoRa Gateway Bridge logs.
I will look in to it. please hold the line
Sorry to bump an old topic, but does this still hold? I can’t seem to find where to configure the gateway discovery feature.
Note that you also need to enable this globally in
Damn, just missed that, I thought they were part of the general conf. On the same note, I can’t find anything related to gateway discovery on the lora-app-server.conf, and I checked internal/config/config.go to make sure it wasn’t just missing from the file.
Oh actually, that might be the only configuration This was refactored a while ago and it used to be in
lora-app-server.toml. Only, this did not work out as when adding multiple network-servers for different regions the config had to match the network-server band, which is the reason why it is now under network-servers.
Ha, I was never gonna find it .
My lora-app-server config file added in /etc/lora-app-server
but i getting issue with gateway ping
so i need to move config file under
When you configure the ping settings in the LoRa App Server, does the App server send the configuration to the gateways via the gateway bridge and then over UDP over the same UDP port as the regular LoRa messages? Or is there a different protocol/port for these sort of messages?
Ah, I understand now. It’s basically just a downlink message that the other gateways listen for, and if they hear it they report some statistics? Is there a documentation page that shows what kind of information/metrics you can get from these discovery pings?
Greetings to everyone,
I was reading this thread, and comparing with the parameters available on the configs (Configuration - ChirpStack open-source LoRaWAN<sup>®</sup> Network Server and Configuration - ChirpStack open-source LoRaWAN<sup>®</sup> Network Server).
However, I don’t see such parameters anymore, but I do see the options on my chirpstack webapp, on the Gateways. Is this feature still available? Is it now only a matter of configuring it on the webpage? All the links @brocaar included in their comments are now 404 BTW…
How would I use this same command using now the chirpstack-application-server flags/command?