frightanic
New Member
Posts: 35
Raspberry Pi: Yes
Other Device: OurWeather (ESP8266), lots of ESP8266/ESP32 modules
|
Post by frightanic on Mar 15, 2018 12:47:28 GMT -8
Interesting. Is it a different type of WiFi router than has been dropping the connection? I can't be sure it's the AP that drops the connection but yes, the two APs are completely different. Do you have an idea how to analyze this any further or what measures to take? The AP out on the patio is just a temporary measure. Did you check the OurWeather code as for how it handles dropped WiFi connections? Are there stable enough measures to re-connect (with exponential backoff or the like)? Is there anything that should be reported on serial in such cases?
|
|
|
Post by SDL on Mar 15, 2018 15:02:15 GMT -8
Frightanic,
I just took your advice and looked at the WiFi code in OurWeather with regards to reconnect. It could be better. I'm wondering now whether I should explicitly require a reconnect if I detect a loss of WiFi. We were relying on the library code. I'll talk this over with John.
BP
|
|
frightanic
New Member
Posts: 35
Raspberry Pi: Yes
Other Device: OurWeather (ESP8266), lots of ESP8266/ESP32 modules
|
Post by frightanic on Mar 15, 2018 15:19:13 GMT -8
Right now it's still just an assumption that WiFi loss causes the system to freeze. I believe we can only ever be certain if you reported all WiFi events to serial. I also thought about DCHP lease renewal problems but pretty much ruled it out as lease duration is in days and OurWeather might freeze after less than 30min.
|
|
|
Post by SDL on Mar 15, 2018 15:40:27 GMT -8
Frightanic,
I think it is very telling that placing an AP outside has stopped this freezing you were experiencing. It is very suspicious. I'll see John tomorrow and see what he thinks.
This is not the browser and REST interface problem that is documented elsewhere.
BP
|
|
|
Post by SDL on Mar 16, 2018 15:32:01 GMT -8
Eduardogodinez,
You do very nice work. One more question. How far is each of the 3 stations away from the router and how does that correlate with lockup? I'm wondering if you have the same problem as frigthanic.
I still want you to shut off the data gathering software and see how the taffects the lockup.
BP
|
|
|
Post by eduardogodinez on Mar 19, 2018 14:43:22 GMT -8
Eduardogodinez, You do very nice work. One more question. How far is each of the 3 stations away from the router and how does that correlate with lockup? I'm wondering if you have the same problem as frigthanic. I still want you to shut off the data gathering software and see how the taffects the lockup. BP Thanks, 3 are less than 30 cms, in my office 1 meter from the AP, each of the four use a Nexxt Sparx201W As you can see in the pictures, all has the same configuration, The current status is: Numer of readings
| First Read
| Last Read
| IDStation - Status
| 1595
| 6/03/2018 16:15:00
| 19/03/2018 16:23:00
| 2 - Online
| 993
| 7/03/2018 12:36:00
| 17/03/2018 00:31:00
| 3 - hang up
| 355
| 8/03/2018 09:48:00
| 17/03/2018 17:00:00
| 1 - hang up
| 405
| 16/03/2018 12:17:00
| 19/03/2018 12:23:00
| 4 - Online
|
only one remain online
|
|
|
Post by SDL on Mar 20, 2018 6:06:00 GMT -8
Eduardogodinez,
I still want you to shut off the data gathering software and see how the that affects the lockup.
BP
|
|
frightanic
New Member
Posts: 35
Raspberry Pi: Yes
Other Device: OurWeather (ESP8266), lots of ESP8266/ESP32 modules
|
Post by frightanic on Mar 20, 2018 22:12:48 GMT -8
SDL if indeed eduardogodinez ' issue and mine are related (something which I have some doubts about) then data gathering is unlikely to have an impact. I for one don't normally run any data gathering software. Just to be sure though I started watch -n 30 curl 192.168.0.48/FullDataString and let that run for several hours. Uptime of OurWeather wasn't affected at all.
|
|
|
Post by SDL on Mar 21, 2018 13:21:33 GMT -8
Fritanic,
Good analysis. I don't think that it is the same problem. Your problem appears to be dropping of the WiFi connection (BTW, sending packets to the device may keep the wifi in place longer - depends on what your AP and the OurWeather ESP8266 are doing). You have demonstrated that.
The freezing of the OurWeather system due to reading from other computers is dependent on the method. We get different results from different browsers (see various threads in the forum) and with different software add-ons in the browsers. Using Visual Studio to do this is yet another way that this problem could occur. I don't know. What Eduardo and I are doing is eliminating possibilities.
You doing the below is good thinking. yet another way to test the data link. Eduardo, do this and report back.
watch -n 30 curl 192.168.0.48/FullDataString Best regards,
BP
|
|
frightanic
New Member
Posts: 35
Raspberry Pi: Yes
Other Device: OurWeather (ESP8266), lots of ESP8266/ESP32 modules
|
Post by frightanic on Mar 22, 2018 8:14:31 GMT -8
|
|
|
Post by SDL on Mar 23, 2018 7:31:09 GMT -8
Eduardo,
OK. Now we have made progress. Since the Weather Station is returning Pings even when "hung" that means that the Wifi is connected (so as suspected frightanic has an entirely different problem) and it is your reading the REST interface the tis hanging the system. IT has something to do with the way your software is interacting with the HTTP calls. Some browsers do this and I suspect the way you are reading the data is doing it.
Do the following:
1) Shut off your data gathering software
2) run the following software on your data gathering software:
watch -n 30 curl 192.168.0.48/FullDataString replacing the IP address with the IP address of your OurWeather unit.
You may have to devise a different way of reading data. Using a different package or a different language.
Best regards,
BP
|
|