-
-
Notifications
You must be signed in to change notification settings - Fork 270
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
lora-gateway-bridge didn`t emit join-accept message #66
Comments
LoRa Gateway Bridge doesn't know anything about the LoRaWAN protocol, so it doesn't know about join-accepts. It only forwards LoRa payloads (which so happens to be a join-request / join-accept). I don't understand your question related to the ACK message, but I think you are referring to the UDP ACK, see also PROTOCOL.txt. |
Sorry for the confusion. node --(join request)--> gateway -> LoRa Gateway Bridge(send PUSH_ACK to gateway immediately and then publish MQTT message) -> loraserver -> lora-app-server--(join-accept)--> loraserver -> MQTT -> LoRa Gateway Bridge -> gateway. so the gateway should receive 2 packets if everything went right,one is PUSH_ACK , the other is join-accept, however , according to tcpdump there is only ACK message , no join-accept message。 |
Are you running the LoRa Gateway Bridge on the gateway itself? If not, could you give that a try? E.g. in my case the downlink to the gateway did not work when using DigitalOceans floating ip. When using the direct IP of the machine however, downlink did work. Usually I install the GW Bridge on the gateway itself so that I can use MQTT TLS and authentication. It will also solve the above connection issue, in case your issue is related to that. |
thank you for your time, I`ll try running the LoRa Gateway Bridge on the gateway |
Perfect, please let us know if that solved your issue (I expect it will), so we can close the issue afterwards. |
After reading the codes and logs, I find out that the LoRa Gateway Bridge didn't subscribe to the tx channel, and thus it wasn't able to get data published by the Loraserver, let along sending data to gateway. By the way,the PROTOCOL.txt did tell us that:
I should have read it carefully, my bad. |
How did you handle the PULL_DATA, did you change something in the Lora-gateway-bridge or you wrote some script for that. I have a setup like this: concentrator--(spi)-->Packet forwarder--(udp)-->Lora-gateway-bridge--(mqtt/pub)-->Mosquitto--(mqtt/sub)-->myScript" i want to transmit some data to my node, so where should i handle the PULL_DATA ? |
I would also like to know where to handle the PULL_DATA |
The whole idea of the LoRa Gateway Bridge is that you don't need to implement the UDP protocol yourself / deal with PULL_DATA. Simply use the MQTT topics as documented here: https://docs.loraserver.io/lora-gateway-bridge/use/data/. LoRa Gateway Bridge will handle the UDP protocol specifics for your. |
Do you have any documentation regarding the hosted version for loraserver? |
If you mean the server hosted by Kyrio, the documentation hosted at https://docs.loraserver.io/ applies to Kyrio too. For other questions it is better to contact Kyrio directly :-) |
I tried to perform OTTA using this.
However it seems the gateway successfully sent join-request message to NS and AS agreed
here are some logs ,
according to tcpdump there is only ACK message , no join-accept message。
The text was updated successfully, but these errors were encountered: