Circle of this route with this one what I made is funny for me. As OT is i have mainly guts filing how what should go and fact that it's my 5'th or so attempt to normalize and fragmentation it to the POWER! with power full dependency solver in my sleeve. THX dpkg ! bash and all other perfection things !

but circle.

Started from camera that there was a plan to make images from time to time to have something to process. Read number from image. Things for today standard normal. This is OT and it's for off-line mainly. So. First of all https ....

S or not to s. If https all sensors: mic, camera, gps, .... from phone I can harvest them as sensors. Imagine no installation nothing. First phone with wifi and web browser. Entering yss page then selecting that you are a source of data on this device and bum.

new Input of .....

this is grate but https -> to http not so good I went to point where my custom https server handler of post'ing data was rerouting from https to http to be able to communicate new data from sensor. YYY a lot of windnes.

No https

you with your device on your server http with your page on it no. untrusdet and u2327404$@#$@%!

this lead to many incoming new data from many devices audio, images, gyro, gps, lumens,....

otdmp-nrf-http-api-plc in coming for the rescue! 

More about it link ...