- This topic is empty.
-
Posts
-
Recent user, currently 29 stations running, 11 more comin on line in several weeks. Android phone APP, Opensprinkler, V2.04
I have never had any connectivity issues since Ive done two things: Correctly got port forwarding set up in the router and connected OS directly to the LAN, no WIFI. For several weeks ive been bringing up the sprinkler system, experimenting, verifying proper behavior, etc. NO ISSUES! T passed weekend we hydro-seeded about 1.5 acreas of lawn. Until today, no issues.
I just tried going into manual mode and each command is initial taken every time I enter the APP. But immediately tells me I need to check the password and the mobil app reverts back the indication that it did what you said. Example, enter manual mode then touch a station, Station turns Green, actually comes on, master valve comes on, water is flowing…but the message comes back and tells me I need to verify my password. If I then tap the station, it gives the message again and does not turn off the station. I have to back out of the app, open again, let it connect and then I can turn it off….but the cycle repeats. I have to do it everytime. Operating from my PC flawless.
I have rebooted open sprinkler, changed my passward via the PC and then on opensprinkler, NO change in behavior.
It is really odd, it lets me do anything once, then seems to be stuck on in authentication. I suspect the errpr is falling through into a bucket (probably zero throuigh masking) and driving a general error.
but the fact that it lets me do one thing and no others suggests it may initially error some some orthogonal issue but then assumes it is authentication and denies subsequent attempts.HELP!
Thank you for the detail, I will be fixing this in the upcoming version and realize it is a problem for multiple users. Another user just posted a similiar problem.
The reason it won’t let you turn it off is it “sees” it as already off (since the AJAX request “failed”) which I still need to look into. I get it didn’t fail but the OS might have sent a redirect instead of a 200 and that got interpreted as an error. Again, I will look into it and get it fixed soon.
Thank you sie for the quick reply.
What I dont understand is how…all of a sudden it started. NO issues before…..Is this only an app issue,….how do I know my programs are running…as noted below a day without water in Houston in August and I can lose $3000 in seed.
This is an app only issue and unrelated to the hardware itself. The feedback is a misinterpretation of the error codes something that varies with browser implementation. I have put a tighter restriction on displaying vague password error’s and now working on analyzing the output of manual mode changes in regard to the mobile app.
Thanks
I believe I have fixed the issue however before I do any releasing I would like to ask if you’re interested in beta testing it for me. I have an APK I can send you and to install you just need to enabled 3rd party developers in the settings.
Thanks!
Update: Here is the link for the betas https://build.phonegap.com/apps/793070. By the way, iOS and Windows won’t work since they require exceptions in signatures.
I would be happy to beta test but I only have windows, osx, and iOS.
Sent from my iPhone using Tapatalk
For iOS you can private message me your UUID and I will add you to my list of approved devices. Then, you can use the Phonegap link to test/update as necessary.
Thanks!
Good morning,
Just installed and it is worse than before. The actions now are not taking place. It simply gives me a password error for anything and the command is not executed
The only way for the password message error to show up is if the device returns a 401 (unauthorized). Unfortunately, the firmware also returns a 401 when manual mode is disabled and a station is toggled.
It sounds like the controller isn’t in manual mode but the app thinks it is. During this state, you will get password errors. Is that what’s happening? I guess I need more information as to the state of the device because this is not a normal behavior and I’m not able to recreate it.
Thanks
Update:
I uninstalled the Beta, went to play store and installed that V. I believe I noted there had been an update on Aug 3rd which corrolates with my issue timing (If memory serves). Did not explicitly enable the update to the best of my knowledge. Is the default to push updates for the Androi? Regardless, I have the same behavior as before; the majority of the time there’s no state change in OS and I always get a password check error. Went to the PC changed my OS passwd and as well noted I could manually run the system as designed. No change in the APP behavior. Rebooted OS (on/off hardboot, the app would not initiate), No change in App behavior.
NOTE: The APP shows manual to be off and wont turn on (password error). Via PC, OS is indeed NOT in manual mode. I turned on a station via PC, re-entered the APP and it showed manual mode on but again would not change or even turn off all stations via the app.
If I can provide additional info, be remote hands, or give you my PWD and let you root around, just let me know. It’s putting a major crimp in my style this weekend. We’re planting beds today and adjusting sprinklers, about 100 of them :), could really use the mobile app…my wifi dies about 10 feet off the porch 😉
Very much appreciate your attention!
-Q
Can you please try the new beta? I made the changes below but I also added a debugger which lets me have some information about the app’s status. For this to work though we both have to be on at the same time therefore let me know when would be a good time. All you have to do is install the newest beta (same link).
I added a yellow status indicator when toggling stations. During this phase, it has sent the request but awaiting confirmation. Also, it uses the status from the device instead of the background color to determine what a station is currently doing (clearing up some confusion). If this isn’t working then something different is causing issues, possibly a caching issue. I hope to resolve it by using the above strategy.
By the way, please note the app expects all control to be done through one device at a time. If you are changing things on the PC, the app continues assuming the previous state. With that said, information is updated periodically and during page changes (applicable info only).
Update: By the way, I did a diff on 1.1.5…1.1.6 and nothing was changed in the manual mode behaviour or error checking. So not sure if that’s when the problem was introduced.
Morning. The play store rev 1.1.6 is the same rev you provided in the link. It seems both are the Aug 3rd update?
Ignore the version number when using the PhoneGap link. You can clearly see it is not the same build by going to the manual mode page and toggling a station. I have updated the visual and backend methods so it should stand out as different.
Based on what I am seeing in the debug session (assuming it is in fact you) appears to be an incorrect password. Manual mode, once enabled, does not require a password to toggle on/off which is why that works fine. However, turning on/off manual mode itself requires a password and when you tried to toggle it off it failed (401). This is directly from the OpenSprinkler. So please check the password in the app under Manage Sites. Hopefully, this will fix the issue.
- You must be logged in to reply to this topic.