Forum Replies Created
-
Posts
-
The native app is a replacement to the web app. As you mentioned, it lacks automatic rain delay and this feature will not make it to the native app (unable to run 24/7 and not ideal device for changes).
The new UI hasn’t been tested against the web app as it’s no longer in active development. It most likely has issues since every iteration of OSPi causes issues. This is why I moved to the mobile_app plugin to get away from these issues. The web app does not use this plugin (hence the failure).
Both can probably be run at the same time however they will fall out of sync. In other words, the apps assume one user at a time and don’t make frequent polls to the device to changes not done within the open app.
Hope that helps.
I just noticed this issue as well and I believe it is due to my plugin for OSPi. If I put an earlier start date, all the logs show up. I will look into it and let you know.
Thanks!
This option exists and is exposed as a global option called watering level. The default is 100% and it works as you described with a range of 0-200%.
Other than the program preview, are you having other issues?
I think moving forward it’d be better to fix the bugs in 2.0 than reverting back. Furthermore, 2.0 offers some new features including logging support for the mobile app. I will take a look at the program preview and see what I can fix however just to clarify, is it just the preview thats wrong or are the programs running incorrectly in 2.0?
Thanks
The last thing described here is exactly how the firmware functions. They can all have the same start time and so long sequential mode is used under settings the firmware will stagger them. This can be visualized in the program preview.
Also, I’ll see about losing the start page in the navigation history. (sorry missed that the first time through)
Welcome back. The 1.9.0 is actually a separate branch of the OSPi software. The branch is named “JM_UI”.
If you need further assistance let me know.
Based on this thread it seems possible to use Cat5: https://groups.google.com/forum/m/#!topic/alt.home.repair/X4UV5YNlF-E
But not recommended I don’t think (since max or worst case current can exceed the cable max)
You don’t need to physically cycle the power either. The timer has a reboot option in software also available in the mobile app.
You have to change the port on the site using the “Manage Sites” button. You can find this from the side panel on the home page or in the settings page. After you change the port, you append the port to the IP using IP:Port. The addition is the colon and the port number (no spaces).
Let me know if that helps.
To be quite honest, I am quite confused why there is a sudden influx of web app users. The native app has been released and offers a better experience (backgrounding, install method, etc) over the web app.
I assume it is due to the SD card. Maybe I will ask Ray to just remove the web app from the SD card.
The only missing feature is logging which has already been built for the OSPi and will soon support Arduino based OpenSprinkler, as well.
Ah okay. I misunderstood your previous comment. This is likely a bug and will be checked out soon. Thanks!
It actually does and based on what @wyone is saying it showed up. Is it not working for you? Also, does it show correctly in the firmware?
Thanks
They are both running android 4.2.2? Any way you can upgrade to KitKat and try again?
I ask because there is no widget whatsoever in 4.2.2. My app is written using web formats and the bundled browser in 4.2.2 for some reason doesn’t have nice inputs. I could hack in a solution for Android 4.2.2 but I would assume a Nexus device has an available upgrade (which are always good).
It’s there, top left of the graph. You don’t see it?
On narrow devices it’s the three letter abbreviation. On wider devices, it’s the full name.
Glad we got things sorted. As we discussed, the problem turned out to be the password used in the mobile application from the App Store. The password needs to be the device password which defaults to opendoor.
I am posting this for other’s who might have similar issues, in case you are wondering.
Thanks!
You said OSPi however mentioned firmware 2.0.4. Just to be clear, are you using a Raspberry Pi connected to an OSPi board? Or are you using an Arduino based OpenSprinkler?
If you are using Raspberry Pi, which OS are you running?
Thank you! I actually badly want to pull logging data in since I already have the UI built.
The hold up is on the Arduino side. I want to try and make the method is similar for both Pi and Arduino user’s so it works well across the board.
Awesome work on the plugin!
Glad to hear things are working! If you have any suggestions regarding the mobile app please free to discuss them. Also, as you mentioned, patches or pull requests would be great as well.
Thanks!
For example, my app requests an IP to work (or finds it if it can).
If you goto your desktop browser and navigate to http://IP:8080 does it work?
