DatBear

If you'd like to send me the logs and help troubleshoot this let me know. You can send me a direct message and attach the logs. Also are you on the latest App Store build? Do you know what version your C4 controller is running (director version).

Lets do a direct message about this since I don't think the general community will benefit from your particular issue at this point and we need to probably troubleshoot some things that are unique to your project and setup. If the resolution proves to something more than configuration issues or you feel the community would benefit from your solution then we could do a post at that time. Generally when cameras fail they fail remotely but work locally. Sounds like yours doesn't even work locally. Which changes the things we need to troubleshoot because different things are going on behind the scenes. Send me a message and we'll dig in to the issues. What would be helpful to know is what version of Control4 is running on your controller and what version of the iOS app you are using. Thanks

Am I correct in that you are viewing the cameras remotely when it fails? What version of the app are you using? Does everything work correctly locally? When you say they used to work but now don't do you know of any changes that occurred between when they did and didn't work? (Did you upgrade your home system, change network gear, did the app update? etc)

I know this doesn't address the browser plugin issue but this is what I use to view my Luma NVR since all my browsers don't work with the plugin. Apple: https://apps.apple.com/us/app/luma-surveillance/id999425761 Android: https://play.google.com/store/apps/details?id=com.snapAV.iVMS&hl=en_US With that app you can view live streams and the NVR's recorded events. I only use it to see the recorded events and view the live cameras in the Control4 App.

What do you mean by tablet? Are you referring to an Android device or iPad? What versions of the App are you using?

I am not an expert at this kind of troubleshooting but what knowledge I do have about it is that it seems like that you have a bad driver. Depending on how much it's spamming the controller with bad arguments being sent can account for any delay in functionality too. Meaning if the controller gets flooded with a bunch of bad driver calls it has to take time processing all of them before it can do some other things in the system. I do know that many drivers did need to be updated to account for changes in the 2.x and 3.x OS handles things. Often this can be resolved by having the dealer check if the driver is out of date and needs to updated or track down or create an issue with the driver creator on the driver. Without more information this is just some suggestions that could be the problem but no one was responding to your post and I at least wanted to point you in the right direction if possible.

DM me if anyone is having a further issue resolving this.

I've gotten more information on this fix. For anyone else that has this problem. Power cycle your controller Unregister your controller, then re-register it. This should resolve cert issues between the controller and mobile clients (Android/iOS)

I just confirmed with the Android team as well. If you are on the latest release of the mobile app and provide me your controller's common name I can forward that to the team to push out an updated cert to your controller. DM me the info.

I didn't see any mentions in the post about android and since I am an iOS developer I posted about the issues I knew directly about. However the fact is that a controller certificate change occurred on the controller which both android and iOS utilize for authentication. The android issue could be unrelated to the reported issues in this thread but to I'll forward this issue to the android team to get their opinion

There were some changes that Apple made to how certificates are handled on iOS 13. It's a hand shaking issue between the mobile client and the controller. The certificate being used on the controller as part of this process needs to be updated. If you directly message me the common names of any of the controllers that are experiencing this behavior I will escalate the issue with our teams to push out new certificates to your 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!

Ah I see I think 3.0 supports both Alexa and Google, I use both in my house, with a mix of Android and Apple for mobile. It's a bit more hodgepodge

If you have a google mini or google home or any of those type of devices and you don't want to add a Raspberry Pi as a bridge you can let google be the bridge and download google assistant to you iPhone. It's a software work around to the problem if you already have the hardware in your home.

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.