Forum Replies Created
-
Posts
-
The webapp is currently pivoting to jQuery Mobile 1.4. This will result in significant changes to theming but will bring lots of new features and speed enhancements. The groundwork has been merged however the upgrade process is still ongoing. If you have any suggestions please let me know.
Current issues:
– About page loads a black bg then flickers to white (issue with panel)
– Current Status title is too long on iPhone, consider renaming title to Status for mobile devices
– Graphical log viewer lost the left/right arrows for legend scrolling
– Remove custom icons and switch to jQM SVG/PNG icons (higher quality)
– I would like to somehow improve the main page header logo. It looks good now but the borders of the text aren’t smooth.
Thanks to charvel, the web app now has language localization support. Charvel used PHP gettext which should be familiar with those able to assist with translations. The framework is completely integrated and supported thanks to his work. Charvel also added translations for most common languages however only login information is translated at this point.
Another interesting thing, date strings are exported to be localized. If editing the PO files (using Poedit, etc), be sure to reference the PHP date string format before editing this however this will allow dates to be shown in the local format.
https://github.com/salbahra/OpenSprinkler-Controller/commit/3b03742f6b0446d9f96642b24c3d90895bd5f191
By the way, earlier I said Arduino but that didn’t really make any sense. My app isn’t hosted on the microcontroller version. Anyhow, I have merged your changes except for the index.php. I have instead added my own changes which allow people to switch between CDN and local at any time. It also lets you choose during the install. The option is contained in the settings menu. Anyone upgrading to the latest commit’s will default to CDN hosted. Simply switching the settings slider and reloading the app will switch you to local resources.
Please let me know how this works.
@opensprinkleruser thank you. The app isn’t downloadable off the App Store because it is a webapp.
Also. It should work over a WAN without a problem.
The Google fonts are used for the flat theme, I believe. Also, the speed gain from using a CDN on a mobile device over a mobile network is tremendous. The Arduino web server is absolutely bare bones with no caching logic. Google’s servers manage this load a lot better. Also, multiple mobile apps might share the same CDN link as a result no download is ever done for the largest files of this mobile app. The app will almost always be accessed with the internet active. Even if you don’t have internet, so long you visit the mobile app once with internet, it will work.
If I am saying something that is incorrect please let me know. Also, show me some speed tests/benchmarks please. Everything I have read/seen suggests large libraries like these should always be on CDN.
169.xxx.xxx.xxx is not routable and is a fake IP basically saying DHCP failed.
The 192.168.0.4 seems to be the IP your after. Is that not working?
I have been keeping up with this forum and want to let people know I haven’t abandoned this project. However, my time is severely constrained with work and research that not much time is left for other projects.
If anyone has the skill to continue development please feel free to fork the code, make changes and send back a pull request. I am more than willing to work with anyone trying to contribute to this project.
Thank you for your understanding and I hope to incorporate some of the suggestions by a future date.
Thank you!
@mikethechap My program does not currently disable the sprinkler based on temperature. That is a great idea and easy to implement. Is there a good value to cut off on? 32F?
My guess is permissions. The index page checks for a config.php if it can’t read one then it redirects to install page.
Check permissions first and we can troubleshoot from there.
The problem lies in all the common firmwares (OS, OSPi interval program and OSBo interval program) not reporting which device/specific version they are. Therefore, I can’t tell between OS vs OSPi and I also can’t tell between OSPi old vs new (before and after large station name support).
I can extend support universally however that will cause problems for some people on the more restricted firmwares. Each time I try to identify between the two I fail especially because the OSPi program is constantly changing so it’s hard to find a unique difference that persists through versions.
Yes, android is supported. The issue your having might not be related to my mobile app. Try the native interface and make sure all your stations are showing up there correctly. If they are, let me know I will try and look into it. Please supply any errors in logs, if any.
Thanks.
If you goto http://rayshobby.net/apps/sprinklers/ it will ask you for the device IP and password. If you put the reply from google with port (eg. 72.63.92.162:8080) and put the password (eg. opendoor) you should be presented with the mobile interface and be good to go.
@paul Glad things are working again for you. The corruption makes sense since the OSPi upgrades have been quite extensive lately.
@revnull wrote:
Errors from the apache error_log:
[Fri Nov 01 15:24:45 2013] [error] [client 10.10.100.239] PHP Notice: Undefined offset: 1 in /srv/http/sprinklers/main.php on line 98, referer: https://10.10.100.3/sprinklers/
[Fri Nov 01 15:24:45 2013] [error] [client 10.10.100.239] PHP Notice: Undefined offset: 3 in /srv/http/sprinklers/main.php on line 102, referer: https://10.10.100.3/sprinklers/
[Fri Nov 01 15:24:45 2013] [error] [client 10.10.100.239] PHP Notice: Undefined offset: 1 in /srv/http/sprinklers/main.php on line 104, referer: https://10.10.100.3/sprinklers/
[Fri Nov 01 15:24:45 2013] [error] [client 10.10.100.239] PHP Notice: Undefined offset: 2 in /srv/http/sprinklers/main.php on line 104, referer: https://10.10.100.3/sprinklers/
[Fri Nov 01 15:24:45 2013] [error] [client 10.10.100.239] PHP Notice: Undefined offset: 4 in /srv/http/sprinklers/main.php on line 104, referer: https://10.10.100.3/sprinklers/
These errors are the Yahoo weather API not working. Probably a temporary thing or the reply has changed (but I don’t think it has).
@revnull wrote:
[Fri Nov 01 15:24:44 2013] [error] [client 10.10.100.239] PHP Notice: Undefined variable: data in /srv/http/sprinklers/sprinklers.php on line 115, referer: https://10.10.100.3/sprinklers/
[Fri Nov 01 15:24:45 2013] [error] [client 10.10.100.239] PHP Notice: Undefined variable: data in /srv/http/sprinklers/sprinklers.php on line 254, referer: https://10.10.100.3/sprinklers/
[Fri Nov 01 15:24:45 2013] [error] [client 10.10.100.239] PHP Notice: Undefined variable: data in /srv/http/sprinklers/sprinklers.php on line 261, referer: https://10.10.100.3/sprinklers/
[Fri Nov 01 15:24:45 2013] [error] [client 10.10.100.239] PHP Notice: Undefined variable: data in /srv/http/sprinklers/sprinklers.php on line 388, referer: https://10.10.100.3/sprinklers/
These errors are more significant and possibly related to variable scope. I will be pushing a fix very soon.
Let me research which files the 1.2/1.8.3 files the firmware is using and make sure the syntax matches what I am testing against. It is really weird that the hosted copy works fine since the logic should be the same.
Just to facilitate the troubleshooting, could you give me sample “source code” of the native interface output. For example, navigate to your OS at http://192.168.1.138/, /vs, /vo, /vp, and /gp?d=0. The output should be brief (not the current DOM state) of each page (just variables and sourcing some javascript).
Basically, my script has to parse the output from the OS and if it’s slightly different it might be causing an issue. I really don’t know which source code to look at for the code you’re 1.2U is using so the output above would be great (feel free to message me if you don’t want to attach it all here).
I will say the regex used has recently changed so something might have broken during that change. Should be an easy fix.
Thanks!
IIS was just a suggestion since you are on Windows. I personally have never used it and not sure what it would take to get PHP working, I am sure you can google this. There are other users who have my app working under IIS, so it is possible.
The web root is defined in the IIS settings for HTTP server. You simply want to put the files in the folder defined in the settings. The files can be downloaded from Github using the zip link (https://github.com/salbahra/OpenSprinkler-Controller/archive/master.zip).
Also, if you are familiar with Apache you use that instead by downloading WinLAMP mini (http://prdownloads.sourceforge.net/winlamp/WinLAMP.4.0.0-mini.exe). This will install PHP and Apache on Windows. Again, either way works just giving you options.
Good luck.
A minor update to OSPi has been posted by Dan which brings compatibility back between OSPi and my mobile app.
Looking towards the future of the mobile app and OS/OSPi, it seems possible to move the mobile app to a mobile theme. I am waiting on Jonathan and Dan’s work to conclude on OSPi to see how the theming system turns out. For OS users, firmware 2.0.1 now hosts the files on an SD card which allows easy modification. This will allow the mobile theme to simply be dropped onto the SD card (and maybe even distributed with the firmware). These are all plans for now but with time should come to realization.
You can use the same Raspberry Pi that is controlling your sprinklers for the mobile app. Just SSH into the Pi, install a web server (ex. Apache), and clone the files into web directory.
Those are the two steps you need to perform and are detailed in the Github install instructions (https://github.com/salbahra/OpenSprinkler-Controller).
Let me know if this helps.
Update: I noticed you specifically said OS 2.0. Do you mean you have an OSPi setup working and now you are trying to get an OpenSprinkler 2.0 (not the Raspberry Pi model) with logging using my app? If so, just install a web server on your Windows machine (IIS, Apache, etc.), install PHP, and clone my files to the web root.
Update: I just saw your screenshot, the problem is the “Hourly” setting at the bottom. This needs to be every minute in order to accurately detect station changes.
Update 2: Use locking is something I would recommend checking.
I just realized, upgrading OSPi for some reason changes the port number…The system disabled error may be because the port has changed from 8080 to 80. Please check this and ensure the port is correct in config.php for the mobile app. If you need to change the port you can edit sd.json in the data directory of OSPi (it is the only fix I found).
Update: An update to OSPi has come out (Github) which should fix all left over issues between the mobile app and OSPi.
@guylior I just issued another update to fix a few more issues however the slider is working fine on my end. I know this is very confusing and I apologize but do you know which version of everything you are running? My program puts all the required information on the bottom of the About page, accessed via the side panel. This is the firmware version and the mobile version number.
As for OSPi, the revision number and date is embedded in ospi.py. If you could give me all of those versions I can try to pinpoint your issue. In the meantime, I will continue improving the support between the two however it will require some code changes on OSPi end, so please be patient while Dan accepts these new changes.
Here are the versions I am currently using:
Mobile Version: 4a66440
Firmware: 1.8.3
Revision: 139
Revision Date: 10/16/13With these versions, everything works except saving option changes. This will be solved as soon as the pull request to OSPi are approved.
Thank you
Sorry for the unusually delayed response however I am aware of the issue as discussed in the separate thread.
The good news, I have pushed a partial fix and should have a full fix coming soon. Sorry for the delays and thank you for your patience!
Update: Full support is here now, I did push some code changes to OSPi that is required to complete the support. The fix is minor and hopefully Dan is able to approve it quickly. Again, sorry for the delay! When I get time, I will check support for OS 2.0.1 which was just released by Ray.
