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.