I’m trying to compile a full list of public OVMS servers, and in particular their capabilities.
Here is what I would like to collect:
Title Location Intended geographic coverage Access policy Access domain name User Registration URL V2 offered? V2 Type V2 Version V2 standard service port (if offered) V2 SSL server port (if offered) V2 HTTP API standard service port V2 HTTPS API standard service port V2 is WebSocket available on HTTP/HTTPS API service port? V3 offered? V3 Type V3 Version V3 MQTT authentication V3 MQTT standard service port V3 MQTT SSL service port V3 MQTT websocket standard service port V3 MQTT websocket SSL service port Notifications supported? APNS (Apple IOS) supported? GCM (Android firebase) supported? MAIL (eMail) supported? EXPO supported? Notes/comments
Grateful if you could reply to this eMail with details of any public OVMS servers that you operate, use, or know-of. Obviously best if the operators could reply directly as they know the capabilities best.
As an example, for api.openvehicles.com <http://api.openvehicles.com/> here are the corresponding details:
Title: Open Vehicles Location: Hong Kong Intended geographic coverage: Globally available Access policy: unrestricted public access for OVMS use only Access domain name: api.openvehicles.com <http://api.openvehicles.com/> User Registration URL: https://www.openvehicles.com/ V2 offered?: yes V2 Type: https://github.com/openvehicles/Open-Vehicle-Server/tree/master/v3/server V2 Version: master head, unmodified (currently 3.0.001-74-gb19aaac) V2 standard service port (if offered): tcp/6867 V2 SSL server port (if offered): tcp/6870 V2 HTTP API standard service port: tcp/6868 V2 HTTPS API standard service port: tcp/6869 V2 is WebSocket available on HTTP/HTTPS API service port?: yes V3 offered?: yes V3 Type: mosquitto V3 Version: 1.6 V3 MQTT authentication: same username+password as #6 V3 MQTT standard service port: tcp/1883 V3 MQTT SSL service port: tcp/8883 V3 MQTT websocket standard service port: not available V3 MQTT websocket SSL service port: tcp/8083 Notifications supported?: Yes APNS (Apple IOS) supported?: Yes GCM (Android firebase) supported?: Yes MAIL (eMail) supported?: Yes EXPO supported?: Yes Notes/comments: none
Thanks, and Regards, Mark
- Title: Turboserv
- Location: Mutterstadt, Germany
- Intended geographic coverage: Globally available
- Access policy: unrestricted public access for OVMS use only
- Access domain name: https://turboserv.0-c.de
- User Registration URL: https://turboserv.0-c.de/register
- V2 offered?: yes 7.1 V2 Type: Custom, compatible with latest master of OVMS Firmware 7.2 V2 Version: master head 7.3 V2 standard service port (if offered): tcp/6867 7.4 V2 SSL server port (if offered): tcp/6870 7.5 V2 HTTP API standard service port: not available 7.6 V2 HTTPS API standard service port: https/443 7.7 V2 is WebSocket available on HTTP/HTTPS API service port?: No
- V3 offered?: yes 8.1 V3 Type: FlashMQ 8.2 V3 Version: 1.23.0 8.3 V3 MQTT authentication: Per vehicle username+password, for external access additional username+password 8.4 V3 MQTT standard service port: tcp/1883 8.5 V3 MQTT SSL service port: tcp/8883 8.6 V3 MQTT websocket standard service port: not available 8.7 V3 MQTT websocket SSL service port: not available
- Notifications supported?: Yes 9.1 APNS (Apple IOS) supported?: Yes 9.2 GCM (Android firebase) supported?: Yes 9.3 MAIL (eMail) supported?: Yes 9.4 EXPO supported?: No
- Notes/comments:
- Rewritten Server + WebGUI and API in Python. API is not compatible with official V3 Server, the documentation of the OpenAPI is available at https://turboserv.0-c.de/docs and https://turboserv.0-c.de/redoc after login.
- NTFY.sh (Public and self hosted Instance) Notification Support
- Easy to use WebGUI
- Optional Trip Tracking (V3 only)
- Protomaps Support
- Key metrics highlighted and all transmitted metrics visible in WebGUI (V2 and V3) for easy debugging
- Remote console support for V2 and V3
- Improved security, V3 vehicle credentials can only readwrite to its own vehicle topic, User created API Keys=MQTT Credentials for accessing all vehicle topics --> Will be fully open sourced a the end of 2025, after fixing some bugs and documentation
Am 22.09.2025 um 02:24 schrieb Mark Webb-Johnson via OvmsDev <ovmsdev@lists.openvehicles.com>:
I’m trying to compile a full list of public OVMS servers, and in particular their capabilities.
Here is what I would like to collect:
- Title
- Location
- Intended geographic coverage
- Access policy
- Access domain name
- User Registration URL
- V2 offered? * V2 Type * V2 Version * V2 standard service port (if offered) * V2 SSL server port (if offered) * V2 HTTP API standard service port * V2 HTTPS API standard service port * V2 is WebSocket available on HTTP/HTTPS API service port?
- V3 offered? * V3 Type * V3 Version * V3 MQTT authentication * V3 MQTT standard service port * V3 MQTT SSL service port * V3 MQTT websocket standard service port * V3 MQTT websocket SSL service port
- Notifications supported? * APNS (Apple IOS) supported? * GCM (Android firebase) supported? * MAIL (eMail) supported? * EXPO supported?
- Notes/comments
Grateful if you could reply to this eMail with details of any public OVMS servers that you operate, use, or know-of. Obviously best if the operators could reply directly as they know the capabilities best.
As an example, for api.openvehicles.com<http://api.openvehicles.com/> here are the corresponding details:
- Title: Open Vehicles
- Location: Hong Kong
- Intended geographic coverage: Globally available
- Access policy: unrestricted public access for OVMS use only
- Access domain name: api.openvehicles.com<http://api.openvehicles.com/>
- User Registration URL: https://www.openvehicles.com/
- V2 offered?: yes * V2 Type: https://github.com/openvehicles/Open-Vehicle-Server/tree/master/v3/server * V2 Version: master head, unmodified (currently 3.0.001-74-gb19aaac) * V2 standard service port (if offered): tcp/6867 * V2 SSL server port (if offered): tcp/6870 * V2 HTTP API standard service port: tcp/6868 * V2 HTTPS API standard service port: tcp/6869 * V2 is WebSocket available on HTTP/HTTPS API service port?: yes
- V3 offered?: yes * V3 Type: mosquitto * V3 Version: 1.6 * V3 MQTT authentication: same username+password as #6 * V3 MQTT standard service port: tcp/1883 * V3 MQTT SSL service port: tcp/8883 * V3 MQTT websocket standard service port: not available * V3 MQTT websocket SSL service port: tcp/8083
- Notifications supported?: Yes * APNS (Apple IOS) supported?: Yes * GCM (Android firebase) supported?: Yes * MAIL (eMail) supported?: Yes * EXPO supported?: Yes
- Notes/comments: none
Thanks, and Regards, Mark
OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
- Title: */Dexter's Weboratory/*
- Location: *Frankfurt, Germany*
- Intended geographic coverage: */Globally available/*
- Access policy: */unrestricted public access for OVMS use only/*
- Access domain name: */ovms.dexters-web.de/*
- User Registration URL: */https://dexters-web.de//*
- V2 offered? */yes/*
- V2 Type: */https://github.com/dexterbg/Open-Vehicle-Server/tree/v2/*
- V2 Version: */v2 head, unmodified (currently 2.13.1-20250520)/*
- V2 standard service port (if offered): */tcp/6867/*
- V2 SSL server port (if offered): */tcp/6870/*
- V2 HTTP API standard service port: */tcp/6868/*
- V2 HTTPS API standard service port: */tcp/6869/*
- V2 is WebSocket available on HTTP/HTTPS API service port? */no/*
- V3 offered? */yes/*
- V3 Type: */FlashMQ/*
- V3 Version: */1.23.0 modified (https://github.com/dexterbg/FlashMQ/tree/ovms-dexter)/*
- V3 MQTT authentication: */same username+password as #6/*
- V3 MQTT standard service port: */tcp/1883/*
- V3 MQTT SSL service port: */tcp/8883/*
- V3 MQTT websocket standard service port: */not available/*
- V3 MQTT websocket SSL service port: */not available/*
- Notifications supported? */yes/*
- APNS (Apple IOS) supported? */yes/*
- GCM (Android firebase) supported? */yes/*
- MAIL (eMail) supported? */yes/*
- EXPO supported? */no (soon)/*
- Notes/comments:
- Addon tools: */web shell, CSV download & auto mailer, Renault Twizy drive profile editor & converter/*
- Addon HTTP API service port: */tcp/80/*
- Addon HTTPS API service port: *tcp/443*
- Addon HTTP/S API coverage: /*command execution, CSV data export (→ https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/624#...)*/
Regards, Michael
Am 22.09.25 um 02:24 schrieb Mark Webb-Johnson via OvmsDev:
I’m trying to compile a full list of public OVMS servers, and in particular their capabilities.
Here is what I would like to collect:
- Title
- Location
- Intended geographic coverage
- Access policy
- Access domain name
- User Registration URL
- V2 offered?
- V2 Type
- V2 Version
- V2 standard service port (if offered)
- V2 SSL server port (if offered)
- V2 HTTP API standard service port
- V2 HTTPS API standard service port
- V2 is WebSocket available on HTTP/HTTPS API service port?
- V3 offered?
- V3 Type
- V3 Version
- V3 MQTT authentication
- V3 MQTT standard service port
- V3 MQTT SSL service port
- V3 MQTT websocket standard service port
- V3 MQTT websocket SSL service port
- Notifications supported?
- APNS (Apple IOS) supported?
- GCM (Android firebase) supported?
- MAIL (eMail) supported?
- EXPO supported?
- Notes/comments
Grateful if you could reply to this eMail with details of any public OVMS servers that you operate, use, or know-of. Obviously best if the operators could reply directly as they know the capabilities best.
As an example, for api.openvehicles.com <http://api.openvehicles.com> here are the corresponding details:
- Title: */Open Vehicles/*
- Location: */Hong Kong/*
- Intended geographic coverage: */Globally available/*
- Access policy: */unrestricted public access for OVMS use only/*
- Access domain name: */api.openvehicles.com/* <http://api.openvehicles.com>
- User Registration URL: */https://www.openvehicles.com//* <https://www.openvehicles.com/>
- V2 offered?: */yes/*
- V2 Type: */https://github.com/openvehicles/Open-Vehicle-Server/tree/master/v3/server/* <https://github.com/openvehicles/Open-Vehicle-Server/tree/master/v3/server>
- V2 Version: */master head, unmodified (currently 3.0.001-74-gb19aaac)/*
- V2 standard service port (if offered): */tcp/6867/*
- V2 SSL server port (if offered): */tcp/6870/*
- V2 HTTP API standard service port: */tcp/6868/*
- V2 HTTPS API standard service port: */tcp/6869/*
- V2 is WebSocket available on HTTP/HTTPS API service port?: */yes/*
- V3 offered?: */yes/*
- V3 Type: */mosquitto/*
- V3 Version: */1.6/*
- V3 MQTT authentication: */same username+password as #6/*
- V3 MQTT standard service port: */tcp/1883/*
- V3 MQTT SSL service port: */tcp/8883/*
- V3 MQTT websocket standard service port: */not available/*
- V3 MQTT websocket SSL service port: */tcp/8083/*
- Notifications supported?: */Yes/*
- APNS (Apple IOS) supported?: */Yes/*
- GCM (Android firebase) supported?: */Yes/*
- MAIL (eMail) supported?: */Yes/*
- EXPO supported?: */Yes/*
- Notes/comments: */none/*
Thanks, and Regards, Mark
OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
participants (3)
-
Carsten Schmiemann -
Mark Webb-Johnson -
Michael Balzer