Darin, PM C4 CX Platform

The testflight link above has been deactivated at this point. Thank you to those of you that downloaded and tested the latest version of the Control4 app. Feel free to move back to the app store version to continue receiving updates, the Apple Vision Pro support will roll out with build 324.15 next week.

Our developers have finished their testing of our app running on Apple Vision Pro, so here is a TestFlight link for early access to a version of the Control4 mobile app that includes support for Apple Vision Pro. Please give it a try and let me know if you are experiencing any bugs. 

https://testflight.apple.com/join/8TASGss5

The iOS team hasn't been able to get to testing of Apple Vision Pro yet due to higher priorities, but once they are able to give it a once over I would be happy to give you early access and get your feedback. 

15 hours ago, Shoe said:

Yea, sure. I grabbed it out of the release notes just to add the reference. I didn't create the release notes.

Thanks for highlighting this mistake in the release notes, I just pinged our tech writer to get this corrected.

2 hours ago, drmark12pa said:

Will the new update fix the issue of using ComposerHE remotely?

No the remote issue with HE is a cloud bug, we have the cloud team working on resolving it. However, the the status still shows as "Fixing", so I don't believe the actual issue is fully resolved yet.  Their is  a comment mentioning a work around being applied for existing HE users to gain remote access though, so if you aren't a brand new HE user then it may be working for you now.

23 hours ago, Scott Murray said:

On Control4's site I'm seeing HE version available is: 3.4.1.706039

Is 3.4.1.705920 the updated C4 3.4.1 OS build #?

If so, wondering if we'll need both upgraded OS and HE build to resolve the previous access issue?  Seems like it.

If you have touch screens in your system you will want to make sure your OS is updated to the latest 3.4.1 version since it resolves a screen jitter issue. 
Here are the updates to the original release notes for 3.4.1:

Quote

Important update: -__.An update to the original release of build of OS 3.4.1 is now available. The updated OS 3.4.1.705920 build - including an updated version of Composer Pro and Composer HE - resolves a UI jitter issue seen on some T4 8" Touchscreens and also resolves connectivity issues between Composer HE and the primary controller.

I just heard release day was moved to next week on Tuesday (2/27/2024), but everything is signed off so I would expect it to be live that day and shouldn't be any additional delays.  

@Cranky Oldman I just DM'd you the info to get the beta version, I believe it matches what will be the final release.
 

1 hour ago, oasisferine said:

Beta version is working fine for me, i had some intial hiccups to get it working had to delete all old versions, and delete all C4 data from C4 appdata folder and it worked fine.

Darin from C4 team was a great help to get it done for me.

3 hours ago, applemike68 said:

How do i add favorites in the new software so it can work with the iwatch app. For the life of me i can’t see to figure this out.  Thank you

This link and video should help.

https://www.control4.com/blog/630/apple-watch-favorites/

Composer HE is expected to release on 2/23/2024, if no additional critical issues are found. If any of you would like early access then DM me and I can get you a copy of the beta version for use/testing.

Composer HE is expected to release on 2/23/2024, if no additional critical issues are found. If any of you would like early access then DM me and I can get you a copy of the beta version for use/testing.

The team is going to look into it, but believes it is due to iOS's CallKit and how it is handling it.

I have a similar experience with Microsoft Teams when getting calls, so I'm not a 100% sure if we are in control of this or if it is managed by iOS. Either way, I've pinged the iOS team to investigate if this is a bug on our side that we can resolve.

We chosen not to have the app be available until we we are able to test compatibility and the experience. You can expect the app to become available once the review and testing process has been completed.  This is the same approach that was taken for supporting iPadOS apps on MacOS with Apple Silicon chips (M1, etc).

A couple additional issues surfaced during the beta for the new Composer HE, so those are being addressed now with a new HE build that should go out for testing soon. We'll be rolling the HE update out once testing and validation pass successfully. We have also identified the gap in testing that allowed this to slip out in an unfunctional state and have updated our testing/release process for HE to ensure this shouldn't happen again in the future. 

A couple additional issues surfaced during the beta, so those are being addressed now with a new HE build that should go out for testing soon. We'll be rolling the HE update out once testing and validation pass successfully. We have also identified the gap in testing that allowed this to slip out in an unfunctional state and have updated our testing/release process for HE to ensure this shouldn't happen again in the future. 

Composer HE's patch build will be a regular update that your notified of on launch it is in beta now and should be out to production relatively soon. I'm not sure of the exact ETA though.

4 minutes ago, Neo1738 said:

Not sure anyone else noticed but my apple watch ultra 2 is so much faster, more stable, and there is now session/transport controls with volume!

 

Glad you noticed the Apple Watch updates!

Composer HE will be a regular update that your notified of on launch it is in beta now and should be out to production relatively soon. I'm not sure of the exact ETA though.

I just spoke with the Composer team and it sounds like if testing goes well then a new update should be rolling out next week that will resolve the issue with Composer HE and OS 3.4.1

5 hours ago, Andrew H said:

I did open a ticket with C4 support yesterday but haven't heard anything yet. I was able to verify just now on a legacy-registered system that I am able to connect, so I'll try tonight to see if switching registration methods works to re-allow access. It's looking like Matt is right and that Connect is required for new systems registered with OVRC immediately.

@Andrew H,
Are you a Control4 dealer? If you want to DM me your account info then I can have someone take a look.

This would either be a bug or a misstep in the OvrC registration process. As you were going through the OvrC registration flow their should have been an option for a Connect or 4Sight account, if you chose Connect then you end up where you are now, but if you chose 4Sight then you can complete the customer hand-off without seeing these screens.

Thanks for passing that along @bnorman


@BDavisNJ

@dblessing
We have the Composer team working to get a new Composer HE for 3.4.1 out the door as quickly as possible to resolve this issue. I don't have an ETA, but I can follow up with that team to see if I can get any additional details or see if they need some end-users to test the changes prior to full release. 

@antneed,
I'm not aware of any outstanding issues.  Can you attempt to connect over 5G, then email yourself the mobile app logs, and DM them to me?  Once I have your logs, I can have an iOS engineer take a look.

The steps to get you mobile app logs are below:

Getting Mobile Logs (New Settings UI)

• Menu
• Settings
• Support
• Support Settings
• Email/Share Logs

Getting Mobile Logs (Old Settings UI)

• Menu
• Settings
• Preferences (Top right corner)
• Email/Share Logs

The bug in 3.4.1 Composer HE will impact all systems running OS 3.4.1 currently.  The team that works on Composer believes they have found the root cause and they should have a patch out soon.

@zaphod,
Thanks for mentioning this, I had the Android development team double check things to make sure everything was setup properly to distribute to all markets since Canada is in the currently supported markets. They discovered that Windows 11 support had been unchecked for the last 2 versions due to a change in the app submission flow with all the updates that Amazon has been making to their developer console. They've fixed the issue and resubmitted the app for review, so you can expect it to be available again within 24-48 hours.

For reference of what countries offer support for the Windows Subsystem for Android and the Amazon App Store you can reference the link below.
https://support.microsoft.com/en-us/windows/countries-and-regions-that-support-amazon-appstore-on-windows-d8dd17c7-5994-4187-9527-ddb076f9493e

4 hours ago, LollerAgent said:

Split.io is a SaaS company that handles feature flagging.  I'm sure C4 is using it to gradually test or roll out features -- although it is a tiny bit odd that the system(s) are designed in such a way that the end user device (the controller) is making these requests and not C4's own backend systems.  I don't totally understand the C4 architecture though.

LollerAgent is 100% correct, we added Split.io into the Control4 platform and applications back around 2019 when we moved to more modern software development and deployment processes. The frequency of polling was actually something we disliked about Split.io and earlier this year we moved off Split.io to Launch Darkly.  So I'm surprised to see a Core controller still talking to Split.io. @416to305 I've sent you a DM for some system info, so I can have an engineer take a look at what is going on.

I believe pi hole devices block communication to both Split.io and Launch Darkly, so you may want to consider whitelisting Launch Darkly to receive new features as they become available. 

pihole -w launchdarkly.com clientstream.launchdarkly.com stream.launchdarkly.com clientsdk.launchdarkly.com sdk.launchdarkly.com app.launchdarkly.com events.launchdarkly.com mobile.launchdarkly.com

On 5/12/2023 at 4:05 PM, Topfox said:

@Darin, C4 PM UI Im in the US on the East Coast, and when I search for the app in the Amazon App store app, it doesn't find anything.  Should I be seeing it? Am I just an idiot a and not doing it correctly?

I did go download the APK from someplace else though and side loaded it.  I still have the same issue in that I can bring up my cameras and see all the thumbnails, but if I select a camera to try to make it bigger it basically crashes and returns me back to the thumbnail view.  Although I will say the crash and return seems to be better in this latest version than it was in the previous 2 versions of the apk.

I would expect that anyone in the US should be able to find it when searching, but I'm not 100% on all the details for how Amazon & Microsoft do there distribution.  I know that in the Amazon app store developer console, it shows that our app is approved for distribution to Windows 11 devices and I'm able to find it by just searching for Control4 within the Amazon Appstore.