FMC003 - Custom MQTT Broker?

TELEMATICS
1

Hello,

we are currently planning a SaaS product that involves vehicle tracking, and Teltonika appears to be a very promising partner for our solution.

For evaluation purposes, we purchased a used FMC003 device, set up the configurator, and successfully updated it to the latest firmware — everything worked smoothly so far.

However, when configuring MQTT, we noticed that only AWS and Azure seem to be available as client types. For our use case, we require integration with a custom MQTT broker (Mosquitto), including support for authentication via username, password, and/or certificates.

Could you please let us know:

  • Is it possible to configure a custom MQTT broker on the FMC003?
  • If not, is this feature supported by other Teltonika devices?
  • Are there any firmware versions, advanced modes, or workarounds that would allow this setup?

This feature is critical for our project, and its availability may determine whether Teltonika devices can be used in our final product.

Thank you very much in advance for your support.

2

Hello @Thomas_Baier,

I hope you are doing well. Unfortunately, FM devices does not support custom broker and can be connected through AWS and Azure platforms on Base Firmware.

However, if you wish to integrate custom MQTT Broker I recommend you to coordinate with one of our Sales Manager so we can further assist you. If you don’t have any contacts with our Sale managers, please contact them on our official website https://teltonika-gps.com/ and click on the “Contact Us” button. When you will click, please fill the form and submit it.

Best regards,
Patrick S.

4

Thanks a lot for the feedback @Patrick_Sangalang, I’ll be reaching out to support anyway because of our project BUT:

I got it working:

  • Set up a VPS with Eclipse Mosquitto as the MQTT broker
  • Configured the broker with TLS using our own CA certificate
  • Created client certificates and signed them with the CA
  • Uploaded the CA, client certificate, and key to the tracker

So basically exactly the same setup we need for AWS Custom according to your instructions.
I’ve been testing it for 24 hours now and everything is working fine so far!

Is there anything on your side that would speak against proceeding this way?