[Tom]

OK Got it William. Yes it’s possible I guess that my use of Zimmerman may be masking a latent issue with the CA Restrictions setting. I really don’t know what that setting is doing in the code.

[Tom]

I’m using Zimmerman with CA Restriction enabled and it seems to be working fine. I’m using the latest version of firmware (2.1.6). Yes, water level comes back in weather diagnostics as 0%, but if you run through the Zimmerman calculation by hand it comes out to -1xx, which clamps to zero. So I think with the latest firmware things are working fine. Also, it’s a nice add to the weather diagnostics that shows the “Last Successful Weather Call” which tells you the last time the OpenSprinkler unit was able to successfully call for weather info. If this shows a recent timestamp, then the OpenSprinkler can get out to the Internet.
tom

[Tom]

OK so “scale” is the value which is returned and used by openSprinkler for % precipitation adjustment. Thanks.

[Tom]

OK then forgive me but I thought zimmerman method used mean temp, precip, humidity. So is zimmerman calc done on server? if so which of these parameters are used? If there is a link describing these parameters and their use pls just provide that and I’ll take a look.

Thanks again.
tom

[Tom]

Hello,

Just noticed I’m not getting proper weather adjustment on OpenSprinkler.

If I use a rest client and do the following GET:

http://weather.opensprinkler.com/weather1.py?loc=pws:KCAROSEV19&key=542f5f8759cd342b

…I get the following response:

&scale=0&rd=-1&tz=16&sunrise=394&sunset=1021&eip=1145262083

Which is different from what I used to get:

scale=0&tz=20&sunrise=422&sunset=1159&maxh=90&minh=50&meant=61&pre=0.130000&prec=0.020000&hc=44&eip=1145262083

… as you can see I’m no longer getting info about humidity, precip, and mean temp.

Any help would be appreciated.

Tom

[Tom]

Hi,

I rebooted the openSprinkler and all problems seem to have gone away. I’ll continue to test the network connectivity to verify things are working well. Thanks for your help.

Tom

[Tom]

OK thanks that info was very helpful. Now I think I understand. I didn’t realize the app was pinging the WU directly for all the weather info and the controller only for the % watering factor.

I agree the controller seems to be having trouble connecting. It is able to talk on my local subnet ok (with some intermittent issues which was the subject of the other post), but it cannot seem to communicate with the Internet at all.

I will try to eliminate the wired Ethernet connection as a suspect next.

In the meantime, can you tell me if there is an easy way to verify if the controller can actually reach the Internet? I’ll try a few things as well…

Thanks for all your help.

Tom

[Tom]

Hi,

I’ve tried changing the station location several times; each time the “weather diagnostics” changes almost immediately. That is, everything changes except for the “Current % Watering” value which remains at 14% always. Not sure how long I need to wait to see if that changes.

So then I used a REST client to hit the URI you gave me with the added parameters of “loc” and “key”. Here is the URI:

http://weather.opensprinkler.com/weather1.py?loc=pws:KCAROSEV19&key=542f5f8759cd342b

And the GET returned the following response:

scale=0&tz=20&sunrise=422&sunset=1159&maxh=90&minh=50&meant=61&pre=0.130000&prec=0.020000&hc=44&eip=1145262083

…so if I then look on the WebApp and check the “Weather Diagnostics” I get the attached screenshot.

Interestingly, however, if you plug in the values into the algorithm you get -106.4 which should be clamped to zero. And yet the screenshot shows the % watering is invariant and still at 14% regardless of station.

Now looking at the response from the GET I see that “scale” is CORRECT in the response to the GET, but wrong on the openSprinkler.

So does this mean my openSprinkler is not communicating properly?

What I don’t understand is: how can the openSprinkler get all the values correct except one??

Tom

Attachments:

1. 

   Screen-Shot-2015-03-23-at-6.35.38-PM.png
   

[Tom]

Screen shot from the OpenSprinkler manual.

Tom

Attachments:

1. 

   Screen-Shot-2015-03-22-at-6.27.38-PM.png
   

[Tom]

Hi again,

It appears I too am experiencing problems with the Zimmerman method calculation. Here is what my weather diagnostics say:

• Min Humidity    50%

• Max Humidity    90%

• Mean Temp    61.9

• Precip yesterday 0.13″

• Precip today        0.02″

• Current % Watering  14%

–> However, if I plug these values into the equation I get -102.4 which means the value should be clamped at zero, right? Further, the % watering has not changed in several days even though previously we received no rain and the calculation yielded significantly higher numbers (like around 30).

It appears no matter what, the number is stuck at 14%. Any ideas?

Thanks.

Tom

Attachments:

1. 

   Screen-Shot-2015-03-23-at-7.03.43-AM.png
   

[Tom]

OK those are great suggestions; I’ll investigate some more and get back to you. Thanks for the quick response!

Tom

[Tom]

Yep I figured I could do that. Just thought it might be a nice feature to avoid having to create a program just to be used once.

Thanks.

Tom

[Tom]

I don’t think you understood my request. I would like to test the operation of the rain sensor feature, assuming the rain sensor works.

Right now, the only way to test my rain sensor feature is to wait until one of my regularly-scheduled programs starts, and then actuate the rain sensor.

This would be simple to do. Just make the rain sensor affect either the “test station” feature or the “run once” feature. Right now they both appear to ignore the rain sensor.

Thanks again.

Tom

[Tom]

Great. Thanks.

[Tom]

Yes agree this would be a great add. Unfortunately, I’m pretty sure Apple’s MFI program (which HomeKit is under) requires a hardware component to be added to your device (approx cost $4), which would require a mod to the board, as well as make all legacy devices incompatible. Still, food for thought.

Tom

[Tom]

Hi,

I recently purchased and installed openSprinkler; I’ve been using it for about three weeks.

I’ve been experiencing intermittent “network failures” as well. Basically the OS unit goes away periodically and I cannot talk to it via either the webApp or the iPhone app. If I wait a few minutes, it always comes back. This happens several times a day.

I’m on the same subnet using local access for both webApp and iPhone app (webApp via computer on wired Ethernet; iPhone app on wifi). My OS unit is using DHCP as recommended. The unit’s IP add is not changing, so that is not the problem. And, I have the OS unit connected via a dedicated Ethernet cable so no wifi issues.

I’m currently running firmware 2.1.2 with hardware version 2.2.

Any suggestions would be appreciated.

[Tom]

Hi,

I’m new here so sorry if the question is a repeat. I see the Zimmerman algorithm needed a fix which was recently added. Can you tell me which firmware requires the fix? Right now I’m running OS with 2.1.2 firmware.

So my main questions are:

1. Is the algorithm correct with 2.1.2?

2. If I upgrade to 2.1.3, will I need to patch the algorithm (appears so from above thread)?

thanks.

tom

[Author]

Posts