This would be a most useful feature for my company’s project. I would like to request that an optional field is added to the payload decoder’s returned object that instructs the HTTP integration to use only the payload decoder’s returned object as the content of the HTTP POST submitted to the specified endpoint.
For example, the decoder may return:
"payload_override" : true,
"signatures": [ "SIG_K1_K7eWqZmnneUHhnhcR9r6LwNnXYSEqpv6HcE124nNfSL5eZADyTDGfXTprxH79cMgh74GAX5Fo9mYiiJQxCMp2cN8hSept7"
This exact JSON message is put into the payload minus the “payload_override” field.
My company is building a decentralized and distributed IoT data platform that uses IPFS as the datalake and blockchain as the access control system. LoRaWAN and TTN is one of the data ingestion methods we’re adding support for. Our customers, and your users, would be interested, we think, in directly accessing the blockchain network avoiding middlemen.
In the meantime, we’ll develop connectors using Azure and AWS as needed.
In case anyone is wondering, no, the decoder is not generating the signatures, this is done on the sensors and is a key feature of our platform. The decoder would need only to do a base58 encoding of a portion of the payload sent by the devices and to build the JSON message in the required format.
Thanks for your consideration!