I can still think of let’s say an OpenSprinkler runtime error or some overload problem causing this “Empty Response” – issue. I don’t need the OpenSprinkler garage installation during this time of the year. I think I will investigate this during the winter season. However, I’m not sure if the Fritz!Box capture feature really monitors the intranet traffic between the WiFi repeater and the OpenSprinkler? The data traffic logged is more likely what is captured in or close to the Fritz!Box? It might be interesting to move the OpenSprinkler next to the Fritz!Box, to see if the issue still exists, if no WiFi repeater is involved. I only changed the CHECK_WEATHER_TIMEOUT parameter in this compilation. Please note that I used a private firmware compilation that requests the weather service every 20 minutes to get this log files. Please have a look at the attached log files. What I can see from the WireShark reports is, that there is no response data missing at all. The OpenSprinkler installed in my garage connects to the WiFi Repeater as this is the nearest local network access. The Fritz!Box allows for monitoring and analyzing the intranet and internet traffic via WireShark. My WiFi setup consists of a Fritz!Box 7590, a WiFi Repeater Fritz!WLANRepeater 310 and two PowerLines Fritz!PowerLine 1240E, Fritz!Powerline 1260E all organized as a Mesh System. I’ve done some investigations in June with OpenSprinkler Firmware 2.1.9 (4), and it is maybe worth to share my findings. Most of the time the weather service is requested successfully. The “Empty Response” isn’t always reported. I think it’s not caused by the recent firmware update. I encountered this issue with OpenSprinkler Firmware 2.1.9 (4), 2.1.9 (7) and actual with 2.1.9 (9). I encountered the same issue with often getting the OpenSprinkler “Empty Response” from my local weather service installed on a Raspberry PI. I switched back to DarkSky temporarily, but their rain data was extremely unreliable last summer. I made a settings export before the update and reloaded the settings after the update.įield “weather” was filled with 192.168.1.25, the IP address of the local weather service at What might have gone wrong?

System diagnostics at OS Web Interface says “Weather service: offline” and “Empty response” and it is not updating the watering percentage. > checked, it is workingįor test purposes, NodeRed queries OS to calculate watering percentage with the call Meteobridge sends data to the local weather service running on another RPi. PWS sends data, it is received my Meteobridge running on a RPi. I am not sure if it is connected to the update, but OS is not getting data from the local weather service.

Last weekend I updated to firmware version 2.1.9 (9) from 2.1.9 (7) and made some tests to change the wifi access point. My PWS powered local weather service was working happily with my OS through the summer months.

Raspberry pi fritz box traffic monitor