Reconnecting Connect Bridge After Modem Change

[liteman78]

We have a Radio RA system with a main repeater and the first generation Connect Bridge. We recently changed ISP's from Comcast to Verizon, in the process switching out the modem/router. The main repeater still works but the Connect Bridge does not. The Lutron application recognizes the Connect Bridge but I have not been able to get it to connect to the system. I have tried different IP addresses without success.

Any help would be appreciated.

[SDR-Mike]

I just had this issue swapping to a better router and modem. I opened Essentials and started a simple file (not even the correct one for my home). "Found" the main repeater and Connect Bridge. Then closed the software without transferring anything. Both the main and Connect are now online with my apps. This happened knowing the ip address of both were compatible with the new subnet I was running. Check the ip address of your main and connect and verify they are compatible with the new modem/router. If not, run the trick I described above and change the main's and Connect's ip address to something that will work with the new equipment.

[liteman78]

I figured out the problem. What I needed to do was to reset the Connect Bridge to factory settings. Because we switched routers I also needed to change the IP address. Finally, I found that my Amazon Echo no longer worked. What I did to fix it was to disable the skill and then reenable it. That forced me to log back into Lutron from the Alexa app. All fixed!

Hopefully, this will help someone else who encounters these problems.

[SparkyCoog]

As much as Lutron recommends local static IP addresses for the connect bridge/main repeater, this is why I try to leave things in DHCP mode if it's an average house without an active IT guy on staff. If you have static IP and the owner replaces their router, more than likely, the static IP address you picked may not be available anymore or could be completely gone if they picked a different subnet scheme (went from 192.x.x.x to 10.x.x.x). If you keep things in DHCP, no matter what else they do to the router or internet, it will find and fix itself.

[pward]

I figured out the problem. What I needed to do was to reset the Connect Bridge to factory settings. Because we switched routers I also needed to change the IP address. Finally, I found that my Amazon Echo no longer worked. What I did to fix it was to disable the skill and then reenable it. That forced me to log back into Lutron from the Alexa app. All fixed!

Hopefully, this will help someone else who encounters these problems.

Changed local IP range from 192.168.1.x to 172.16.1.x. Lutron RA2 remote app stopped working. Rebooting device doesn't help. If I reset the connect-bdg2, does it loose my entire house configuration? Trying to avoid having to have a service tech have to visit for something so basic. But if I reset that device and loose all my configuration, that would be worse.

[Rowdy R.]

Hello.
Factory Defaulting the Connect-BDG2 will not delete the house configuration. However, it will require you link it again through the computer software and then send a transfer file to access it from the home. If you do not have access to the software on the computer we would recommend reaching out to a local tech to have that changed.

[pward]

Hello.
Factory Defaulting the Connect-BDG2 will not delete the house configuration. However, it will require you link it again through the computer software and then send a transfer file to access it from the home. If you do not have access to the software on the computer we would recommend reaching out to a local tech to have that changed.

OK, thanks for the quick reply. I downloaded the software, but don't have the configuration file, so I went back to the 192.168.1.1 gateway for now, and will go through my local dealer. Lutron should make this work with DHCP - changing routers is very common.