November 8, 2016 at 11:30 am #44521
To start, I really can not thank you guys enough for all of your work on this project. It is a great system you have created. And then coupled with the support you give to noobs like myself… Well I can not speak highly enough about all of you.
Now, I am not positive this is the correct place to post my issue, but i think it is.
My current system is:
JBtek 8 relay board
I just added a JBtek 4 relay board to give me enough stations for both my front and back yards.
System Versions were (before firmware upgrade on 11/7/2016):
App Version: 1.6.0
Hardware Version: OSPI-AC
I followed section “B” on the above upgrade page, and now the system appears to not be working.
During the upgrade, I received no errors. When I check the status of the opensprinkler ‘service’, the Pi reports back that the service is running with no errors.
Yet when I try to access the App (the UI) from a web browser on my primary computer running Linux Mint, or from the Android app, I get an error saying unable to connect. The Pi is still connected to the network as I can ping the Pi and from the Pi I can ping my other computers.
I also hooked up a monitor and started a web browser (Mozilla) on the Pi itself, and tried to access the App and through accessing the “local host” and it still came back as unable to connect.
I had it programmed to run every Tuesday morning, but it did not run. I would assume that this is a result of the upgrade resetting everything back to default, but as I am unable to access the thing, I am unable to import my config file that i saved before the upgrade.
I really do not want to start over from a fresh new install, but if you guys think that is the best route to take, I will do it.
I see that there appears to be an issue with the windows phone app, but since I am not running any Microsoft device to access my OSPI system, I wanted to start a new thread. I hope you do not mind.November 8, 2016 at 11:38 am #44523
Which port are you using to connect to your OSPi? OSPi defaults to port 8080.November 8, 2016 at 11:51 am #44524
I did not specify any port number from a web browser, and from my understanding, it should then default to 8080. As for the Android app, there is not an option for port number. I know when entering the IP address, one can add on the port number, but i did not try that.
Also, I tried to connect to the OSPI using both the IP address and the Pi name (which is OSPI).November 8, 2016 at 11:52 am #44525
Yes please append “:8080” to the IP you enter in the app. Such that you use:
Thank youNovember 8, 2016 at 11:58 am #44528
I will try that tonight when i get home.
If that does not work, by chance do you have any other idea’s on what I should try?November 8, 2016 at 12:08 pm #44529
That’s the issue. If it doesn’t work we can go from there.November 8, 2016 at 12:24 pm #44530
Thank you Samer. I will let you know tonight.November 8, 2016 at 7:30 pm #44542
Thank you for your help. Your solution worked like a charm.
Please forgive me, since I am a complete noob and know next to nothing about all this, may i ask a few questions?
Was the port number changed in this new build from the previous build?
Also, I thought port 8080 was the default port for web servers or am I mistaken?
Lastly, i really do appreciate your help and the time you have taken to help myself and all other users of your software.
DarinNovember 8, 2016 at 7:38 pm #44543
No problem! The default web port is 80 however since the Pi usually runs a web server OpenSprinkler uses 8080 so it doesn’t conflict. This wasn’t a recent change but the port is configurable so it’s possible you had a different port set.November 8, 2016 at 7:41 pm #44545
Thanks for the fast response. I am now trying to figure out how i changed the port number previously because i do not remember doing so. lol
Again, thank you for your help. Have a great week.
- You must be logged in to reply to this topic.