I’m trying to use the Webhook integration to send uplink data to my device for further processing. Although the base url is configured to use an https://x.x.x.x:8443 connection it is unsuccessful due to my device having a self-signed certificate, reported error is “x509_certificate_invalid”.
Is there a way I can configure the integration to ignore this error, or connect using http rather than https?
No to either.
But you could use LetsEncrypt to provide a real certificate.
That’s a pity, I don’t think my end device (Tridium JACE 9000) has the option to use LE, people have tried in the past and failed. Even if I could get a valid cert from them installed this then requires a reboot of the device to recognise the newly installed cert, I don’t have this option every 60-90 days
I take it you mean your end point - in the confusion on nomenclature end device = device = node = sensor = thingy-ma-jig.
That’s a bit of an omission on their part and perhaps something they could build in to the firmware.
The other alternatives are to seek out a low cost certificate that can run for a while & install that.
Or send to a small web server that you can configure to proxy for your Tridium - web server receives uplink and then passes it on to your box. I have that setup for such things - domain name + hosting for £8/year.
Thanks, I’ll look in to these options. It’s never simple