I have my 2GIG controller set in secondary mode. It picked up the light switches and other devices from my VeraSecure device no problem. They showed up at alarm.com as well. I also have the KwikSet locks in the VeraSecure. They previously we in the 2GIG and worked fine. The 2GIG did not pick them up from the VeraSecure like the switches were. Any ideas why they were not? I do not see them on alarm.com nor in Locks in the 2GIG panel.
Correction: the locks showed up in the 2gig once I added codes to the locks via the VeraSecure UI. They do not show up in alarm.com though thus I cannot disarm the panel when I unlock the door. I assume that this is due to alarm.com not being aware of the locks. Is this correct?
Also, I added a new device and it showed up in 2gig after I did a check network but alarm.com does not see it. Does alarm.com take a while to see the new devices? It has been over an hour. Is there anything that I have to do to make alarm.com aware of the new device or does the 2gig send the new data automatically?
I did Reset Controller on the 2GIG panel. I removed the device related to the 2gig panel from VeraSecure. I then did Learn Controller on 2GIG and then Add device on VeraSecure. After a while this process was complete. Alarm.com showed all of the devices. However, alarm.com seems to think that one of the locks is offline and I cannot use it to disarm the panel as a Rule. It shows up as a device selection for a Rule involving Disarm/Arm panel so that I can specify which locks are unlocked when I arm the panel for Away. If I look at the alarm.com android app and select Locks I see all of the locks but the one lock in question does not have a checkbox on it like the others have. I can control all of the locks no problem from VeraSecure so the locks are all functional. Does anyone have any ideas why I have a problem with one of the locks with alarm.com?
However, alarm.com seems to think that one of the locks is offline and I cannot use it to disarm the panel as a Rule. It shows up as a device selection for a Rule involving Disarm/Arm panel so that I can specify which locks are unlocked when I arm the panel for Away. If I look at the alarm.com android app and select Locks I see all of the locks but the one lock in question does not have a checkbox on it like the others have. I can control all of the locks no problem from VeraSecure so the locks are all functional. Does anyone have any ideas why I have a problem with one of the locks with alarm.com?
The wireless link between the Vera and the Lock does not indicate that a successful link should occur between the 2GIG Panel and the lock. The two controllers do not send messages through one another, and there may be something which failed in the initial transmission when learning the 2GIG as a secondary controller, or in a subsequent network rediscovery.
What model numbers are the locks? Are they all the same? Is the one that is failing different than the others? Note that there are older versions of the Kwikset (the 909 I think) which are not compatible with the 2GIG panel.
Also, be sure when pairing the 2GIG Panel as a secondary controller that it is within a few feet of the Vera through the pair process.
Also, I added a new device and it showed up in 2gig after I did a check network but alarm.com does not see it. Does alarm.com take a while to see the new devices? It has been over an hour. Is there anything that I have to do to make alarm.com aware of the new device or does the 2gig send the new data automatically?
Yes, there can be a delay between adding a device and the panel updating ADC with that device’s status, etc.
If you do not see the device after a long period, you’ll want to contact your provider (it looks like this is not regarding a suretyDIY account). There are back-end diagnostic tools which can help.
The locks are all the same. The locks are compatible with the 2GIG panel since they we working with it no problem when the 2GIG was the primary controller. This is the first time I have tried them with the VeraSecure and make the 2GIG secondary.
I did not have the VeraSecure within a few feet of the 2GIG panel so maybe that is the issue. I will try that tonight.
Regarding the few feet proximity. Is that necessary? I have plenty of zwave devices in between the 2GIG and the VeraSecure and I thought that the communication would occur through the mesh network. If that is not the case, then I can understand the need for the proximity of the two controllers, which I will try anyway tonight.
Regarding the few feet proximity. Is that necessary? I have plenty of zwave devices in between the 2GIG and the VeraSecure and I thought that the communication would occur through the mesh network. If that is not the case, then I can understand the need for the proximity of the two controllers, which I will try anyway tonight.
Yes, from experience the proximity is necessary.
When pairing the controllers or any non-NWI Z-wave node, communication between the controller and the device being learned in will not be repeated through the network. Locks and thermostats are the most susceptible to issues arising from this.
I place the VeraSecure within a few feet and finally got all of the locks to alarm.com. I had to unpair three of them with VeraSecure and add them back in. Then I Reset Controller on 2GIG. Then Add device on VeraSecure and pressed Learn Controller. I left it in that mode for about 15 minutes. So that is all good now.
What do I need to do if I add a new zwave device? Do I just add it to the VeraSecure and then Check Network on the 2GIG? All should get added to 2GIG and alarm.com?
What do I need to do if I add a new zwave device? Do I just add it to the VeraSecure and then Check Network on the 2GIG? All should get added to 2GIG and alarm.com?
If similar to prior Vera models, yes, devices added to Vera should be automatically recognized after a short delay by the 2GIG panel and after, Alarm.com.
I spoke too soon about the locks. The locks all appeared in the alarm.com android app with checkboxes beside each. This means that it picked them up from the 2GIG panel but when I check one of them and press Lock nothing happens. Only one of the locks actually work as expected. The other two do not. Any ideas?
I spoke too soon about the locks. The locks all appeared in the alarm.com android app with checkboxes beside each. This means that it picked them up from the 2GIG panel but when I check one of them and press Lock nothing happens. Only one of the locks actually work as expected. The other two do not. Any ideas?
It does not look like this is in reference to a suretyDIY subscription. Without access to back-end diagnostics it is very difficult to say. As long as the steps were followed you should be good, but there may be unseen issues.
I would recommend not using the app at all to troubleshoot. Does the 2GIG panel show the locks as having failed? What color is your Services Button?
If you press Services > Z-wave > Check Network, what is the result?
The panel does not show failure. alarm.com website does not show failure. But when I click lock on one of the locks all is good and behaves properly. On another, it takes a minute or so to change the state of the lock. On the third one no state changes. If I unpair the troublesome locks from VeraSecure and then wait a while, will the 2GIG automatically take away the reference to the lock in the 2GIG and then remove the reference in alarm.com? If so, then I can repair the troublesome locks again on the VeraSecure. I assume that the 2GIG will automatically add the devices to the 2GIG and then to alarm.com?
The result of check network shows no error.
In this case it would be best to be able to see commands and whether or not the module has acknowledged them. Try just controlling the locks from the alarm panel. Do they function as expected there? You may simply be having an issue with the module receiving too many commands or processing too many Z-wave requests. This can lead to commands backing up in the buffer.
You would need to speak with your provider regarding commands and whether or not your module is acknowledging them.
One thing you might try is updating the firmware of the 2GIG panel. Are you using 1.17 yet? If not that may be a good thing to try if your provider supports it. 1.17 adds a Z-wave command queuing feature to the 2GIG panel to assist with command processing. Make sure to contact your provider and verify that this is an option for you.
One thing that I have encountered with the 2GIG as a secondary controller to VeraSecure is that the locks seems to lose the ability to unlock with a code and that they do not disarm the panel quickly if at all. They worked as expected for a day or so. So I have :reset controller" on the 2GIG and removed the locks from VeraSecure. Then I added the locks back into the 2GIG. The 2GIG only has the locks now and no other zwave devices. The locks work fine as usual now. I wonder why they didn’t work properly when the 2GIG was secondary. I have not been able to get 1.17 firmware put onto my 2GIG either. The monitoring company has failed to do it even though they said they can do it and have done it.
I have not been able to get 1.17 firmware put onto my 2GIG either. The monitoring company has failed to do it even though they said they can do it and have done it.
Looks like this is likely referencing service in Canada, is that correct? Unfortunately suretyDIY does not currently provide service outside of the United States.
Note with a 2GIG GO!Control you can upgrade locally via the 2GIG update cable and firmware file download, as long as your provider supports such an update. Always check with your provider to verify that it will not cause any problems.
One thing that I have encountered with the 2GIG as a secondary controller to VeraSecure is that the locks seems to lose the ability to unlock with a code and that they do not disarm the panel quickly if at all. They worked as expected for a day or so. So I have :reset controller” on the 2GIG and removed the locks from VeraSecure. Then I added the locks back into the 2GIG. The 2GIG only has the locks now and no other zwave devices. The locks work fine as usual now. I wonder why they didn’t work properly when the 2GIG was secondary.
Problems with lock communication is commonly a problem during the pairing process. The absolute most important thing to remember is that proximity is required when learning in the locks. There is no benefit trying to learn them in from a distance as it very often causes issues down the line if not immediately.
Locks should be within 6 feet of the controller when learned in. After moving devices to their permanent spots, run a network rediscovery.
With the second controller the same applies. The locks should be within 6 feet when learned in, and the controllers should be within 6 feet when paired.
I had the controllers within a few feet of each other but the locks were not. But they eventually were paired and worked fine with 2GIG and with VeraSecure. 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.
I will have to buy a firmware cable to flash the 2GIG myself so that will likely be the next step.
I should mention that one lock WAS within six feet when paired with both controllers. That lock for sure went into the bizarre mode of not unlocking after a time.
The cable from your site indicates firmware 1.5 or higher needed. I have 1.13 and the latest is 1.17. Please explain.