Jonathan, C4 Engineer

This is a database upgrade issue within the app. It doesn't happen often and depending on your app that's installed and what you might be installing over it there can occur some conflict in the upgrade or change. Simplest fix is to delete the app and install it again.

This is in our pipeline to be fixed and the current state is fixing. This means it will be included in either this coming beta release or the next one. The engineer is currently unavailable so I don't have a more precise date at the moment.

Those who have duplicated the issue. Can you provide the following to assist us with troubleshooting? Interface Device: Android/T3/T4/iOS Director Version: Mobile App Version (if applicable): Also if you can confirm if it's not working for all interfaces you have not just T3/T4s if that's where it occurs? Meaning if it's reproducible on a T3 is it also reproducible on Android or iPhone.

Thanks for reporting this. I'll get a bug written up on it and I'll reach out to you @Topfox with some additional information gather for the team to troubleshoot.

For those of you who are seeing the loading progress instead of the spinner we are using this as a way to show a feature we added to help with users who were experiencing timeouts while trying to connect to their system. In the Preferences section there is a toggle in Advanced that says Extended Sync. When on this just makes the connection process have a longer time to try and connect and sync. When that feature is on the app will show the progress bar to indicate a sync is happening with the project not just a connect to the project. Sync's can take much more time especially if you have a large project. What appears to be a revert in the code is actually reusing some old visual behavior to specifically indicate what's happening when connecting. Sync or just connect. The underlying code wasn't reverted. However some changes can affect your experience in unintended ways. Once you feel you have an issue be sure to report it in the Troubleshoot board to make sure we get visibility on outstanding issues. Not all of the devs will dig through this post looking for latest comments on the releases.

Send me a DM and I'll get a help ticket created for your issue.

I believe the version with the fix is going to be 322.21. Once you get this version please let me know if this continues to be a problem for you.

What app version are you using? We have fixed a recent issue with getting some icons. Would be good to know if there's something different in your setup that we didn't have on our test systems

Yes this isn't a sync or setting issue. We had a small issue with displaying celsius. We fixed this already and you should be seeing this fixed in the next Test Flight build

We do have a minimum OS version requirement to be able to utilize all of the new network speed and connection improvements. Which is 3.2.4

This is as designed. We try to locate the controller on the network using using a broadcast protocol however this doesn’t work over subnets. When we can’t find the controller we then rely on a web service call that requires a 4sight license. If you connect once on the subnet and we discover the option we save it for further use

Delete the app and reinstall it. Sorry for the inconvenience. Resetting the app doesn't actually remove the database. It just clears it out. Deleting the app and reinstalling it will fix that migration problem.

Forwarded to Android team to create an issue to look into it.

Are you referring to the IA standalone app or the intercom feature within the OS3 Home app? We are aware of some of the intercom issues currently experienced by some users I just want to gather some more specific information about your feedback. - Thanks

Ok I understand now. So this is something we're aware of and working to resolve.

There are a few things that could mean. Are you talking about about the time it takes to open the app from getting a notification? It you could be referring to the call speed of video and audio while in the call? Depending on what you are referring to the answer is maybe. I know that's not too helpful but intercom calls and the process for notifications and answering calls is a different communication path than logging in and using your home. Our focus was on the latter. The path to communicate with the controller and main features of the app were the main focus of this last release. But rest assured we understand the needs to make intercom work as fast as possible and we are always working to improve that process as well.

Your controller needs to be updated. It needs to be on 3.24 and above.

Can you send me a direct message with your contact information and I'll get a bug created for your camera issue?

Please do. We'd be happy to take a look and get it working again for you!

Yep an overhaul to the connectivity code was released. You should be seeing significant improvement with connection speeds. Update in App Store ASAP

When you say viewed in the C4 UI what does that mean exactly? T3, T4, Android/iOS.

As a mobile dev that works for Snap One (Control4) one of the duties we perform is to look on the forums for issues being reported on the mobile platform. If you would like your issue to be noticed you can help out by creating your title in a manner that helps us identify the post as one that's in need of some help/troubleshooting for the mobile apps. The posts that catch our eye are ones that are in the Troubleshooting and bugs discussion board. I propose you start your title first with the platform you're having an issue with then the feature or component that doesn't seem to be working correctly. Example Titles iOS: Intercom not working on ..... iOS: Camera does not stream when (remote/local) etc Android: Now Playing doesn't..... Another thing we will always ask you when trying to support you is what is your director version and app version. It's helpful if you can already include that in the description of your post along with the steps you follow to cause the issue. Once we see your post we'll reach out to let you know we are creating a ticket and ask you to PM your email so we can work with you directly on the issue. We would also most likely ask for your application logs at this point in the direct communcation. So recap Post in Troubleshooting/Bugs Include Platform(iOS/Android/etc) in the title along with feature or component that is the issue Include app and director version in the body as well as the steps your following to produce the issue

As a mobile dev that works for Snap One (Control4) one of the duties we perform is to look on the forums for issues being reported on the mobile platform. If you would like your issue to be noticed you can help out by creating your title in a manner that helps us identify the post as one that's in need of some help/troubleshooting for the mobile apps. The posts that catch our eye are ones that are in the Troubleshooting and bugs discussion board. I propose you start your title first with the platform you're having an issue with then the feature or component that doesn't seem to be working correctly. Example Titles iOS: Intercom not working on ..... iOS: Camera does not stream when (remote/local) etc Android: Now Playing doesn't..... Another thing we will always ask you when trying to support you is what is your director version and app version. It's helpful if you can already include that in the description of your post along with the steps you follow to cause the issue. Once we see your post we'll reach out to let you know we are creating a ticket and ask you to PM your email so we can work with you directly on the issue. We would also most likely ask for your application logs at this point in the direct communcation. So recap Post in Troubleshooting/Bugs Include Platform(iOS/Android/etc) in the title along with feature or component that is the issue Include app and director version in the body as well as the steps your following to produce the issue

As a mobile dev that works for Snap One (Control4) one of the duties we perform is to look on the forums for issues being reported on the mobile platform. If you would like your issue to be noticed you can help out by creating your title in a manner that helps us identify the post as one that's in need of some help/troubleshooting for the mobile apps. The posts that catch our eye are ones that are in the Troubleshooting and bugs discussion board. I propose you start your title first with the platform you're having an issue with then the feature or component that doesn't seem to be working correctly. Example Titles iOS: Intercom not working on ..... iOS: Camera does not stream when (remote/local) etc Android: Now Playing doesn't..... Another thing we will always ask you when trying to support you is what is your director version and app version. It's helpful if you can already include that in the description of your post along with the steps you follow to cause the issue. Once we see your post we'll reach out to let you know we are creating a ticket and ask you to PM your email so we can work with you directly on the issue. We would also most likely ask for your application logs at this point in the direct communcation. So recap Post in Troubleshooting/Bugs Include Platform(iOS/Android/etc) in the title along with feature or component that is the issue Include app and director version in the body as well as the steps your following to produce the issue

I can create a ticket for you if you like for the devs to take a look at your issue. You can PM me directly. Include your email, what version of director and the iOS app you're using in the message. Also include what iPhone model you're using since you indicated it's a specific issue to your device.