[natebarnz]

Apparently they changed the subdomain on freshdesk to openthings. https://openthings.freshdesk.com/support/home

I took me quite a while to somehow come across this. Would be nice if they updated their docs.

[natebarnz]

Hi Ray,

The system appears to crash. I cannot connect to it with the iphone app, chrome app, or direct ip address. The direct ip address connections loads the black screen and even says loading for a second before going totally black. The API does not respond either. So far the only solution has been to power cycle the unit.

I will submit the support ticket as you said.

Thanks
-nate-

[natebarnz]

Hi,

Since I upgraded to the latest firmware my DC 2.3 model seems to crash once every day or two. I have never had an issue before and now I have to manually turn the unit off and then back on to fix the problem.

Has anyone else experienced this since upgrading?

Thanks
-nate-

[natebarnz]

@Ray: Thanks for your response. I actually could never get my time zone to set correctly until I manually set it before selecting a location. After I selected my location and added my api key the ability to manually change the time zone was lost. So to be clear I never was able to get the time zone from setting my location. I’ve tried resetting to factory defaults more than once along with the most minimal configuration possible to try and get the weather calls to be successful. Is there a chance my unit is defective in some way? I doesn’t seem likely to me however I’m at a complete loss at this point.

[natebarnz]

Lots of great information. Thanks Ray and DaveC.

I ran a series of tests from my rpi server (see results below) on the same switch connected to the same router via DHCP, just as my OS device is. I have tried zip,lat/long,city/state,pws as loc settings in the past and nothing has ever returned a successful call for me. Also just to confirm all my DHCP devices have no connectivity issues and I have quite a few scripts running from cron sending and receiving data from my internal servers.

curl “http://weather.opensprinkler.com/weather0.py?loc=85749”
&scale=-1&rd=-1&tz=20&sunrise=446&sunset=1058&eip=*********

This one using zip and my wunderground api key with weather1
curl “http://weather.opensprinkler.com/weather1.py?loc=85749&key=*********”
&scale=0&rd=-1&tz=20&sunrise=444&sunset=1057&eip=*********

And using my weather station
curl “weather.opensprinkler.com/weather1.py?loc=pws:KAZTUCSO435&key=*********”
&scale=0&rd=-1&tz=20&sunrise=444&sunset=1057&eip=*********

And just for good measure I did a weather2 call
curl “weather.opensprinkler.com/weather2.py?loc=pws:KAZTUCSO435&key=*********”
&scale=-1&rd=-1&tz=20&sunrise=444&sunset=1057&eip=*********

From what I can tell the data being returned seems accurate and in the correct format.

@Ray: Is there a way to initiate the firmware weather call and see its results? Is there another way to test that the firmware can reach the outside world properly to prove that it is or isn’t a connectivity or network settings issue? When I test my wunderground API key from the UI does it run it through the firmware or does it just test from the UI? My OS is on DHCP which all my other devices use successfully.

Any further help to try and isolate the issue would be great.

Thanks
-nate-

[natebarnz]

Hi DaveC,

Thanks again for all your help. I had no issue looking up the host from an internal server however my traceroute seems a little odd, it stops before it got to the final ip (see routes below). I also tried setting my location to “Tucson, Arizona” and “Tucson, AZ” but was not able to get either to set properly. After I imported the updated settings file it ended up setting “loc” to “undefined” on both attempts (example settings file below).

I’m also still a bit confused because when I have the location set to lat/long or a weather station it does show correct data in the “weather diagnostics” screen (see attached image). This makes me assume that it is making some sort of successful call to the wunderground API in which it returns the data that it prints on the screen. I’m assuming its making the call ok but just not saving or setting it on the system. Unless OS is waiting for some sort of call back that gets blocked by the firewall, however I would guess that it would be documented if this were the functionality since most people likely have their OS behind a firewall.

I noticed my eip is always set to 0, could this be a problem?

If I could simulate the real call from a local server to see what happens that certainly would be great. Ray can you help with that?

Thanks!

weather.opensprinkler.com is an alias for os-weather.elasticbeanstalk.com.
os-weather.elasticbeanstalk.com has address 54.148.153.152
os-weather.elasticbeanstalk.com has address 52.10.151.144

traceroute to 54.148.153.152 (54.148.153.152), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 0.538 ms 0.398 ms 0.461 ms
2 209.194.249.145 (209.194.249.145) 8.532 ms 8.472 ms 8.411 ms
3 207.114.135.73 (207.114.135.73) 32.772 ms 32.706 ms 32.647 ms
4 209.136.143.5 (209.136.143.5) 32.582 ms 32.532 ms 32.471 ms
5 173.227.35.254 (173.227.35.254) 32.413 ms 32.282 ms 32.208 ms
6 206.169.93.73 (206.169.93.73) 32.143 ms 24.749 ms 24.667 ms
7 216.64.187.197 (216.64.187.197) 24.603 ms 16.536 ms 16.330 ms
8 64.129.234.198 (64.129.234.198) 45.963 ms sjc1-pr1-xe-1-3-0-0.us.twtelecom.net (66.192.249.26) 45.839 ms sjc1-pr1-xe-0-3-0-0.us.twtelecom.net (66.192.249.22) 45.705 ms
9 equinix01-sfo5.amazon.com (206.223.116.177) 45.596 ms 45.475 ms 45.350 ms
10 205.251.229.171 (205.251.229.171) 64.314 ms 205.251.229.175 (205.251.229.175) 57.480 ms 205.251.229.177 (205.251.229.177) 64.068 ms
11 54.240.242.39 (54.240.242.39) 57.219 ms 54.239.41.228 (54.239.41.228) 57.101 ms 205.251.229.189 (205.251.229.189) 60.128 ms
12 205.251.232.141 (205.251.232.141) 64.165 ms 205.251.232.153 (205.251.232.153) 64.066 ms 205.251.232.108 (205.251.232.108) 71.479 ms
13 54.239.48.181 (54.239.48.181) 71.356 ms 205.251.232.165 (205.251.232.165) 71.266 ms 205.251.232.63 (205.251.232.63) 71.175 ms
14 * * *

traceroute to 52.10.151.144 (52.10.151.144), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 0.393 ms 0.352 ms 0.368 ms
2 209.194.249.145 (209.194.249.145) 18.554 ms 18.617 ms 18.557 ms
3 207.114.135.73 (207.114.135.73) 26.711 ms 26.649 ms 26.592 ms
4 209.136.143.5 (209.136.143.5) 26.529 ms 26.468 ms 26.420 ms
5 173.227.35.254 (173.227.35.254) 26.365 ms 26.308 ms 26.248 ms
6 206.169.93.73 (206.169.93.73) 28.068 ms 10.928 ms 10.743 ms
7 216.64.187.197 (216.64.187.197) 10.616 ms 22.485 ms 22.332 ms
8 64.129.234.198 (64.129.234.198) 46.543 ms 46.454 ms sjc1-pr1-xe-0-3-0-0.us.twtelecom.net (66.192.249.22) 46.369 ms
9 equinix01-sfo5.amazon.com (206.223.116.177) 46.290 ms 46.207 ms 46.125 ms
10 54.240.242.12 (54.240.242.12) 76.126 ms 205.251.229.175 (205.251.229.175) 64.822 ms 205.251.229.171 (205.251.229.171) 64.646 ms
11 54.240.242.21 (54.240.242.21) 64.560 ms 205.251.232.108 (205.251.232.108) 64.570 ms 54.239.42.6 (54.239.42.6) 63.773 ms
12 54.239.41.228 (54.239.41.228) 63.637 ms 205.251.232.161 (205.251.232.161) 63.551 ms 205.251.232.155 (205.251.232.155) 70.541 ms
13 205.251.232.155 (205.251.232.155) 70.378 ms 54.239.48.179 (54.239.48.179) 70.284 ms 205.251.232.167 (205.251.232.167) 70.199 ms
14 * * *

{“settings”:{“devt”:1451985655,”nbrd”:1,”en”:1,”rd”:1,”rs”:0,”rdst”:1452259421,”loc”:”undefined”,”wtkey”:”59b89138184f425d”,”sunrise”:360,”sunset”:1080,”eip”:0,”lwc”:1451985159,”lswc”:0,”lrun”:[0,0,0,0],”curr”:0,”sbits”:[0,0],”ps”:[[0,0,0],[0,0,0],[0,0,0],[0,0,0],[0,0,0],[0,0,0],[0,0,0],[0,0,0]],”wto”:{“h”:90,”t”:90,”r”:90}},”programs”:{“nprogs”:1,”nboards”:1,”mnp”:28,”mnst”:4,”pnsize”:20,”pd”:[[11,127,0,[16564,0,0,0],[600,1500,0,0,1500,0,0,0],”Main”]]},”options”:{“fwv”:216,”tz”:20,”ntp”:1,”dhcp”:1,”ip1″:192,”ip2″:168,”ip3″:1,”ip4″:204,”gw1″:192,”gw2″:168,”gw3″:1,”gw4″:1,”hp0″:80,”hp1″:0,”hwv”:23,”ext”:0,”sdt”:0,”mas”:0,”mton”:0,”mtof”:0,”urs”:0,”rso”:0,”wl”:100,”den”:1,”ipas”:0,”con”:150,”lit”:100,”dim”:15,”bst”:320,”uwt”:1,”ntp1″:50,”ntp2″:97,”ntp3″:210,”ntp4″:169,”lg”:1,”mas2″:0,”mton2″:0,”mtof2″:0,”fwm”:1,”fpr0″:100,”fpr1″:0,”re”:0,”reset”:0,”dexp”:0,”mexp”:6,”hwt”:220},”status”:[0,0,0,0,0,0,0,0],”stations”:{“masop”:[255],”ignore_rain”:[0],”masop2″:[0],”stn_dis”:[236],”stn_seq”:[255],”stn_spe”:[0],”snames”:[“Lawn”,”Shrubs”,”S03″,”S04″,”Trees”,”S06″,”S07″,”S08″],”maxlen”:24}}

Attachments:

1. 

   Screen-Shot-2016-01-05-at-9.24.34-AM.png
   

[natebarnz]

Thanks for the response DaveC. I tried to use WireShark but couldn’t seem to find the api call. I’m capturing on the LAN for the OS internal ip address and see lots of UI related calls but nothing else. I’m sure i’m doing something wrong with it.

Although my firewall is the most basic I did disable it to see if it would work and it did not. I also tried making API calls from a PC on my local network and was able to see the response just fine. My firewall allows all responses from connections created from the internal network and I have no issues with any other internal calls that I’m aware of.

I’m not sure of the exact call that OS uses to query wunderground however I did try a few random ones with my api key and they were all successful. Does anyone know if the API call requires a callback? If so then even a basic firewall would certainly block the call back. I don’t see why a callback would be necessary since it appears you can get all the data you need from simple HTTP api requests that return formatted data in the response.

I’m really at a loss here. I’m starting to wish I installed the pi extension so I would have more access to see whats going on.

Any other suggestions would be great. Maybe an example of the internal API call would be useful here too, I can’t seem to find it anywhere.

Thanks
-nate-

[natebarnz]

Hi Ray,

Thank you for the reply. I have tried that but still am not making any progress with my issue. My current settings are below. My last weather call seems to updated as it should and the data it returns is accurate every time I check. I do however still not get a last successful weather call as you can see in the attached image. Any other ideas?

{“settings”:{“devt”:1451313356,”nbrd”:1,”en”:1,”rd”:0,”rs”:0,”rdst”:0,”loc”:”pws:KAZTUCSO435″,”wtkey”:”59b89138184f425d”,”sunrise”:360,”sunset”:1080,”eip”:0,”lwc”:1451311209,”lswc”:0,”lrun”:[4,1,1500,1451296801],”curr”:0,”sbits”:[0,0],”ps”:[[0,0,0],[0,0,0],[0,0,0],[0,0,0],[0,0,0],[0,0,0],[0,0,0],[0,0,0]],”wto”:{“h”:90,”t”:90,”r”:90}},”programs”:{“nprogs”:1,”nboards”:1,”mnp”:28,”mnst”:4,”pnsize”:20,”pd”:[[11,127,0,[16564,0,0,0],[600,1500,0,0,1500,0,0,0],”Main”]]},”options”:{“fwv”:216,”tz”:20,”ntp”:1,”dhcp”:1,”ip1″:192,”ip2″:168,”ip3″:1,”ip4″:204,”gw1″:192,”gw2″:168,”gw3″:1,”gw4″:1,”hp0″:80,”hp1″:0,”hwv”:23,”ext”:0,”sdt”:0,”mas”:0,”mton”:0,”mtof”:0,”urs”:0,”rso”:0,”wl”:100,”den”:1,”ipas”:0,”con”:150,”lit”:100,”dim”:15,”bst”:320,”uwt”:1,”ntp1″:50,”ntp2″:97,”ntp3″:210,”ntp4″:169,”lg”:1,”mas2″:0,”mton2″:0,”mtof2″:0,”fwm”:1,”fpr0″:100,”fpr1″:0,”re”:0,”reset”:0,”dexp”:0,”mexp”:6,”hwt”:220},”status”:[0,0,0,0,0,0,0,0],”stations”:{“masop”:[255],”ignore_rain”:[0],”masop2″:[0],”stn_dis”:[236],”stn_seq”:[255],”stn_spe”:[0],”snames”:[“Lawn”,”Shrubs”,”S03″,”S04″,”Trees”,”S06″,”S07″,”S08″],”maxlen”:24}}

Thanks
-nate-

Attachments:

1. 

   Screen-Shot-2015-12-28-at-2.39.25-PM.png
   

[natebarnz]

dun4cheap,

I appreciate your assistance. I hope I don’t have a faulty unit. I’m a software developer and IT professional so I like to think I am a bit more capable than your average joe when it comes to setting up a mostly “plug and play” device. I’ve tried just about everything I could think of. I have even tried doing it all from the API but still to no avail.

If I begin with a freshly reset unit and simply add my wunderground api key and weather station pws key through the http UI, iphone app, or chrome extension, I would hope that it would work. I think I’ve ruled out any local network issues since it is requesting and displaying accurate live information from the wunderground API, and it can also connect and sync with the opensprinkler.com shared storage. Maybe I have faulty hardware or software. I guess the last thing I could try would be to reinstall the firmware, although mine came factory with the latest version since I just bought it a couple of months ago.

Hopefully Ray can chime in here and get this resolved for me.

[natebarnz]

Hi dun4cheap,

Thanks for your reply. I had previously read your posts as I was researching the issue. I feel as if I have tried so many different things, resetting to factory defaults and trying to simply just get the weather data to pull. Unfortunately nothing has worked. I’ve tried setting my location with the map by locating my weather station and also by just selecting a random nearby non pws point, still nothing. It gets my location name correct but the timezone is wrong and the weather data never get as last successful call date. I did find a way to get my timezone correct, I had to wipe my location so it was empty and then the UI let me manually adjust my timezone. So I set my timezone correctly and then saved my changes. Now it keeps my time zone correct but I still can’t seem to get the weather data to pull successfully.

So to try what I believe you are suggesting I have remove my location altogether. I verify that it is empty in the JSON config and then set my location again. I then verify that my location is set to the desired weather station, “loc”:”pws:KAZTUCSO435″. However it still does not work. I have also tried rebooting between these changes as sometimes the location in the UI does not show that it changed. I then try to set my location to a non pws, just lat/long coords “loc”:”32.26273,-110.73243″. I get the same results, I can see weather data for my location on the main UI page and when I run the weather diagnostics I get accurate information for my location, however still not last successful call.

Although I don’t know if any technical logging occurs for wunderground api calls, I do believe it is working. My key is correct and when its entered I see all the weather stations on the map, which doesn’t happen if I don’t have a key installed. I also see accurate data in the diagnostics and the main screen, all implying to my assuming eyes that the api is working and returning data. Why the system does not record a last successful call is still beyond me.

Let me know if you think I didn’t try what you suggested correctly.

Thanks
-nate-

[natebarnz]

Thanks Ray. Do you think it would be possible to use 24 AWG wire at approximately 250ft? I ask because I have some existing cat5 already in place that I could re-route with relative ease to a remote valve.

[natebarnz]

Thanks for the reply Ray. That is great however I was hoping for a more economical solution where I can buy just a single OpenSprinkler controller and have it communicate with some sort of relay or remote receiver that will trigger a valve. Any recommendations for that?

Thanks
-nate-

[Author]

Posts