News - Dexter's Weboratory

Partitionierungs-Schema

2026-08-05T18:26:00+02:00

Im Zuge der letzten Veröffentlichungen ist das OVMS-v3-Firmware-Image bis nahe an die ursprüngliche Grenze von 4 MB für die Anwendungspartition herangewachsen, wie sie im alten Partitionierungsschema (factory, ota_0, ota_1 – jeweils 4 MB auf einem 16-MB-Flash-Speicher) festgelegt war. Um weiterhin neue Funktionen und Fehlerbehebungen bereitstellen zu können, haben wir ein aktualisiertes Partitionierungsschema mit größeren Anwendungspartitionen eingeführt; die Firmware-Versionen ab 3.3.006 sind nun für den Betrieb mit diesen erweiterten Partitionen ausgelegt. Module, die weiterhin das alte 4-MB-Partitionierungsschema verwenden, werden bald keine neueren Firmware-Images mehr aufnehmen können und somit keine weiteren OTA-Updates mehr erhalten.

Dementsprechend kann die OVMS-Firmware-Version 3.3.006 (oder höher) eine Push-Benachrichtigung an Sie senden, in der Sie aufgefordert werden, ein Upgrade des Partitionierungsschemas durchzuführen:

Note
The module is running an outdated flash partitioning scheme.
OTA updates will soon stop working due to its 4MB size limit.
Upgrading is recommended to leverage the limit to 7MB.
To upgrade, open the web UI, menu Config -> Partitioning.

Sie können sich natürlich dafür entscheiden, die alte Partitionierung beizubehalten; das Modul wird damit weiterhin funktionieren. Allerdings ist Version 3.3.006 die letzte Version, die in das alte Partitionierungsschema passt; künftige Versionen lassen sich ohne ein Upgrade nicht mehr installieren.

Um auf dem aktuellen Stand zu bleiben, müssen Sie Ihr Modul zunächst auf die neueste MAIN- oder EAP-Firmware-Version aktualisieren und anschließend über die Web-Oberfläche (Config → Partitioning) ein einmaliges Partitionierungs-Upgrade durchführen – wie in den OVMS-Downloads und der OTA-Anleitung beschrieben. Bei diesem Upgrade-Vorgang wird der Flash-Speicher des Moduls neu partitioniert und Ihre Installation migriert, sodass künftig auch größere Firmware-Images verwendet werden können.

Sobald das Partitionierungs-Upgrade erfolgreich abgeschlossen ist, erhält Ihr OVMS-Modul wie gewohnt weiterhin MAIN-, EAP- oder EDGE-Updates. Sie profitieren von laufenden Verbesserungen und Fehlerbehebungen, ohne durch die bisherige Größenbeschränkung von 4 MB eingeschränkt zu sein. Wenn Sie unsicher sind, welches Partitionierungslayout Ihr Modul verwendet, oder Hilfe beim Upgrade benötigen, konsultieren Sie bitte die Online-Dokumentation von OVMS oder die Download-Seite Ihres Firmware-Anbieters bzw. wenden Sie sich vor der Durchführung an den Support.

Einzelheiten zur Durchführung des Partitionierungs-Upgrades finden Sie in der OVMS-Dokumentation unter:

https://docs.openvehicles.com/en/latest/userguide/partitioning.html

Mit besten Grüßen
Ihr & euer OVMS-Entwicklerteam

Firmware-Release 3.3.006

2026-07-18T10:02:00+02:00

Die Firmware Version 3.3.006 liegt nun in "main" für alle Nutzer bereit.

Änderungen in dieser Version:

- smart EQ:
    As soon as the 12V trickle charge begins, a timestamp is generated and stored in `m_12v_trickle_charge_times`.
    The counted value is set in `xsq.12v.trickle.count`.
    Within `Ticker3600`, a routine removes all timestamps older than 24 hours and updates `xsq.12v.trickle.count` by -1.
    New metric:
      xsq.12v.trickle.count                  -- Count of 12V trickle-charge cycles in 24h
    updated metric:
      xsq.bms.contactor.cycles (vector int)  -- [0]=max, [1]=now, [2]=consumed, [3]=diff, [4]=1h_counted_changes
    New config:
      [xsq] bms.alert.above.cycles (int)     -- alert threshold for cycles counted; default 50000
      [xsq] bms.contactor.1h.limit (int)     -- limit for contactor cycles changes per hour for alerting; default 8
- OTA/firmware: include tools to mitigate 4MB firmware size limit by upgrading the partitioning scheme;
    for details see: https://docs.openvehicles.com/en/latest/userguide/partitioning.html
- VW e-Up: extended battery health / aging info (with web UI integration): total battery age,
    charge time counters AC/DC and parked battery state times (by SOC & temperature ranges)
    (inspired by OBD Amigos)
  New metrics:
    xvu.b.time.charged.ac                 -- Total time charged AC [Hours]
    xvu.b.time.charged.dc                 -- Total time charged DC [Hours]
    xvu.b.time.parked                     -- Total time parked [Days]
    xvu.b.time.parked.cold                -- Total time parked below  0 °C [Days]
    xvu.b.time.parked.empty               -- Total time parked below 10% SOC [Days]
    xvu.b.time.parked.full                -- Total time parked above 90% SOC [Days]
    xvu.b.time.parked.hot                 -- Total time parked above 30 °C [Days]
    xvu.b.time.parked.state               -- Park times matrix: 6 SOC x 8 temperature ranges
    xvu.b.time.total                      -- Total battery age [Days]
- Server V3 (MQTT): AWS IoT Core compatibility fixes:
    - mTLS client certificate authentication for MQTT brokers that require it
      (e.g. AWS IoT Core). Configured via web UI (Config → Server V3).
    - Fixed MQTT CONNECT to omit empty username/password for certificate-only auth.
    - New option "retain.depth.limit": disables RETAIN on deep topics (>8 segments)
      for brokers like AWS IoT Core that reject them.
- Autostart: added init option "minimal" to boot with just basic networking as configured; this is
    now the first fallback in case of repeated early crashes, aiming at keeping the module reachable
    in case of a bug in a higher level module / configuration. Auto init will be disabled only if
    early crashes continue in minimal mode.
  Config extension:
    [auto] init                           -- "no" / "yes" / "minimal" (default "yes")
- Server V3: the MQTT client ID to use can now be configured. While not normally necessary, changing the
    client ID may be necessary to discard an existing MQTT server session when changing the username.
  New configs:
    [server.v3] clientid                  -- MQTT client ID, default: vehicle ID
- New vehicle: Cadillac CT5
    Initial support includes: VIN, fuel level (SOC), and run state.
    The CT5 uses the GM Global B platform which requires authentication
    so polling isn't currently possible. Instead we listen to CAN
    bus #5 which is present on the audio amplifier connector X3 in
    the trunk.
- Command framework: add command to run commands in a background task, allowing the execution of long
    running commands via the server v2/v3 command channel or ssh without triggering the watchdog.
    Example: run ota flash http ; module reset
    Commands will be interpreted just as in a regular shell/console, so can be abbreviated etc.
    Note: using this is not strictly necessary for the builtin web shell & HTTP REST API, as the web
      framework already uses an individual task for each command execution, but it's still possible.
  New command:
    run [-n] [-S] [-P]  [; ]
      Run command(s) in background task (log tag: 'bgshell'), send output via notification.
      Use a single ';' to separate multiple commands.
      Notification default mode (type) is 'info' (-ni), -ns = 'stream', -no = off.
      Notification subtype scheme: 'cmd.full.command.name'
      Default task stacksize is 6144, default task priority is 5.
- chevrolet_c6_corvette: Add TPMS support.
- swcan: module included in the default build configuration. SWCAN bus must be initialized manually 
	from the car module. During initialization, CAN3 will be deinitialized and CAN4 used for SWCAN. 
	Configuration "use_swcan_adapter" has been added to Voltampera and Boltev vehicles.
- New vehicle: Volkswagen e-Golf via J533 connector
    Initial support added for: Odometer, SoC, Est. Range, Charge Status, PRNDL State, VIN
    https://docs.openvehicles.com/en/latest/components/vehicle_vwegolf/docs/index.html
- Module: added heap integrity check + alert command for usage in e.g. custom event scripts,
    enables adding checks on specific system events and/or with higher frequency.
    Example: perform heap integrity check when the server V2 gets stopped:
      vfs echo "module check alert" /store/events/server.v2.stopped/90-checkheap
  Command extension:
    module check alert                    -- Check for and send one-off alert on heap corruption
- VFS: added echo command to write a line to a file
  New commands:
    vfs echo                  -- Write  to , creating/replacing the file
- smart EQ:
  New commands:
    xsq ed4scan                           -- Output ED4scan-like BMS diagnostic data
                                             (battery health, SOC kernel data, cell resistance,
                                             contactor cycles, temperatures, voltages)
- Module: add heap tracing tools -- NOTE: heap tracing will for now not be enabled by default on user builds.
    This is meant to be used by developers to track down heap corruptions. If you encounter many
    random crashes, ask your maintainer to provide a debug build to you with heap tracing enabled,
    and let her/him guide you through the usage, or grant him/her remote access to your module.
    See: https://docs.espressif.com/projects/esp-idf/en/v3.3/api-reference/system/heap_debug.html
  New commands:
    module trace start [num_records]    -- init & start heap tracing, num_records defaults to 500
    module trace stop                   -- stop heap tracing & cleanup memory
    module trace pause                  -- pause heap tracing for inspection
    module trace resume                 -- resume heap tracing
    module trace status                 -- show current status
    module trace dump                   -- dump allocations & frees recorded
- Module: added heap integrity alert, added task ownership to heap check report, added task handles to
    task log, added debug options to web UI (Config → Notifications)
  New config:
    [module] debug.heap.alert           -- [bool] perform heap check every 5 minutes, send alert on
                                            corruption (default: no)
  New event:
    system.heap.corrupted               -- Heap corruption detected
  New notification:
    [alert] debug.heap.corruption       -- Heap corruption details
  Command extension:
    test heapcorruption   -- default: 'restore', use 'keep' to test heap alert
  History record extension:
    "*-OVM-DebugTasks" v2: per task record extended by 
- Module framework: enable remote use of the system's heap corruption test, i.e. command "module check"
    can now be used within any shell or command channel, not just the USB console.
  New command(s):
    test heapcorruption -- test for heap integrity checker
- Workaround for iOS Open Vehicle App 1.8.6
    Workaround for legacy iOS App, hiding zero/negative temperatures to keep other TPMS data visible.
    This workaround only manipulates the TPMS temperature metric in message W.
- New vehicle: FIAT eDoblo via OBD-II port
    Initial support added for:
      VIN, SoC, SoH
      Door status
      Odometer
      HV, LV battery voltage
      temperatures
- TPMS framework: added sensor mapping commands for wheel rotation/swap scenarios
    New commands:
      tpms map status   -- show current TPMS sensor-to-wheel mapping with details
      tpms map get      -- machine-readable output like message Y without header MP-0 Y
      tpms map set      -- remap sensors using wheel position names (e.g., fl=rr fr=fl rl=fr rr=rl)
      tpms map reset    -- reset mapping to default (e.g. FL=0, FR=1, RL=2, RR=3)
    Config: [vehicle] tpms.xx (sensor index per wheel position, layout by GetTpmsLayout())
    Note: requires vehicle to implement UsesTpmsSensorMapping() returning true
- New vehicle: Maxus T90 EV (MT90) via OBD-II port
    Initial support added for:
      VIN, SOC, SOH & READY state
      AC plug / pilot detection
      Lock status
      Odometer
      Temperature metrics
- Renault Twizy: support added for standard metric "v.e.aux12v" (base system awake),
    OBD polling (DTC checks) enabled already with base system awake
    (= DTC available in STOP conditions)
- VW e-Up: enable framework climate preconditioning scheduler web UI
    (Note: climate control only available with T26 connection)
- Vehicle framework: Scheduled precondition control with duration support
    Centralized implementation for all vehicles with per-vehicle override capability.
    Supports multiple time slots per day with individual duration settings (5-30 minutes).
    Global enable/disable switch with config persistence.
    copy function to duplicate schedules across multiple days.
  New commands:
    climatecontrol schedule set    -- Set schedule for a day, times format: HH:MM[/duration][,HH:MM[/duration],...]
                                                     Examples: "07:30", "07:30/10", "07:00/5,17:30/15"
                                                     Duration in minutes
    climatecontrol schedule list               -- List all configured schedules with next scheduled event
    climatecontrol schedule clear     -- Clear schedule for specific day or all days
    climatecontrol schedule copy  
                                               -- Copy schedule from one day to others
                                                     Examples: "mon tue-fri", "fri sat,sun"
                                                     Supports range syntax (tue-fri) and comma-separated lists
    climatecontrol schedule enable             -- Enable scheduled precondition (global switch)
    climatecontrol schedule disable            -- Disable scheduled precondition (global switch)
    climatecontrol schedule status             -- Show schedule status and configured times
  New config:
    [vehicle] climate.schedule.           -- Schedule for day (mon/tue/wed/thu/fri/sat/sun)
                                                  Format: HH:MM[/duration][,HH:MM[/duration],...]
    [vehicle] climate.precondition             -- Enable/disable scheduled precondition (bool, default false)
  precondition scheduler features: (ported from ZOE PH2)
    - Multiple times per day support (comma-separated: "07:30/5,17:45/10")
    - Individual schedule per weekday
    - Automatic trigger based on system time
    - Integration with existing climate control
    - Web UI configuration page at /cfg/preconditionschedule
    - Automatic restart mechanism for extended runtime (configurable HVAC duration)
    - Duplicate prevention (same time won't trigger twice)
    - Copy function for quick weekly schedule setup
- smart EQ:
    Add multiple CAN frame parsers for energy and charging metrics
    Add automatic 12V ADC factor recalculation history tracking
- Renault Zoe Ph2:
    - Added temperature-based PTC auto-enable feature
      - Auto-enables PTCs when outside temperature in range (default 9.5-20°C)
      - Configurable via Web UI or console commands
    New config:
      [xrz2] auto_ptc_enabled           -- [bool] enable auto-PTC based on temperature (default: no)
      [xrz2] auto_ptc_temp_min          -- [float] minimum temperature for auto-enable (default: 9.5°C)
      [xrz2] auto_ptc_temp_max          -- [float] maximum temperature for auto-enable (default: 20.0°C)
    Restructured the entire codebase for improved readability
    Removed the water pump lifetime metric and water pump reset command
    Added custom metrics for motor/inverter state monitoring (rotor/stator currents and temperatures)
    New metrics:
      xrz2.m.temp.stator1               -- Stator temperature sensor 1 (°C)
      xrz2.m.temp.stator2               -- Stator temperature sensor 2 (°C)
      xrz2.m.temp.rotor.raw             -- Rotor temperature raw estimation (°C)
      xrz2.m.temp.rotor                 -- Rotor temperature estimated (°C)
      xrz2.m.current.stator.u           -- Stator phase U current, absolute value (Amps)
      xrz2.m.current.stator.v           -- Stator phase V current, absolute value (Amps)
      xrz2.m.current.stator.w           -- Stator phase W current, absolute value (Amps)
      xrz2.m.current.rotor1             -- Rotor current sensor 1 (Amps)
      xrz2.m.current.rotor2             -- Rotor current sensor 2 (Amps)
      xrz2.m.rotor.resistance           -- Rotor reference resistance (Ohms)
      xrz2.m.rotor.voltage              -- Rotor excitation voltage I×R calculated (Volts)
    Added manual PTC activation for heating while charging or when the compressor is defective
    Added a lighting command, similar to the key fob button
    Added a coming-home function
    Added remote preconditioning via the key fob
    Added PV/Solar charging mode to suppress per-session charge start/stop notifications on PV-controlled wallboxes
      Sends a single summary notification when the charge cable is unplugged, including the total kWh charged across all sessions
    Added DC/DC activation and keep-alive via OVMS
      Enables and keeps the HV system alive regardless of lock status or whether the Zoe was previously asleep
      Automatically activates the DC/DC converter to recharge the 12 V battery when the voltage threshold is reached
      Added configurable post-ignition DC/DC runtime (0–60 min) to reduce contactor wear during short stops or when preparing the Zoe for a trip
      Added manual DC/DC activation with configurable SOC and time limits, ideal for powering 230 V inverters, for example while camping
    Added a working trunk unlock command
    Added TXCallback to verify successful message transmission
    Added ECU feedback handling instead of sending messages blindly; currently implemented only for the coming-home function
    Added wake-up messages for when the CAN bus is asleep
- Wifi: added command to restart the Wifi network into the default (autostart) config,
    and added default for the AP SSID on the apclient mode.
  New/changed commands:
    wifi restart                        -- Restart Wifi network into autostart config
    wifi mode apclient                  -- Parameter  is now optional, defaults to autostart config
- Cellular: added option to restrict the modem network type to 2G/3G/4G. Restricting
    the network type may help in case of frequent network losses / reconnects.
  New config:
    [modem] net.type (string)           -- auto/2G/3G/4G, default/empty=auto
- smart EQ:
    Hardened poll reply & CAN parsing (REQUIRE_LEN / DLC guards, corrected switch fallthrough).
    Automatic 12V ADC factor recalculation using CAN 12V voltage.
    New config:
    [xsq] calc.adcfactor (bool)             -- activate sutomatic ADC factor recalculation (default false)
    [xsq] adc.samples (int)                 -- default 4
- Cellular: GPS auto pause on parking reactivate when Car awakes. This reduces time to first GPS fix.
  New config:    
    [modem] gps.parkreactawake (bool)   -- GPS is switched on for the gps.parkreactlock (minutes) time when the GPS parking pause is active and the car wakes up (default: no)
- server V3 (changes):
    Chunked metric transmission to limit burst size:
      TransmitAllMetrics(): up to 100 metrics per tick, continues next call.
      TransmitModifiedMetrics(): up to 150 modified metrics per tick.
    Priority path for GPS/time metrics with optional extras:
      Default priority: v.p.latitude, v.p.longitude, v.p.altitude, v.p.speed, v.p.gpsspeed, m.time.utc
    New update Command:
      server v3 update priority                   -- send prioritized metrics
- Webserver: Server V3 (MQTT) config page
    Added priority sending controls:
      [server.v3] updatetime.priority (bool)      -- prioritize selected metrics while the vehicle is awake, update in car on interval
      [server.v3] updatetime.immediately (bool)   -- metrics should be sent immediately when they change
      [server.v3] metrics.priority (string)       -- comma separated metric names; supports * and prefix* wildcards
      [server.v3] metrics.include (string)        -- comma separated metric names; supports * and prefix* wildcards
      [server.v3] metrics.exclude (string)        -- comma separated metric names; supports * and prefix* wildcards
      [server.v3] metrics.include.immediately (string)    -- comma separated metric names; supports * and prefix* wildcards
      [server.v3] metrics.exclude.immediately (string)    -- comma separated metric names; supports * and prefix* wildcards
      [server.v3] queue.sendall (int)             -- queue size send 'sendall' metrics, default 100 metrics per ticker1
      [server.v3] queue.modified (int)            -- queue size send 'modified' metrics, default 150 metrics per ticker1
- Webserver: adjustable websocket TX job queue size to accomodate high update
    frequencies / stream payload sizes and/or slow clients / client connections
  New config:
    [http.server] ws.txqueuesize  -- in jobs, default 50
- server V3 (additions):
    Added MQTT client on-demand requests to reduce baseline data usage (authenticated per client, with basic rate-limiting to prevent abuse):
      /client//request/metric   -- payload: one or multiple metric name
                                                     Supports wildcards: * (all), prefix* (simple prefix match); mid-string wildcards (e.g. "bat*temp") and '?' are not supported.
                                                     Example: "v.b.*" matches all metrics starting with "v.b."
                                                     Each matching metric is published immediately on its normal topic.
      /client//request/config   -- payload: param/instance (single pair)
                                                     Response topic: /client//config//
    Subscription topic count increased (MQTT_CONN_NTOPICS=4) to include the two new request channels.
- server V3:
    The number of metrics sent per update is limited to 20 and is split into multiple packets if necessary. Only updated data is sent.
    Prioritize GPS tracking metrics, update interval set at Vehicle stream setting for smoother tracking
    new config:
      [server.v3] "updatetime.priority" (bool) -- enable/disable prioritizing GPS tracking
- smart EQ: removed vehicle specific GPS on/off at parking -> moved to cellular
- Vehicle notifications: grid log (history records `*-LOG-Grid`) V2 additions:
    pos_odometer
- Server V3: 
  added configurable connect stabilization & random jitter (server.v3 conn.stable_wait / conn.jitter.max) before MQTT connect to reduce reconnect storms.
- Cellular: 
  safeguarded CGATT attach/detach (only with mux/PPP), added NetLoss retry limit & optional power‑cycle recovery to prevent loops.
- esp32wifi:
  The OVMS will switch from Wifi APClient to Wifi Client mode after the timeout reached and a client is not connected. "APClient" will be restored upon reboot/network restart.
  new config, settings at Wifi:
    [network] wifi.ap2client.timeout   -- Wifi Mode APClient to client timeout in minutes (default 30 minutes)
    [network] wifi.ap2client.enable    -- Wifi Mode APClient to client enable/disable (default disable)
    [network] wifi.ap2client.notify    -- Notify when Wifi APClient to Wifi Client mode switched (default disable)
- Vehicle framework: signal generator operation state changes
  New events:
    vehicle.gen.start         -- Power delivery started
    vehicle.gen.stop          -- Power delivery stopped
    vehicle.gen.pilot.on      -- Pilot signal present
    vehicle.gen.pilot.off     -- Pilot signal gone
    vehicle.gen.timermode.on  -- Generator timer has been enabled
    vehicle.gen.timermode.off -- Generator timer has been disabled
- Cellular: GPS auto pause on parking reactivate option added (update position).
  New config:
    [modem] gps.parkreactivate (minutes)   -- park time in minutes for auto reactivate for GPS lock (gps.parkreactlock), 0 = disabled
    [modem] gps.parkreactlock  (minutes)   -- GPS lock for 5 minutes until automatic shutdown during parking time (default 5 minutes)

Die vollständige Änderungshistorie ist hier abrufbar: changes.txt

Danke an alle beteiligten Open-Source-Unterstützer, Tester und Entwickler!

Totalausfall Rechenzentrum (gelöst)

2026-05-09T10:41:00+02:00

Der Server war heute im Zeitraum 8:04 Uhr bis 9:46 Uhr komplett unerreichbar, und Verbindungen per IPv6 waren noch bis 10:40 Uhr gestört.

Ursache war eine Routing-Störung, von der das gesamte Rechenzentrum betroffen war, inklusive der Dienste unseres Providers selbst.

Stand jetzt sind alle Dienste wieder erreichbar, Module und API-Clients sollten sich bereits automatisch neu verbunden haben, ansonsten empfiehlt sich ein Neustart.

Sorry für die Unannehmlichkeiten.

Ergänzender Hinweis zu Problemen dieser Art: die Status-Seite ist ein extern gehosteter Monitoring-Dienst, und man kann Status-Updates dort auch abonnieren (Button oben rechts).

Microsoft Mailsperre (gelöst)

2026-01-25T08:48:00+02:00

Betrifft alle Nutzer mit e-Mail-Adressen bei einem Microsoft-Maildienst (outlook.com, live.com, hotmail.com etc.): Microsoft haben das gesamte IP-Netz, in dem der OVMS-Server liegt, gestern abend um 21:00 Uhr CET auf deren interne Mail-Sperrliste gesetzt.

Der Server ist bei Microsoft offiziell als dedizierter Server registriert, Microsoft halten sich also hier nicht an ihre eigenen Regeln.

Die Entsperrung ist beantragt, wie lange dies dauert steht in den Sternen.

Update 16:51 Uhr CET: die Sperrung wurde seitens Microsoft aufgehoben, Mails an Microsoft-Domains werden wieder zugestellt.

Firmware-Release 3.3.005

2025-07-18T09:11:00+02:00

Die Firmware Version 3.3.005 ist nun in "eap" verfügbar, und wird in ca. 7 Tagen in "main" veröffentlicht.

Änderungen in dieser Version:

- Cellular: GPS auto pause on parking option added (power saving).
  New config:
    [modem] gps.parkpause     -- park time in seconds for auto pause, 0 = disabled (default)
- New vehicle: NIU MQi GT EVO or GT 100 electric scooters (NEVO)
  https://docs.openvehicles.com/en/latest/components/vehicle_niu_gtevo/docs/index.html
- Smart EQ 453:
    TPMS pressure alert settings at Features
    add information commads xsq climate|counter|mtdata|reset|start|total
- Nissan Leaf:
    ZE1 inital release
    Fix: Poll state not set to off when charging stopped by OVMS
    Enh: SOH_instrument now float not int to support ZE1 instrument values 
    Enh: Copy v.b.p.temp.max to v.b.temp so that max battery temp displays in app
- Smart EQ 453:
    DDT4all simple support, a full List of commands at www.smart-EMOTION.de
- VW e-Up (OBD): decode & display battery cell level health status & battery module
    health history, provide v.b.capacity (net capacity in kWh)
  New metrics:
    xvu.b.c.soh               -- Array: SOH [%] of each HV battery cell
    xvu.b.hist.soh.mod.   -- Array: SOH [%] history of each battery module (NN=01…14/17)
  New web page:
    /xvu/battsoh          -- Battery pack & cell SOH info
- Smart EQ 453:
    add timebased Pre-heat/cool Control 
      - can set at Website -> Smart ED/EQ 4.Gen -> Climate/Heater 
      - at App Features #4: on = 1 off = 2, #5 time like 05:15 = 515, #6 5/10/15 Minutes = 0/1/2
    add GPS powersaving mode at parking
    add 12V alert raised, the car starts the 12V charging process for 15 Minutes
    add Network type switch, option to lock LTE only. Needed, when the Provider has no Datastream at GSM
- CAN: add error flag decoding (included in can status output)
  New commands:
    can  explain [errorflags]    -- Decode error flags into human readable text 
- DBC Files
  Add unit support
  Add extended signals/multiplexing support
  Add support for enum values.
- OVMS Server v3: Ability to define less frequent MQTT communication to save data charges and power
  Events:
    Excludes clock.* events from being published at the start of every minute.
  New configs:
    [server.v3] events.legacy_topic  -- Whether to publish every event on the legacy /event topic as well as
                                        the MQTT-style topic. Defaults to true to preserve existing behaviour.
                                        Recommended to set to false if you don't use the legacy topic.
    [server.v3] updatetime.keepalive -- Max number of seconds to allow the MQTT connection to be idle before
                                        sending PINGREQ. Should be set slightly shorter than the network's
                                        NAT timeout and the timeout of your MQTT server. If these are unknown
                                        you can use trial and error. Symptoms of keepalive being too high are
                                        a lack of metric updates after a certain point, or "Disconnected from
                                        OVMS Server V3" appearing in the log. In previous releases this used
                                        the Mongoose default of 60. New default value 1740 aligns with
                                        observed Hologram timeout of 1800.
- Metrics
  add new Standard Metrics
    v.b.capacity          -- Main battery usable capacity [kWh]
    v.c.timestamp         -- Date & time of last charge end [DateLocal]
    v.g.timestamp         -- Date & time of last generation end [DateLocal]
- Server V2:
  add to MsgStat
    v.c.kwh.grid          -- Energy drawn from grid during running session [kWh]
    v.c.kwh.grid.total    -- Energy drawn from grid total (life time) [kWh]
    v.c.timestamp         -- Date & time of last charge end [seconds]
    v.b.capacity          -- Main battery usable capacity [kWh]
  add to MsgFirmware
    m.net.mdm.mode        -- Cellular connection mode and status [LTE,Online]
  add to MsgGen
    v.g.timestamp         -- Date & time of last generation end [seconds]
- Vehicle: keep charge time as long as chargeport active
- Vehicle: Implement events and scripting for Auxillary batttery monitor
  New events:
    vehicle.aux.12v.normal
    vehicle.aux.12v.charging
    vehicle.aux.12v.blip
    vehicle.aux.12v.dip
    vehicle.aux.12v.charging.blip
    vehicle.aux.12v.charging.dip
    vehicle.aux.12v.low
  New commands:
    vehicle aux [status]
    vehicle aux monitor [status]
    vehicle aux monitor enable [[low-threshold] [charging-threshold]]
    vehicle aux monitor disable
  Duktape Support:
    OvmsVehicle.AuxMon.Enable
    OvmsVehicle.AuxMon.Disable
    OvmsVehicle.AuxMon.Status
- Cellular: GPS run state signals added.
  New events:
    system.modem.gpsstart       -- GPS has started
    system.modem.gpsstop        -- GPS has stopped
- Cellular: receive & send SMS, forward SMS & USSD to user. Note: no system notification
  support (and not planned), this is primarily meant to forward provider info only
  sent via SMS or USSD or expected to be received via SMS.
  New events:
    system.modem.received.sms
  New notifications:
    [info] modem.received.sms
    [info] modem.received.ussd
  New commands:
    cellular sendsms   […]
- MG:
  Add new vehicle MG4
  Supports Short, Medium and Long Range Variants
- Implement custom CLI commands with Duktape function OvmsCommand.Register()
- Support for *,? wildcards in vfs ls and vfs rls commands.
- Smart EQ 453:
    add 5min Booster preheat cool
    add TPMS pressure
    add Internal Temp
    add Doors status
    add Charging Metrics
    add BMS Temperatures
    add Charging metrics
    add option to change TMPS Sensors position
    add option for IOS users to display TMPS values
- Support for completion in vfs commands.
- Separate Polling from the Vehicle implementation
  New commands:
    poller status
    poller pause
    poller resume
    poller trace on|txrx|all|off|status-- Control verbose logging
    poller times on|off|status|reset   -- Control poller timing metrics
  Duktape Support:
    OvmsPoller.GetPaused
    OvmsPoller.GetUserPaused
    OvmsPoller.Pause
    OvmsPoller.Resume
    OvmsPoller.Trace
    OvmsPoller.GetTraceStatus
    OvmsPoller.Times.Start
    OvmsPoller.Times.Stop
    OvmsPoller.Times.Reset
    OvmsPoller.Times.GetStatus
- Duktape support for Metric Age / Stale
  New Duktape methods
    OvmsMetrics.IsStale
    OmvsMetrics.IsFresh
    OvmsMetrics.Age

Die vollständige Änderungshistorie ist hier abrufbar: changes.txt

Danke an alle beteiligten Open-Source-Unterstützer und -Entwickler!

Apple/iOS App-Benachrichtigungen: Störung behoben

2025-05-20T10:38:00+02:00

Störung bei Apple/iOS App-Benachrichtigungen

2025-05-19T13:14:00+02:00

Aktuell funktionieren leider die Push-Benachrichtigungen des V2-Servers für Apple/iOS-Geräte nicht.

Das gilt für alle V2-Server-Installationen. Wir arbeiten an der Problembehebung.

Ausweichoptionen sind Push-Nachrichten via Mail (im Fahrzeug-Editor aktivierbar), oder Push-Nachrichten über Pushover (Modul: Config → Pushover).

Bitte entschuldigt die Unannehmlichkeiten, wir informieren euch, sobald das Problem behoben ist.

IPv6-Support

2024-12-27T16:31:00+02:00

https://dexters-web.de/ hat jetzt auch eine IPv6-Adresse.

Ein IPv6-fähiger Client verwendet diese idR. automatisch und vorrangig. Ob das der Fall ist kann über folgende Testseite geprüft werden:

https://dexters-web.de/test-ipv6

Hinweis: die OVMS-API-Adresse "ovms.dexters-web.de" bleibt wie bisher rein IPv4, da das Modul noch kein IPv6 unterstützt (ist auch noch nicht absehbar).

Warum IPv6?

Allgemein, weil es das IPv4-Protokoll langfristig ablösen wird.

Konkret jetzt, weil IPv4-Adressen bereits Mangelware sind, und immer mehr Provider zu einem Verfahren greifen, bei dem alle Provider-Kunden sich einen beschränkten Satz an IPv4-Adressen teilen (CGNAT).

In diesem Fall sind leider auch alle Kunden eines Providers durch IP-Sperrungen zum Schutz gegen Angriffe betroffen; Websites sind dann zeitweise aus dem gesamten Providernetz heraus nicht erreichbar.

IPv6 löst das Problem dieser "Sippenhaft", da damit wieder genügend viele Adressen verfügbar sind, so dass jeder PC wieder seine eigene Adresse erhält.

Geplante Serverwartung

2024-11-26T19:09:00+02:00

In der Nacht vom 5. auf den 6. Dezember wird der Server im Zeitfenster zwischen 23 Uhr und 1 Uhr (CET) wegen Wartungsarbeiten im Rechenzentrum unseres Providers für vorr. maximal 30 Minuten offline sein.

Leider lässt sich der Zeitpunkt nicht genauer eingrenzen, bitte plant ggf. entsprechend.

MQTT-Server

2024-05-07T13:55:00+02:00

Ab sofort stelle ich hier zusätzlich zum V2/MP-Server einen V3/MQTT-Hub bereit.

Der MQTT-Server ("Server V3" im Modul) ist derzeit als Ergänzung zum V2-Server gedacht. Er dient vorerst rein als Datendrehscheibe für MQTT-Clients. Für die Archivierung von Daten, für Push-Nachrichten, die Web-Shell etc. wird weiterhin eine aktive V2-Verbindung benötigt (diese kann aber parallel zur V3-Verbindung laufen).

Hinweis: V3/MQTT ist im Modul derzeit noch als "experimentelles Feature" eingestuft, d.h. die Funktionalität und der Datenaufbau können sich ggf. noch ändern. Das definierte Topic-Schema soweit ist auf der Entwickler-Mailingliste nachlesbar, und ein einfacher Perl-Client ist im OVMS Github-Repository herunterladbar.

Der Zugriff auf den MQTT-Server erfolgt mit dem Login des Nutzerkontos. Alle Fahrzeuge eines Nutzers können nach dem OVMS-Standard-Topicschema unter dem Nutzerlogin gemeinsam verwaltet und abgefragt werden.

Serveradresse: ovms.dexters-web.de
Ports: MQTT-Standard, d.h. 1883 unverschlüsselt / 8883 verschlüsselt (TLS)
Username & Passwort: des Haupt-Nutzerkontos hier
Topic-Präfix: OVMS-Standard, d.h. ovms/<username>/<vehicleid>/

Der Zugriff ist nur auf die eigenen Topics nach diesem Schema erlaubt.

Wichtig: bei einer Änderung des Konto-Passworts sollten alle MQTT-Clients solange pausiert werden, bis diese das neue Passwort haben. Andernfalls droht eine temporäre IP-Sperrung für Clients, die noch mit dem alten Passwort zugreifen.

Vorlage für den Aufruf des OVMS-Beispiel-Clients:

ovms_v3shell.pl --server ovms.dexters-web.de --port 8883 --tls --username '…' --password '…' --id '…'

Vorlage für Aufruf des Mosquitto-Clients mit JSON-Ausgabe:

mosquitto_sub -h ovms.dexters-web.de -p 8883 -u '…' -P '…' -t '#' -F %j

Vorlage für Ausführung eines OVMS-Kommandos (stat) mit dem Mosquitto-Client:

mosquitto_rr -h ovms.dexters-web.de -p 8883 -u '…' -P '…' \
  -t 'ovms/username/vehicleid/client/rr/command/1 \
  -e 'ovms/username/vehicleid/client/rr/response/1' \
  -m 'stat'