Michael, My observations are consistent with Issue 112. Just now, as I prepared to answer your email, I found that I could not ping or ssh to OVMS. When I connected to the serial console, wifi and network status indicated UP. Shortly after connecting I also saw log messages from server-v2 indicating messages sent, yet the iPhone app said 23 minutes since OVMS was heard. Then shortly thereafter I started getting the connection attempt loop with "mg_connect(api.openvehicles.com:6867) failed: cannot parse address" indicating hostname lookup failure. I restored connectivity with "wifi mode off" then "wifi mode client". In this instance, my router indictated that OVMS was associated, but I have had instances in the past where the router indicated that OVMS was not associated and yet OVMS claimed wifi was up. So, yes, I definitely believe that the wifi system is failing to detect and report disconnects. But even if that is fixed, there may be instances where there is a network problem upstream from the access point that prevents the server from connecting. In those cases we should try backing off to the modem. The iPhone does that for its connection if enabled in the configuration. If Mark does not have code for this in process already, maybe I can help. Is there any additional diagnostic logging that could be added to determine whether the wifi driver is failing to indicate the disconnection or our esp32wifi code is missing the indication? I am running with the current openvehicles/esp-idf. I have not tried espressif/esp-idf. I was hoping to dig into this event using the log file, but when I connected I found that the system had restarted on an illegal instruction exception after I entered the log-to-file command two days ago. -- Steve On Sun, 30 Dec 2018, Michael Balzer wrote:
Steve,
we've got an open issue on the connection failure detection: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/112
Mark also planned to do a rework of our Wifi integration to better handle some event situations IIRC. But do you see a wifi system event on connection loss, that should be handled? The situations I checked did not show any events we should have handled better, it just lost the connection.
Can you try the current idf version? There are quite some Wifi related entries in the change history, I'm still hoping the update will solve some of these problems.
If you hesitate because of the config partition problem: that's just a one time event when doing the upgrade, you can restore your config afterwards.
Regards, Michael