Mobile and Webapp issue

[girvin13]

I am running a Samsung S24 with the latest software version OneUI version 7.0, Android Version 15. I have the mobile app as well as the Google Play app on my phone. With the mobile app, I am using Firefox version 140.0.3 installed from the Play Store. I have 3 OS’s that I have added through the OTC keys. I can see all 3 areas with no problem from either the app or the mobile app. The issue is when I run a manual station for any given amount of time and when the station finishes. I try to run another station manually and the station does not run. I get the same results from either app. I have attached a link to IMGUR of a screen recording from my phone today of the Google Play app. I would have attached the video here but it is over 8mb.

If I connect through the local network with Firefox, they work correctly and I can run multiple manual runs consecutively.
All of the controllers are DHCP and they are MAC reserved.

https://imgur.com/tjwN6eB

[Ray]

We need to know your OpenSprinkler app version and also the firmware version running on your controller. Instructions on how to find these versions can be found here:
https://openthings.freshdesk.com/support/solutions/articles/5000859137-troubleshooting-and-technical-help

What’s the difference between ‘mobile app’ and ‘google play app’? Isn’t Google Play app the mobile app on Android phones? I am not aware how to install the mobile app in firefox.

[girvin13]

Sorry Ray,

The Google app version is 2.4.75

Creek Area
App version 2.4.75
OS firmware 2.2.1 (1)
Hardware version 3.3 – AC

Prop House
App version 2.4.75
OS firmware 2.2.0 (3)
Hardware version 3.2 – AC

Retail Area
App version 2.4.75
OS firmware 2.2.1 (1)
Hardware version 3.2 – AC

I meant the webapp where you enter app.opensprinkler.com in a browser. Sorry

[Ray]

Is the issue you are reporting happening on all three controllers?

[girvin13]

Yes.

[Ncp294]

Hello!! I am currently looking into this issue but I am struggling to reproduce the error you’ve encountered. Would you be able to turn on the developer console in Firefox (ctrl + shift + i), try the back to back manual run again, and send a picture/video/text of what is in the console? This may show info that would help determine why this is happening.

Thanks,
Nate

[girvin13]

Nate,

I am not having any issues when I am connecting to the controllers via Firefox on the PC through the IP address. The issue is with the Google Play app on my smartphone and the app.opensprinkler.com through Firefox. I also tested the app.opensprinkler.com with Edge and I get the same results. If I hit the refresh button, the station will manually run. If I try the same run a second time, it does not run.

I enabled the console but what function do I use after I enable it to capture the info you need?

[Ncp294]

Yes, I was testing with the app.opensprinkler as well no worries there. If you are able to just do what you did in the video above (running a station, then another afterward) and see if anything shows that would be amazing.

Thanks again,
Nate

[girvin13]

Nate,

When the console is open, nothing happens that I can tell. Not sure what is supposed to happen.

[Ncp294]

I see, I see. I have two more options you can try.

1. Open the web app in a private browsing window and try again to see if possible cached files are causing the issue.

2. With the console open, go to the network tab to show the traffic between the network and controller. If there is no requests being sent when you try the second run that will help source the root of the problem as well.

Thanks for your patience,
Nate

[Ray]

@girvin13, could you submit a support ticket at:
support.opensprinkler.com
That way you don’t post sensitive information such as your OTC token and your device password to this public forum. I deleted what you pasted because it contains sensitive information that should be on a public forum.

We found at least one thing that’s correlated with the symptom you are observing, that is, your controller’s connect to the OTC server is being rejected every 10 seconds or so. That probably explains why the second time you try to turn on water it doesn’t work. It also explains why it doesn’t affect local connection since the issue happens with the OTC connection. Exactly why this is happening, we don’t know yet, but let’s continue the conversation on the support site and we can send you further diagnostic instructions.

[Author]

Posts