Routing Your Data: MQTT vs Webhooks

The WiCAN Pro allows you to send your vehicle's telemetry data to external servers. But with multiple ways to send this data, which one should you choose?

Here is a breakdown of the available methods and when to use them.

1. MQTT (Best for Real-Time & Home Assistant)

MQTT is a lightweight, real-time messaging protocol. It uses a "publish/subscribe" model, requiring a central server called an MQTT Broker (like Mosquitto).

  • How it works: The WiCAN maintains an open connection to the broker and streams data instantly as it polls the car.
  • Pros: Extremely fast, uses very low bandwidth, and is natively supported by Home Assistant. Perfect for creating live, real-time dashboards.
  • Cons: Requires you to set up and host an MQTT broker.
  • When to use it: Use MQTT if you are integrating with Home Assistant, building a local live dashboard, or using the WiCAN primarily on your own home Wi-Fi network.

2. Webhooks / HTTP POST (Best for Cloud & Custom Servers)

A Webhook is a standard web request. Instead of maintaining a constant connection, the WiCAN packages the data into a JSON file and "pushes" it to a specific web address.

  • How it works: Every time the WiCAN gathers data, it opens a connection, sends the JSON payload to your server's URL, and closes the connection.
  • Pros: Universally supported. Almost every modern web service, custom database, or cloud platform can accept a Webhook without needing a dedicated messaging broker.
  • Cons: Slightly higher bandwidth and overhead than MQTT. Not ideal for millisecond-level real-time data.
  • When to use it: Use Webhooks if you are sending data to a custom web app, a cloud database, or a cloud automation platform.

3. Native Integrations (e.g., ABRP)

The WiCAN Pro also supports sending data directly to specific third-party services, like A Better Routeplanner (ABRP) for EV trip planning.

  • How it works: You simply paste your ABRP user token into the WiCAN Automate interface. The device handles all the formatting behind the scenes to match exactly what the ABRP servers expect.
  • When to use it: Use this when you want a plug-and-play solution for a supported app without needing to build your own server or broker.
Table of Contents