@Emil Thank you for your response.
I really hope the Twist SDK is released as soon as possible.

The next firmware update will allow for the previous call signature as well.

@Emil It's been what? A year? "Still on the roadmap" Yes of couse it should be! WHEN? WHEN? How hard is it to understand? We will probably sit here in 5 years and you will say "Still on the roadmap guys!!!".

See https://community.flic.io/topic/18460/button-name-23-characters

Wow 14 days go by with out a reply ?

Is anyone out there ??

@michael-4 Probably the response is too big to fit in the RAM memory given to your application. Do you know how big the response is?

@Emil It might be kind of insecure, but with some devices the only API supported. I would like to make requests to a WiiM device. Their API only supports HTTPS with a self-signed certificate. https://www.wiimhome.com/pdf/HTTP API for WiiM Mini.pdf

The Flic Hub configured with the Flic App UI is unable to make requests too, even when I turn off the validation. Is there some way to debug the hub's requests? Requests with curl work ok:

curl 'https://redacted.hostname.fi/httpapi.asp?command=setPlayerCmd:mute:0' --insecure -D - -vvv * Trying 10.0.0.39:443... * Connected to redacted.hostname.fi (10.0.0.39) port 443 * ALPN: curl offers h2,http/1.1 * (304) (OUT), TLS handshake, Client hello (1): * (304) (IN), TLS handshake, Server hello (2): * (304) (IN), TLS handshake, Unknown (8): * (304) (IN), TLS handshake, Request CERT (13): * (304) (IN), TLS handshake, Certificate (11): * (304) (IN), TLS handshake, CERT verify (15): * (304) (IN), TLS handshake, Finished (20): * (304) (OUT), TLS handshake, Certificate (11): * (304) (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 * ALPN: server did not agree on a protocol. Uses default. * Server certificate: * subject: C=CN; ST=Shanghai; L=Shanghai; O=linkplay; OU=linkplay; CN=www.linkplay.com; emailAddress=mail@linkplay.com * start date: Nov 14 12:24:18 2018 GMT * expire date: Nov 11 12:24:18 2028 GMT * issuer: C=CN; ST=Shanghai; L=Shanghai; O=linkplay; OU=linkplay; CN=www.linkplay.com; emailAddress=mail@linkplay.com * SSL certificate verify result: self signed certificate (18), continuing anyway. * using HTTP/1.x > GET /httpapi.asp?command=setPlayerCmd:mute:0 HTTP/1.1 > Host: redacted.hostname.fi > User-Agent: curl/8.4.0 > Accept: */* > * HTTP 1.0, assume close after body < HTTP/1.0 200 OK HTTP/1.0 200 OK < Date: Mon, 18 Mar 2024 19:29:14 GMT Date: Mon, 18 Mar 2024 19:29:14 GMT < Server: Boa/0.94.13 Server: Boa/0.94.13 < Connection: close Connection: close < Content-Length: 2 Content-Length: 2 < Last-Modified: Mon, 18 Mar 2024 19:29:14 GMT Last-Modified: Mon, 18 Mar 2024 19:29:14 GMT < Content-Type: text/html Content-Type: text/html < * Closing connection OK

Anyway, here's a use case to use https with no cert validation. 🕵♂

@mark-gitsham Currently that's not supported unfortunately. We have plans to add that option though.

@flic-16 Can you try this base64 encode method instead:

function base64Encode(str) { return Duktape.enc('base64', str); }

Hello Emil, is there any update on this? Thanks!

@abboberg Thx, and I do know that and used it in the past. I guess I forgot about this one. So much for remembering things. Of course, this means I need to configure each and every butten separately by hand instead of using the SDK for the whole hub.

Thx anyway!
Joachim

@oskar I try to get the hub to communicate with Touch Designer. As I understood I need to fill in the correct IP and Port in the first line of the main.js
Unfortunately I can't get it to work. The console tells me that the message is sent but nothing happens in Touch Designer. Any hints on that?
All the best, Pascal

@flameeyes Could you explain a bit how your ipv6-only hostname certificate is set up and works technically, and what CA signs it?

Hey @rs, very late to the party here.

The Flic hub does not appear to have third party integrations, although the Hue API looks pretty straightforward.

Did you find the Hue developer docs? https://developers.meethue.com/develop/get-started-2/

Did you have much luck/progress?

How can I help?

Hey @jonas-wallin, I’m very late to the party although more than happy to help (pro bono), if you still need the assist!

Hey @andy, a little late to the party here, looks like you’re trying to integrate to the old LightwaveRF Connect series.

I have Connect series in my house and have successfully used their API, although my Flic hub simply sends button clicks to a Raspberry Pi which does the integration to LightwaveRF.

Have you had any luck/progress on this? How can I help?

@martinm When an incoming FIN packet is received from the remote endpoint, the socket is automatically properly closed unless the allowHalfOpen option is set. If that option is set, the socket is properly closed at the time when both an incoming FIN has been received and the local user has called the end method on the socket (in any order). Nothing is done at garbage collection time, so if you use the allowHalfOpen property, remember to close the socket by calling the end method. If the allowHalfOpen is not set, you can still use the end method to send your own FIN packet.