Network error

I, too, had this problem and found that the only solution was to reboot OpenSprinkler. I also run HomeSeer, and developed an event to recognize when OS was offline to warn me.

I tried any number of approaches, including an access point that was just 10 feet away. I finally gave up and switched to OpenSprinkler Pi. The Pi has a much more robust TCP/IP stack. Haven’t had the problem since, and the access point is now 20′ and two walls away. (My original OS installation had a wired ethernet connection to a TP-Link powerline connection. That worked just fine, although I really dislike using powerline for communications.)

Incidentally, I’m impressed by the reliability of the wifi connection on the OSBee. I have two of those, both out-of-doors, one of them using solar power and the other powered by the 24VAC sprinkler power (bucked down). Even in the worst of winter here, -20 degrees F in the early morning, both of these continue to communicate.

Rog

I’ve just compiled a fresh instance 2.1.9(9) and uploaded to a wemos d1 and having the same problem, getting Network Error and a notification about corrupted weather data. Running a 2.1.9(3) version on an ESP32 over a year without any issues, that one can gather the weather data correctly. Any idea how to solve this problem? (otherwise if I turn of the location everything works fine.)

It was a fresh upload to a brand new Wemos D1 module. I’ve already tried the factory reset but didn’t help. Can you give me a hint how to use the http api to reset the corrupted string?

This is definitely not a known issue for firmware 2.1.9(9). I am not sure whether it has to do with your Wemos. Probably the easiest way to set the parameter is to go to:
http://raysfiles.com/os/TestOSAPI.html
type in your OpenSprinkler’s IP, port number, password, choose the ‘Change Option (co)’ API, then
Option name: wto
Option value: {}
this will set an empty string for wto. Hopefully it works.

Honestly I really don’t know what’s causing it. We’ve tried everything we can, including changing the Ethernet library and released 2.1.9(10) which you’ve tried. We have never been able to reproduce the issue internally, so without observing the issue happening we can’t debug it. Also, what zsolesz79 was asking is a separate issue — it has to do with a corrupted flash memory string, this has nothing to do with losing Ethernet connection.

update: I couldn’t clear the “wto” string with value: {} as you advised, it still shows corrupted characters: “wto”:{���y”:””}

I’ve tried this:
Option name: wto
Option value: “key”:””
With this I’m getting “wto”:{“key”:””} and the error disappears, weather service working again until I change the location again on the GUI.

I’m using wifi only

Do you have a download link for a compiled stock version? Unfortunatelly I don’t have another nodemcu to test with, I’ll get one next week.

I’ve tried with rev9, it looks good. So I assume my problem had to with the compilation but I don’t know why. I’ve download the sources from github, put them into the platformio project directory and hit Build. Got no errors at all so I don’t know where to look for the problem 🙁
(I’ve tried to compile it Arduino IDE too without any problems but still getting the error… )

I am glad to hear you’ve figured it out, although I am still puzzled why newer ESP8266 platform would result in such difference. Do you know the esp8266 core version that these newer platforms use? The current OpenSprinkler firmware is compiled with ESP8266 core 2.7.4 (as shown in the Makefile and build instructions). I’ve compiled it with the latest core version 3.0.2 as well but have not fully tested it. I am not sure what core versions platformio uses.

I am surprised you were able to get the firmware compiled with core 3.0.0. It has been a while but I remember when I tried to compile the firmware with 3.0.2 I had to make a number of significant changes to even get it to compile. The main advantage of core 3.0.x is that it unifies the handling of WiFi with wired Ethernet (using lwip2). Since both use the same WiFi API functions, OTA update works with wired Ethernet as well (currently with firmware 2.1.9 OTA updates only works with WiFi as wired Ethernet uses a separate library). I will probably check in the changes I made to a separate branch on github. I made the changes as an initial step to prepare for firmware 2.2.0, but it’s quite far from being completed.