HaloSmartHome

We also have the same building set up with a TON of other ioT platforms and gear for testing and have literally no problem with other apps connecting at speed. For example we have a complete Alarm.com monitored system , a complete Vivint monitored system, Hubitat Hub/Platform, Smarthings Platform , Googles Suite of products, 40+ Hue light bulbs, etc, etc. All of which have apps that connect multiple services together that only take within 1-2 seconds tops to connect via mobile. I am puzzled at how C4 is featured as a premier platform, and IMO has the BEST looking UI of them all, Takes 10x longer to load, and Cost 10x as much at the same time. Figured someone on here would know something if its been going on for a while or just an overseen error on our part.

@South Africa C4 user @lippavisual Does the VPN really help that much? If so Why / What is it doing to create that speed? @zaphod That is exactly why we are asking. The farther away from the location we are... The longer it takes to connect. This leads me to believe there could be some kind of location/proximity handshake happening - could be for geo data mining purposes behind the scenes. I would assume others having the same issue would agree that there is a poorly placed block somewhere in the architecture of that could be improved. Entertaining this off-sounding idea would explain a lot of things with latency because every time you try to log into your system, your cell phone first would send a signal to the cellular towers... then how many other handshakes / steps happen before it finally loads? I would like to know what the structure of that is because it feels like its making a bunch of pitstops if you get my drift.

Location : Tampa, Florida.

We would like to know if anyone has solutions on speeding up the 4Sight connection when using a mobile device remotely? We have found several threads talking about the issue of iOS devices connecting slower than Android devices, As well as mobile devices taking anywhere from 10-20 seconds to connect in general whenever the user is off-site. So far the solutions we have tested and read are as follows: A) Making sure the control4 OS is up to date. B) Turning off iPhones "Low Data Mode & Data Saver Mode" under settings > cellular > cellular data options. C) Resetting the phones "Cellular Network Connection" under general > reset. D) Changing the DNS settings on the homes WiFi routers primary and secondary slots to use the Cloudflare DNS 1.1.1.1 , and googles 8.8.8.8 to get faster connections. E) Changing the DNS settings in composer for the project to also use Cloudflare and Google DNS as primary and secondary. F) Turning off the phone setting "use Wifi when cellular is not strong" on the phone so there's not added delay in processing. Testing Notes: 1. When WiFi is ON - and we are on-sight of the location, average mobile app connection time = 2 seconds. 2. When WiFi is OFF - and we are on-sight of the location, average mobile app connection time = 6 seconds using cellular only. 3. When we are off-sight of the location by 1 mile... average connection time = 10 seconds. 4. When we are off-sight of the location by 5+ miles average connection time = 14 seconds. The farther away from the controller, the longer the mobile app takes to load. Why is this? Maybe we can get C4 engineers involved in providing a solution. Questions: Is there a way of getting the data to load faster by attaching some type of cellular communicator to the EA controller / Or storing the projects data and settings onsite using external storage ton sync to the mobile device faster? Suggestion to Engineers: Suggestion 1 - You could split up the app load times by dispersing the entire average load time over small incremental user functions... For example by clicking lights, make the button swell for 1/2 a second and have it show a 1 second load bar to keep the user engaged... and recreate this for each button experience. Anything "Favorited" would have a higher priority load speed as you could make the less used devices load a hint slower for a wonderful end user experience. This would actually be able to take a 12 second loading screen and make it a wonderful experience. Suggestion 2 - Allow the app to save certain data on the users mobile device so it does not have to load through your servers every time / Or have some sort of direct connection that a users cellphone sends signals directly to the controller.