Error response if I disable the Exosite cloud

IoT Connectors / Product as a Service
1

Currently, I have multiple IoT devices running on the Exosite cloud and I’m having an iOS app that runs with the device and cloud.

Due to a reason, if I shut down my Exosite cloud services and shift to my own server, in that case, the IoT devices that are currently on Exosite cloud and using Exosite APIs, what error they will receive? Is there any standard error code or any other exception that Exosite could return in the request of an Exosite API?

Thanks in advance…

2

Sorry to hear you will be shutting down your Exosite account. Let us know if we can help with some other path.

On to answer your question though.

When your device is talking to our Device API (assuming HTTP for now since not specified), you are going to get 204 responses as you are writing values to a resource.

> POST /onep:v1/stack/alias HTTP/1.1
> Host: <IOTCONNECTOR_ID>.m2.exosite.io
> Content-Type: application/x-www-form-urlencoded
> X-Exosite-CIK: <TOKEN>
> Accept: */*
> Content-Length: 89

| data_in={"0001"}

Typical Response on successful write to a resource

< HTTP/1.1 204 No Content
< date: Tue, 17 May 2022 15:27:19 GMT
< server: Murano

If you were to delete that IoT Connector, your device clients will begin to get SSL handshake errors - there is no HTTP response.

If you tested with a cURL command from a shell for example:

curl --request POST \
  --url https://<IOTCONNECTOR_ID>.m2.exosite.io/onep:v1/stack/alias \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'X-Exosite-CIK: <TOKEN>' \
  --data 'data_in={"0001":0}'

response:

curl: (35) error:1404B410:SSL routines:ST_CONNECT:sslv3 alert handshake failure

Each device client will handle this slightly differently depending on the libraries / code language.

3

Hello Mike,

Thanks for the reply. The information that you provide is very helpful for us.