OurWeather losing WiFi connection (looks like freeze)

Thanks, looking forward to new code. I've been monitoring github.com/switchdoclabs/OurWeatherWeatherPlus for new stuff ever since I discovered this issue. The "REST interface hanging" situation is clear, the forum threads about that are hard to miss. As the OLED should continue to update in that case I knew it must be something else (remember mine freezes).

I appreciate your support and fully understand your situation. I often find myself in your shoes for the open-source projects I maintain.

The good news is that v030 works i.e. it doesn't break anything AFAICT. The bad news is that it doesn't fix my problem.

Test procedure:

• OurWeather out on patio
• switch back to original AP (i.e. the temporary one on the patio turned off)
• OurWeather hooked up through FTDI
• serial monitor in Arduino IDE running
• no continuoues data gathering software i.e. no hits against the REST API

BTW, my thinking is that maybe all these WeatherUnderground failures are screwing with the web software. One difference in my system here is that I am transmitting to the weatherunderground all the time.

If you aren't using the WeatherUnderground, could you set up a station for an experiment? It's free and pretty easy to do. See the WeatherUnderground manual on

shop.switchdoc.com/products/ourweather-complete-weather-kit

under downloads.

I'm also working on the Thunderboard Interface too for OurWeather but before we release that, we would like to get this fixed.

BP

Your second test is pretty interesting. For it to be a valid one, we need to have the same external hardware and the same software hooked up to it. I still think this is a software problem (maybe in an ESP8266 library).

It would be interesting for you to take the same software that you used on your NodeMCU and then run it on the WeatherPlus ESP8266. Then we have an apples to apples test.

I am taking one of our units and putting a fail for WeatherUnderground on it and see what happens.

I'm liking that we are starting to get some real data on what this might be.

BP

The results are in but...they're inconclusive for me.

I had two devices out on the patio connected to the AP inside the house.
- device 1: naked NodeMCU v2 module on a breadboard running OurWeather v30
- device 2: fully assembled WeatherPlus Kit including all sensor running NodeMCU firmware and a small Lua script that provides an HTTP endpoint. Of course, neither access to sensors nor OLED are integrated into the software.

Both have been running for over 24h without a hiccup or freeze.

I made yet another effort over the Easter weekend. Flashed v31 to the WeatherPlus board and created a Wunderground account to let OurWeather publish data there. That worked for 8h until the system completely froze again. Then I opened the outdoor case for the umpteenth time, disconnected OLED & AM2315 and rebooted. 2h later the system was frozen again. So, I also unplugged the wind & rain plugs and rebooted the nearly naked system. Again, it stalled shortly afterwards.

As reported earlier in all cases the device was still pingable. However, it didn't upload data to WU when in frozen state. Hardware problems with any of the sensors can now definitely be ruled out.

Sorry, I'm done with this. I won't start to rebuild OurWeather on the NodeMCU stack (adding AM2315 et.al.) just to figure out what the problem could be. I've already invested way too many hours with debugging and analysis for what is essentially an off-the-shelve product; KickStarter or not.

Of course it's not just me who's frustrated, disappointed and annoyed but primarily my daughter who I built the weather station with and for. First the dead USB cable in the package, then the hassle/failure with the USB connector and now this.


I don't think I'm asking too much when I expect a replacement WeatherPlus board is going to be dispatched to me soon, right? I'm backer #9.