Introduction - Control4 iOS Developer

[Anish]

23 hours ago, hunger said:

 

From initial launch mine takes about six seconds to connect and the screen to appear over a cellular connection which, from what I remember, was about the same under 2.x.


Sent from my iPad using Tapatalk Pro

 

Not for all of us unfortunately. 

[JoelC]

On 11/26/2019 at 12:44 PM, DatBear said:

Joel or a product manager would have to respond directly to this for anything to carry any weight.  I believe there are some very small edge cases where an IP is needed to be set when using a controller in a what some people called "Cabin Mode" which is essentially the controller has no internet access and needs to operate as if it did, at least in terms of security and logging in.  If that feature makes it's way into 3.0 I would imagine it would be to address that use case more than to allow access to your system via VPN without a 4sight license. 

@terminaldisclaimer Unfortunately, Control4 does not directly support VPN access. The issue blocking VPN access is that most VPNs don't forward multicast packets across the VPN. Our mobile apps use multicast to find the controller that is running the home automation system. If you can setup your VPN to forward multicast packets (both directions), then there is a good chance the apps will be able to connect over VPN.

[JoelC]

On 11/30/2019 at 8:20 AM, Anish said:

Hi. Could you do something about the slow startup time of the iOS app on os 3.1.xx using 4sight. The new iOS update made it better but it still takes over 20 seconds to connect remotely. 
 

on os 2.xx using vpn it was instantaneous. What’s the point of paying for a 4sight service when it’s so slow to start... 

@Anish I agree, twenty seconds is too long. Would you mind saying your country (or direct messaging me (DM))? I don't have time frames, but we are working on speeding up remote connection times for countries outside of North America.  

[Vercingetorix]

13 minutes ago, JoelC said:

@terminaldisclaimer Unfortunately, Control4 does not directly support VPN access. The issue blocking VPN access is that most VPNs don't forward multicast packets across the VPN. Our mobile apps use multicast to find the controller that is running the home automation system. If you can setup your VPN to forward multicast packets (both directions), then there is a good chance the apps will be able to connect over VPN.

Will "Cabin Mode" be re-introduced to version 3?

[JoelC]

On 11/29/2019 at 2:42 PM, hunger said:

Hi Jonathan,

I am thrilled that you have volunteered to get involved. It's really painful for customers when issues are encountered that are likely beyond the purview of a dealer to address.

My issue is regarding camera integration. The iOS version of the Control4 app for version 3.x frequently (>95%) crashes when tapping on a camera image to bring up a live view. Using Xcode and downloading the crash logs, it is crashing in SurgeiOS, which I suspect may be https://github.com/Jounce/Surge. The Android version does not crash and displays the video as expected. I am using three channels of an Axis M7014 four-channel SD video encoder with analog cameras and an Axis M1025 camera.

I have tried uninstalling and reinstalling the app, etc.

Incident Identifier: F1477E85-6108-449F-98A0-1266B6DB3957
CrashReporter Key:   97269969dc1691ac0bc60ec3d38692333aceb731
Hardware Model:      iPhone11,2
Process:             Control4 [32739]
Path:                /private/var/containers/Bundle/Application/175E6D19-B5FD-405A-9C3C-217400C3FA5D/Control4.app/Control4
Identifier:          com.control4.app3
Version:             95 (3.1.3)
AppStoreTools:       11B48b
AppVariant:          1:iPhone11,2:13
Code Type:           ARM-64 (Native)
Role:                Foreground
Parent Process:      launchd [1]
Coalition:           com.control4.app3 [2204]

Date/Time:           2019-11-29 12:39:06.3211 -0800
Launch Time:         2019-11-29 12:29:49.2211 -0800
OS Version:          iPhone OS 13.2.3 (17B111)
Release Type:        User
Baseband Version:    2.02.12
Report Version:      104

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000004
VM Region Info: 0x4 is not in any region.  Bytes before following region: 4310843388
      REGION TYPE                      START - END             [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->  
      __TEXT                 0000000100f24000-0000000100f28000 [   16K] r-x/r-x SM=COW  ....app/Control4

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [32739]
Triggered by Thread:  26

Thread 26 name:  Dispatch queue: com.apple.root.default-qos
Thread 26 Crashed:
0   SurgeiOS                          0x00000001029923f8 0x102974000 + 123896
1   SurgeiOS                          0x00000001029922ac 0x102974000 + 123564
2   SurgeiOS                          0x0000000102990c40 0x102974000 + 117824
3   SurgeiOS                          0x0000000102a0910c 0x102974000 + 610572
4   SurgeiOS                          0x0000000102981c38 0x102974000 + 56376
5   SurgeiOS                          0x000000010298046c 0x102974000 + 50284
6   SurgeiOS                          0x00000001029802c0 0x102974000 + 49856
7   SurgeiOS                          0x0000000102980170 0x102974000 + 49520
8   Control4                          0x0000000100fe45e8 0x100f24000 + 787944
9   Control4                          0x0000000100f5c690 0x100f24000 + 231056
10  libdispatch.dylib                 0x0000000181b88b7c _dispatch_call_block_and_release + 32
11  libdispatch.dylib                 0x0000000181b89fd8 _dispatch_client_callout + 20
12  libdispatch.dylib                 0x0000000181b8c414 _dispatch_queue_override_invoke + 672
13  libdispatch.dylib                 0x0000000181b98bd4 _dispatch_root_queue_drain + 348
14  libdispatch.dylib                 0x0000000181b99384 _dispatch_worker_thread2 + 120
15  libsystem_pthread.dylib           0x0000000181befa54 _pthread_wqthread + 216
16  libsystem_pthread.dylib           0x0000000181bf5c7c start_wqthread + 8
 

This is not a new problem. It  was a problem that I had hoped would go away when upgrading from 2.x to 3.x but did not. I don't recall when it started happening but it was a quite a while ago when upgrading the iOS Control4 2.x app from one version to another.

I can send you the crash dump to if you like. I didn't want to attach it just in case it contained anything that should be private.

Henry

P.S. It also crashes on iOS 13.3 with a SIGSEGV in thread 0 but I did not want to bother you with that.

@hunger (If you haven't already) Could you email app logs to appsupport@control4.com with your make and model of the camera it crashes on. We did change out the iOS camera rendering engine at the beginning of the year. Unfortunately, some (mostly older) cameras experienced issues. The easiest way to email logs is to go in the app to Settings > Preferences () > Email Logs.

[JoelC]

21 minutes ago, Vercingetorix said:

Will "Cabin Mode" be re-introduced to version 3?

@Vercingetorix Yes, we never removed cabin mode, but unfortunately there have been a couple bugs that blocked some customers from connecting to a system that is not connected to the internet. To my knowledge the issues have been fixed and released. 

[Vercingetorix]

35 minutes ago, JoelC said:

@Vercingetorix Yes, we never removed cabin mode, but unfortunately there have been a couple bugs that blocked some customers from connecting to a system that is not connected to the internet. To my knowledge the issues have been fixed and released. 

My mistake.  I thought "Cabin Mode" was associated with being able to specify the IP address of the controller, or the app using the last known IP address as shown under "IP Address".  Thanks for clarifying.  

[Anish]

On 12/4/2019 at 2:17 AM, JoelC said:

@Anish I agree, twenty seconds is too long. Would you mind saying your country (or direct messaging me (DM))? I don't have time frames, but we are working on speeding up remote connection times for countries outside of North America.  

South Africa 

[South Africa C4 user]

4 hours ago, Anish said:

South Africa 

I am told that we (South Africa) are getting new (better) servers in Q1 2020 and can expect a marked improvement in performance at that stage...

[hunger]

[mention=122596]hunger[/mention] (If you haven't already) Could you email app logs to appsupport@control4.com with your make and model of the camera it crashes on. We did change out the iOS camera rendering engine at the beginning of the year. Unfortunately, some (mostly older) cameras experienced issues. The easiest way to email logs is to go in the app to Settings > Preferences () > Email Logs.

Thanks! I have done so.

Henry


Sent from my iPhone using Tapatalk Pro

[Bubben]

On 11/27/2019 at 3:48 PM, Bubben said:

That is correct, im using the latest 2.10.X os. 
Some of my drivers are up to date, and some are not. But you believe this issue is related to drivers and not iOS?

I’ve verified that it works in iOS12 on iphone, works on 8.2 on iPad, works on iPadOS, but not on iOS13 on iPhone. 

Any response to this?

Is this an issue you heard of before, or does everyone else have search-capability on their iphone with ios13?

I cant be the only one that cant go to OS3, Because of to many EA-controllers?

Edit: My bad, meant HC-controllers, not EA. 

[Jonathan, C4 Engineer]

On 12/12/2019 at 11:08 AM, Bubben said:

Any response to this?

Is this an issue you heard of before, or does everyone else have search-capability on their iphone with ios13?

I cant be the only one that cant go to OS3, Because of to many EA-controllers?

I may have lost some of your details of your issue throughout this thread if so it might be best to message me directly. But if I understand the issue correctly, you're on OS 2.x and you are saying that you've lost features of searching for some or all of your services? But your last comment states an inability to go to OS3 because of the number of EA-controllers  you have in your project. So your issue seems a little conflated between 2 different issues. I am not familiar with the code base for OS2.x because that predates my involvement with mobile at Control4. But I can say in regards to searching on OS3 drivers being up to date play a big role in what's displayed per service. When in comes to this version the driver-UI interaction was redesigned and the audio/video drivers control the UI and the app's capabilities for the service. The iOS version shouldn't be a factor with search appearing or not.

If you do update to OS3.0 and are dealing with a major driver (ie. Deezer, TuneIn, Pandora, iHeart Radio...etc) any search issues you are having should go away as long as the drivers are the latest. If  my comments don't address the issue you are having or need further explanation message me directly so we can discuss further.

Thanks!

[Flash2k6]

Any idea when Control4 is going to update their Apple TV driver to support the MRP protocol so we can go back to IP based controls instead of using IR for IOS13?  Even with the Apple Bridge and the latest IP driver, it still doesn't work.  Only way I can get it working currently is via IR or via a third party driver, but I'd prefer the original native C4 driver.