Because the STA wifi was present, the modem connection was not used, but since the wifi was unstable, communication with the v2 server failed and connections attempts from the web client mostly timed out. This morning I changed wifi to client only, and now it is running reliably even though my router still indicates weak signal strength. So something about apclient mode makes this harder. -- Steve On Thu, 21 Jun 2018, Mark Webb-Johnson wrote:
Perhaps the wifi signal to the garage is just not good enough at this time (the router indicates a weak signal for that host).
Sounds possible. I think we discussed this before; about having the network connection tested and if it fails a lot then falling back to a lower-priority interface.
Regards, Mark.
On 21 Jun 2018, at 3:00 PM, Stephen Casner <casner@acm.org> wrote:
Mark,
Memory is fine. I had not set DNS 8.8.8.8 but changing that did not help. I stopped wifi and then started it again:
OVMS# wifi mode off Stopping wifi station... I (33798269) esp32wifi: Stopping WIFI station I (33798269) netmanager: Interface priority is pp3 (10.170.41.247/255.255.255.255 gateway 10.64.64.64) I (33798269) netmanager: Set DNS#0 8.8.8.8 I (33798269) netmanager: Set DNS#1 8.8.4.4 I (33798269) wifi: station: 60:03:08:9a:32:80 leave, AID = 1 I (33798279) wifi: n:7 0, o:7 0, ap:7 2, sta:7 0, prof:7 I (33798279) netmanager: Interface priority is pp3 (10.170.41.247/255.255.255.255 gateway 10.64.64.64) I (33798279) netmanager: Set DNS#0 8.8.8.8 I (33798279) netmanager: Set DNS#1 8.8.4.4 I (33798279) esp32wifi: AP station disconnected: id: 1, MAC: 60:03:08:9a:32:80 I (33798299) wifi: flush txq I (33798299) wifi: stop sw txq I (33798299) wifi: lmac stop hw txq I (33798309) netmanager: Interface priority is pp3 (10.170.41.247/255.255.255.255 gateway 10.64.64.64) I (33798309) netmanager: Set DNS#0 8.8.8.8 I (33798309) netmanager: Set DNS#1 8.8.4.4 I (33798309) netmanager: WIFI access point is down I (33798309) esp32wifi: AP stopped OVMS# wifi mode apclient US33 Revelstoke Starting WIFI as Access Point and Client... I (33836189) wifi: mode : sta (30:ae:a4:43:9c:28) + softAP (30:ae:a4:43:9c:29) I (33836199) netmanager: Interface priority is pp3 (10.170.41.247/255.255.255.255 gateway 10.64.64.64) I (33836199) netmanager: Set DNS#0 8.8.8.8 I (33836199) netmanager: Set DNS#1 8.8.4.4 I (33836199) netmanager: WIFI access point is up I (33836199) esp32wifi: AP started with SSID: US33, MAC: 30:ae:a4:43:9c:29, IP: 192.168.4.1 I (33839029) wifi: ap channel adjust o:1,1 n:7,2 I (33839029) wifi: n:7 0, o:1 0, ap:7 2, sta:7 0, prof:1 I (33839789) wifi: state: init -> auth (b0) I (33839789) wifi: state: auth -> assoc (0) I (33839789) wifi: state: assoc -> run (10) I (33839829) wifi: connected with Revelstoke, channel 7 I (33839829) wifi: pm start, type: 1 I (33867039) wifi: state: run -> auth (7c0) I (33867039) wifi: pm stop, total sleep time: 2396430 us / 27205294 us I (33867039) wifi: n:7 0, o:7 0, ap:7 2, sta:7 0, prof:7 I (33867039) netmanager: Interface priority is pp3 (10.170.41.247/255.255.255.255 gateway 10.64.64.64) I (33867039) netmanager: Set DNS#0 8.8.8.8 I (33867039) netmanager: Set DNS#1 8.8.4.4 I (33867039) esp32wifi: STA disconnected with reason 7 I (33873259) netmanager: Interface priority is pp3 (10.170.41.247/255.255.255.255 gateway 10.64.64.64) I (33873259) netmanager: Set DNS#0 8.8.8.8 I (33873269) netmanager: Set DNS#1 8.8.4.4 I (33873269) esp32wifi: STA disconnected with reason 201 I (33883259) netmanager: Interface priority is pp3 (10.170.41.247/255.255.255.255 gateway 10.64.64.64) I (33883259) netmanager: Set DNS#0 8.8.8.8 I (33883259) netmanager: Set DNS#1 8.8.4.4 I (33883259) esp32wifi: STA disconnected with reason 201 I (33893259) wifi: n:7 2, o:7 0, ap:7 2, sta:7 0, prof:7 I (33893259) wifi: state: auth -> auth (b0) I (33894259) wifi: state: auth -> init (2) I (33894259) wifi: n:7 0, o:7 2, ap:7 2, sta:7 0, prof:7 I (33894269) netmanager: Interface priority is pp3 (10.170.41.247/255.255.255.255 gateway 10.64.64.64) I (33894269) netmanager: Set DNS#0 8.8.8.8 I (33894269) netmanager: Set DNS#1 8.8.4.4 I (33894269) esp32wifi: STA disconnected with reason 2
Then I tried 'module reset', but that did not cure it, either. I set the STA wifi password again and at first it looked like that might have helped, but no. Perhaps the wifi signal to the garage is just not good enough at this time (the router indicates a weak signal for that host).
-- Steve
On Thu, 21 Jun 2018, Mark Webb-Johnson wrote:
Steve,
That is mg_parse_address in mongoose.c.
Seems to be quite a few conditions can result in 'cannot parse address', but not all of them about actually parsing addresses.
Is memory ok? I suggest you use dns '8.8.8.8 1.1.1.1' (rather than relying on access point dns servers), as that will cope better with a network interface switch.
Regards, Mark.
On 21 Jun 2018, at 12:58 PM, Stephen Casner <casner@acm.org> wrote:
My OVMS v3.1 has been installed in the car for some hours and now the network operations are stuck in some way. I detected this when I found that the app had no status for two hours. When I connect to the USB console, I see the reason:
I (28236429) ovms-server-v2: Connection is api.openvehicles.com:6867 US33 I (28236429) ovms-server-v2: Status: Connecting... W (28254039) ovms-server-v2: Connection failed E (28254039) ovms-server-v2: Status: Error: Connection failed I (28254239) ovms-server-v2: Status: Disconnected I (28273429) ovms-server-v2: Connection is api.openvehicles.com:6867 US33 I (28273429) ovms-server-v2: Status: Connecting... W (28290959) ovms-server-v2: Connection failed E (28290959) ovms-server-v2: Status: Error: Connection failed I (28291159) ovms-server-v2: Status: Disconnected
And now, as I look, a variation:
I (28527429) ovms-server-v2: Connection is api.openvehicles.com:6867 US33 I (28527429) ovms-server-v2: Status: Connecting... E (28533869) ovms-server-v2: mg_connect(api.openvehicles.com:6867) failed: cannot parse address| E (28533869) ovms-server-v2: Status: Error: Connection failed I (28547429) ovms-server-v2: Connection is api.openvehicles.com:6867 US33 I (28547429) ovms-server-v2: Status: Connecting... E (28553979) ovms-server-v2: mg_connect(api.openvehicles.com:6867) failed: cannot parse address| E (28553979) ovms-server-v2: Status: Error: Connection failed
OVMS# network status Interface#3: pp3 (ifup=1 linkup=1) IPv4: 10.170.41.247/255.255.255.255 gateway 10.64.64.64
Interface#2: ap2 (ifup=1 linkup=1) IPv4: 192.168.4.1/255.255.255.0 gateway 192.168.4.1
Interface#1: st1 (ifup=1 linkup=1) IPv4: 192.168.1.82/255.255.255.0 gateway 192.168.1.254
DNS: 192.168.1.254
Default Interface: st1 (192.168.1.82/255.255.255.0 gateway 192.168.1.254) OVMS# wifi status Power: on Mode: Access-Point + Client mode
STA SSID: Revelstoke MAC: 30:ae:a4:43:9c:28 IP: 192.168.1.82/255.255.255.0 GW: 192.168.1.254
AP SSID: US33 MAC: 30:ae:a4:43:9c:29 IP: 192.168.4.1 AP Stations: 0
Anything else to look at before I reset? The module does respond to ping, but not to the web browser nor ssh on the STA wifi.
-- Steve _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev