Thank you for the response.
I will preface this with I’m trying to learn this and well being new to this I am pretty sure I’ve messed things up…Excuse the long explanation but I am trying to be as clear as I know how here.
Basically I took a github repo for an end node in WLE5, modified it slightly for a custom board I spun, loaded the code and was fortunate enough to see payloads coming into TTN. I then created a webhook to Cayenne LPP (which I enabled on the end node) and yup I see data coming through. I then went into the tx section of FW and dropped in the command CayenneLppAddDigitalOutput which was nice enough to push itself up through the gateway and over to Cayenne so that I could create a digital button with on / off. I press this button and see that my application end point gets a received downlink message on TTN, but the LED on the node does not turn on as expected (ie Cayenne shows button on). The JSON message shows a lot of cryptic stuff but I do see a key / value pair “decoded_payload” : { “value_1” : 1} which does seem to change back and forth from 0 to 1 when I press the button in Cayenne.
I then proceed to open the message and copy the json section labeled “data” . I take that into the end node downlink message, set this to JSON and paste. Now two things that stick out. Firstly if I change the JSON “f_port” value from 99 to 2 (which seems to be the switch case that the RX section of FW wants to see) AND secondly change the Messaging Downlink in TTN FPort from 1 to 2 then at least the code breaks within the FW albeit the other data (Buffer Size and Buffer) seems to be 0.
So getting to the issue :
First I don’t have a serial port wired to the board.
Second I have no clue what Bytes I need to send down to see if the code is working…Sure I can send the 02 01 01 (Port, BufferSize, LED On) but that doesn’t work as the FW doesn’t get as far as the above where I modified the JSON and sent it down. Clearly there are more bytes that need to be sent it’s just that after looking at the JSON I don’t have a clue given that much of the message looks encoded…ie “correlation_ids” key, “frm_payload” key…