[Ovmsdev] Poor wifi performance

[Stephen Casner]

Last night the OVMS wifi claimed to be up while my router said OVMS
was not active (which I interpret to mean not associated).  I was
expecting the condition of OVMS to deteriorate further such that the
mg_connect error loop would occur again, but this morning wifi
connectivity was working again and OVMS had not rebooted.  I guess the
wifi reception improved enough to associate again.

                                                        -- Steve

On Fri, 21 Dec 2018, Stephen Casner wrote:

> I'm still having poor wifi performance with 3.1.011.  As with earlier
> releases, when I find OVMS is not responsive over wifi and connect to
> the serial port I find this error repeating:
>
> E (57630676) ovms-server-v2: mg_connect(api.openvehicles.com:6867) failed: cannot parse address|
> E (57630676) ovms-server-v2: Status: Error: Connection failed
> I (57637436) ovms-server-v2: Connection is api.openvehicles.com:6867 US33
> I (57637436) ovms-server-v2: Status: Connecting...
> E (57650836) ovms-server-v2: mg_connect(api.openvehicles.com:6867) failed: cannot parse address|
> E (57650836) ovms-server-v2: Status: Error: Connection failed
> I (57657436) ovms-server-v2: Connection is api.openvehicles.com:6867 US33
> I (57657436) ovms-server-v2: Status: Connecting...
>
> This can be cured by "wifi mode off" then "wifi mode client ..." to
> bring wifi back up again.  The really bad part is that the wifi system
> does not recognize that it has lost connectivity so the primary
> interface does not switch over to the modem.
>
> The "cannot parse address" error suggests that Mongoose is in some
> strange state.  I've put in some debugging code to investigate just
> how the parse is failing, and I'm waiting for it to get back into this
> error loop.
>
> Meanwhile, my ssh connection to OVMS dropped and my router says the
> OVMS station is down, so I went to hook up to the serial console
> again.  This mongoose complaint is not happening (yet).  But the wifi
> does not recognize that it has no association with my router:
>
> OVMS# wifi status
> Power: on
> Mode: Client mode
>
> STA SSID: Revelstoke (-81 dBm)
>   MAC: 30:ae:a4:43:9c:28
>   IP: 192.168.1.74/255.255.255.0
>   GW: 192.168.1.254
> OVMS# network status
> Interface#2: pp2 (ifup=1 linkup=1)
>   IPv4: 10.170.41.247/255.255.255.255 gateway 10.64.64.64
>
> Interface#1: st1 (ifup=1 linkup=1)
>   IPv4: 192.168.1.74/255.255.255.0 gateway 192.168.1.254
>
> DNS: 8.8.8.8 8.8.4.4
>
> Default Interface: st1 (192.168.1.74/255.255.255.0 gateway 192.168.1.254)
> OVMS# server v2 status
> State: Connected
>        OVMS V2 login successful, and crypto channel established
> OVMS#
>
> Even though server-v2 sends updates periodically, the failed wifi is
> not detected.  So I guess that is the root problem.  I'm expecting
> that after some time the mongoose state will deteriorate such that the
> parse error occurs again and I can at least investigate that part.
>
>                                                         -- Steve
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>
>