But, while the TTN Console shows the data coming in, the Cayenne dashboard steadfastly says:
" Your dashboard appears when Cayenne receives data from this device. Set up your device to transmit more frequently to speed up the process."
What am I missing?
Should I have programmed the Node with a special Sketch?
I don’t expect to see correctly formatted/parsed data yet (I know it does not send LPP-formatted data) but I would at least see the RSSI and SNR information, showing that the communication is occurring.
Related question - instead of “Cayenne LPP”, there is also a “The Things Node” as a choice in the Cayenne Device selection. What would I use that for (as opposed to the “Cayenne LPP” object?
That is great - I have done that and it all works. Thanks again.
I have one more question if I may (to anyone who may know):
In the sketch for my TTN Node, how do I handle incoming downlink transmissions?
I can find plenty of examples for Arduino boards, etc. but not for the TTN Node.
All I want is “proof of concept”, i.e. to flash the LED when I send a digital or an analogue packet back down to the TTN Node.
I have tried adapting the “LPPDecode” and LMIC examples but nothing seems to come in, despite the TTN console showing “scheduled”, “confirmed” and “confirmed ack”.
I have added the function message() at the end of my Sketch .ino file and I call ttn.poll(); at the end of the SendData() function which is called from the TheThingsNode::loop() function (via various callbacks) which is called from my main loop() function.
So I think I have fully and accurately complied with your instructions.
However, the message() function is never called, whether I send a downlink byte from the TTN device panel or punch a change in the Analog Output widget in Cayenne - both of which are reported in the data stream view on the TTN console…
Indeed, looking at the data stream, all that calling ttn.poll() does is to send a second, single byte transmission with a payload of 0x00 right after each main payload message.
Again, I am probably doing something wrong but clearly I am not setting up for the message() function to be called when a downlink message occurs.