jakblak

Hey @bdo21,
See my responses below.
 

Hey @bdo21,
See my responses below.
 

Hey @bdo21,
See my responses below.
 

Hey @bdo21,
See my responses below.
 

Hey @bdo21,
See my responses below.
 

We have quite a few performance metrics inside of the OS3 app and one of those is cold-start time while remote (i.e. not on your local network) and the connection times in some regions, as many of you have experienced, is sub-optimal and outside of the range we feel is acceptable.  Obviously connection times are a YMMV type of thing that depends heavily on your home internet speed, size of your project, cellular signal, etc... but we definitely see connection times in these regions that fall outside of what is "normal".
While we are striving for faster connection times both locally and remote, our attention is fully focused on the customers in these regions where the connection times are higher than what the majority of our customers are experiencing.  As such, we have formed a cross-functional team to address the problem at a team level as well as holistically.
It will take us some time to make these changes and roll them out, but I wanted to let everybody know that we understand the difficulty and the frustration and we are committed to fixing it.
I have now received several reports about this and have received logs from @Anish (thanks btw), and I have an engineer looking into the problem as I'm typing this.  I will create a post (or update here) when we figure out, and fix the issue.
 
 

We have quite a few performance metrics inside of the OS3 app and one of those is cold-start time while remote (i.e. not on your local network) and the connection times in some regions, as many of you have experienced, is sub-optimal and outside of the range we feel is acceptable.  Obviously connection times are a YMMV type of thing that depends heavily on your home internet speed, size of your project, cellular signal, etc... but we definitely see connection times in these regions that fall outside of what is "normal".
While we are striving for faster connection times both locally and remote, our attention is fully focused on the customers in these regions where the connection times are higher than what the majority of our customers are experiencing.  As such, we have formed a cross-functional team to address the problem at a team level as well as holistically.
It will take us some time to make these changes and roll them out, but I wanted to let everybody know that we understand the difficulty and the frustration and we are committed to fixing it.
I have now received several reports about this and have received logs from @Anish (thanks btw), and I have an engineer looking into the problem as I'm typing this.  I will create a post (or update here) when we figure out, and fix the issue.
 
 

We have quite a few performance metrics inside of the OS3 app and one of those is cold-start time while remote (i.e. not on your local network) and the connection times in some regions, as many of you have experienced, is sub-optimal and outside of the range we feel is acceptable.  Obviously connection times are a YMMV type of thing that depends heavily on your home internet speed, size of your project, cellular signal, etc... but we definitely see connection times in these regions that fall outside of what is "normal".
While we are striving for faster connection times both locally and remote, our attention is fully focused on the customers in these regions where the connection times are higher than what the majority of our customers are experiencing.  As such, we have formed a cross-functional team to address the problem at a team level as well as holistically.
It will take us some time to make these changes and roll them out, but I wanted to let everybody know that we understand the difficulty and the frustration and we are committed to fixing it.
I have now received several reports about this and have received logs from @Anish (thanks btw), and I have an engineer looking into the problem as I'm typing this.  I will create a post (or update here) when we figure out, and fix the issue.
 
 

We have quite a few performance metrics inside of the OS3 app and one of those is cold-start time while remote (i.e. not on your local network) and the connection times in some regions, as many of you have experienced, is sub-optimal and outside of the range we feel is acceptable.  Obviously connection times are a YMMV type of thing that depends heavily on your home internet speed, size of your project, cellular signal, etc... but we definitely see connection times in these regions that fall outside of what is "normal".
While we are striving for faster connection times both locally and remote, our attention is fully focused on the customers in these regions where the connection times are higher than what the majority of our customers are experiencing.  As such, we have formed a cross-functional team to address the problem at a team level as well as holistically.
It will take us some time to make these changes and roll them out, but I wanted to let everybody know that we understand the difficulty and the frustration and we are committed to fixing it.
I have now received several reports about this and have received logs from @Anish (thanks btw), and I have an engineer looking into the problem as I'm typing this.  I will create a post (or update here) when we figure out, and fix the issue.
 
 

We have quite a few performance metrics inside of the OS3 app and one of those is cold-start time while remote (i.e. not on your local network) and the connection times in some regions, as many of you have experienced, is sub-optimal and outside of the range we feel is acceptable.  Obviously connection times are a YMMV type of thing that depends heavily on your home internet speed, size of your project, cellular signal, etc... but we definitely see connection times in these regions that fall outside of what is "normal".
While we are striving for faster connection times both locally and remote, our attention is fully focused on the customers in these regions where the connection times are higher than what the majority of our customers are experiencing.  As such, we have formed a cross-functional team to address the problem at a team level as well as holistically.
It will take us some time to make these changes and roll them out, but I wanted to let everybody know that we understand the difficulty and the frustration and we are committed to fixing it.
I have now received several reports about this and have received logs from @Anish (thanks btw), and I have an engineer looking into the problem as I'm typing this.  I will create a post (or update here) when we figure out, and fix the issue.
 
 

Not a problem, I'm always happy to help.  The development team is working through the issue with the web services team.  I'll post here when I know more

go to stations and make sure you have it visible there too

Not a problem, I'm always happy to help.  The development team is working through the issue with the web services team.  I'll post here when I know more

Well kind of related, I did upgrade to 13.1.2 so maybe that triggered TouchID to stop working within the app. It's been a tough week keeping up with the iOS updates lol. But at least it hasn't started to crash the app again.
EDIT: On second thought I think you're absolutely right @brentethat this is an iOS issue and not an app issue. Sorry for the false alarm! @jakblak

Unfortunately his look at the logs didn't really help, although I did appreciate that he took the time to do it. He looked at the logs and just confirmed that the logs say that the issue is that the DS2 wasn't responding the call, hinting at a network issue.... But again....If the NVR connects great and for that matter just a ping using CMD prompt connects.... the issue is definitely part software.
I sent him a message saying almost the same thing as my post. We will see if he has any feedback. 

Hi @Anish, if you're interested I'd be happy to have my team take a look at your app logs to see if we can diagnose why your connection times are slow.  

Hi @Anish, if you're interested I'd be happy to have my team take a look at your app logs to see if we can diagnose why your connection times are slow.  

A new version of the 2.10 beta app is out and it has the fix for crashing at startup when using biometrics (TouchID/FaceID).  If you've already downloaded TestFlight you'll be notified of the new build, if not, then you can use this following link (it's the same one from my previous post).
 
https://testflight.apple.com/join/EtAiX35m

Hi all, iOS 13 did cause some problems for the 2.10.x version of the Control4 app.  As many of you have seen, iOS 13.1 fixed the problem with the missing icons but other issues remain.  The development team has fixed those issues and we have submitted a new version of the app for beta review.  Once the app has been approved for beta testing I will post a download link in this thread.
Thanks for everyone's patience

Hi all, iOS 13 did cause some problems for the 2.10.x version of the Control4 app.  As many of you have seen, iOS 13.1 fixed the problem with the missing icons but other issues remain.  The development team has fixed those issues and we have submitted a new version of the app for beta review.  Once the app has been approved for beta testing I will post a download link in this thread.
Thanks for everyone's patience

Hi all, iOS 13 did cause some problems for the 2.10.x version of the Control4 app.  As many of you have seen, iOS 13.1 fixed the problem with the missing icons but other issues remain.  The development team has fixed those issues and we have submitted a new version of the app for beta review.  Once the app has been approved for beta testing I will post a download link in this thread.
Thanks for everyone's patience

Hi all, iOS 13 did cause some problems for the 2.10.x version of the Control4 app.  As many of you have seen, iOS 13.1 fixed the problem with the missing icons but other issues remain.  The development team has fixed those issues and we have submitted a new version of the app for beta review.  Once the app has been approved for beta testing I will post a download link in this thread.
Thanks for everyone's patience

Hi all, iOS 13 did cause some problems for the 2.10.x version of the Control4 app.  As many of you have seen, iOS 13.1 fixed the problem with the missing icons but other issues remain.  The development team has fixed those issues and we have submitted a new version of the app for beta review.  Once the app has been approved for beta testing I will post a download link in this thread.
Thanks for everyone's patience

I'm not a dealer but I can comment on this.  The connection times are slower than they were in OS2 due to an underlying change in the networking technology used to talk to the controller.  The team is hard at work on reducing connection times and we've already made great strides and we're continuing to reduce them further.  We'll be dropping a public beta of the app in the next month or so with these connection improvements and I'll post the link in this thread so if you're interested you can give it a try.  In the meantime, thanks for your patience

Hi @GSC4Home,
As we were evaluating the 3.0 development timeline there were certain features that had to be cut to ensure that critical functionality and overall quality was baked into our initial release.  Unfortunately, "Dedicated Mode" was one of those features.  Nobody likes when features are cut, including ourselves, but we felt that with the option to enable "Guided Access" (Enable Guided Access) on an iPad that our time would be better spent adding critical features that iOS doesn't provide by default.
 
With that said, we're always sensitive to customer requests and if this is a highly-desired feature relative to other requests it may make a return.