-
Notifications
You must be signed in to change notification settings - Fork 147
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
Query: Integration with Chirpstack #105
Comments
I tried it. It did not work. Unfortunately, I don't know any alternatives besides buying a cheap LoRaWAN gateway like TTIG. I avoided more headatches. I hope you can find a solution for your case |
I am currently trying it with Chirpstack in Kubernetes. Nevertheless I was not able to transmit data from my node via the 1CH Gateway to Chirpstack, this is what I am currently struggling with. For the Gateway you simply need to set the variable _TTNSERVER to point to the IP or DNS-name of the server where the Chirpstack gateway bridge is located. You also need to set the corresponding _TTNPORT. Don't forget that the communication is UDP. |
Have you tried to use ABP (i.e: Not to use OTAA)? Need to use session keys for the node. And node needs to fix to one channel. Single channel gateway can not use OTAA. |
I do have this working + integrated with InnoDB - give me a few days to collate my config - yes single channel will only work with ABP |
I'm trying to make connections to ChirpStack, but the gateway doesn't show up and no messages from ABP devices reach the ChirpStack server. I put the values in _THINGSERVER and _THINGPORT |
Can you elaborate on why it would only work with ABP, and is that restriction specific to Chirpstack or does it apply to other platforms as well? I've been struggling to get my sensors working with this and chirpstack for the past few days, will try APB now but curious as to why OTAA won't work, thanks. Im on eu868 freq |
OTAA requires at least 2 mandatory channels for the gateway. |
I try this fix #72 |
Thanks, I temporarily got around it by editing the library but will try that as it does look like a better solution. |
Yes only u need change these values in the gateway, and in more up in the same sketch there is another variable for TTNPort, in the gateway nothing more. If u continue with problems the problem is the server not 1ch gateway |
The single channel gateway is just that. Lorawan uses multiple channels for
send receive on different frequencies based on the frequency plan of your
country. OTAA needs acks comming back from network server in strict time
windows ... single channel can't do that.
…On Sun, 17 Jul. 2022, 7:43 am Isak van der Walt, ***@***.***> wrote:
I do have this working + integrated with InnoDB - give me a few days to
collate my config - yes single channel will *only* work with ABP
Can you elaborate on why it would only work with ABP, and is that
restriction specific to Chirpstack or does it apply to other platforms as
well? I've been struggling to get my sensors working with this and
chirpstack for the past few days, will try APB now but curious as to why
OTAA won't work, thanks.
—
Reply to this email directly, view it on GitHub
<#105 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQTSH7MSD36F57EXDBRHEETVUNCK5ANCNFSM5KSNBBZA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Does this single channel gateway integrate with Chirpstack?
if Yes, please suggest which documentation to refer to.
if No, please suggest if there is any alternate way to integrate it.
The text was updated successfully, but these errors were encountered: