The next firmware update will allow for the previous call signature as well.
Group Details Private
FlicTeam
Employees at Shortcut Labs
-
RE: IRTCP v1.0.0 (Hub server for using IR module via HTTP)
-
RE: Question re Validate Certificate(s) option in Internet Request
@willliam The Flic Hub can generally connect to servers that use Let's Encrypt certificates so there must be some other error.
The Wireshark tool cannot be run from within a web browser. You must download the software and run it. I'd appreciate if you could try this. After starting the program, you select "Capture" on your wifi or ethernet interface. Then it starts to log packets. At this time, either run the curl command as instructed in my previous post. Or, if your TLS server runs on the same computer as the one running Wireshark, please try to access the https server using the Flic Hub. Then stop the capture, save, and send me/upload the capture file.
-
RE: Question re Validate Certificate(s) option in Internet Request
@willliam Can you instruct me how I can myself generate such certificates in order to be able to reproduce the problem?
Alternatively run
curl --tls-max 1.2 https://YOUR_URL
in the terminal while capturing the traffic using Wireshark and upload the trace file. -
RE: TlsFailure - Latenode Webhook
@dhtbrowne I just tried. Seems to work fine now.
-
RE: Question re Validate Certificate(s) option in Internet Request
@willliam Can you give me a domain name/url to test with?
-
RE: Event Logs?
@bytheedgeuk We will investigate this. I'll see if we can change to make it possible to omit the value entirely instead of sending an empty bytestring.
-
RE: TlsFailure - Latenode Webhook
@dhtbrowne The server sends an invalid certificate chain according to https://datatracker.ietf.org/doc/html/rfc5246 7.4.2 Certificate certificate_list:
This is a sequence (chain) of certificates. The sender's certificate MUST come first in the list. Each following certificate MUST directly certify the one preceding it.
This is a trace when connecting to that server:
As you can see, the second certificate is incorrectly duplicated so hence the last one does not certify the one preceeding it.If you go to https://www.digicert.com/help/ you can also see that the server is incorrectly configured (second certificate is duplicated):
I suggest you to reach out to the website owner to fix the problem.
-
RE: Event Logs?
@bytheedgeuk could you try an empty PIN by just writing "hex:" in the field?
-
RE: Event Logs?
@bytheedgeuk It's a bit annoying that the PIN code is defined by the Matter standard to be an arbitrary byte array and not a 6-digit integer or something. Byte arrays are entered in hex format using the syntax "hex:010203" to represent the byte aray [1, 2, 3].
Therefore, if your PIN code consists of the ASCII string "123456", then the PINCode field should be written as hex:313233343536. Note that the PINCode field is optional though according to the Matter standard.
Note that the PIN code is not the setup code written on the Matter sticker (with QR code) but a code you set yourself in the lock manufacturer's app (assuming the lock supports a PIN code).
-
RE: Event Logs?
@bytheedgeuk no such log is available unfortunately.
What smart lock are you using and how have you configured your flic action?