This_is_the_fun_stuff Posted June 3, 2020 Share Posted June 3, 2020 We’ve been getting a single keypad chime every 3 minutes from our interlogix concord4 panels when the system is disarmed in ready mode. I’ve been researching with our monitoring company but when they reached out to interlogix for support, they indicated a recent Control4 update may have led to this. Has anyone encountered this and have any additional information? Also wondering if there’s a log I can check to see if any controller or driver updates have been pushed. This started on the morning of 6/1. My next step is to disconnect the superbus automation module to see if I can isolate it to the module/control 4 but thought I’d see if anyone had any information before I go down that path. Quote Link to comment Share on other sites More sharing options...
dzagha Posted June 4, 2020 Share Posted June 4, 2020 I am having the same issue. Started a couple of days after the latest upgrade. I disconnected the power to the superbus and removed it from the alarm system and the beeping has stopped. Quote Link to comment Share on other sites More sharing options...
mikeryder Posted June 4, 2020 Share Posted June 4, 2020 I am getting the same behavior (tone every 3 mins). I use Control4 95% of the time to arm/disarm my alarm system, so it isn't a great option for me to disconnect Control4. We called Interlogix tech support who said a lot of people with Control4 have called reporting the same issue. I haven't made any changes to the alarm system or Control4 in the past several weeks. I am running Control4 v3.1.2, SuperBus 2000 RS-232 driver v111, Concord4 Security Panel. @dzagha A couple days after which upgrade? Quote Link to comment Share on other sites More sharing options...
dzagha Posted June 4, 2020 Share Posted June 4, 2020 I am running 3.1.3 and it started just after midnight eastern time Monday. Quote Link to comment Share on other sites More sharing options...
mikeryder Posted June 4, 2020 Share Posted June 4, 2020 I think mine started overnight from 6/2 to 6/3. I am running 3.1.2 and you are running 3.1.3. The driver in Control4 for the alarm connection was last updated in November and I have had it on my system for months, so I doubt that is the issue. I have Alarm.com for monitoring. You? I'm just searching for similarities. Quote Link to comment Share on other sites More sharing options...
dzagha Posted June 4, 2020 Share Posted June 4, 2020 I have had it set up for over a year with no issues. I also have Alarm.com. How is the superbus connected to your controller? Mine is using a Global Cache iTach IP2SL. Quote Link to comment Share on other sites More sharing options...
lippavisual Posted June 4, 2020 Share Posted June 4, 2020 What info is the panel providing? Do any of you have Composer HE? The issues I usually see and have heard with Concord panels is that it shows a Ground Fault, leading to the beeping. This is the ground connection between the alarm panel and C4 controller over the RS232 cable. Quote Link to comment Share on other sites More sharing options...
dzagha Posted June 4, 2020 Share Posted June 4, 2020 The panel is showing SYSTEM OK, my alarm company said all was fine with the system and that it looked like control4 was sending a signal to the panel. Definitely not a ground fault issue. Quote Link to comment Share on other sites More sharing options...
This_is_the_fun_stuff Posted June 4, 2020 Author Share Posted June 4, 2020 I use a different monitoring company. No events show on the keypad or in the panel event history when this occurs. If the system is in ready status, it’s just the single tone but it reoccurs every 3 mins. If it’s armed, the tone happens once and also asks for code to be entered, then doesn’t happen again. We are also heavy users of arming and disarming via C4 and would rather not disconnect the automation. I’ve been leaving a less vulnerable zone open when we are disarmed to avoid the beeping. So far I’ve tried resync’ing the driver to the controller and rebooting the controller to no avail. I also removed a couple c4 zones that are no longer on the panel, but have never been an issue. Rebooted again, but still have the beep. I also use an ip2sl for C4 serial connectivity. Quote Link to comment Share on other sites More sharing options...
This_is_the_fun_stuff Posted June 4, 2020 Author Share Posted June 4, 2020 I was able to set a debug log on the superbus driver and this seems to be what's happening when the beep occurs: Resync flag set. Do a resync now... TimeDate:SetTimeDate 2020.06.04 14:15:03 Received ACK OnTimeDateTimer Not in programming mode yet TimeDate Retries Exceeded Received ACK Every few seconds in ready mode, it throws the below message about the Panel date and system date. Then looks to be hitting an issue with retrying to many times. Panel reported date doesn't match system date. Trigger a Resync... Attaching a bigger set of the log. The line "!!!!!! Zone 3 CLOSED !!!!!!" is where I closed the open zone and it went to ready mode. c4_superbus_log.txt Quote Link to comment Share on other sites More sharing options...
mikeryder Posted June 4, 2020 Share Posted June 4, 2020 I enabled logging and confirmed the same messages you are seeing when the beep occurs: HandleMessage(): FromSerialCommand[SirenSynchronize], FromSerialData[] Resync flag set. Do a resync now... TimeDate:SetTimeDate 2020.06.04 17:15:19 Received ACK OnTimeDateTimer Not in programming mode yet TimeDate Retries Exceeded Received ACK HandleMessage(): FromSerialCommand[SirenSetup], FromSerialData[?] Quote Link to comment Share on other sites More sharing options...
mikeryder Posted June 4, 2020 Share Posted June 4, 2020 We need somebody with a normally functioning (non-beeping) Interlogix Superbus to compare logs to. Quote Link to comment Share on other sites More sharing options...
This_is_the_fun_stuff Posted June 4, 2020 Author Share Posted June 4, 2020 So I made 2 changes and have been beepless for the last 30 mins. Finger crossed that it holds. There's a setting in the driver.xml for the superbus driver called <can_set_time>true</can_set_time>. I updated this to false, updated the driver and rebooted the controller a couple times. This by itself didn't seem to address the issue. In the composer driver settings, I updated the partition 1 "default user code" to blank and hit "set". Not sure why I had a code in there, I use quick arm and enter a code to disarm. After that setting change, I have not had any additional beeps. Fingers crossed and hopefully this helps others. Quote Link to comment Share on other sites More sharing options...
dzagha Posted June 5, 2020 Share Posted June 5, 2020 Are either of you running Homebridge by any chance? There was also a TVOS update around the same time. Quote Link to comment Share on other sites More sharing options...
This_is_the_fun_stuff Posted June 5, 2020 Author Share Posted June 5, 2020 no Homebridge for me. Quote Link to comment Share on other sites More sharing options...
dzagha Posted June 5, 2020 Share Posted June 5, 2020 Thank you, that narrows things down a bit. Quote Link to comment Share on other sites More sharing options...
mikeryder Posted June 5, 2020 Share Posted June 5, 2020 I don't have Homebridge either. Quote Link to comment Share on other sites More sharing options...
l3anks Posted June 9, 2020 Share Posted June 9, 2020 Same issue here running 3.1.3. C4 is attempting to set the date and time every few minutes and is causing the annoying beeps. There are times where it stops beeping for hours and other times every minute. Logs show "Panel reported date doesn't match system date. Trigger a Resync..." I have a the user code set and use that functionality. I'm also running homebridge Quote Link to comment Share on other sites More sharing options...
l3anks Posted June 9, 2020 Share Posted June 9, 2020 Just noticed a new version of this driver is now available: 114 Upgraded ... so far so good Quote Link to comment Share on other sites More sharing options...
This_is_the_fun_stuff Posted June 9, 2020 Author Share Posted June 9, 2020 Good find. I’ll update my driver tonight. Based on the change log it looks like the issue was something related to dates in June and July which lines up with the timing of my issue. Thanks! Version 114 Fix a date/time bug that shows up in June and July. Quote Link to comment Share on other sites More sharing options...
l3anks Posted June 10, 2020 Share Posted June 10, 2020 Has been 8+ hours and no chime. Driver update seems good and resolved the issue Quote Link to comment Share on other sites More sharing options...
dzagha Posted June 11, 2020 Share Posted June 11, 2020 Last night I had one beep at midnight but nothing since. Anyone else? Quote Link to comment Share on other sites More sharing options...
mikeryder Posted June 12, 2020 Share Posted June 12, 2020 I updated the driver and haven't heard a beep since. Quote Link to comment Share on other sites More sharing options...
dzagha Posted June 12, 2020 Share Posted June 12, 2020 It beeped again at midnight, I may try deleting the driver and starting from scratch. Quote Link to comment Share on other sites More sharing options...
Jonathan Lee Posted June 13, 2020 Share Posted June 13, 2020 How can I update my driver with Composer HE v3.1.3? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.