jakblak

Hey @bdo21,

See my responses below.

On 2/21/2020 at 9:30 AM, bdo21 said:

 

1) Intercom Anywhere overrides the iPhone silent switch. My wife in particular is not going to enable do not disturb mode in the Intercom App each time she wants the phone to be silent at work. Can intercom anywhere not override the silent iPhone function?

In order to allow the app to show early media (the ability to show who's at the front door without actually answering the call) we were not able to leverage Apple's CallKit functionality.  CallKit allows developers to integrate with the native iOS telephony mechanism that gives customers the ability to silent incoming calls (both cellular and voip).  In addition, Apple doesn't expose an API to determine if the phone's silent switch is on/off.  This is clearly a sub-optimal customer experience, so the solution that is built into the app today is that you can select the "Silent" ringtone in the app settings or you can put the app in DnD (also in the app settings).  Once a call comes in, you can either deep-press on the notification or swipe to ignore or answer the call.  

With that being said, this is the biggest complaint we get regarding Intercom Anywhere and will be changing in the next version.  The app will support CallKit and incoming intercom calls will be treated just like a regular phone call and will honor the phone's DnD state and silent switch.  Sorry for the delay, but it is coming.

 

2) Can intercom anywhere only ring mobiles depending on other variables? If the alarm is armed, I want it to ring the mobiles but if someone is home (so the alarm is not armed), it doesn’t need to ring any mobiles

I'll lump 2 and 3 together since they're essentially the same question.  Can I, either not deliver calls or cancel calls based on programming and system state?  The way things work now is that if there is programming associated with a DS2 button press, then the comm server will not send out a call to the mobile devices.  This is a great suggestion and one that I believe could provide a lot of value to customers.  I'll create a ticket and submit it to the product manager.

 

3) Can intercom anywhere stop ringing after a trigger event? If someone opens the front door (which the alarm contact can show), the touch panels and mobiles can stop ringing. I know they stop ringing if someone answers but if we are near the front door, we are not going to answer on the intercom first before opening the door

See response to #2

 

22 hours ago, timelinex said:

Android app has not been updated and I still haven't heard back from Jak, after messaging him a few times for an update.

I will be trying to put a POE extender around the middle of the run to improve my connection. But disappointed in the lack of update on the app, especially after a bug was confirmed that made the app completely unusable.

Sorry guys, I have been on vacation for the past couple of weeks and I'm just catching up now.  I'll talk with the Android engineer and see what the status is of this bug

Edit: Looks like this has been fixed and is slated for release in the next 2-3 weeks

20 hours ago, Anish said:

Just updated to iOS 13.2 and latest rendition of c4 app. My 4sight is appreciably faster. 15 seconds to ready. Intranet still about 2-3 seconds 

@jakblak  thanks - you’ve produced the goods...

Thanks @Anish but I can't take any of the credit, it was my team that made the speed improvements and bug fixes.  While we have made progress, there is still work to be done both within the app and within our infrastructure and services to increase speed even more .  These additional changes are in progress but will take a little while to roll out since they require work and coordination between multiple teams.

16 hours ago, SMHarman said:

Know anymore. Enquiring minds and all that.

Sent from my E6603 using Tapatalk
 

We have quite a few performance metrics inside of the OS3 app and one of those is cold-start time while remote (i.e. not on your local network) and the connection times in some regions, as many of you have experienced, is sub-optimal and outside of the range we feel is acceptable.  Obviously connection times are a YMMV type of thing that depends heavily on your home internet speed, size of your project, cellular signal, etc... but we definitely see connection times in these regions that fall outside of what is "normal".

While we are striving for faster connection times both locally and remote, our attention is fully focused on the customers in these regions where the connection times are higher than what the majority of our customers are experiencing.  As such, we have formed a cross-functional team to address the problem at a team level as well as holistically.

It will take us some time to make these changes and roll them out, but I wanted to let everybody know that we understand the difficulty and the frustration and we are committed to fixing it.

On 9/30/2019 at 7:58 AM, LollerAgent said:

I have found that while the newest app is MUCH quicker than the original OS3 app (both locally and remotely), it sometimes fails to connect when not launching freshly.  The fix is usually to kill the app and re-launch it.. which results in a 1-2second connection most times.

I have now received several reports about this and have received logs from @Anish (thanks btw), and I have an engineer looking into the problem as I'm typing this.  I will create a post (or update here) when we figure out, and fix the issue.

8 hours ago, Anish said:

I did. He’s on it as we speak. Thanks Jakblak

Not a problem, I'm always happy to help.  The development team is working through the issue with the web services team.  I'll post here when I know more

23 hours ago, Anish said:

After upgrading to os3 my 4 sight takes about 20 seconds bring up my splash screen and takes a few more seconds to populate the rooms.  Even after upgrading to os 13.1. Works superfast intranet - it’s just on 4sight that’s the problem 
 

Hi @Anish, if you're interested I'd be happy to have my team take a look at your app logs to see if we can diagnose why your connection times are slow.  

6 hours ago, EverAction said:

Definitely appreciate these updates. I was worried the 2.10 app would be forgotten. The bugs I noticed is the Listen app icon not showing, the app not readjusting from Portrait, to Landscape, to Portrait again. And if you set the passcode on the App and lock it with TouchID, after a day or so when you go to the app it insta-crashes. Deleting the app and re-adding the system without setting a passcode with TouchID fixes the issue. So I've just left the passcode off for now.

A new version of the 2.10 beta app is out and it has the fix for crashing at startup when using biometrics (TouchID/FaceID).  If you've already downloaded TestFlight you'll be notified of the new build, if not, then you can use this following link (it's the same one from my previous post).

https://testflight.apple.com/join/EtAiX35m

49 minutes ago, pinkoos said:

Since we have your ear, any way to get my remote working again with TvOS 13 and OS 2.0/Director 2.9?

 

Hi @pinkoos, unfortunately @EverAction is correct here.  We were not informed by Apple ahead of time that they would be making changes that would prevent the old IP driver from working .  You could of course always use the IR driver or if that's not feasible because of having to run IR buds or other reasons, there is the officially supported IP driver.

44 minutes ago, EverAction said:

Definitely appreciate these updates. I was worried the 2.10 app would be forgotten. The bugs I noticed is the Listen app icon not showing, the app not readjusting from Portrait, to Landscape, to Portrait again. And if you set the passcode on the App and lock it with TouchID, after a day or so when you go to the app it insta-crashes. Deleting the app and re-adding the system without setting a passcode with TouchID fixes the issue. So I've just left the passcode off for now.

Hi @EverAction, thanks for the feedback.  The bug with some of the icons missing is actually a bug in iOS that is fixed in 13.1.  In regards to the passcode/TouchID crash, I'll get my team on it and we'll get another build out and I'll post it here

Well, it took much longer than expected but the updated 2.10 app finally made it through the beta approval process.  You can access the beta version of the 2.10 app by clicking the link below and following the instructions to download TestFlight and install the app.  This version specifically addresses UI problems when rotating the app.  If there are other problems, please feel free to send me a PM, post here, or give feedback via TestFlight.

Thanks everyone

https://testflight.apple.com/join/EtAiX35m

Hi all, iOS 13 did cause some problems for the 2.10.x version of the Control4 app.  As many of you have seen, iOS 13.1 fixed the problem with the missing icons but other issues remain.  The development team has fixed those issues and we have submitted a new version of the app for beta review.  Once the app has been approved for beta testing I will post a download link in this thread.

Thanks for everyone's patience

5 hours ago, GSC4Home said:

What happened to the "Dedicated Mode"?  I had that on an iPad in an iPort on the wall.  Since the upgrade I have to launch the application every time I want to use C4.  I liked dedicated mode.  I don't need the iPad features.  I just want to be able to use the Navigator.

Hi @GSC4Home,

As we were evaluating the 3.0 development timeline there were certain features that had to be cut to ensure that critical functionality and overall quality was baked into our initial release.  Unfortunately, "Dedicated Mode" was one of those features.  Nobody likes when features are cut, including ourselves, but we felt that with the option to enable "Guided Access" (Enable Guided Access) on an iPad that our time would be better spent adding critical features that iOS doesn't provide by default.

With that said, we're always sensitive to customer requests and if this is a highly-desired feature relative to other requests it may make a return.

That’s good to know, glad you got it working.  As an FYI for those of you using the Intercom Anywhere app you can double-tap the call timer on iOS (or long-press on Android) to see advanced call stats including packet loss percentage and call quality stats.

Either way, here's an updated driver.  It should work identically to the ST9 driver.  Try sending the commands I posted above and if you get the correct output then everything should work. 

receiver_HT-NT3_Network_DriverWorks__Sony.c4z

@Cartnj: Try typing the following commands.

gSystemVolumeDisplay = "STEP"
local tParams  = {LEVEL="80", OUTPUT=1000}
PRX_CMD.SET_VOLUME_LEVEL(1000, tParams)

If you have the right driver, it should result in the following output

ProcessVolumeLevel(level in=80, level out=40)
PRX_CMD.SET_VOLUME_LEVEL(), volumeLevel_Step = 40

I’ll check it out a little later tonight @Cartnj

@timelinex, I wrote the Intercom Anywhere app for iOS and work closely with the engineer that wrote it for Android and I'm sure he'd be interested in this problem.  Would you mind clearing the logs within the Intercom Anywhere app, reproducing the problem, then gathering the logs and sending them to me in a PM?   We may not be able to fix it, but we might be able to point you in the right direction.

@dinom and @Cartnj the updated drivers are attached.  For whatever reason the documentation has been lost when I converted them from C4I to C4Z files (Sorry, I haven't written drivers for a few years).  I'll pass the updated Lua code along to the driver team and hopefully they can put out an official fix.

receiver_HT-ST9_Network_DriverWorks__Sony.c4zreceiver_HT-NT3_Network_DriverWorks__Sony.c4z

Thanks guys, I'll update both of them 

OK great, this will be easy to fix.  I'll create a new driver with the changes to get it working and I'll attach it to this post when I get done.  Look for it in the next day or two.  Thanks @dinom and @Cartnj

@Cartnj Did that result in the UI showing 80 and the sound bar showing 40?

Sorry, had a bad variable name in that one before last

Ok @Cartnj, last one.

gSystemVolumeDisplay = "STEP"
local output = 0
local volumeLevel_Step = 80
local minDeviceLevel = 0
local maxDeviceLevel = 50
local volumeLevel_Conv = ConvertVolumeToDevice(volumeLevel_Step, minDeviceLevel, maxDeviceLevel)
tVolumeSetCommandMap_Step[output].value = volumeLevel_Conv
command = tVolumeSetCommandMap_Step[output]
QueueCommand(command)

Wrong snippet

@Cartnj: will you try changing the value of volumeLevel_Step to something under 50 and try again?