Hello.
I managed to connect neonious one to AWS IoT. I can't believe my eyes. It connects over mqtts with all AWS credentials supported. It publishes to topics and subscribes also.
AWS package aws-iot-device-sdk with dependencies weights above 20 MB, but I've made bundle with webpack and it is only 227 kB. Then I downloaded all credentials and bundle to neonious via IDE, made bundle entry point and it SIMPLY WORKS!!
PS Of course I've made this
require('mqtt-packet').writeToStream.cacheNumbers = false

@neoniousTR Your documentation isn't bad, trust me It's obviously made with consumer in mind. Thank you very much for this great job

If I would use

createFirmwareStream()

in neonious one, what it expect on input? Entire image with all the components (lowjs files, IDE files, static files(if used) and so on)? By what means I could make this image?

As I see, lowjs upgrade for neonious one for now has to options - either by IDE or by esptool (like it is described in HackingTool reflashing process). Is that right?

Thank you, Thomas.
If there is possibility to selfsigning - why isn't it the default option? Because you want to track lowjs usage?
Is there some checking process while OTA? What if image would be corrupted while transferring? It would brick the device?

@neoniousTR Thank you. It becames clearer. So when I use lowsync, it performs signing logic. But who is on duty when we use OTA. For ex, we first make lowsync build with "ota_update_support": true, then lowsync flash. So at this stage our image got watermarked. Then we make lowsync build again. At this stage image has not got watermarked yet. And then we OTA update with this image. Suppose client and device are both in one local network without internet access. As a result, I got working device w/o watermark. Is it right?
Why don't you sign the image at build stage?

I’m very sorry, Thomas. I can’t understand this. Is anywhere detailed description?
What are the differences between basic and professional low.js?
Is this signing process only professional Lowjs related?
Are flashing images option supported only by lowjs professional?
I intend to use lowjs for IoT devices. There is, among others, the task to update firmware over the air. So the question is - what would be appropriate workflow and licensing for this? Is it possible to make one, signed image and then OTA flash it to ten thousand of devices? Is signing process kinda protection from unlicensed usage of lowjs professional?

@neoniousTR when I use OTA - is there also some signing process under the hood?

@neoniousTR Thanks. It's now clear for me.
Could you explain what means this sentence here
"This call needs Internet access to sign the low.js code. None of the static or factory files (together the user files) are transferred to the neonious servers, however". Who signs and what?

@neoniousTR
Why 5.1? There is 6+ in neonious description.

Is it possible to transfer new upgraded software to neonious one (application, not system) and then programmatically reboot it to run this software?