I have a v3 OMVS module that is configured to my custom ovms server.
Autostart v2 server is configured
The cellular modem is disabled (and has never been enabled).
Autostart v2 server is configured
The cellular modem is disabled (and has never been enabled).
My Leaf only has wifi when I have it parked at home.
The v2 server update configuration is using the default for connected (60) and Idle (600)
Vehicle Module Hardware Info:
Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/3
Firmware: 3.3.004-4-gab8f16b7/ota_0/main (build idf v3.3.4-849-g6e214dc335 Mar 30 2024 08:08:21)
Running partition: ota_0
Boot partition: ota_0
Factory image: 3.3.001-33-g58d01654
OTA_O image: 3.3.004-4-gab8f16b7
Wifi Status:
Power: on
Mode: Access-Point + Client mode
STA SSID: <hidden> (-68.1 dBm) [fixed]
MAC: 24:d7:eb:73:93:cc
IP: 192.168.51.11/255.255.240.0
GW: 192.168.51.1
AP: d0:21:f9:51:a9:22
AP SSID: <hidden> (20 MHz, channel 6)
MAC: 24:d7:eb:73:93:cd
IP: 192.168.4.1
AP Stations: 0
The Leaf was in the mechanic's shop for ~3 weeks with no Wifi connectivity. When I brought the Leaf home, I did not realize it, but my custom ovms server was down. I got the server up and running, but even after waiting 15 minutes for the car to connect, it did not do so. Given the v2 server idle timeout was 600 seconds, I assumed that 15 minutes would be enough. I am able to connect to the module and my custom server with a web browser.
The module was on my wifi network, and connecting to its status page showed the following under the Server box:
State: Waiting for network connectivity
Server is ready to start
OVMS v3 server has not been started
On the status page of the module, clicking "Start v2" had no effect. Clicking "Stop v2" then "Start v2" made it work. The status now shows:
State: Connected
OVMS V2 login successful, and crypto channel established
Any idea why the vehicle module would not start the server and was stuck on "Waiting on network connectivity"?
The v2 or v3 servers will only start once the network connectivity is established.
That said, please make sure v2 server is set to auto-start under that section of the config.
The network was connected and it's set to auto start the V2 server.
The message from the v2 server "Waiting on network connectivity" means it is waiting for network connectivity (either wifi client or cellular). I am not aware of how it can be showing that message if there was actually connectivity established.
Perhaps if in that state, you can provide the output of:
If it happens again I will get you that info. Thanks!
But to be clear, it was on WiFi, I could connect to the IP address with my web browser, the server was running, and it was like this for over 15 minutes.
Hitting stop and start v2 instantly fixed the problem. :-)
markwj, here's the output you requested.
Keep in mind the server v2 is running on 192.168.51.10 (on my local network), I'm on that same network (192.168.51.15), and I'm http connected into the ovms module on my house wifi (not on the OVMS network). My OVMS can *only* access my server when it's parked in my garage at my house--there is no cellular connection.
So the module is clearly online since I'm connected to its webpage running these commands, on the same wifi network as the server v2. Yet it says it's waiting for a network connection (and will never recover).
This seems to happen when it's unable to reach my server for an extended period of time. For instance, I didn't realize it, but my server went down for ~48 hours, and when I got it back up, the vehicle module refused to reconnect... ever.
As always, clicking "stop V2" and then "start V2" on the OVMS status page (http://192.168.51.11/#/status) will get it functioning again.
OVMS# server v2 status State: Waiting for network connectivity Server is ready to startOVMS# module summary OVMS MODULE SUMMARY Module Version: 3.3.004-4-gab8f16b7/ota_0/main (build idf v3.3.4-849-g6e214dc335 Mar 30 2024 08:08:21) Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/3 12v: 12.3v MODEM Status Model: State: PoweredOff Ticker: 117474 User Data: 0 UART: FIFO overflows: 0 Buffer overflows: 0 Parity errors: 0 Frame errors: 0 Driver Buffer overflows: 0 Mux: Not running PPP: Not running GPS: Not running Configuration [auto] dbc: no egpio: no ext12v: no init: yes modem: no obd2ecu: ota: no scripting: yes server.v2: yes server.v3: no vehicle.type: NL wifi.mode: apclient wifi.ssid.ap: OVMS wifi.ssid.client: **redacted** (but it was correct) [can] [dbc] [egpio] monitor.ports: [http.plugin] [http.server] [locations] [log] file.enable: no file.path: level: info [modem] apn: hologram apn.password: apn.user: enable.gps: no enable.gpstime: no [module] cfgversion: 2022121400 init: done [network] dns: [notify] report.trip.enable: no [obd2ecu] [obd2ecu.map] [ota] auto.allow.modem: no auto.hour: 2 http.mru: https://ovms.dexters-web.de/firmware/ota/v3.3/main/ovms3.bin server: https://ovms.dexters-web.de/firmware/ota tag: [password] module: **redacted** server.v2: **redacted** server.v3: **redacted** [plugin] [plugin.disabled] [plugin.enabled] [plugin.repos] [power] 12v_shutdown_delay: 30 enabled: no modemoff_delay: 96 wifioff_delay: 0 [pushover] [sdcard] maxfreq.khz: 20000 [server.v2] port: 6867 server: 192.168.51.10 tls: no updatetime.connected: updatetime.idle: [server.v3] port: server: 192.168.51.10 tls: no topic.prefix: updatetime.connected: updatetime.idle: user: OVMS [ssh.info] fingerprint: **redacted** [ssh.keys] [ssh.server] key: **redacted** [system.adc] factor12v: 188.9 [tpms] [usr] [vehicle] 12v.alert: 1.6 12v.ref: 12.6 12v.shutdown: 11.5 12v.shutdown_delay: 5 12v.wakeup: 11.9 12v.wakeup_interval: 240 id: LEAF2017 minsoc: 7 name: stream: 0 timezone: CST6CDT,M3.2.0,M11.1.0 timezone_region: America/Chicago units.accel: miphps units.accelshort: mpss units.consumption: mipkwh units.distance: M units.distanceshort: feet units.pressure: psi units.speed: miph [wifi.ap] OVMS: **redacted** [wifi.ssid] **redacted** (but it was correct): **redacted** [xnl] autocharge: yes cabintempoffset: .0 canwrite: yes cfg_ev_request_port: 1 maxGids: 502 minrange: minsoc: modelyear: 2017 newCarAh: 115 rangedrop: soc.newcar: no socdrop: soh.newcar: no suffrange: suffrangecalc: ideal suffsoc: 69 REPORT ENDSConfig and status seems ok. Maybe you are seeing some bug after extended server outages (48 hours, as you say), that we haven't seen before.- probably because our primary public servers wouldn't be down for anywhere near that time.