Sensibo binding - can't read pod status

I tried to use the Sensibo binding for Sensibo Sky,

  • Platform information:
    • Hardware: RPi 3 B+
    • OS: openhabian
    • Java Runtime Environment: openjdk version “1.8.0_152”
    • openHAB version: openHAB 2.4.0~20181104134837-1 (Build #1412)

To get the sensibo API working I use the followinG:

var curlCommand1 ="curl -sSH \"Accept: application/json\" \"https://home.sensibo.com/api/v2/users/me/pods?apiKey=<API-KEY>\"" 

var String PodID

/*** Read Pod ID ***

rule "Read Pod ID"

  when
    System started
  then
  logInfo("rule_read_PodID", "PodID at start = " + PodID)
  try {          
    var String PodsResult
    do {
      logInfo("rule_read_PodID", "curl sentence is \r\n" + curlCommand1)
	  PodsResult = executeCommandLine(curlCommand1, 2000)
	  logInfo("rule_read_PodID", "PodID = " + PodsResult)
    } while (!PodsResult.contains('"status": "success"'))

    PodID = transform("JSONPATH", "$.result[0].id", PodsResult)
  }

  catch(Throwable t) {
    logError("ReadPodID", "Error was caught: {}", t)
  }

end


The initial curl-command works fine, and returns my Pod ID (8 characters):

2018-11-28 22:47:46.745 [INFO ] [ome.model.script.Read Sensibo Pod ID] - receives {"status": "success", "result": [{"id": "<myID>"}]}

Then in the next read attempt, I should read the status.

var curlCommand2 ="curl -sSH \"Accept: application/json\" \"https://home.sensibo.com/api/v2/users/me/pods?podsID=<podsID>/acstates?apiKey=<API-KEY>&limit=1&fields=acState -v\""

var String PodStatus

/*** Read Sensibo State ***

rule "Read Sensibo State"

  when
    System started
  then

  Thread::sleep(10000)

  try {
    var String PodStatus 
      
    do {
      Thread::sleep(5000)
	  logInfo("rule_read_SensiboState", "curl sentence is \r\n" + curlCommand2)
	  PodStatus = executeCommandLine(curlCommand2, 5000)
	  logInfo("rule_read_SensiboState", "PodStatus = " + PodStatus)

    } while (!PodStatus.contains('"status": "success"'))
    ..

This does not look as good:

2018-11-30 22:49:51.011 [INFO ] [.model.script.rule_read_SensiboState] - PodStatus = curl: (1) Protocol ""https" not supported or disabled in libcurl

If I use the same https request as supplied in the “curl-command2” I get the correct reply from the API, but not from the rule or when using the full curlCommand2 from the consol

With -v attached to the curl command in the consol - I get:

* Trying 54.77.241.118...
* TCP_NODELAY set
* Connected to home.sensibo.com (54.77.241.118) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* NPN, negotiated HTTP1.1
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Unknown (67):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: CN=home.sensibo.com
*  start date: Nov  4 14:14:05 2018 GMT
*  expire date: Feb  2 14:14:05 2019 GMT
*  subjectAltName: host "home.sensibo.com" matched cert's "home.sensibo.com"
*  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
*  SSL certificate verify ok.
> GET /api/v2/users/me/pods?podsID=Cxch4i7t/acstates?apiKey=I0V9XUqZ3npef5NXadoszBWhLN3Qdz&limit=1&fields=acState HTTP/1.1
> Host: home.sensibo.com
> User-Agent: curl/7.52.1
> Accept: application/json
>
< HTTP/1.1 401 Unauthorized
< Server: nginx
< Date: Fri, 30 Nov 2018 15:28:29 GMT
< Content-Type: text/plain
< Transfer-Encoding: chunked
< Connection: keep-alive
< Vary: Cookie
< X-Frame-Options: SAMEORIGIN
<
* Curl_http_done: called premature == 0
* Connection #0 to host home.sensibo.com left intact
login_required

Is there anyone who have seen this and solved the issue?