The cable from your site indicates firmware 1.5 or higher needed. I have 1.13 and the latest is 1.17. Please explain.
1.5 < 1.6 < 1.8 < 1.9.6 < 1.10 < 1.12 < 1.13, etc.
1.17.03 is the latest Alarm.com applicable version as of this post.
Ok. I read it as 1.50. Sorry. I just ordered the cable.
Ok. I read it as 1.50. Sorry. I just ordered the cable.
No problem. 1.5 is a very old version.
The issue is that they stopped working code-wise meaning that if the door was locked and the panel was armed, entering a code did not unlock the door. I had to delete the codes and re-enter the code. Then it worked again for a while but went into the same state.
Whether or not the panel is armed would not have an impact on unlocking the door lock at the lock, to clarify. Are you saying the codes do not work after a time at the locks themselves? Or are you saying you also had a rule to unlock the door when you disarm the alarm panel?
If a code which is saved in the lock stops functioning when punched in at the lock, that indicates either a lock malfunction or one of the controllers overwrote the codes. Have you used any software associated with the Vera to control/adjust codes in the locks as well?
In the one lock’s case (maybe others), the code was not usable. In another instance when the code was able to unlock the door, the panel was not disarmed. We had to disarm the panel manually. None of these problems occur when the panel is Primary and has the locks paired with it. The VeraSecure has all of the other zwave devices. No other software was in control of the locks while the 2GIG was a Secondary paired with the VeraSecure. Alarm.com had the same codes as the VeraSecure had programmed into the keylocks. If I did not assigned pin codes to the devices in VeraSecure then the locks would not appear in the 2GIG. I added the pin codes to VeraSecure device locks before I paired the 2GIG to the VeraSecure.
If I did not assigned pin codes to the devices in VeraSecure then the locks would not appear in the 2GIG. I added the pin codes to VeraSecure device locks before I paired the 2GIG to the VeraSecure.
This is likely where the problem is then. If the codes were not added through Alarm.com, the 2GIG panel would not be able to match the lock user slots to codes sent via a different controller. If they at any point tried to sync with ADC, the lock codes may have been deleted if no corresponding user slot was set in ADC.
In general codes should be created in Alarm.com as they need to sync with both the alarm panel and the lock. It would make sense that the lock just connected to the 2GIG panel would not see this issue.
Yeah, that makes sense but if I do not assign the pin codes to the lock and then I Reset controller and Learn Controller on the 2GIG, the locks do not appear in the 2GIG and thus alarm.com. That said, perhaps I did not wait long enough. So I can try it again and wait for a while to verify that the devices all show up.