IoTagent-LoRaWAN icon indicating copy to clipboard operation
IoTagent-LoRaWAN copied to clipboard

FIWARE IoT Agent for LoRaWAN protocol (with CayenneLpp and CBOR data models)

Results 27 IoTagent-LoRaWAN issues
Sort by recently updated
recently updated
newest added

## Proposed changes This report is on IoTagent-LoRaWAN works on ASIA923 with little modification. Similar change may be applied to AU915/US915 and other regions. This pull request is not intended...

## Proposed changes As discussed within the TSC, badge and links for FIWARE clones of the container image should be switched to quay.io ## Types of changes What types of...

Hello, Here I am trying to send uplink messages from the Things network with payload format cayenellp and using Fiware LoRaWAN IoTagent, I could see data traffic coming to lorawan...

Hello, I am hoping you can assist me with a problem I am experiencing. I have set up the LoRaWAN IoT Agent with TTN, correctly providing the ApiKey and establishing...

Hi @chicco785 @jason-fox @taliaga @roberto-castillo @fgalan As per my understanding of the code there is no SOUTHBOUND supported in LoRaWAN. (Sending measures from Orion to LoRaWAN) Please confirm my above...

enhancement

## Problems found The first problem I found is that if the iotagent is provisioned with a group, and thus, subscribed to a topic if the broker disconnects in my...

### Description: Getting error while sending device provisioning request to IoTAgent LoRaWAN. ### Steps to reproduce: ``` curl --location --request POST 'http://localhost:4061/iot/devices' \ --header 'accept: application/json' \ --header 'Fiware-Service: openiot'...

## Proposed changes This PR correctly pass as message to be decoded for ttn v3 `message.uplink_message.frm_payload`. ## Types of changes What types of changes does your code introduce to the...

Hi @jason-fox, Could you please help me in understanding this, ### Description: Unable to Provision device in IoTAgent LoRaWAN with Scorpio broker v2.1.13 as context broker. ### Steps to reproduce:...

with ttn v3 the encoded payload is stored at `message.uplink_message.frm_payload` and not at `message.payload_raw`

bug