From mark at webb-johnson.net Mon Sep 22 08:24:50 2025 From: mark at webb-johnson.net (Mark Webb-Johnson) Date: Mon, 22 Sep 2025 08:24:50 +0800 Subject: [Ovmsdev] Public OVMS Servers Message-ID: <8B502E0F-683B-4E9D-AAD6-6012AA4AB357@webb-johnson.net> 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 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 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From carsten.schmiemann at pfalz-mail.de Mon Sep 22 08:59:20 2025 From: carsten.schmiemann at pfalz-mail.de (Carsten Schmiemann) Date: Mon, 22 Sep 2025 00:59:20 +0000 Subject: [Ovmsdev] Public OVMS Servers In-Reply-To: <8B502E0F-683B-4E9D-AAD6-6012AA4AB357@webb-johnson.net> References: <8B502E0F-683B-4E9D-AAD6-6012AA4AB357@webb-johnson.net> Message-ID: <25A7BE33-423A-49A4-8B98-5E91FB90E0E5@pfalz-mail.de> 1. Title: Turboserv 2. Location: Mutterstadt, Germany 3. Intended geographic coverage: Globally available 4. Access policy: unrestricted public access for OVMS use only 5. Access domain name: https://turboserv.0-c.de 6. User Registration URL: https://turboserv.0-c.de/register 7. 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 8. 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 9. 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 10. 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 : 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: 1. Title 2. Location 3. Intended geographic coverage 4. Access policy 5. Access domain name 6. User Registration URL 7. 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? 8. 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 9. Notifications supported? * APNS (Apple IOS) supported? * GCM (Android firebase) supported? * MAIL (eMail) supported? * EXPO supported? 10. 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 here are the corresponding details: 1. Title: Open Vehicles 2. Location: Hong Kong 3. Intended geographic coverage: Globally available 4. Access policy: unrestricted public access for OVMS use only 5. Access domain name: api.openvehicles.com 6. User Registration URL: https://www.openvehicles.com/ 7. 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 8. 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 9. Notifications supported?: Yes * APNS (Apple IOS) supported?: Yes * GCM (Android firebase) supported?: Yes * MAIL (eMail) supported?: Yes * EXPO supported?: Yes 10. Notes/comments: none Thanks, and Regards, Mark _______________________________________________ OvmsDev mailing list OvmsDev at lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev -------------- next part -------------- An HTML attachment was scrubbed... URL: From dexter at expeedo.de Tue Sep 23 02:25:16 2025 From: dexter at expeedo.de (Michael Balzer) Date: Mon, 22 Sep 2025 20:25:16 +0200 Subject: [Ovmsdev] Public OVMS Servers In-Reply-To: <8B502E0F-683B-4E9D-AAD6-6012AA4AB357@webb-johnson.net> References: <8B502E0F-683B-4E9D-AAD6-6012AA4AB357@webb-johnson.net> Message-ID: 1. Title: */Dexter's Weboratory/* 2. Location: *Frankfurt, Germany* 3. Intended geographic coverage: */Globally available/* 4. Access policy: */unrestricted public access for OVMS use only/* 5. Access domain name: */ovms.dexters-web.de/* 6. User Registration URL: */https://dexters-web.de//* 7. V2 offered? */yes/* 1. V2 Type: */https://github.com/dexterbg/Open-Vehicle-Server/tree/v2/* 2. V2 Version: */v2 head, unmodified (currently 2.13.1-20250520)/* 3. V2 standard service port (if offered): */tcp/6867/* 4. V2 SSL server port (if offered): */tcp/6870/* 5. V2 HTTP API standard service port: */tcp/6868/* 6. V2 HTTPS API standard service port: */tcp/6869/* 7. V2 is WebSocket available on HTTP/HTTPS API service port? */no/* 8. V3 offered? */yes/* 1. V3 Type: */FlashMQ/* 2. V3 Version: */1.23.0 modified?(https://github.com/dexterbg/FlashMQ/tree/ovms-dexter)/* 3. V3 MQTT authentication: */same username+password as #6/* 4. V3 MQTT standard service port: */tcp/1883/* 5. V3 MQTT SSL service port: */tcp/8883/* 6. V3 MQTT websocket standard service port: */not available/* 7. V3 MQTT websocket SSL service port: */not available/* 9. Notifications supported? */yes/* 1. APNS (Apple IOS) supported? */yes/* 2. GCM (Android firebase) supported? */yes/* 3. MAIL (eMail) supported? */yes/* 4. EXPO supported? */no (soon)/* 10. Notes/comments: 1. Addon tools: */web shell, CSV download & auto mailer, Renault Twizy drive profile editor & converter/* 2. Addon HTTP API service port: */tcp/80/* 3. Addon HTTPS API service port: *tcp/443* 4. Addon HTTP/S API coverage: /*command execution, CSV data export (? https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/624#issuecomment-832180726)*/ 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: > > 1. Title > 2. Location > 3. Intended geographic coverage > 4. Access policy > 5. Access domain name > 6. User Registration URL > 7. V2 offered? > 1. V2 Type > 2. V2 Version > 3. V2 standard service port (if offered) > 4. V2 SSL server port (if offered) > 5. V2 HTTP API standard service port > 6. V2 HTTPS API standard service port > 7. V2 is WebSocket available on HTTP/HTTPS API service port? > 8. V3 offered? > 1. V3 Type > 2. V3 Version > 3. V3 MQTT authentication > 4. V3 MQTT standard service port > 5. V3 MQTT SSL service port > 6. V3 MQTT websocket standard service port > 7. V3 MQTT websocket SSL service port > 9. Notifications supported? > 1. APNS (Apple IOS) supported? > 2. GCM (Android firebase) supported? > 3. MAIL (eMail) supported? > 4. EXPO supported? > 10. 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 > ?here are the corresponding details: > > 1. Title: */Open Vehicles/* > 2. Location: */Hong Kong/* > 3. Intended geographic coverage: */Globally available/* > 4. Access policy: */unrestricted public access for OVMS use only/* > 5. Access domain name: */api.openvehicles.com/* > > 6. User Registration URL: */https://www.openvehicles.com//* > > 7. V2 offered?: */yes/* > 1. V2 Type: > */https://github.com/openvehicles/Open-Vehicle-Server/tree/master/v3/server/* > > 2. V2 Version: */master head, unmodified > (currently?3.0.001-74-gb19aaac)/* > 3. V2 standard service port (if offered): */tcp/6867/* > 4. V2 SSL server port (if offered): */tcp/6870/* > 5. V2 HTTP API standard service port: */tcp/6868/* > 6. V2 HTTPS API standard service port: */tcp/6869/* > 7. V2 is WebSocket available on HTTP/HTTPS API service port?: */yes/* > 8. V3 offered?: */yes/* > 1. V3 Type: */mosquitto/* > 2. V3 Version: */1.6/* > 3. V3 MQTT authentication: */same username+password as #6/* > 4. V3 MQTT standard service port: */tcp/1883/* > 5. V3 MQTT SSL service port: */tcp/8883/* > 6. V3 MQTT websocket standard service port: */not available/* > 7. V3 MQTT websocket SSL service port: */tcp/8083/* > 9. Notifications supported?: */Yes/* > 1. APNS (Apple IOS) supported?: */Yes/* > 2. GCM (Android firebase) supported?: */Yes/* > 3. MAIL (eMail) supported?: */Yes/* > 4. EXPO supported?: */Yes/* > 10. Notes/comments: */none/* > > > Thanks, and Regards, > Mark > > _______________________________________________ > OvmsDev mailing list > OvmsDev at lists.openvehicles.com > http://lists.openvehicles.com/mailman/listinfo/ovmsdev -- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: