How to add a custom data converter to can2mqtt?

Copy the template from src/converter/mymode.rs, implement the Converter trait in Rust with towards_mqtt and towards_can methods, register it in all.rs, and use the mode name in your CSV config file.

Can can2mqtt handle CAN FD frames or only standard CAN?

The README doesn't mention CAN FD support; it likely only handles standard CAN frames up to 8 bytes, so check the source code or issues for any FD extensions, but out-of-the-box, it's limited to basic CAN.

What's the difference between can2mqtt and using SocketCAN tools directly with MQTT?

can2mqtt simplifies bridging by handling mapping and conversion automatically via CSV config, whereas SocketCAN tools require scripting for each message, making can2mqtt better for structured integrations but less flexible for raw data handling.

How to debug can2mqtt if messages aren't flowing?

Use the -v flag for verbose output, and employ external tools like mosquitto_pub/sub for MQTT and cansend/candump from can-utils for CAN bus, as recommended in the debugging section.

Is can2mqtt suitable for automotive OBD2 data integration?

Yes, if OBD2 data is transmitted over CAN bus; map the relevant CAN IDs to MQTT topics and use converters like uint322ascii for numeric data, but custom modes may be needed for specific OBD2 PIDs.

What MQTT brokers are compatible with can2mqtt?

Any standard MQTT broker supporting TCP connections, such as Mosquitto or EMQX; specify the connection string with username and password in the command line, as shown in the usage example.

Open-Awesome

can2mqtt

MITRustv3.0.1

A bidirectional, configurable bridge between CAN-Bus and MQTT with flexible data conversion modes.

GitHub

102 stars26 forks0 contributors

What is can2mqtt?

can2mqtt is a Rust-based bridge that connects CAN-Bus networks to MQTT brokers, enabling bidirectional communication between industrial/automotive CAN systems and IoT messaging protocols. It solves the problem of integrating legacy CAN devices into modern IoT ecosystems by mapping CAN IDs to MQTT topics with configurable data conversion.

Target Audience

Developers and engineers working with industrial automation, automotive systems, or IoT projects that need to interface CAN-Bus devices with MQTT-based messaging infrastructure.

Value Proposition

Developers choose can2mqtt for its simplicity, configurability, and extensibility—it provides a lightweight, self-contained solution with flexible data conversion modes and the ability to add custom converters without complex dependencies.

Overview

CAN-Bus -- MQTT bridge: bidirectional, configurable and extendable

Use Cases

Best For

Integrating automotive CAN-Bus data into home automation systems
Bridging industrial CAN devices to cloud-based IoT platforms
Prototyping CAN-to-MQTT interfaces for embedded systems
Converting CAN sensor data to MQTT for real-time monitoring
Creating virtual CAN interfaces for testing IoT applications
Extending legacy CAN networks with modern messaging protocols

Not Ideal For

Systems requiring dynamic, real-time configuration changes without service restarts
Projects needing advanced CAN bus message filtering or preprocessing before MQTT publishing
Teams without Rust programming expertise for custom data conversion modes
Environments preferring graphical or web-based management over command-line and CSV configuration

Pros & Cons

Pros

Bidirectional Flexibility

Supports full two-way communication with optional unidirectional modes, allowing tailored integration for specific use cases as shown in the direction mode settings.

Simple CSV Configuration

Uses a straightforward CSV file to map CAN IDs to MQTT topics, making setup quick and human-readable without complex programming.

Extensible Converter System

Allows users to implement custom conversion modes in Rust by following the template in the README, providing adaptability for unique data formats.

Lightweight and Portable

Offers statically linked binaries with no dependencies, easy to deploy on embedded systems like Raspberry Pi, as demonstrated in the installation instructions.

Cons

CAN Interface Complexity

Requires setting up socket-can interfaces, which can be challenging on non-Linux systems or with specific hardware, as admitted in the 'How do I get a socket-can interface?' section.

Limited Built-in Converters

Only includes basic conversion modes; advanced data handling necessitates custom Rust development, adding overhead for non-standard use cases.

Static Configuration Model

Relies on a static CSV file that must be edited and reloaded for changes, lacking dynamic or programmatic configuration options for real-time adjustments.

Frequently Asked Questions

Related Projects

zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨

Stars15,751

Forks2,053

Last commit2 days ago

Bambuddy

Your Bambu Lab. No Cloud. Your Rules. Self-hosted command center for Bambu Lab — from one A1 to an entire print farm.

Full featured Z-Wave Control Panel UI and MQTT gateway. Built using Nodejs, and Vue/Vuetify

Stars1,247

Forks252