Something went wrong during commissioning of my device. Maybe the battery should not have been connected before commissioning at the terminal (2), but I got instructions to do so. Anyway, I still saw a spinner on the web-page to commission on the next day.
So what was correct; in the Console, the kiss app and the kiss device was configured, including integrations (http and database) and a payload format decoder.
What was not correct; On my TTN gateway, I received messages from the hardcoded DevAddr (26011F0F). This is a default code in the Arduino source at the
https://github.com/YourproductSmarter/KISSLoRa-demo, in the demo app. Since every device should have a unique number, I guess the OTAA didn’t work out correctly in my case.
After some attempts for minor reconfigurations, I decided to do the following:
- Then install Arduino, board and libraries using
- Then follow the TX RX example using
https://github.com/YourproductSmarter/KISSLoRa-demo/tree/master/Examples/LoRa_TX_RX, program the device, look in the Arduino Serial Monitor for the DevEUI
- At the Console, within the kiss-lora application, created a second KISS-LORA device, using OTAA (use the DevEUI printed in the Serial Monitor in the Arduino app)
- Then copy over from Console > Applications > kiss-lora-xx > Devices > kiss-lora, the Overview tab, scroll down to the Example code. These lines are to be copied to the Arduino sketch of the TX RX
- Adjust the TX RX example with the copied two lines of OTAA appEui and appKey, and upload the sketch to the device again.
- Using this, I see messages coming in the Console > Applications > kiss-lora-xx > Devices > kiss-lora, and select the Data tab
- Also, in the Overview tab, you can enter a value in the Downlink, like
00, press Send, and at the next communication from the device to TTN, the downlink message is returned to the device, and the RGB led switches ON or OFF (alternates).
- In Console > Applications > kiss-lora-xx, select Overview tab, scroll down to Access Keys, press copy-to-clipboard.
- Then select Integrations tab, then Data Storage and Go-to-platform which opens Swagger in another tab
- Then at the top, press Authorize, then in the dialog paste the Access key
- Then click Query and
try it out, and a JSON list of raw messages is returned.
So the above now works, so it is time for the