Hi Jared - I have a nrf9160 Thing Plus as well as your original ones. There is a slight difference with the interrupts on the LIS2H between the two. and the sensor library is expecting two interrupts from the device, Is there an easy way around this. I’m not getting any motion events on the tracker, as the interrupt is not wired….
Additionally, I’m trying to bypass using your Pyrinas server and feed the data to my own MQTT server with a node-red backend. I have it publishing and subscribing using CBOR no problems, but I’m struggling with the FOTA part, and in particular how to “trick” the nrf9160 into decoding the ota pub string.
I’m unclear what has to be in the payload, and the format it has to be in. - when I step through the QCBOR code its a black hole.
From what I can tell, it just needed 12 bytes of raw data, including the 4 bytes for the version and an eight byte hash.
It’s not working though so if you are able to let me know what the entire byte string is and the format that is received at the nrf9160 that would be a big help
Here is what I have so far (that doesn’t work)
var hash = [0×31,0×32,0×33,0×34,0×35,0×36,0×37,0×38];
var manifest = {};
manifest.version = {};
manifest.version.major = 0×01;
manifest.version.minor = 0×02
manifest.version.patch = 0×03
manifest.version.commit = 0×04
manifest.version.hash = new Array(8);
manifest.version.hash = hash;
manifest.host = “somewhere.com”;
manifest.file = “my_app.bin”;
manifest.force = false,
msg.payload = manifest;
and this doesn’t work either
buf_ota = Buffer([161,0,140,1,2,3,4,11,12,13,14,15,16,17,18]);
msg.payload = buf_ota;
Thanks for the help
Regards
Marshall
