Thank you for catching the inconsistency in the compose file. In our tests, it didn’t affect the operation of the containers, but it was a bug nonetheless.
In the latest version of the compose file, we fixed it. Furthermore, we switched to Kafka 3.9 and KRaft and, in general, made things a little faster and lighter. The main improvement is that we expose the broker to the host so you can connect to it from your own app.
Going to the MQTT issue, unfortunately, you did not provide enough details for us to figure out the issue.
Some generic advice:
The connector runs inside the Kafka docker container, under the lenses docker network. So, it can connect to the internet, other containers in the lenses docker network, and IP addresses that are routable via the docker host. If you run your MQTT server on your localhost as an example, it wouldn’t be the same localhost as the container’s. You could try to use your IP address (e.g., 192.168.1.10) to see if that works, though it depends on the configuration of your operating system and docker installation.
It can be useful to check Connect’s logs. You can do it like this:
Regarding updating the connector configuration, I will inform our development team. I think that the Connect API doesn’t inform us back when a change cannot be applied due to bad settings.