I’m building an open-source drive and charging log on top of BMW CarData — the layer above the sensors. It turns the stream into actual drives and charging sessions, with history, cost per session, and efficiency over time. Roughly TeslaMate, but CarData-native.
Here’s where the UI is at, running on invented data for now:
Thanks to the CarData-via-MQTT guide at BMW CarData directly via MQTT and to dj0abr for the bridge — that’s what this builds on.
Now the reason I’m posting. My own iX3 doesn’t arrive until March 2027, so I have no real data to build against, and writing the derivation logic against invented fixtures is a reliable way to get it wrong.
What would help enormously is a raw MQTT dump from an existing setup. Even 24 hours is useful; a week covering a few drives and at least one charge would be ideal.
If you’re already running dj0abr/bmw-mqtt-bridge against your own Mosquitto, it’s roughly:
mosquitto_sub -h <broker> -t '<vin>/#' -v > dump.log
Happy to take it with the VIN and coordinates stripped. What I actually need is timing, ordering, gaps, and how the stream behaves when the car goes to sleep. I’m specifically after the messy parts: missed session endings, duplicate messages, reconnects after token refresh.
In return: it’s open source, you get early access, and I’ll credit anyone who contributes data.
Any model welcome — I don’t need an iX3 specifically. Older cars are just as useful for this.