[Samer]

Sorry about the bug. This was actually discovered in 1.4 and I thought I fixed the issue in 1.4.1 but clearly it’s still occurring.

The reason the app is manipulating the IP is because it sees a local IP and noticed port forwarding is setup correctly so it’s changing the IP from the local to the external one.

Thanks for the report and I’ll let you know as soon as I have a complete fix.

[Samer]

Hi, Regarding the first question: I use a general query to Weather Underground using the documented API calls therefore I am not sure why it doesn’t show up in the popup map. It may be a setting under the weather station on Weather Underground’s website.

For the second issue, the string comes from the city reported by the personal weather station. Reporting “ILAZIOROM38” on the home page doesn’t contribute much other than a jumble of letters and numbers. If this is inaccurate then it’s likely configured wrong (the personal weather station). I have noticed the city can be somewhat incorrect for other weather stations as well and will reexamine for a better way to retrieve the city name.

Thanks!

[Samer]

Hi, The gear icon is correct and the top item is an input for the station name. I realize this isn’t very clear as many people have voiced their concern. I will be updating this in the next version.

[Samer]

This error means you didn’t mark SSL on the site manager page for the device.

[Samer]

Again, can you please provide details? What is the error? etc.

[Samer]

Internal error 500 means your Proxy is failing because OpenSprinkler will not return a 500 error code.

[Samer]

As I said in my previous message, paste your error here please.

Please do try to provide as much information otherwise this thread can grow to 100 pages without any resolution.

[Samer]

Right, those are the same symptoms as yesterday. Like we discussed, it is your SSL certificate that is using a weaker SHA-1 algorithm causing FireFox and Opera to reject the certificate. If you say your using SHA-256 now, then you should post any error messages you are getting from FireFox console here.

Also, you don’t need to use betaui as the issue is unrelated. Therefore, you can continue using: https://ui.opensprinkler.com/js.

Thanks

[Samer]

The white screen was caused by an incorrect URL. The correct beta UI URL is: https://betaui.opensprinkler.com/js.

Furthermore, this issue was resolved without the need for using the beta. The underlying issue was FireFox complaining of a weak self-signed certificate. The secondary issue was the Javascript URL used by OpenSprinkler was non-secure by default and caused an issue when the primary site being accessed is using SSL.

Thanks

[Samer]

I sent you an email so we can further troubleshoot the issue.

Thank you

[Samer]

Result 2 means your password is wrong. Use the same hash that worked earlier.

[Samer]

Can you try to use https://betaui.opensprinkler.com ?

[Samer]

Yes, it needs to be your password but MD5 hashed (sorry this page needs an update and is a bit behind). If you don’t you how to MD5 hash your password, you can use this tool: http://www.md5.net/md5-generator/

[Samer]

On the same network as the OpenSprinkler, navigate to it’s web page without using any SSL or proxies. Goto: http://opensprinkler/su.

This will open a basic white page with two input boxes. The top is the Javascript URL which defaults to http://ui.opensprinkler.com and the other is the password which should be MD5 hashed.

Basically, the browser does not want to load non-secure content, is my understanding of the error.

Update: I think I fixed another issue regarding the loader and SSL issues. If you still have issues use https://betaui.opensprinkler.com as the Javascript URL on the /su page.

[Samer]

Oh, okay on the /su page where you put the Javascript URL: be sure to put https. For example, the default Javascript URL is http://ui.opensprinkler.com change this to https://ui.opensprinkler.com.

Also, just so you know this issue is only when using the web site. This shouldn’t occur when using the Google Chrome extension in the store or the FireFox addon.

Try changing the URL which should fix your issue.

[Samer]

Firmware prior to 2.1.0 required an interval time greater than 0 to actually schedule the program. Also, the end time is for programs that repeat, this defines an absolute end time that the program cannot be scheduled to run after. If you don’t want the program to repeat, put a very high interval (23 hours).

Once the firmware is updated the program scheduling becomes a lot clearer.

Thanks for the understanding and hopefully Ray can help with the firmware update issue.

[Samer]

Hi, If you have a OpenSprinkler 2.1, then you need to be in bootloader mode for the device to be recognized.

Do you know which hardware version you have?

[Samer]

Michael,

This site is predominantly for OpenSprinkler and RFToy is not sold on this site. Rayshobby.net has a forum for both RFtoy and ESPtoy. You can find it here: http://rayshobby.net/phpBB3/

[Samer]

The controller keeps a daily average of the watering level which changes every 15 minutes. Therefore, I would examine the average watering level for that day and seeing if the average corresponds better to the actual run time. If it doesn’t, the program was likely started right before the watering level adjusted to a low level.

The average can be found on the logs page in the Table view.

[Samer]

Okay, so if your certificate is expired, we know this won’t work within the applications (specifically iOS) so we are only discussing web based access.

I looked up OpenWRT/lighthttpd and am fairly confident you can add the CORS header by doing the following:

1) Open the file /etc/lighttpd/lighttpd.conf on the device by using nano or vi.

2) Add the following code:

 setenv.add-response-header = (
      "Access-Control-Allow-Origin" => "*" 
    ) 

If this doesn’t work, feel free to send the screenshots in Hungarian. The general error should be apparent however it is likely CORS related issues.

Thanks!

[Samer]

I understand your setup and also the issue.

For the app, when using an SSL proxy, it has to have a valid SSL certificate. There isn’t anyway around this from my app’s perspective as these are limits by the OS. Furthermore, my framework (PhoneGap) doesn’t have a way to allow non-valid SSL certificates. Therefore, it needs to be valid. I personally pay for a few domains and use a router or linux server to update my DNS (if it changes). I also use the domain with StartSSL to get a valid SSL certificate.

Regarding the web interface, like I said earlier, the CORS header is missing. Which deamon are you using for your SSL proxy (Apache, nginx, etc)? Here is a sample Apache configuration to fix the issue:

<IfModule mod_headers.c>
        # Add support for cross origin requests
        Header set Access-Control-Allow-Origin "*"
</IfModule>

If you want to see the error message, right click the browser window and push “Inspect Element” anywhere. This will open a new window which has a “Console” tab. This tab will show you error messages in red and when you get kicked back to the home screen you will likely get an error here. If you can, send the error message my way so we can confirm the issue.

Lastly, addressing your point about the URL: If you check SSL it uses ‘https://’ where as the standard is ‘http://’. That’s the only difference.

Thanks

[Samer]

If you are using the mobile application, they are sensitive to the certificate being valid. This means a self signed certificate will not work. Personally, I use startssl.com for free valid SSL.

Regarding the direct IP it should work fine however your proxy has to add a allow cross origin header (or least forward it from the original request) in order to work from the direct IP.

If this doesn’t make sense let me know and I can try to better explain.

Thank you.

[Samer]

Sorry, unfortunately only stations 1-8 can be designated as master station in the current firmware.

[Samer]

Oh, I neglected to ask which firmware you are using.

The Pi just recently started supporting the Arduino firmware now known as unified firmware. This is the firmware I write the UI for which is also used on the mobile applications. This is the firmware that recently got an updated UI.

Both firmware’s have some sort of auto update at this point. The unified firmware can auto-update the UI/front-end while Dan’s Python firmware can do entire firmware updates from the UI or automatically (using plugins).

[Samer]

Any station that you want to activate the master valve needs to be flagged to do so.

To change the setting of each station, tap the gear icon next to the station name. If you are using the recently updated UI with the new home screen this can be done right on the home screen. Otherwise, you will find this in the “edit stations” page.

Hopefully this resolves the issue.

[Author]

Posts