Darin, PM C4 CX Platform

I passed the info about the new Push API from Hue to our drivers team and they said it is in their backlog to move in that direction with a future driver update, but couldn't give me a timeline on when to expect it since they had some other driver updates in front of it.

@chrism, Are you a dealer or an end-customer. I have Hue in my project and can confirm 1-4 is working properly on the 3.3.0 build just released to production. 1. Make sure your using the new Philip's Hue Light (OS 3.3.0+) drivers (v72) with your bulbs and that the Hue bridge driver is updated to the latest (v 849) and then make sure your Poll interval is set, this is the polling rate that it will check for state changes. So if you make a change in the Hue app it will take this long before C4 is in-sync with what is shown in the Hue app. (Default rate is 30 seconds) For 2 & 3, The T3 & T4 have the functionality, it is under a long press of the bulb icon > color. However, it may just need to sync with the feature flag server before it is available. It does a check-in for feature changes every 15 minutes or so, you can reboot the device to speed things up. We are in the process of moving to a new service that will be instant, because the sync delays associated with the current feature flag service can cause confusion. ^ See above What kind of switch are you binding it too? When bound to a keypad, everything is working properly in my system for on, off, and dimming. (See attached image)

@zaphod, You will definitely see improvements with OS 3.2.4, but the HC800 couldn't support all the changes needed to work with the new servers. So you would need to replace the HC800 with a EA, CA, or CORE series controller to see all the speed improvements.

We discovered a bug that caused push notifications to become unregistered in some cases which would lead to not receiving incoming call. We just submitted a 322.20.0 build with a fix to Apple and it will be available as soon as it makes it through their review process. If you'd like early access to this build you can get it from TestFlight here: https://testflight.apple.com/join/bI6oH4Gu

Here are the 3 different connection types, pictured top to bottom. Local Remote (Legacy) Remote (New)

@Amr, I noticed on your bug report that you have an HC800 running your system. Unfortunately, we weren't able to get all the speed improvements working against that controller's older chipset, so you will see some speed improvements but won't have the complete optimized experience. In order to get optimal speeds you'll need an EA or CA series controller with OS 3.2.4 or above.

@South Africa C4 user Can you pull logs from your iPad and DM them to me, so I can write up a bug for the team to look into. This was a complete overhaul of how things connect/work, so it is possible a bug or two were missed.

You should see improvements across the board especially for remote connection times, the updated version to look for is 322.18 or above. When connecting over 4Sight look for the lightning bolt to know you connected through the new Lightning servers, but be aware that these remote speed improvements only work with the newer OS 3 builds so it may require an OS update to get the speed improvements if your system is running an outdated OS. Here is a video of me connecting over 4Sight on a solid Wi-Fi connection averaging 2-3 seconds to be fully connected. RPReplay_Final1652165140.mov

@Rob21 So you will launch the app and all your favorites show up except for lighting scenes, but then if you force close and relaunch they'll show up? The next time this happens can you grab mobile app logs and PM them to me, so I can write a bug up for the iOS team to look into?

@South Africa C4 user Today we released 322.5.0 this version includes the changes that @ChrisHendersonmentions above that should resolve your camera snapshot issue. Can you update your app, test, and let us know if you are still seeing any camera issues?

Hi @Dueport, The purple camera issues on Apple silicon chips (M1) used in the new macs is being worked on. It is an issue relates to the multimedia library we use and the way macs emulate iOS apps. I don't have a current ETA on a fix, but it is being investigated and should be fixed in the coming months.

@msgreenf Thanks for bringing me into the conversation. I just chatted with the iOS team about this and these crashes are being caused by a crash in the media framework library that is used with the Control4 OS 3 app, we have an escalated ticket submitted to the library developer to address the issue and will release an updated iOS app with a fix as soon as it becomes available.

Hi @JAJUTI, I believe the only way you can get an older version is if you had it installed previously then the app store is supposed to let you download the newest version that is compatible, but that is all handled by the OS & Apple's app store so I don't know the steps to make this happen. It sounds like htjunkie was able to get this to work at some point in the past.

@IntrinsicGroup The statement below is no longer correct. As of Dec 2nd 2021, Control4 systems running OS 3.1.3 and above can access drivers like this through phones & tablets. It just requires that the driver is updated to support the new javascript API. See https://control4.github.io/docs-driverworks-proxyprotocol/#javascript-api

321.46.1 doesn't fix cameras on M1 Macs, but the iOS team is working on it and we should have that fixed in early 2022.

321.46.1 is going through Apple's review process now with a fix for this.

This functionality is now available for all OS 3 customers.

The OS 3.2.4 release is to support the official release of Multi-Display Manager (which went into a public beta with OS 3.2.3) and address bugs.

Happy to announce that as of today, WebView drivers can now work on iOS & Android mobile devices with 321.46+ OS 3 mobile app and a controller running OS 3.1.3+. However, it does require updates by the driver writer using the latest DriverWorks SDK to take advantage of this new functionality. If you have WebView drivers you or a client uses that you'd like available on mobile, you'll need to reach out to driver writers with an update request to extended their driver with mobile support.

Update to 321.40, Intercom in OS 3 for iOS was just released today.

Update to 321.40, Intercom in OS 3 for iOS was just released today.

Update to 321.40, Intercom in OS 3 for iOS was just released today.

Update to 321.40, Intercom in OS 3 for iOS was just released today.

Correct, we have addressed the alignment issue and release the automatic update. The team believes they have located the problem with the indoor/outdoor temperature, but are still working through a resolution for it. I'll give you guys an update once we have a fix go into beta. Right now the only work around to get it fixed is to have a dealer set it through the UI config agent in Composer Pro, I've seen others confirm that this work around has fixed it for them.

@wiley This was broken in the last iOS update that went out alongside the OS 3.2.3 release. It only impact thermostats that rely on v1 driver protocols. We have a fix for this being tested in our beta group right now, assuming no critical issues are found the build should be released to production around Oct. 12th. Schedules are still accessible through the Android mobile app or a touch screen. If you need to control something immediately and don't have access to one of these devices you can use a free Android emulator like https://www.bluestacks.com/ to run the app on your computer. Sorry for the inconvenience.