5 posts / 0 new
Last post
Lothsahn
Autostart connection to v2 server not working ("Waiting for network connectivity")
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). 
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"?
markwj
markwj's picture
Any idea why the vehicle

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.

Lothsahn
The network was connected and

The network was connected and it's set to auto start the V2 server.

markwj
markwj's picture
The message from the v2

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:

  • server v2 status
  • network status
  • module summary
Lothsahn
If it happens again I will

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.  :-)

Log in or register to post comments
randomness