April 2026 - OvmsDev - Open Vehicles

Firmware size approaching 4 MB limit
by Michael Balzer 18 Apr '26

18 Apr '26

Everyone, with the latest vehicle additions, the firmware size has now grown to 4,015,328 bytes in build 3.3.005-485-gc4664881. Our flash partitioning scheme is currently designed to provide three firmware partitions (factory, ota_0 & ota_1) of 4MB = 4,194,304 bytes each. So we've now got 178,976 bytes = ~4% left. Options beyond the 4 MB limit: a) split features, e.g. vehicle support, into two or more builds b) repartition into two firmware partitions of 6 MB each, reusing the factory partition for OTA c) switch to an ESP32 WROOM module with 32 MB flash (possible?) We've got some time left, new vehicles normally don't need that much space, I just wanted to raise awareness. Regards, Michael -- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926

5 43

OPENVEHICLES.COM server relocation
by Mark Webb-Johnson 11 Apr '26

11 Apr '26

Apologies for the late notice, but I need to urgently relocate the openvehicles.com server. This will likely cause some outages, as follows: Within the next few hours, the website will move. It will be unavailable during that time. Similarly, the api.openvehicles.com <http://api.openvehicles.com/> services (OVMS server v3 and mosquito) will move. There should be no interruption, other than DNS switch times (< 1 hour). I plan to take down the mail server early tomorrow morning (Hong Kong time), and it will likely be down for the most of the day. The will likely be night time for USA and Europe. Once all the mailing list data has been transferred, I will re-enable the mail server, and send an announcement here to confirm. Regards, Mark.

5 10

Help
by Tamás Kovács 04 Apr '26

04 Apr '26

I noticed the following on my car, a Hyundai Ioniq AE 28kWh. Unfortunately, the 12V battery discharged several times in the cold weather and I was looking for a solution to fix this. The selected car kept the car awake all the time and the consumption was > 500mA. Then I started switching the module to NONE when I wasn't driving it or charging it and then I ran into the error that polling doesn't work anymore. I'm attaching a command output. If I restart OVMS (module reset), it works fine again until I switch to NONE. -- Kovács Tamás

1 0

VW e-Golf: working on comfort CAN / climate scheduler support
by Andreas Jansson 04 Apr '26

04 Apr '26

Hi all, I'm Andreas, based in Sweden, owner of a 2019 VW e-Golf. I've just joined the list to let you know I'm working on adding comfort CAN support to the e-Golf vehicle module, with climate scheduler control as the primary goal. With VW discontinuing the Car-Net app due to the decommissioning of 2G, e-Golf owners lost the ability to trigger climate controls remotely. The car's built-in e-manager timer still works, but can't be changed remotely. That's the gap I'm trying to close. The existing e-Golf module (PR #1327) reads SoC, odometer, range and charge status via the diagnostic and powertrain CAN buses at J533, but the comfort CAN has remained unimplemented. A few things I'm leaning on: - thomasakarlsen/e-golf-comfort-can has comfort CAN traces from an actual e-Golf showing BAP traffic on the climate and scheduler LSGs - MIGINC/BAP_RE documents the MQB BAP protocol structure and Climatronic ID mappings - drgrandios/ovmslogs has annotated e-Up BAP frame decoding that maps closely to what appears in the e-Golf traces Cross-referencing these makes the scheduler write path look doable, and the e-Up implementation in OVMS looks like a useful reference. I'm working in a fork (investigation branch) where I'm collecting all relevant context and building a test suite before touching any car-side code. I have an OVMS module and will be doing all testing on my own car before anything comes near a PR. If there are other e-Golf owners on the list, or anyone who has looked at this before, I'd be glad to hear from you. Fork: https://github.com/slothish/Open-Vehicle-Monitoring-System-3-VWeGolf/tree/i… Andreas

2 1