Skip to content

Releases

v1.7.4 (beta)

v1.7.4 (beta) Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 17 Nov 22:35

Fixed

  • Shared I2C bus without a lock: the RTC (DS1307) and the motion sensor (MPU-6050) share one bus. The bus driver only locks a single transfer, not the read-out afterwards, so the gyro task (every 100 ms) and the web server reading the clock could get each other's bytes – wrong motion values (which also gate CAN sending) or a wrong time. A common lock now keeps write, request and read-out together. The PMU is on its own bus and not affected.

Added

  • Observation for "parked" (DID 0x210E): parked is still recognised by the exact value B = 8. Each value the car sends is written to the syslog once per start (CAN, "0x210E neu"), so the rule can be settled on real data later.

Flash in the browser: https://idmate-app.github.io/IDTelemetry/flasher/

v1.7.3 (beta)

v1.7.3 (beta) Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 17 Nov 22:31

Fixed

  • Web update failing silently: when the upload broke off (connection lost, restart during the upload), the page still showed a green "restarting"; rejected uploads (wrong password, variant, image) and write or check errors only went to the serial console. Now every failure goes to the syslog (OTA, with the reason and the bytes received), an upload that did not finish is reported at the next start, and the next start also tells whether the update took: "Update uebernommen: old -> new" or "Update NICHT uebernommen". The settings page remembers the running build before the upload, reloads after the restart and compares: it says whether the new firmware runs, and shows the result of the last update under the firmware slot. A new upload after a broken one no longer fails at the start.
  • CAN driver restarted on every voltage dropout: while driving, the PMU now and then reported the supply as gone for 1–2 s, and each time the CAN driver was reinstalled for listen-only mode and back (175 times on one trip). Listen-only mode now starts only after the supply has been gone for 3 s; back to normal operation is immediate. Sending stays blocked during any dropout as before.

Flash in the browser: https://idmate-app.github.io/IDTelemetry/flasher/

v1.7.2 (beta)

v1.7.2 (beta) Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 14 Nov 07:54

Added

  • Switch for the mobile network (Config → SIM / APN, on by default): off, the modem stays unpowered – no LTE, no data use, no network search. The stick then works like the Lite variant: it keeps collecting and hands the data over only in a WLAN from WiFi Upload; on the road the server does not see the car. Bluetooth (ABRP helper, live data) is unaffected, so the three data paths – server over LTE, ABRP over Bluetooth, display device over Bluetooth – can each be switched on their own. The modem's internal GNSS is off with it; the external GPS is not. Values learned by IDmate arrive over WLAN only. The status display shows LTE OFF. Takes effect after a restart.

Changed

  • End of a trip without the modem task (mobile network off): "supply voltage gone for 5 s → take the last point and stop recording" and the point "Schlafen" before sleeping were both done by the modem task. With the modem off the sleep logic does both itself, so a trip ends the same way with and without LTE. Nothing changes while the modem is on.

Flash in the browser: https://idmate-app.github.io/IDTelemetry/flasher/

v1.7.1 (beta)

v1.7.1 (beta) Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 14 Nov 05:59

Fixed

  • Two Bluetooth devices at once (ABRP on the phone and a display device on the tablet): the stick stopped advertising with the first connection, so a second device could not find it; and when one device disconnected, the ELM327 emulation took the other one for gone too and ABRP got no more answers. The stick now keeps advertising while a connection is free (3 in total), and "disconnected" means that no device is connected any more. A further device connecting no longer discards ABRP's command in progress.

Added

  • Switch for the ABRP helper (Config → BLE / ABRP, on by default): off, the stick does not offer the ELM327 emulation (service FFE0). With both the helper and the live data off, the stick does not advertise over Bluetooth at all. Takes effect after a restart.

Flash in the browser: https://idmate-app.github.io/IDTelemetry/flasher/

v1.7.0 (beta)

v1.7.0 (beta) Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 14 Nov 05:55

Added

  • Live data over Bluetooth for display devices (docs/live-ble.md): a paired device in the car – e.g. the IDmate app for Android Auto – gets state of charge, power, speed, odometer, temperatures, charging state and position straight from the stick, as CBOR telegrams over a GATT notification (1 s while driving, 30 s standing). Off by default (Config → BLE / ABRP), takes effect after a restart. The stick stays the one OBD master: the feature reads the telemetry cache and does not query the bus. The ELM327 emulation for ABRP is unchanged.
  • Pairing window: the telegrams go to a device paired with a six-digit code only (link encrypted and authenticated). The code is created when Pair a device is pressed on the config page, is valid for 3 minutes and for one attempt, and is not stored. A fixed code could be worked out from radio range in about 20 attempts; outside the window a secret random code is in force that is replaced after every attempt.

Flash in the browser: https://idmate-app.github.io/IDTelemetry/flasher/

v1.6.11 (beta)

v1.6.11 (beta) Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 07 Nov 05:57

Added

  • Which task ran when the watchdog fired: on a task-watchdog reset the stick now notes the task running on each core (RTC memory, survives the reset) and writes it to the syslog after the restart, e.g. WATCH Task-Watchdog nach 512s Laufzeit: Kern 0 lief "ipc0", Kern 1 "async_tcp". Diagnosis only, no change in behaviour (step 1 of the watch tower). Trigger: the crash of 2026-11-06 15:04 during a charging stop, where only the watchdog itself was visible in the backtrace.

Flash in the browser: https://idmate-app.github.io/IDTelemetry/flasher/

v1.6.10 (beta)

v1.6.10 (beta) Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 07 Nov 05:34

Changed

  • Dashboard odometer everywhere: the km offset from IDmate (fixed, the dashboard reads ~5 km more than CAN) is now added to the rows sent to IDmate too, not only to the answers to ABRP. The info telegram reports the offset in force ("odo"), so IDmate knows from when its km are dashboard km (the charge print stops adding its own +5 km from then on; needs IDmate 1.2.269). The switch on the configuration page now only covers the display SoC for ABRP.

Flash in the browser: https://idmate-app.github.io/IDTelemetry/flasher/

v1.6.9 (beta)

v1.6.9 (beta) Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 07 Nov 05:27

Fixed

  • Interior temperature 10 °C too high: the OBDb formula (A:B / 10) gave 31–32 °C with the climate set to 20 °C; ABRP shows the sensor 1–2 °C above the setting. Now A:B / 10 − 10 °C (log of 2026-11-06: 20.9–22.3 °C).

Flash in the browser: https://idmate-app.github.io/IDTelemetry/flasher/

v1.6.8 (beta)

v1.6.8 (beta) Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 07 Nov 05:23

Added

  • ABRP gets the SoC and odometer as shown in the car. IDmate learns both with "BMS lernen" (display SoC as a function of the CAN SoC, optionally with temperatures; odometer offset from the dashboard km typed in once) and sends them to the stick, retained on <topic>/cfg, encrypted with the same AES key as the telegrams. The stick applies them only to its Bluetooth answers to ABRP (DID 028C SoC, 295A odometer); what it sends to IDmate stays raw, the learning needs it. Received over LTE and WiFi, stored in NVS, shown on the configuration page (BLE / ABRP), switchable there ("ABRP bekommt SoC und km-Stand wie im Auto", default on). Needs IDmate 1.2.267.

Flash in the browser: https://idmate-app.github.io/IDTelemetry/flasher/

v1.6.7 (beta)

v1.6.7 (beta) Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 06 Nov 20:54

Added

  • Energy content, auxiliary power and cabin temperature are now decoded and sent (payload bits 20–22, already understood by IDmate). Formulas from the open vehicle database OBDb (Volkswagen-ID3) and checked against this car's raw bytes:
    • 2AB8 (ECU 710): bytes C:D × 25 Wh = energy content (kWh). Check: 54.5 kWh at SoC 65.9 % and 51.75 kWh at 62.4 %, both ≈ 83 kWh at 100 %.
    • 0364 (ECU FC0076): signed A:B / 10 = power of all HV auxiliary consumers (heater, A/C, 12 V converter), kW. Log: 0.4–1.6 kW.
    • 2613 (ECU 746): signed A:B / 10 = interior temperature, °C.

Flash in the browser: https://idmate-app.github.io/IDTelemetry/flasher/