jrdiandrea

It's been a very long time.....I posted and others commected long ago about the connectivity of the ap....disconnecting consistantly while in us when the iphone screen ws closed or yu left the ap for a period. Well, earlier this week the latest update nor provides smooth always connected state while using the ap. I've used it now a few times and it is a great experience. I can go the screen on impulse and it is there and active and responsive. No waiting 3-4 seconds for it to reconnect. It has improved in small increments the last couple updates but now it's just about perfect. It's like it used to be. THANK YOU to those involved making this happen!

It's been a very long time.....I posted and others commected long ago about the connectivity of the ap....disconnecting consistantly while in us when the iphone screen ws closed or yu left the ap for a period. Well, earlier this week the latest update nor provides smooth always connected state while using the ap. I've used it now a few times and it is a great experience. I can go the screen on impulse and it is there and active and responsive. No waiting 3-4 seconds for it to reconnect. It has improved in small increments the last couple updates but now it's just about perfect. It's like it used to be. THANK YOU to those involved making this happen!

It's been a very long time.....I posted and others commected long ago about the connectivity of the ap....disconnecting consistantly while in us when the iphone screen ws closed or yu left the ap for a period. Well, earlier this week the latest update nor provides smooth always connected state while using the ap. I've used it now a few times and it is a great experience. I can go the screen on impulse and it is there and active and responsive. No waiting 3-4 seconds for it to reconnect. It has improved in small increments the last couple updates but now it's just about perfect. It's like it used to be. THANK YOU to those involved making this happen!

Outside looking in it's easy to see that the point of view appears that there's just one group that makes everything work. Because there's just 1 app that allows us all to interface with our homes but in reality there's a dev group for drivers, one for core controller work, QT, OvrC, Cloud Services, Android and iOS to name a few. Sometimes we all have a piece of the pie and we implement things at different times base on priorities for the group. But rest assured we are all moving towards the same goals and that's the best customer experience we can provide. It really is our passion. Thanks for hanging in there with us as we improve with every release.

Not a beta tester. But I did get a c4 app update that rolled out this morning. With this update both the slider and buttons and the position on the processor are all working and syncing as they should. The slider and buttons are working together now and I see no anomalies. I only spent about 5 minutes testing it but looked good to me. I did not test the mute button.,....

I just completed the movie i was watching and powered down the Datasat and unplugged it. It has rebooted. I’ll be running it again later this evening and will report back. 
thx!

Ugh. Didn’t think far enough…. It’s probably the Datasat, huh?

Wow. After all this time....you've gotta be thrilled with that!! Congrats!

I cant tell my clients that they need to upgrade to a ca10, because of faster connection speeds..
I dont know how communication inside c4 works, but i dont know any other smarthome that needs so much time for the connection.

Yikes! I do remember seeing you post often in other threads a while back. I thought those issues for you in Africa had been addressed. At least that was the impression i got. But then again I guess I didn't pay close attention as it wasn't an issue I had to deal with. And have multiple homes creates an obvious need for fast consistent response and connection.

Thanks for the replies.  Good to know I am not alone, but still feels like something that should be addressed, given that 2.0 didn't have this issue. 
 

‘Well, I’m mostly talking about local access but a criteria of “cameras in less than 30 seconds” for remote access makes remote access pretty much unusable for me.  I use C4 on my phone mostly to view cameras or trigger experience buttons after I’ve received a Pushover alert (usually after a doorbell or motion event) and I need to see cameras in a second or two, not just under 30.
But - even excluding cameras - overall OS3 is more sluggish than OS2 with the same project and EA5 from a performance standpoint running the system.  It’s just easier to notice when you are using an iPad.

Os 3 with all its added features still has many bugs including this one. Some of us pay for 4sight subscription and still have to wait 45 to 60 seconds to populate  the screen which is thereafter extremely laggy. Remote usage of our control 4 system is non functional.
@jakblakwas looking into this.  
 
I am deeply disappointed with oS3.xx as I consider remote operation as a  core functionality for my purposes. 
 

I’ve got a CA-10 and a massive project.  When on local WiFi, the app loads pretty much instantaneously.  Less than 2 seconds and no lag with experience buttons on the main screen.  This and the speed of refreshing navigators was the most noticeable improvement when we moved to a CA-10.
I can’t comment on the “normal” load speed on cellular as we have an issue with Control4 servers in our part of the world, which I am told (and really hope) will be fixed this quarter. My current load times are 20 plus seconds when on cellular and then I really see the Experience Button lag,

It’s pretty noticeable if you have any experience buttons on the main screen of a room or an active audio session.  Both take significantly longer to finish populating once the room is loaded. It’s pretty bad from an end user perspective.  I use an iPad for about 90% of my control interactions when I’m not using voice control with the rest on a T3.
 
 I’m considering buying a CA-10 and I’d be fine doing so if I knew that would be enough to overcome the noticeable sluggishness I’ve experienced since moving to OS 3.1.  It’s certainly not my wireless network (significantly improved); it has to be some combination of OS3 and the EA5.

Control4 is under new leadership and the feature is at the moment not looking good 
Hopefully they will see the light 

a newer release will speed that up - control4 is working on that right now