<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="text">News - Dexter&apos;s Weboratory</title>
	<subtitle type="text">News. OVMS-Firmware, App und Server f&#xfc;r EU</subtitle>
	<updated>2026-01-25T16:53:54+01:00</updated>
	<id>http://dexters-web.de/f/feed/news-dexter-atom.xml</id>
	<link rel="alternate" type="text/html" hreflang="de" href="http://dexters-web.de/aktuell"/>
	<link rel="self" type="application/atom+xml" href="http://dexters-web.de/f/feed/news-dexter-atom.xml"/>
	<rights>Copyright (c) 2026 Dexter's Web</rights>
	<generator uri="http://www.shopdriver.de/" version="1.0">ShopDriver</generator>

	<entry>
		<title type="html">Microsoft Mailsperre (gel&#xf6;st)</title>
		<link rel="alternate" type="text/html" href="https://dexters-web.de/microsoft-mailsperre-gelöst-text_116.htm"/>
		<id>https://dexters-web.de/microsoft-mailsperre-gelöst-text_116.htm</id>
		<updated>2026-01-25T08:48:00+01:00</updated>
		<published>2026-01-25T08:48:00+01:00</published>
		<author>
			<name>Dexter&apos;s Web</name>
			<uri>https://dexters-web.de</uri>
			<email>dexter@dexters-web.de</email>
		</author>
		<content type="html">
			&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;Der Server ist bei Microsoft offiziell als dedizierter Server registriert, Microsoft halten sich also hier nicht an ihre eigenen Regeln.&lt;/p&gt;

&lt;p&gt;Die Entsperrung ist beantragt, wie lange dies dauert steht in den Sternen.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Update 16:51 Uhr CET:&lt;/b&gt; die Sperrung wurde seitens Microsoft aufgehoben, Mails an Microsoft-Domains werden wieder zugestellt.&lt;/p&gt;

		</content>
	</entry>
	
	<entry>
		<title type="html">Firmware-Release 3.3.005</title>
		<link rel="alternate" type="text/html" href="https://dexters-web.de/firmware-release-3.3.005-text_115.htm"/>
		<id>https://dexters-web.de/firmware-release-3.3.005-text_115.htm</id>
		<updated>2025-07-18T09:11:00+01:00</updated>
		<published>2025-07-18T09:11:00+01:00</published>
		<author>
			<name>Dexter&apos;s Web</name>
			<uri>https://dexters-web.de</uri>
			<email>dexter@dexters-web.de</email>
		</author>
		<content type="html">
			&lt;p&gt;Die Firmware Version 3.3.005 ist nun in &quot;eap&quot; verf&#xfc;gbar, und wird in ca. 7 Tagen in &quot;main&quot; ver&#xf6;ffentlicht.&lt;/p&gt;

&lt;p&gt;&#xc4;nderungen in dieser Version:&lt;/p&gt;

&lt;blockquote&gt;
&lt;pre&gt;
- 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 &amp; display battery cell level health status &amp; 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.&lt;NN&gt;   -- Array: SOH [%] history of each battery module (NN=01&#x2026;14/17)
  New web page:
    /xvu/battsoh          -- Battery pack &amp; cell SOH info
- Smart EQ 453:
    add timebased Pre-heat/cool Control 
      - can set at Website -&gt; Smart ED/EQ 4.Gen -&gt; 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 &lt;bus&gt; 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&apos;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&apos;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 &quot;Disconnected from
                                        OVMS Server V3&quot; 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 &amp; time of last charge end [DateLocal]
    v.g.timestamp         -- Date &amp; 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 &amp; 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 &amp; 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 &amp; send SMS, forward SMS &amp; 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 &lt;receiver&gt; &lt;text&gt; [&lt;text&gt;&#x2026;]
- 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
&lt;/pre&gt;
&lt;/blockquote&gt;

&lt;p&gt;Die vollst&#xe4;ndige &#xc4;nderungshistorie ist hier abrufbar:
&lt;a target=&quot;_blank&quot; href=&quot;https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/master/vehicle/OVMS.V3/changes.txt&quot;&gt;changes.txt&lt;/a&gt;
&lt;/p&gt;

&lt;p&gt;Danke an alle beteiligten Open-Source-Unterst&#xfc;tzer und -Entwickler!&lt;/p&gt;

		</content>
	</entry>
	
	<entry>
		<title type="html">Apple/iOS App-Benachrichtigungen: St&#xf6;rung behoben</title>
		<link rel="alternate" type="text/html" href="https://dexters-web.de/apple-ios-app-benachrichtigungen-störung-behoben-text_114.htm"/>
		<id>https://dexters-web.de/apple-ios-app-benachrichtigungen-störung-behoben-text_114.htm</id>
		<updated>2025-05-20T10:38:00+01:00</updated>
		<published>2025-05-20T10:38:00+01:00</published>
		<author>
			<name>Dexter&apos;s Web</name>
			<uri>https://dexters-web.de</uri>
			<email>dexter@dexters-web.de</email>
		</author>
		<content type="html">
			
		</content>
	</entry>
	
	<entry>
		<title type="html">St&#xf6;rung bei Apple/iOS App-Benachrichtigungen</title>
		<link rel="alternate" type="text/html" href="https://dexters-web.de/störung-bei-apple-ios-app-benachrichtigungen-text_113.htm"/>
		<id>https://dexters-web.de/störung-bei-apple-ios-app-benachrichtigungen-text_113.htm</id>
		<updated>2025-05-19T13:14:00+01:00</updated>
		<published>2025-05-19T13:14:00+01:00</published>
		<author>
			<name>Dexter&apos;s Web</name>
			<uri>https://dexters-web.de</uri>
			<email>dexter@dexters-web.de</email>
		</author>
		<content type="html">
			&lt;p&gt;Aktuell funktionieren leider die Push-Benachrichtigungen des V2-Servers f&#xfc;r Apple/iOS-Ger&#xe4;te nicht.&lt;/p&gt;

&lt;p&gt;Das gilt f&#xfc;r alle V2-Server-Installationen. Wir arbeiten an der Problembehebung.&lt;/p&gt;

&lt;p&gt;Ausweichoptionen sind Push-Nachrichten via Mail (im Fahrzeug-Editor aktivierbar), oder Push-Nachrichten &#xfc;ber Pushover (Modul: Config &#x2192; Pushover).&lt;/p&gt;

&lt;p&gt;Bitte entschuldigt die Unannehmlichkeiten, wir informieren euch, sobald das Problem behoben ist.&lt;/p&gt;

		</content>
	</entry>
	
	<entry>
		<title type="html">IPv6-Support</title>
		<link rel="alternate" type="text/html" href="https://dexters-web.de/ipv6-support-text_112.htm"/>
		<id>https://dexters-web.de/ipv6-support-text_112.htm</id>
		<updated>2024-12-27T16:31:00+01:00</updated>
		<published>2024-12-27T16:31:00+01:00</published>
		<author>
			<name>Dexter&apos;s Web</name>
			<uri>https://dexters-web.de</uri>
			<email>dexter@dexters-web.de</email>
		</author>
		<content type="html">
			&lt;p&gt;https://dexters-web.de/ hat jetzt auch eine IPv6-Adresse.&lt;/p&gt;

&lt;p&gt;Ein IPv6-f&#xe4;higer Client verwendet diese idR. automatisch und vorrangig.
Ob das der Fall ist kann &#xfc;ber folgende Testseite gepr&#xfc;ft werden:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://dexters-web.de/test-ipv6&quot;&gt;&lt;code&gt;https://dexters-web.de/test-ipv6&lt;/code&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;u&gt;Hinweis&lt;/u&gt;: die OVMS-API-Adresse &quot;ovms.dexters-web.de&quot; bleibt wie bisher rein IPv4, da
das Modul noch kein IPv6 unterst&#xfc;tzt (ist auch noch nicht absehbar).&lt;/p&gt;


&lt;h3&gt;Warum IPv6?&lt;/h3&gt;

&lt;p&gt;Allgemein, weil es das IPv4-Protokoll langfristig abl&#xf6;sen wird.&lt;/p&gt;

&lt;p&gt;Konkret jetzt, weil IPv4-Adressen bereits Mangelware sind, und immer mehr Provider zu einem Verfahren
greifen, bei dem alle Provider-Kunden sich einen beschr&#xe4;nkten Satz an IPv4-Adressen teilen (CGNAT).&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;IPv6 l&#xf6;st das Problem dieser &quot;Sippenhaft&quot;, da damit wieder gen&#xfc;gend viele Adressen verf&#xfc;gbar
sind, so dass jeder PC wieder seine eigene Adresse erh&#xe4;lt.&lt;/p&gt;

		</content>
	</entry>
	
	<entry>
		<title type="html">Geplante Serverwartung</title>
		<link rel="alternate" type="text/html" href="https://dexters-web.de/geplante-serverwartung-text_111.htm"/>
		<id>https://dexters-web.de/geplante-serverwartung-text_111.htm</id>
		<updated>2024-11-26T19:09:00+01:00</updated>
		<published>2024-11-26T19:09:00+01:00</published>
		<author>
			<name>Dexter&apos;s Web</name>
			<uri>https://dexters-web.de</uri>
			<email>dexter@dexters-web.de</email>
		</author>
		<content type="html">
			&lt;p&gt;In der Nacht vom &lt;b&gt;5. auf den 6. Dezember&lt;/b&gt; wird der Server im Zeitfenster &lt;b&gt;zwischen 23 Uhr und 1 Uhr (CET)&lt;/b&gt; wegen Wartungsarbeiten im Rechenzentrum unseres Providers f&#xfc;r &lt;b&gt;vorr. maximal 30 Minuten offline&lt;/b&gt; sein.&lt;/p&gt;

&lt;p&gt;Leider l&#xe4;sst sich der Zeitpunkt nicht genauer eingrenzen, bitte plant ggf. entsprechend.&lt;/p&gt;

		</content>
	</entry>
	
	<entry>
		<title type="html">MQTT-Server</title>
		<link rel="alternate" type="text/html" href="https://dexters-web.de/mqtt-server-text_110.htm"/>
		<id>https://dexters-web.de/mqtt-server-text_110.htm</id>
		<updated>2024-05-07T13:55:00+01:00</updated>
		<published>2024-05-07T13:55:00+01:00</published>
		<author>
			<name>Dexter&apos;s Web</name>
			<uri>https://dexters-web.de</uri>
			<email>dexter@dexters-web.de</email>
		</author>
		<content type="html">
			&lt;p&gt;Ab sofort stelle ich hier zus&#xe4;tzlich zum V2/MP-Server einen V3/MQTT-Hub bereit.&lt;/p&gt;

&lt;p&gt;Der MQTT-Server (&quot;Server V3&quot; im Modul) ist derzeit als Erg&#xe4;nzung zum V2-Server gedacht. Er dient vorerst rein als Datendrehscheibe f&#xfc;r MQTT-Clients. F&#xfc;r die Archivierung von Daten, f&#xfc;r Push-Nachrichten, die Web-Shell etc. wird weiterhin eine aktive V2-Verbindung ben&#xf6;tigt (diese kann aber parallel zur V3-Verbindung laufen).&lt;/p&gt;

&lt;p&gt;Hinweis: V3/MQTT ist im Modul derzeit noch als &quot;experimentelles Feature&quot; eingestuft, d.h. die Funktionalit&#xe4;t und der Datenaufbau k&#xf6;nnen sich ggf. noch &#xe4;ndern. Das definierte Topic-Schema soweit ist auf der &lt;a target=&quot;_blank&quot; href=&quot;http://lists.openvehicles.com/pipermail/ovmsdev/2018-July/012641.html&quot;&gt;Entwickler-Mailingliste&lt;/a&gt; nachlesbar, und ein einfacher Perl-Client ist im &lt;a target=&quot;_blank&quot; href=&quot;https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/tree/master/client&quot;&gt;OVMS Github-Repository&lt;/a&gt; herunterladbar.&lt;/p&gt;

&lt;p&gt;Der Zugriff auf den MQTT-Server erfolgt mit dem Login des Nutzerkontos. Alle Fahrzeuge eines Nutzers k&#xf6;nnen nach dem OVMS-Standard-Topicschema unter dem Nutzerlogin gemeinsam verwaltet und abgefragt werden.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Serveradresse: &lt;code&gt;ovms.dexters-web.de&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Ports: MQTT-Standard, d.h. &lt;code&gt;1883&lt;/code&gt; unverschl&#xfc;sselt / &lt;code&gt;8883&lt;/code&gt; verschl&#xfc;sselt (TLS)&lt;/li&gt;
&lt;li&gt;Username &amp;amp; Passwort: des Haupt-Nutzerkontos hier&lt;/li&gt;
&lt;li&gt;Topic-Pr&#xe4;fix: OVMS-Standard, d.h. &lt;code&gt;ovms/&amp;lt;username&amp;gt;/&amp;lt;vehicleid&amp;gt;/&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Der Zugriff ist nur auf die eigenen Topics nach diesem Schema erlaubt.&lt;/p&gt;

&lt;div class=&quot;alert alert-warning&quot;&gt;
  &lt;strong&gt;&lt;u&gt;Wichtig&lt;/u&gt;:&lt;/strong&gt; bei einer &lt;strong&gt;&#xc4;nderung des Konto-Passworts&lt;/strong&gt; sollten alle MQTT-Clients solange &lt;strong&gt;pausiert&lt;/strong&gt; werden, bis diese das neue Passwort haben. Andernfalls droht eine &lt;strong&gt;tempor&#xe4;re IP-Sperrung&lt;/strong&gt; f&#xfc;r Clients, die noch mit dem alten Passwort zugreifen.
&lt;/div&gt;

&lt;p&gt;Vorlage f&#xfc;r den Aufruf des OVMS-Beispiel-Clients:&lt;br&gt;
&lt;pre&gt;ovms_v3shell.pl --server ovms.dexters-web.de --port 8883 --tls --username &apos;&#x2026;&apos; --password &apos;&#x2026;&apos; --id &apos;&#x2026;&apos;&lt;/pre&gt;
&lt;/p&gt;

&lt;p&gt;Vorlage f&#xfc;r Aufruf des Mosquitto-Clients mit JSON-Ausgabe:&lt;br&gt;
&lt;pre&gt;mosquitto_sub -h ovms.dexters-web.de -p 8883 -u &apos;&#x2026;&apos; -P &apos;&#x2026;&apos; -t &apos;#&apos; -F %j&lt;/pre&gt;
&lt;/p&gt;

&lt;p&gt;Vorlage f&#xfc;r Ausf&#xfc;hrung eines OVMS-Kommandos (&lt;code&gt;stat&lt;/code&gt;) mit dem Mosquitto-Client:&lt;br&gt;
&lt;pre&gt;mosquitto_rr -h ovms.dexters-web.de -p 8883 -u &apos;&#x2026;&apos; -P &apos;&#x2026;&apos; \
  -t &apos;ovms/username/vehicleid/client/rr/command/1 \
  -e &apos;ovms/username/vehicleid/client/rr/response/1&apos; \
  -m &apos;stat&apos;
&lt;/pre&gt;
&lt;/p&gt;

		</content>
	</entry>
	
	<entry>
		<title type="html">Firmware-Release 3.3.004</title>
		<link rel="alternate" type="text/html" href="https://dexters-web.de/firmware-release-3.3.004-text_109.htm"/>
		<id>https://dexters-web.de/firmware-release-3.3.004-text_109.htm</id>
		<updated>2024-03-23T10:29:00+01:00</updated>
		<published>2024-03-23T10:29:00+01:00</published>
		<author>
			<name>Dexter&apos;s Web</name>
			<uri>https://dexters-web.de</uri>
			<email>dexter@dexters-web.de</email>
		</author>
		<content type="html">
			&lt;p&gt;Die Firmware Version 3.3.004 ist nun in &quot;eap&quot; verf&#xfc;gbar, und wird in ca. 7 Tagen in &quot;main&quot; ver&#xf6;ffentlicht.&lt;/p&gt;

&lt;p&gt;&#xc4;nderungen in dieser Version:&lt;/p&gt;

&lt;blockquote&gt;
&lt;pre&gt;
- MG EV Added support for MG5 (2020 - 2023) Short Range
- MG EV Added support for MG ZS EV (2023 - ) and MG5 (2020 - 2023) Long Range
- OVMS Server v3 metrics filtering
  New configs:
    [server.v3] metrics.include         -- Comma-separated list of metric names (with possible wildcard) matching metrics to send
    [server.v3] metrics.exclude         -- Comma-separated list of metric names (with possible wildcard) matching metrics to not send
- Renault Zoe Phase 2: Initial support
- Improved output of bms shell command for narrow windows.
  New commands:
    bms volt                            -- Output only voltage info if available
    bms temp                            -- Output only temperature info if available
- Hyundai Ioniq 5: Initial support
- Support for specifying units in scripts
  New commands:
    metrics units                       -- Display available unit identifiers
    metrics get                         -- Get at a particular metric value (with a specified unit)
  Extended commands:
    metrics set                         -- Support setting with a specified unit
  Extend functions
    OvmsMetrics.Value                   -- Optionally specify a unit (and make &apos;decode&apos; work) and to get values with units.
    OvmsMetrics.GetValues               -- Optionally specify a unit to get values with units.
    OvmsMetrics.AsFloat                 -- Optionally specify a unit
  New DukTape function
    OvmsMetrics.HasValue                -- Returns true if the metric has a valid value.
- Added power consumptions units:  kWhP100K,KPkWh,MPkWh
- Consolidate custom trip power consumption metrics to single value (kWhP100K)
  in Kia Niro and Kia Soul
- VFS: sorted directory listings &amp; recursive directory listings
  New commands:
    vfs rls &lt;path&gt;                      -- List &lt;path&gt; and all subdirectory contents
- Vehicle: emit standard events on charge/generator connection type changes
  New events:
    vehicle.charge.type                 -- Vehicle charge connection type has changed (e.g. ccs/type2/&#x2026;)
    vehicle.gen.type                    -- Vehicle generator connection type has changed
- CAN logging: add possibility to log events (name) and metrics (JSON object with name, value, unit)
  New configs:
    [can] log.events_filters            -- comma-separated list of filters (with possible wildcard) matching an event name
    [can] log.metrics_filters           -- comma-separated list of filters (with possible wildcard) matching a metric name
- Add units Bar, Permille
- Add user configuration for groups of metrics
  Adds the &apos;ToUser&apos; unit that converts to the user specified unit.
  Add -u to &apos;metrics list&apos; to view metrics as  user units.
- Add completion for metrics set/get as well as units
- Mini Cooper SE: Initial support
- Hyundai Ioniq vFL: trip metrics, range estimations, TPMS, web configuration,
    charge type detection, charge speed &amp; time estimation
  New configs:
    [xhi] ctp.maxpower                -- Default charge power limit [kW] for charge time estimations, default 0 = unlimited
    [xhi] ctp.soclimit                -- SOC level [%] for secondary charge time estimation (sufficient SOC), default 80
    [xhi] notify.charge.delay.ccs     -- Wait time [sec] for DC charge power to ramp up before sending the notification, default 15
    [xhi] notify.charge.delay.type2   -- &#x2026; same for AC charging, default 3
    [xhi] range.ideal                 -- ideal new car range [km], default 200
    [xhi] range.user                  -- typical current user range [km], default 200
    [xhi] range.smoothing             -- Number of SOC samples, default 10 = ~ 5% SOC
    [xhi] tpms.pressure.warn              -- default 230 [kPa]
    [xhi] tpms.pressure.alert         -- default 220 [kPa]
    [xhi] tpms.temp.warn              -- default 90 [&#xb0;C]
    [xhi] tpms.temp.alert             -- default 100 [&#xb0;C]
  New metrics:
    xhi.b.range.user                  -- actual current user range [km]
    xhi.e.state                       -- General/ignition state flags
- Module: support deep sleep schedules
  New commands:
    module sleep                      -- Shutdown all components and enter deep sleep for a time span or until a specific time.
- Add support for user-configured metrics in the web interface and plugins:
   Adds an extra &apos;units&apos; stream from the websocket containing sub-streams:
     - metrics (for the current user unit/label for each metric) (subscribe to units/metrics)
     - prefs (for any user preferences for unit groups/types) (subscribe to units/prefs)
   Adds proxy arrays metrics_user[] , metrics_label[] available to plugin pages.
   Adds various browser javascript functions and methods for plugins related
     to displaying user configurations Auto-converts metric display to user
     units in plugins that use attributes
- Cellular: add GPS/GNSS state control commands (for power management)
  New commands:
    cellular gps [status]             -- output current modem GPS/GNSS subsystem status
    cellular gps start                -- start modem GPS/GNSS subsystem
    cellular gps stop                 -- stop modem GPS/GNSS subsystem
- CAN framework: add bus reset command
  New commands:
    can [can1&#x2026;4] reset                -- reset the CAN interface
- Vehicle: add support for custom command handlers, see&#x2026;
https://docs.openvehicles.com/en/latest/userguide/scripting.html#ovmsvehicle-command-plugins
- Renault Twizy: read battery energy available from BMS (thanks to Martin Bitz)
  New metrics:
    xrt.b.energy.avail                -- Current battery energy available [kWh] (aged)
    xrt.b.energy.full                 -- Maximum battery energy capacity [kWh] (aged, needs full charge)
- Add button on web file editor to reload obd2ECU (when obd2ECU is enabled).
- Vehicle: add support for a geofence for valet mode similar to parking/flatbed warnings.
  New Configs:
    [vehicle] valet.alarmdistance     -- How far away from the original position before raising an alert (in metres)
    [vehicle] valet.alarminterval      -- How often the alarm can be raised in minumtes
- Add metric and events related to obd2ecu process:
  New metric:
    m.obdc2ecu.on                     -- Is the OBD2ECU process currently on.
  New events:
    obd2ecu.start                     -- Called after the OBD2ECU process is started.
    obd2ecu.stop                      -- Called before the OBD2ECU process is stopped.
- Web UI: Add configuration for Valet and Flatbed geofence to the Locations config page.
- Network: New &apos;network ping&apos; command to ping (ICMP) hostname or IP address. (ESP-IDFv4+ only / needs to be enabled in menuconfig - Developer Options)
- Vehicle: add automatic module shutdown/reboot based on 12V battery voltage level
  New configs:
    [vehicle] 12v.shutdown            -- Shutdown voltage level (default: disabled)
    [vehicle] 12v.wakeup              -- Reboot minimum voltage level after shutdown (default: any)
    [vehicle] 12v.wakeup_interval     -- Reboot test interval in seconds (default: 60)
  New events:
    vehicle.alert.12v.shutdown        -- 12V shutdown threshold reached, entering deep sleep
- BYD Atto 3 initial support
- Vehicle: add 12V shutdown delay &amp; notification
  New configs:
    [vehicle] 12v.shutdown_delay      -- Shutdown delay in minutes (default: 2)
  New events:
    vehicle.alert.12v.low             -- 12V shutdown voltage level detected
    vehicle.alert.12v.operational     -- 12V recovered above shutdown level
  New notifications:
    [alert] batt.12v.shutdown         -- Alert about imminent 12V shutdown
- VFS toolkit: add recursive options to mkdir (-p) &amp; rmdir (-r) commands
- Renault-Zoe-Ph1: add Cabin Pre-heat/cool Control 
&lt;/pre&gt;
&lt;/blockquote&gt;

&lt;p&gt;Die vollst&#xe4;ndige &#xc4;nderungshistorie ist hier abrufbar:
&lt;a target=&quot;_blank&quot; href=&quot;https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/master/vehicle/OVMS.V3/changes.txt&quot;&gt;changes.txt&lt;/a&gt;
&lt;/p&gt;

&lt;p&gt;Danke an alle beteiligten Open-Source-Unterst&#xfc;tzer und -Entwickler!&lt;/p&gt;

		</content>
	</entry>
	
	<entry>
		<title type="html">Serverumzug</title>
		<link rel="alternate" type="text/html" href="https://dexters-web.de/serverumzug-text_108.htm"/>
		<id>https://dexters-web.de/serverumzug-text_108.htm</id>
		<updated>2024-03-03T15:37:00+01:00</updated>
		<published>2024-03-03T15:37:00+01:00</published>
		<author>
			<name>Dexter&apos;s Web</name>
			<uri>https://dexters-web.de</uri>
			<email>dexter@dexters-web.de</email>
		</author>
		<content type="html">
			&lt;p&gt;dexters-web.de ist soeben auf einen neuen Server umgezogen.&lt;/p&gt;

&lt;p&gt;Das betrifft nat&#xfc;rlich auch den OVMS-Server. Wer bislang bereits den Namen &lt;code&gt;ovms.dexters-web.de&lt;/code&gt; statt der IP-Adresse verwendet hat, muss nichts &#xe4;ndern.&lt;/p&gt;

&lt;p&gt;Wer noch mit der IP-Adresse zugreifen muss oder m&#xf6;chte, der muss diese auf die neue IP einstellen: &lt;code&gt;85.195.96.186&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Mit der Serverumstellung habe ich auch die Android-Benachrichtigungen serverseitig auf die neue GoogleAPI (Firebase Cloud Messaging) umgestellt. Dazu passend gibt es eine neue App-Release, die ebenfalls die neue API verwendet. Die alte App wird Nachrichten nur noch bis Ende Juni erhalten, dann schaltet Google das alte API ab.&lt;/p&gt;

&lt;p&gt;Dazu ein Hinweis: falls ihr nach dem App-Update keine Nachrichten erhaltet, startet das Ger&#xe4;t einmal komplett neu.&lt;/p&gt;

&lt;p&gt;Falls irgendwelche Probleme mit dem Server auftreten bitte ich um Mitteilung.&lt;/p&gt;

		</content>
	</entry>
	
	<entry>
		<title type="html">Firmware-Release 3.3.003</title>
		<link rel="alternate" type="text/html" href="https://dexters-web.de/firmware-release-3.3.003-text_107.htm"/>
		<id>https://dexters-web.de/firmware-release-3.3.003-text_107.htm</id>
		<updated>2023-01-16T13:29:00+01:00</updated>
		<published>2023-01-16T13:29:00+01:00</published>
		<author>
			<name>Dexter&apos;s Web</name>
			<uri>https://dexters-web.de</uri>
			<email>dexter@dexters-web.de</email>
		</author>
		<content type="html">
			&lt;p&gt;Firmware 3.3.003 ist nun in &quot;main&quot; verf&#xfc;gbar. Release 3.3.002 (03/2022) hatte ich vergessen hier zu beschreiben, daher jetzt hier mit dabei.&lt;/p&gt;

&lt;blockquote&gt;
&lt;pre&gt;
2022-09-01 MWJ  3.3.003  OTA release
- Toyota RAV4 EV: Initial support added. Only the Tesla bus is decoded and just listening so far.
- Location: configurable flatbed movement alarm repetition
  New configs:
    [vehicle] flatbed.alarminterval     -- in minutes, default 15, 0 = single alarm
- GPS: added normalized signal quality level, added web UI live status info
  New metrics:
    v.p.gpssq                           -- GPS signal quality [%] (&lt;30 unusable, &gt;50 good, &gt;80 excellent)
    v.p.gpstime                         -- Time (UTC) of GPS coordinates [Seconds]
- Location: flatbed movement alarm only with reliable positioning
  New configs:
    [vehicle] gps.sq.good               -- SQ level for location state &quot;reliable&quot;, default 60
    [vehicle] gps.sq.bad                -- SQ level for location state &quot;unreliable&quot;, default 40
  New events:
    gps.sq.good                         -- GPS position is now reliable
    gps.sq.bad                          -- GPS position is now unreliable
- Improvements to SIM7600 driver to support E-UTRAN LTE only cellular providers
- Enhance &apos;cellular cmd&apos; to show output from modem

2022-03-07 MWJ  3.3.002  OTA release
- Maxus eDeliver3: Updated speed PID
- Bolt EV: Add early Bolt EV support
- Maxus eDeliver3: Add CCS Charging
	rewrite polling system
- Volt/Ampera:: added notification for &quot;fuel&quot; metric.
    new config: [xva] notify_va_metrics 	(bool, default no)
- Server V2/V3: added manual update request
    Note: the servers normally don&apos;t need a manual trigger to perform
    data updates, they listen to metrics changes and events. Use this
    only if you need extraordinary single updates as fast as possible.
  New commands:
    server v2 update [all|modified]     -- Request V2 data update
    server v3 update [all|modified]     -- Request V3 data update
- Notifications: add tracing (debug logging) of stream notifications
  New commands:
    notify trace all                    -- Enable logging of stream notifications
- Nissan LEAF:
 - Remote heating/cooling now works on 2011-2012 LEAFs
 - Stop charge feature added, works via app
 - Charge to Limit SOC and/or range added with a top-up feature.
 - Improved charging metric logic.
 - Fixed incorrect HVAC (Climate Control) status when charging (for 2013+).
 - 9 new metrics added
    xnl.v.b.max.gids (Max number of GIDs the battery can reach (for 2016+))
    xnl.v.b.heatrequested (Battery is requesting heater elements to turn on (for 2013+))
    xnl.v.b.heatergranted (Vehicle is OKing heater elements to turn on (for 2013+))
    xnl.v.c.chargeminutes3kW (The 3kW charge time estimate the car calculates)
    xnl.v.c.chargebars (Remaining charge &quot;bars&quot; on dashboard)
    xnl.v.c.event.notification (Used to not send duplicate notifications for charge to limit feature.)
    xnl.v.c.event.reason (When charge to limit feature starts the charge shows if was triggered due to range or SOC limit.)
    xnl.v.c.state.previous (Used to better handle charging substate, shows previos charging state timed to ticker.10.)
    xnl.cc.rqinprogress (Indicates the period betwen arrival of climate control action message and climate control activation.)
 - Wakeup command now charges 12V battery if connected to EVSE
 - 2011-2012 LEAF now reads AC voltage from grid
 - Fix to watchdog timer for modem driver without GPS enabled

&lt;/pre&gt;
&lt;/blockquote&gt;

&lt;p&gt;Die vollst&#xe4;ndige &#xc4;nderungshistorie ist hier abrufbar:
&lt;a target=&quot;_blank&quot; href=&quot;https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/master/vehicle/OVMS.V3/changes.txt&quot;&gt;changes.txt&lt;/a&gt;
&lt;/p&gt;

&lt;p&gt;Danke an alle beteiligten Unterst&#xfc;tzer und Entwickler!&lt;/p&gt;
		</content>
	</entry>
	</feed>
