Has anyone managed to connect Tulip Machine Data Source (or Connector) to either the Moquette MQTT broker within the device side AWS greengrass deployment or cloud side within AWS Iot Sitewise? I can set this up for both with MQTT Explorer, but when using the same client and certificates/keys all I get from Tulip is “Test Failed [500] Error: Timeout”
Occaisionally I get
“Test failed: Client connection test failed: write EPROTO C0B7F7A9B67F0000:error:0A000412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1586:SSL alert number 42”
(42? surely not… IYKYK)
which suggested a certificate issue - but it is the same certificate that works on MQTT Explorer.
When I setup Kepware IoTGateway with AWS greengrass I did have to do an odd extra certificate registration in Windows (which was undocumented and found by one of the AWS support people) - I thought something similar might be needed here but apart from the fields once MQTTS is selected there doesnt seem to be anywhere for additional certificate registration.