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.