-
1. set remotly Payloadmask to A1(161) `14 86` on fPort2 in ttnv3 console.
2. then request config Data: `80`on fPort2 ttnv3
3. the bytes are: `05 0e 00 00 1e 00 32 08 1e a8 **a1** 33 2e 30 2e 33 00 …
-
- [X] The issue is present in the latest release.
- [X] I have searched the [issues](https://github.com/brocaar/chirpstack-network-server) of this repository and believe that this is not a du…
-
Hi and thanks for the library, I really like the APIs and I'm going to try it for my project.
I'm wondering, is there some specific example for working with Class C devices (EU frequency)?
-
#### Summary
To specify the correct MAC & PHY Version combinations to the users and also to specify which are currently supported by The Things Stack.
#### Why do we need this ?
It will help …
-
There are some LoRaWAN devices being sold for regions like Europe, where they only know how to function on 3 channels. This is technically LoRaWAN compliant and therefore we need a way for the user to…
-
To whom it may concern,
…
-
**Describe the bug**
I did a update from 2.7 to 2.9 via deb pack.
Now I can still receive mqtt message but I did not get the values into thingsboard. For me it looks like that the parser is not wor…
-
I'm in Perth Australia on AU915 with only a Sensecap in range, and using a 3rd party sensor I can't configure or modify.
It works fine on TTS, but on Helium in the console, almost every uplink appear…
-
Hi Bernd, I hope you're fine. I try send "Helllo" over LoRaWAN wşth ESP32. But I saw serial "timeout waiting for BUSY now". I defined txen and rxen. And I send picture and LoraWAN settings. What shoul…
-
### Description of defect
While working on a LoRaWAN application using the mbedOS LoRaWAN implementation our devices showed some non wanted behaviour. When transmitting an uplink with a nbTrans v…