Enhanced V3/MQTT Server Support

The V3/MQTT server service provided here now includes the following additional features:

1. Connection and V3 Live Status
2. V3 Shell and Command API
3. V3 Email Notifications
4. V3 Server Data Archive
5. V3 Error Monitoring

Connection and V3 Live Status

To support the shell function and assist with troubleshooting, the Vehicle Editor, Vehicle Status, and shells now display the current connection status of the module and its peers (interactive clients) for both the V2 and V3 servers.

Key status metrics received via the V3 connection are also translated into V2 status data records, allowing the vehicle's current live status to be displayed even without a V2 connection. In this process, the V3 status data replaces the V2 status data on the server, meaning it can also be retrieved by a V2 app or via the V2 API (albeit without automatic push updates). To avoid interfering with regular parallel V2 operation, this occurs automatically only when the V2 connection is offline.

V3 Shell and Command API

The V3 shell allows for the interactive execution of shell commands on the module via an existing V3/MQTT connection. Advantages over execution via the V2 connection include, among other things, generally higher speed and the correct handling of commas (the V2 protocol requires these to be converted into semicolons).

A disadvantage compared to the V2 shell is that V2/MP protocol commands cannot be executed via the V3 shell (and API); only V3 text commands are supported. Furthermore, the special syntax for modem and USSD commands is not supported here; these must be sent using the V3 commands cellular cmd and cellular sendussd.

Analogous to the command API for the V2 connection, the server also provides an HTTP REST API for command execution via the V3/MQTT connection. Example using curl:

curl 'https://dexters-web.de/api/ovms/cmd_v3' \
--data-urlencode 'fn.vehicleid=MYCAR123' \
--data-urlencode 'fn.carpass=mysecret' \
--data-urlencode 'fn.cmd=charge start'

Details on using both command APIs are explained here in the user guide.

V3 Email Notifications

The module sends important alerts as text-based push notifications. Previously, anyone wishing to receive these without a V2 connection had to rely on the Pushover client built into the module (Module UI Config → Pushover). The server can now optionally forward these via email as well.

This feature can be enabled in the vehicle editor. For users who temporarily activate both V2 and V3 connections simultaneously, forwarding can be configured to occur only when the V2 connection is offline.

If required, push notifications can be filtered at the module level by channel and subtype; please refer to the User Guide.

V3 Server Data Archive

The module sends extended telemetry data ("Historical Records") as CSV datasets to the V3/MQTT server; however, under normal circumstances, only the most recent state is retained. With this new option (enabled in the vehicle editor), this data can now also be transferred to the V2 database. When enabled, live status data is also recorded for 24 hours, mirroring the V2 server functionality.

The data can be downloaded using the tool on the vehicle status page, retrieved via the V2 server API and the HTTP REST API, and optionally sent daily via email. As with the V2 function, the server automatically assigns field names to known data records during export.

V3 Error Monitoring

To assist users in setting up the V3 connection, the server now monitors V3/MQTT connections for error reports and, where appropriate, sends emails with information regarding potential errors in the module or client configuration.