In the particulate matter configuration you can indicate in the API where you can send your own data.
The crazy thing is if I do this via Antagonist, the data does not arrive on my own web server, but if I test via another hosting, the data does arrive from the particulate matter.
The data is in Sensor data, but if it is on your own web server, this is easier.
Anatagonist himself says that it disabled TLS 1.1, could this be due to this ???
I give in the configuratie in the api my serveradres.
Then the data of the particulate matter is going to my serveradres.
Normally is works good but not by Antagonist.
Antagonist is a webhoster in the Netherlands.
If i choose for another webhoster then it works good.
Maybe works Anagonist with tls 1.2 and Sensordata with tls 1.1 and then it is not working…
Hello @mandersp,
the firmware is supporting TLS 1.2. But with the limited cpu and memory we needed to limit the supported ciphers to the following:
TLS_RSA_WITH_AES_128_CBC_SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
TLS_RSA_WITH_AES_128_CBC_SHA
TLS_RSA_WITH_AES_256_CBC_SHA
All others would either use too much RAM or would need nearly a minute for the handshake. This would cause timeouts of the HTTP requests.
The available RAM of the NodeMCU limits the available cipher suites to the following:
TLS_RSA_WITH_AES_128_CBC_SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
TLS_RSA_WITH_AES_128_CBC_SHA
TLS_RSA_WITH_AES_256_CBC_SHA