MQTTS support in the suite-connector's local connection about suite-connector HOT 3 CLOSED

Thanks for the report. Actually, I see this as a global feature. It can be applied to all components which are connected to the local broker. In any case, I'll create new issues to cover them. About this particular one, I have some comments:

for enabling SSL on the MQTT connection (or stay with plain, if disabled)

This can be automatically handled by the broker URL i.e. if it starts with mqtts://... then it's MQTTS. Is it enough or something else is desired? Currently, we have localAddress property which can cover this scenario.

for setting the host and port where the local MQTT broker has been bound to listens for MQTTS connections

There is localAddress property which can do the job, host and port are part of the broker URL.

from suite-connector.

I assume reusing the local_address property is a better option as you mentioned. I was mistaken since in the current implementation it start with "tcp://"

And yes, you are totally right - I forgot the fact that both port and address are supplied in the value for the local_connection property. Indeed, no need to duplicate them.

from suite-connector.

Thanks a lot for your feedback. I'll update the issue description.

from suite-connector.