Hi,
I’m setting up an OVMS v3 (OVMS-33-7600G) module on a Nissan Leaf (2014) to replace Nissan’s original remote climate control service, which is no longer supported.
Goal: remote climate control / pre-heating
Vehicle module: OVMS v3 (ESP32)
Location: Finland
Current status
-
Firmware updated successfully via microSD
→ now running 3.3.005 (OTA) -
Module works locally:
-
CAN data OK (SOC, ODO, GPS lock, etc.)
-
Web UI accessible via local WiFi (192.168.4.1)
-
-
Cellular modem:
-
SIM: Hologram global IoT SIM
-
Local operator: Elisa (Finland)
-
LTE online, PPP connected
-
DNS working (8.8.8.8 visible)
-
Hologram dashboard confirms SIM is active and data usage increases when OVMS is powered
-
-
Server settings:
-
Server:
api.openvehicles.com -
Port:
8883 -
TLS enabled
-
Username = OVMS user
-
Vehicle ID = code printed on the device label
-
Passwords consistent across module, server account and app
-
Problem
OVMS Server V3 never reaches “Connected”:
-
Status stays at “Connecting…”
-
Log shows: Launching OVMS Server V3 connection (oscv3)
-
Never transitions to Connected
-
OVMS App cannot connect either
What I have already tried
-
Firmware update + multiple reboots
-
Re-entered all credentials carefully
-
Verified Vehicle ID matches the physical device label
-
Restarted modem and network interfaces
-
Confirmed cellular data is flowing via Hologram dashboard
Questions
-
Any known issues or special requirements when using Hologram SIM with OVMS Server V3?
-
Anything specific to verify regarding TLS / MQTT on Server V3?
-
Any known problems with OVMS firmware 3.3.005 and Server V3?
Happy to provide logs or screenshots if needed.
Thanks in advance.
You could try alternative V3 servers such as: ovms.dexters-web.de or turboserv.0-c.de. I'm using turboserv.0-c.de for V3 and ovms.dexters-web.de for v2 - also I use the 'OVMS connect' app on iPhone and this combination works really well. Using the Hologram SIM service and v2 and v3 work fine, Currently on 3.3.005-628-gec1448e2 firmware and the servers both work with that firmware. In the case of turboserv I bought the app, and I donated to dexters to help with costs of running the servers
hope this helps!
I am trying to setup the turboserv as an alternative V3 server for OVMS Connect app. (the v2 server work just fine and I get the data to the OVMS app).
I do have an account at turboserv.0-c.de already and trying to connect with OVMS.
But I do not have prefix specified. What shall I put in there? Is the username and password are the ones I am accessing the turboserv account or they are the Key Prefix and Full API Key?
The v2 dexter and v3 turboserv should work parallel without any issues I guess (apart from bigger bandwidth usage).
Many thanks,
Hi, so when you sign up to turboserv.0-c.de you will have a user name and the vehicle will have and ID BUT its not clear what goes where. So the user ID portion of the V3 login will have vehicle ID (counter intuitive!) and the the 'topic prefix' will be - ovms/site login USERNAME/VehicleID/ - hope that helps?
laid out like:
Server: turboserv.0-c.de
Enable TLS
Username: unique-vehicle-identity (as you've named on server)
Password: your password for server
Topic Prefix: ovms/login-user-name/vehicleID-SAME as username above/
Thank you very much. It is somewhat clear now. :)
I will give it a go and let you know.
Brilliant. Works! Thank you very much!