Darin, PM C4 CX Platform

The Control4 for OS 3 app has officially been released through the Amazon app store on Windows Subsystem for Android. Note that the Microsoft and Amazon haven't rolled out support to all countries and regions yet, but as they do this will become available to you. Here is their current list of Countries and regions that support Amazon Appstore on Windows. https://support.microsoft.com/en-us/windows/countries-and-regions-that-support-amazon-appstore-on-windows-d8dd17c7-5994-4187-9527-ddb076f9493e

Are you using Google Chrome? I ran into this the other day and Firefox worked perfectly, but Chrome was having issues. I think the latest versions of Chrome may have created some kind of incompatibility.

Yes, the phone needs to be logged into the project to complete setup and adding a Halo remote through an iPad or Android tablet will be supported. No plans to support this from the T3/T4 at the time.

I just tracked down that bug Jonathan wrote up for the volume slider (CI-20790) and that fix is included in iOS version 322.29. This build just went to beta last Thursday and is scheduled for release to production on August 9th. If you would like to join the iOS beta to test things early and provide feedback on whether it resolves your issue you can do so using the link below. https://testflight.apple.com/join/bI6oH4Gu

If you use the latest version of Android Subsystem then you shouldn't need 4Sight. They fixed things so that now the Android emulator has access to the local network.

The latest Windows Insider versions of Android Subsystem have fixes for networking that will likely resolve your issues. I have it installed on my PC and it is working well, we have plans to support the OS 3 app on Windows 11 once Amazon/Microsoft are our of their public beta and our app can be downloaded directly from the Amazon app store, but for now we aren't making any specific app changes to address Windows 11 issues since the Android Subsystem still appears to be under development. https://blogs.windows.com/windows-insider/2022/05/20/update-to-windows-subsystem-for-android-on-windows-11/ https://blogs.windows.com/windows-insider/2022/07/06/update-to-windows-subsystem-for-android-on-windows-11-july-2022/

@DIEHARD / @daveva, v117 of the Alexa driver has been installed on both of your systems for testing. Let me know if this resolves the issue for you.

@DIEHARD / @daveva, Team found a caching issue and will have it fixed in v117. Are you both fine with me installing it on your systems to make sure it fixes your issues with scene add/remove/rename not working before release to production?

@DIEHARD / @daveva I DM'd you both for additional info, so I can have your issues looked into.

The driver team was able to confirm v115's fixes quickly thanks to help from @SHPRemote so the release of v114 was skipped and v115 has now officially been released to production. Everyone should get the update in the next 24-48 hours. @DIEHARD Let me know if this resolves everything with your HDMI Matrix once you get the update.

@DIEHARD Team believes they tracked down and resolved your issue it will go out with v114 soon. @SHPRemote They also believe they have tracked down your issue and will release that in v115 once tested and ready.

@DIEHARD The Alexa driver team let me know they verified the issue you reported and are working on a fix for it. Thanks again for the detailed write up.

@Don Cohen Happy to help where I can.

@DIEHARD Thanks for the detailed write up. I've passed this along both your posts to the Alexa driver team to investigate the HDMI Matrix further. I'll let you know when I hear back from them.

Alexa driver v113 has been officially released, anyone with Composer Pro access can go update the driver now. Everyone else your systems should automatically update to this version in the next 24-48 hours. It should resolve the following issues: discovery not working on OS 2.9.1 systems av source discovery not working for sources distributed through a matrix switch DVD proxy source discovery not working

@DRP Yes, once I know it has been officially released I'll let you guys know.

Alexa driver v113 is in testing now with fixes for the 3 issues mentioned in this thread, so we should have those fixes pushed out to you guys soon.

DVD proxy issue was confirmed and they are working to fix it now.

Due to Amazon's new requirements, v112 was force updated on all systems to make sure they keep working with Amazon's servers going forward. The team will be swarming around these 3 issues since they slipped into production, so I expect they should have fixes pushed out of all of them relatively soon. I'll try to keep track of things so I can provide you guys with some updates on where things are at, but like I said not my expertise so you may need to remind me to check for you. These won't mean anything to you, but they'll help me track things down to keep you guys updated. DRIV-7915 DRIV-7920 DRIV-7921

This is not my area of expertise, but the PM and engineers that would don't have C4Forums accounts so I'll pass along what they said.

We were able to get @dw886's issue resolved specific to Android, but @slash007 your issue is likely different. Let me know what OS version you are on and if your a dealer or end-customer, so I can think through the best way to get your system logs to have this looked into further.

Sounds like your a dealer if you have a showroom. I'll DM you my email and we can loop in the correct engineers to help figure out what's happening. I'm assuming that you both (@dw886 / @slash007) are running latest or near latest OS? Either 3.2.4 or 3.3.0 with the latest driver updates as well?

This issue wouldn't be due to the Stealth Mode feature as that is only available and used by iOS. It sounds like either something with how audio is transmitted broke entirely or the DS2 hardware failed. I'd need a full set of system logs retrieved by your dealer to have someone look into what is happening.

Yes, this is available in the Intercom Anywhere experience inside the OS 3 app.

+1 for Rachio