[franzstein]

Yes.

Attachments:

1. 

   Configuration.jpg
   

[franzstein]

There is no general rule how to setup these values. I run my sprinklers every second day with a default time of 30 minutes. The only change I made is to set the humidity base to 65%, which I found more suitable for German weather conditions. You have to play a little bit with the setup to find out what best suits your needs.

It is also a good idea to search the forum for e.g. ‘Zimmerman’ and read through the posts to get some ideas. I’m using Zimmerman since two years now and don’t see any bigger issues. The parameters can be easily adjusted.

[franzstein]

My updated post with the typo in the command line is still awaiting moderation!

Nevertheless, You will find the same story in the post “local-weather-service-onto-a-raspberry-pi-issue given above”. Please have also a closer look at the post from November 5, 2019 at 4:56 pm. If you follow this comments given by @Peter you can have a look in the observations.json file to see a history of the data available right now.

[franzstein]

Please have also a look at https://opensprinkler.com/forums/topic/local-weather-service-onto-a-raspberry-pi-issue/. There are some more hints given to this issue.

[franzstein]

Sorry. There was a typo in the command line for the weather service check. See correction above!

[franzstein]

The Baseline_ETo_Data.bin file has to be downloaded separately from: http://www.mediafire.com/file/n7z32dbdvgyupk3/Baseline_ETo_Data.zip/file.

I’m not sure about your configuration? For example, you have to tell OpenSprinkler the IP address of the weather server. Is it 192.168.1.50:3000? What is the OpenSprinkler IP? I have a different local IP for OpenSprinkler.

You can check that the Weather Service is working via:

http://192.168.1.50:3000/weather1.py?loc=49.47369,10.94380&wto=”h”:100,”t”:100,”r”:100,”bh”:70,”bt”:60,”br”:0

Please modify the command with your GPS coordinates!!!

This should result in something like

&scale=19&tz=56&sunrise=311&sunset=1282&eip=3232281125&rawData={“weatherProvider”:”local”,”h”:77.97,”p”:0.2,”t”:57,”raining”:1}&errCode=0

[franzstein]

Looks great! You can omit the ETo error message if you copy the Baseline_ETo_Data.bin file to the ~\weather\baselineEToData\ directory.

[franzstein]

I use WeeWX 3.9.2 right now. There are problems with WeeWX 4.0.0 in conjunction with Netatmo PWS. Please have a look at: https://github.com/matthewwall/weewx-netatmo/issues/15.

[franzstein]

I use Meteoware in addition to WeeWX to transfer the Netatmo data to Wunderground. In cases of heavy rainfall the precipitation summaries of WeeWX gives less rain amounts than Netatmo or Wunderground. Everything else works perfect!

[franzstein]

You have to install the weather service locally and change the address of weather service to your local installation, e.g. 192.168.178.33:3000.

[franzstein]

Yes. It’s necessary to install the weather service locally. Please refer to https://github.com/OpenSprinkler/OpenSprinkler-Weather/blob/master/docs/local-installation.md for details.

[franzstein]

Interesting question! From what I know it transmits data to the local weather only, if you add the server_url line to the Wunderground section. In general it should be possible to transmit to Wunderground, too. However, there are probably some changes to WeeWX needed?

[franzstein]

I’m using a Netatmo Weather Station consisting of an indoor and outdoor module, a rain gauge and an aenometer in conjunction with OpenSprinkler DC 3.1. The rain gauge can’t be used as a standalone product. The Netatmo Weather Station sends encrypted weather data peridiocally to netatmo servers. The encryption blocks end-users from accessing the data. You have to use the netatmo API to obtain the data from the netatmo servers.

The corresponding setup of how to connect a Personal Weather Station to a Local Weather Service is described here: OpenSprinkler Weather Service.

[franzstein]

Today I updated my OpenSprinkler 3.1 – DC from Firmware Version 2.1.9 (2) to 2.1.9 (3). The update went very easy. No factory reset and no change of the WiFi address was performed during the update process. There was also no need to restore the saved configuration, as everything was still in place afterwards. However, after the update the OpenSprinkler’s clock is ahead with 10 hours! I checked the timezone variable “tz”:56, which corresponds to my local time UTC+2.

After following the hints given in this thread I changed the NTP IP address from 50.97.210.169 to 0.0.0.0, which will make OpenSprinkler use the default NTP server pool.ntp.org. This gives the correct local time again and solves the issue!

I am not sure where the NTP IP address 50.97.210.169 comes from? I think it’s not pointing to a valid NTP server anymore and has to be removed to get the correct local time.

[franzstein]

@Ray Thanks for your quick response. The screenshot shows yesterday’s watering at my local time 7:00 am. Immediately after the watering the water level was given with 67%. It changes thereafter!

Running above command gives:

	
0	
0	0
1	"wl"
2	68
3	1586570325
1	
0	0
1	"wl"
2	68
3	1586577527
2	
0	0
1	"wl"
2	67
3	1586584729
3	
0	0
1	"wl"
2	65
3	1586592079
4	
0	0
1	"wl"
2	64
3	1586599281
5	
0	0
1	"wl"
2	62
3	1586606483
6	
0	0
1	"wl"
2	61
3	1586613685
7	
0	0
1	"wl"
2	61
3	1586620887
8	
0	0
1	"wl"
2	62
3	1586628089
9	
0	0
1	"wl"
2	63
3	1586635291
10	
0	0
1	"wl"
2	62
3	1586642493
11	
0	0
1	"wl"
2	61
3	1586649695
12	
0	0
1	"wl"
2	60
3	1586656897
13	
0	0
1	"wl"
2	58
3	1586664099
14	
0	0
1	"wl"
2	56
3	1586671301
15	
0	0
1	"wl"
2	55
3	1586678503
16	
0	0
1	"wl"
2	54
3	1586685705
17	
0	0
1	"wl"
2	56
3	1586692907
18	
0	0
1	"wl"
2	59
3	1586700109
19	
0	0
1	"wl"
2	59
3	1586707311
20	
0	0
1	"wl"
2	58
3	1586714513

The corresponding Unix time to look at is 1586584729. Our local time zone is GMT+2, due to the summertime valid now.

[franzstein]

@Peter, You are right. I changed to my locally hosted Weather Service and realized thereafter that I still receive the weather data from WU. Depending on the existence of a WU Key and PWS name the weather data is received from WU or local WeeWX reports.

Sorry for the confusion.

[franzstein]

@prinzeisenherz1, Please try this again. First you have to enter your Wunderground Key and thereafter select the location with the PWS reporting to Weather Underground.

It has worked for me!

Attachments:

1. 

   Screenshot_20191107-141920_OpenSprinkler1.jpg
   

[franzstein]

@Peter, well done, weather data is reported now:

http://192.168.178.39:3000/weather1.py?loc=49.47369,10.94380&wto="h":100,"t":100,"r":100,"bh":70,"bt":65,"br":0

&scale=0&tz=52&sunrise=434&sunset=1007&eip=3232281125&rawData={"weatherProvider":"local","h":91.4,"p":0.01,"t":45.4,"raining":0}&errCode=0

Many Thanks.

[franzstein]

@peter, Ok let’s see if things are runnining by tomorrow.

There is also a forum “edit” problem or maybe it’s to late for me and I should better go to bed? Please find below a copy of the now missing #63163 reply.

@peter, thanks again for your help. Unfortunately there exists still a problem with the weather data.

Requesting the weather service with e.g.:

http://192.168.178.39:3000/weather1.py?loc=50,1&wto=“h”:100,”t”:100,”r”:100,”bh:70,”bt”:59,”br”:0

results in:

&errCode=10&scale=100

Looking at syslog shows:

….
Nov 5 21:58:21 raspberrypi weewx[19139]: restx: Wunderground-PWS: Published record 2019-11-05 21:55:00 CET (1572987300)
Nov 5 21:58:24 raspberrypi weewx[19139]: cheetahgenerator: Generated 8 files for report SeasonsReport in 3.14 seconds
Nov 5 21:58:25 raspberrypi weewx[19139]: imagegenerator: Generated 14 images for SeasonsReport in 1.00 seconds
Nov 5 21:58:25 raspberrypi weewx[19139]: copygenerator: copied 5 files to /var/www/html/weewx
Nov 5 21:59:29 raspberrypi npm[16942]: There is insufficient data to support Zimmerman calculation from local PWS.
….

Looking at old syslog files shows that these kind of logs are still missing:
Jun 14 23:55:49 raspberrypi npm[357]: OpenSprinkler Weather Observation: {“action”:”updateraw”,”ID”:”anyText”,”PASSWORD”:”anyText”,”softwaretype”:”weewx-3.9.1″,”baromin”:”29.854″,”dewptf”:”57.4″,”humidity”:”062″,”dateutc”:”2019-06-14 21:55:00″,”dailyrainin”:”0.00″,”winddir”:”161″,”tempf”:”71.1″,”windspeedmph”:”0.6″,”windgustmph”:”2.5″,”rainin”:”0.00″}

Sorry for bothering you again.

[franzstein]

@PrinzEisenherz1, please be aware that the OpenSprinkler Weather Service in its newest version 2.0.1 provides a different Weather Underground interface.

The weather observation is calculated over the last 24 hours and not for the last day. The values given by the system diagnosis are therefore different, if compared to the Weather Underground website. Please have a look at the corresponding Weather Server GitHub repository for details.

I don’t know why this has changed? In my opinion, using yesterdays weather data might be the more preferable solution for the Zimmerman Watering Method.

[franzstein]

@peter, many thanks for your help. I have changed the port setting to 3000 and the Weather Service is running now without errors.

Unfortunately, there is still a problem with WeeWX’s built-in Weather Underground plug-in. I am running WeeWX and the Weather Service on the same Raspberry PI. According to the hints given in The WeeWX Project I have modified the /etc/weewx/weewx.conf file as follows:

    [[Wunderground]]
        enable = true
        station = anyText
        password = anyText
        server_url = http://127.0.0.1:80/weatherstation/updateweatherstation.php
        rapidfire = False

Unfortunately, WeeWX failed to send the weather observation onto the local Weather Service:

pi@raspberrypi:~ $ sudo /etc/init.d/weewx start
[ ok ] Starting weewx (via systemctl): weewx.service.
pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
Nov  5 09:26:45 raspberrypi weewx[18240]: engine: Using binding 'wx_binding' to database 'weewx.sdb'
Nov  5 09:26:45 raspberrypi weewx[18240]: manager: Starting backfill of daily summaries
Nov  5 09:26:45 raspberrypi weewx[18240]: restx: StationRegistry: Registration not requested.
Nov  5 09:26:45 raspberrypi weewx[18240]: restx: Wunderground-PWS: Data for station anyText will be posted
Nov  5 09:26:45 raspberrypi weewx[18240]: restx: PWSweather: Posting not enabled                                                        .
Nov  5 09:26:45 raspberrypi weewx[18240]: restx: CWOP: Posting not enabled.
Nov  5 09:26:45 raspberrypi weewx[18240]: restx: WOW: Posting not enabled.
Nov  5 09:26:45 raspberrypi weewx[18240]: restx: AWEKAS: Posting not enabled.
Nov  5 09:26:45 raspberrypi weewx[18240]: engine: Starting up weewx version 3.9.2
Nov  5 09:26:45 raspberrypi weewx[18240]: engine: Starting main packet loop.
Nov  5 09:31:47 raspberrypi weewx[18240]: manager: Added record 2019-11-05 09:30:00 CET (1572942600) to database 'weewx.sdb'
Nov  5 09:31:47 raspberrypi weewx[18240]: manager: Added record 2019-11-05 09:30:00 CET (1572942600) to daily summary in 'weewx.sdb'
Nov  5 09:31:50 raspberrypi weewx[18240]: cheetahgenerator: Generated 8 files for report SeasonsReport in 3.13 seconds
Nov  5 09:31:51 raspberrypi weewx[18240]: imagegenerator: Generated 14 images for SeasonsReport in 1.01 seconds
Nov  5 09:31:51 raspberrypi weewx[18240]: copygenerator: copied 5 files to /var/www/html/weewx
Nov  5 09:32:02 raspberrypi weewx[18240]: restx: Wunderground-PWS: Failed to publish record 2019-11-05 09:30:00 CET (1572942600): Failed upload after 3 tries

I’m not sure what causes the problem? There is maybe a change in the WeeWX Wunderground interface. The WeeWX change history 3.9.2 (14 Jul 2019)states:

Posts to the Weather Underground now use https, instead of http. Thanks to user mljenkins! PR #378.

Any ideas how to solve this issue?

[franzstein]

Hi Rob,

Enabling or disabling a “warm day afternoon program” has to be done manually or you have to use the OS API Interface for this purpose.

One possibility for temperature control might be to use the IFTTT Webhooks feature to send corresponding API commands to OS. IFTTT interfaces for Private Weather Stations (PWS) like Netatmo or weather services like Weather Underground (WU) allow for triggers like temperature rises above or drops below x °C.

Please have a look at discussions like Enable/Disable Program and look at other examples given in this forum for IFTTT applets.

Hope to be some help.

Regards

Franz

[franzstein]

There is no minor revision shown in the About information. Is there another way to check the firmware details? I think I will wait for the 2.1.9 firmware release to update my OpenSprinkler. I don’t need the feature to enable or disable an existing program right now. But it is good to know that it will be at least available with the latest 2.1.8 firmware release.

Attachments:

1. 

   OS-About.jpg
   

[franzstein]

Hello Ray,

I have tried to use the change program (/cp) API to enable or disable an existing program. Unfortunately, it does not work as described. The error returned is {“result”:16} Data Missing (e.g. missing required parameters). Details are:

Get Program Data via http://x.x.x.x/jp?pw=xxx results in:

{“nprogs”:2,”nboards”:1,”mnp”:35,”mnst”:4,”pnsize”:16,”pd”:[[51,1,2,[420,0,0,0],[1800,1800,1800,0,0,0,0,0],”Summer 2019″],[50,1,2,[16474,0,0,0],[600,600,600,0,0,0,0,0],”Hot Summer 2019″]]}

Enable program via http://x.x.x.x/cp?pw=xxx&pid=1&en=1 results in:

{“result”:16}

App Version: 2.0.3, Firmware: 2.1.8, Hardware version: 3.0 – DC

Any ideas?

[franzstein]

I updated above table to reflect OpenSprinkler-Weather service Version 2.0.0 changes.

.------------------------------------------.
| Weather  | Watering | Weather  |    ET    |
| Provider |   Data   |   Data   |   Data   |
|----------|----------|----------|----------|
| DarkSky  |   Yes    |   Yes    |   Yes    |
|----------|----------|----------|----------|
|   OWM    |   Yes    |   Yes    |   Yes    |
|----------|----------|----------|----------|
|    WU    |   Yes    |    No    |    No    |
|----------|----------|----------|----------|
|  Local   |   Yes    |    No    |    No    |
°----------°----------°----------°----------°

According to Ray’s Announcement DarkSky is used as the default Weather Provider. OWM’s data quality is rather poor, which is also true for my location. Weather Underground (WU) does not provide average solar radiation. It can’t be used for the ET Weather Adjustment Method.

[Author]

Posts