C4 Lover Posted August 28, 2016 Share Posted August 28, 2016 You assume wrong - it works fine on the Concord4, though I cannot speak for others. You can no longer program 'key presses' as you once could - and yes you would create a separate user and code - those credentials then get entered under the appropriate partition(s) and you can programmatically disarm. Arming also assumes it will not require a code to arm. Hi Cyknight - your comment about the new driver not allowing individual key presses drums up a question. When I leave my house I programmed ARM TO STAY + 4. The 4 adds "NO DELAY" when a sensor is opened. Does the new driver allow for this? Sent from my iPhone using Tapatalk Quote Link to comment Share on other sites More sharing options...
Cyknight Posted August 28, 2016 Share Posted August 28, 2016 No, I'd have to check to be sure, but most of these sort of functions are replaced with alternate methods. Quote Link to comment Share on other sites More sharing options...
C4 Lover Posted August 28, 2016 Share Posted August 28, 2016 That would be great if you could check as I will not order a new board if it can't be done. The "no delay" is a critical component of my alarm for obvious reasons. Sent from my iPhone using Tapatalk Quote Link to comment Share on other sites More sharing options...
Cyknight Posted August 28, 2016 Share Posted August 28, 2016 There are separate commands for no-delay arming to stay and away in the driver. Quote Link to comment Share on other sites More sharing options...
C4 Lover Posted August 28, 2016 Share Posted August 28, 2016 There are separate commands for no-delay arming to stay and away in the driver. That's is great - thanks so much for taking the time to confirm!!! Sent from my iPhone using Tapatalk Quote Link to comment Share on other sites More sharing options...
Cyknight Posted August 28, 2016 Share Posted August 28, 2016 No prob - I have it in my own system, just needed a moment to connect and look Quote Link to comment Share on other sites More sharing options...
drmark12pa Posted September 14, 2016 Share Posted September 14, 2016 I've just added 2 window sensors to my system (GE Concord 4 with EA5 primary controller on most up to date software). However, I am unable to get the 2 new sensors to be recognized by C4. I've tried going into Composer (as has my dealer remotely) and going under the PROPERITES and hitting the READ PANEL to pull them into the system but they still don't show up. All of my other sensors do show up. Any suggestions on how to get the C4 to recognize these sensors which are 100% working with my security system just not showing up in C4. Quote Link to comment Share on other sites More sharing options...
d1amund Posted September 14, 2016 Share Posted September 14, 2016 ^ Make note of which driver you are using and the connection to the serial port in Composer. Delete the security driver from the project. Re-add the driver and re-make the connection in composer with the appropriate serial port. Quote Link to comment Share on other sites More sharing options...
drmark12pa Posted September 14, 2016 Share Posted September 14, 2016 10 minutes ago, d1amund said: ^ Make note of which driver you are using and the connection to the serial port in Composer. Delete the security driver from the project. Re-add the driver and re-make the connection in composer with the appropriate serial port. I don't believe I have the ability to delete a driver as I only have Composer consumer edition. Is there any other way of making the C4 system read the panel? The sensors are definitely programmed in and work but for some reason C4 doesn't see them in the project. However, something that is strange is that my Android C4 program does show them as Unknown Zones #33 and #34 which correctly corresponds to their learned sensor numbers. They do no show up anywhere in Composer..... Quote Link to comment Share on other sites More sharing options...
d1amund Posted September 14, 2016 Share Posted September 14, 2016 Thanks for clarifying, I assumed you meant Composer Pro. Have your dealer log in and do it. Quote Link to comment Share on other sites More sharing options...
drmark12pa Posted September 21, 2016 Share Posted September 21, 2016 So after wrestling with multiple issues with the new Interlogix driver for my Concord4 (couldn't get 2 additional sensors added, old keyfabs couldn't be used to trigger events for the * or the LIGHTBULB button with the new driver), my dealer finally put the old driver back in...... everything working perfectly now it would appear. So, what is the benefit really to the new driver? I didn't see much difference other than the sleek appearance on the on screen interface. Functionality seemed diminished in my case with the loss of keyfab usage and then the trouble I was having adding 2 more sensors. Quote Link to comment Share on other sites More sharing options...
drmark12pa Posted September 21, 2016 Share Posted September 21, 2016 One thing in going back to the previous driver, I appear to now be missing the ability to send a notice to specifically indicate which sensor is being triggered. I've tried to text myself the 6 variables listed under Security->Device variables which are HOME_STATE, AWAY_STATE,DIARMED_STATE,ALARM_STATE, DISPLAY_TEXT, TROUBLE_TEXT. I thought the DISPLAY TEXT was the one I used before but when I send myself both text and PUSH notification it's blank. I've tried every combo of PRESSING "*" on security with and without a delay but cannot seem to figure out a way to send what is on the security panel display to myself via text or push alert. Quote Link to comment Share on other sites More sharing options...
C4 Lover Posted October 8, 2016 Share Posted October 8, 2016 On September 21, 2016 at 5:12 PM, drmark12pa said: One thing in going back to the previous driver, I appear to now be missing the ability to send a notice to specifically indicate which sensor is being triggered. I've tried to text myself the 6 variables listed under Security->Device variables which are HOME_STATE, AWAY_STATE,DIARMED_STATE,ALARM_STATE, DISPLAY_TEXT, TROUBLE_TEXT. I thought the DISPLAY TEXT was the one I used before but when I send myself both text and PUSH notification it's blank. I've tried every combo of PRESSING "*" on security with and without a delay but cannot seem to figure out a way to send what is on the security panel display to myself via text or push alert. I am on an older board and have ordered a new one to take advantage of the new interface. In discussions with CyKnight it seems I should be fine but in reading drmark12pa I am wondering if I should leave well enough alone. Can anyone on the thread give me advice on if I am doing the right thing. My alarm is a central part of my C4 setup. The new interface and additional reporting with the most current board and driver is appealing but not if I might lose other functions. Any others who upgraded have a positive or negative experience? Please do share. Quote Link to comment Share on other sites More sharing options...
Cyknight Posted October 8, 2016 Share Posted October 8, 2016 In the end it will depend on what you use now. A few options are 'lost' in that direct programming is not available. This in particular pertains to the loss of the ability to send keypad number presses in programming, and direct programming based on keyfob buttons. That said, you get most functions you'd use numbers for back in direct button presses, and while direct keyfob presses are gone - this can still be done via the security panel itself (program the panel to trigger an output based on the keyfob press, sense that output and program from there, or if you used keyfobs to d specific tasks on arm/disram by that 'user' - you assign a keyfob to a user, and program directly fro the user arming/disarming. There's no doubt the new driver works differently, and if you are very used to and comfortable with programming the old driver - you may experience the 'move' as a loss of function. On the other hand, it has a much nicer interface, you gain a lot of options of using states and events you didn't have before both for events and actions, plus direct viewing of open zones in the GUI within the security interface and zone open/closure and alarm state history as well. Whether you prefer one or the other is up to you. Quote Link to comment Share on other sites More sharing options...
C4 Lover Posted October 8, 2016 Share Posted October 8, 2016 Cyknight - you seem to be on top of your game with the Concord 4. I have had it for 5 years but the reason I am even considering the move to the new board are a few strange problems. Will the new board fix them? Who knows but I wonder if you have seen these issues to determine if they would be corrected in the latest driver. 1. I include the disarm codes in my program to automate door locks, lighting scenes, set HVAC, etc. when I enter and exit my house using a NYCE keyfob. The key is that MOST of these events fire off ONLY once the alarm is DISARMED. The strange thing is that about 20% of the time, the ALARM will NOT disarm yet all of the downstream programming as a result of the command to "disarm" fires off flawlessly every time. How could this be? Attached is a graphic of what my touch screen shows when I run into this problem. Check out how it shows ARMED yet on the right it shows the wrong information. As you know, it should say AWAY NO DELAY or STAY NO DELAY. The text you see there shows up only when the left side text shows DISARMED. To correct this I simply have to DISARM the system again and it corrects itself. Is this a driver issue? I am on the EA-5 and it only cropped up when I moved from the HC800 to the EA-5. I have tried every combination of pauses in-between the entry of the DISARM command and my 4 digit code. 2. When I look at the serial debug mode, every so often I see the following errors. Not sure if these could be a source of the issue above. I can't find any documentation on how to decipher those codes. 322052A – RS232 Error 052A – RS232 Error 2a - RS232 Error 3. If the new driver has the potential to solve my problem, then my other problem is that I use the * off the older driver to force the keypad to display the text. I have this running within timers when my front door opens. After 30 seconds, the * is used to see if the "FRONT DOOR OPEN" text is displayed. If true, then it allows the front door lock to stay open while repeating an announcement that the door is open. When the door is closed, upon checking again with the * command, the lock then shuts. This has worked flawlessly and is preferred over the 30 second autolock that is built into the black and decker locks. All that to ask, do I understand that the new driver will not allow me this functionality? If you have any insights or ideas, please do share because I would prefer to not change out my unit if I can solve my problem. Quote Link to comment Share on other sites More sharing options...
C4 Lover Posted October 8, 2016 Share Posted October 8, 2016 For what it's worth, I also was able to ARM the system to "STAY NO DELAY" via the Concord 4 panel, but then it improperly showed DISARM on the left and the proper message on the right. I then tried arming and disarming about 10 times after that and it worked fine. I sure am baffled! Quote Link to comment Share on other sites More sharing options...
mikeryder Posted October 22, 2019 Share Posted October 22, 2019 I'm sorry for resurrecting an old thread. My question is related to a Concord 4 panel with the new Super Bus driver as the old driver does not work with Control4 v3. I installed the new driver and had it working to do basic tasks with the security system. It seems like the option from the old driver of entering numbers to the security panel is missing (and somebody mentioned the same on this thread). I use Control4 to bypass particular zones on my alarm system. With the old driver, I could send # + <CODE> + Zone. Is there any way to accomplish this on the new driver? Thanks in advance. 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.