LOR Mobile app: "Waiting for response from computer"

[Tim Fischer]

I don't think I had this issue last year, but I didn't use the mobile app much. I've seen it several times this year.

Sometimes when I launch the mobile app, I get the message "Waiting for response from computer". This response evidently never comes, because it never moves past this screen. If I go back to the show computer and shut down the control panel and re-open it, the mobile app will work again, for a time anyway.

Thoughts?

[PhilMassey]

I've seen that exact behavior too. Possibly when I was pushing the edge of the WIFI range.

[Tim Fischer]

Definitely not a Wifi thing. Show computer is hardwired, and the phone can be anywhere (plus I think that app should work even on cell data)

 

[k6ccc]

37 minutes ago, Tim Fischer said:

I think that app should work even on cell data

It does.

 

[PhilMassey]

Yeah, but the phone is on WIFI when it can get it. Perhaps at the switchover to cellular.

[Jeremiah Ackermann]

I’ve had to switch off WiFi and just use cellular data when on the fringe of the WiFi range. Same with music streaming apps that I try to use when doing yard work.

[Tim Fischer]

I guess the part I'm not understanding is why it takes me shutting down the control panel to reset it. I can go back inside, kill the mobile app, relaunch it, and it will still say "waiting for connection".

 

[k6ccc]

Rather than killing the CP and restarting, just go into the Mobile App section of the CP, and uncheck the selection for "Allow the mobile app to test lights and control your show?".  Then re-enable that checkbox.  That usually works for me.

 

[Tim Fischer]

11 hours ago, k6ccc said:

Rather than killing the CP and restarting, just go into the Mobile App section of the CP, and uncheck the selection for "Allow the mobile app to test lights and control your show?".  Then re-enable that checkbox.  That usually works for me.

 

That has worked... sometimes. It didn't work one time, where the reboot of the CP did, so i switched over to bouncing the CP. I can try it again next time I see this happen...

 

-Tim