I believe I am running into the same issue with discovery of a EnvisaLink 3 that is currently in use (connected??) with a Vera lite. This post seems a bit old now but I am inclined to help solve this problem if possible.
My status: Brand new OH 2 install using the “Hassle-free” setup. Add the EnvisaLink add-on, start discovery.
I attempt to manually add the DSC panel 1st because that seems like the natural thing to do***.
That is not possible due to what appears to be a UI bug choosing the bridge. When I get to that part of the manual setup of the panel where you select “bridge”, the UI appears to try and drop down to an empty list. Immediate frustration.
So now I go back and notice that there are other elements that may need to be added first like the TCP Server and/or the Envisilink.
I add both, but only the TCP server is “online”. During setup of the Envisilink I used the default port and entered my non-default Envisilink user password (working with Vera). But it did not go online. Not sure where to go from here, so I try to add the panel again which now allows me to select the bridge I added but still only the TCP server is online.
I added my process in the hope that this will be used to improve the process for setting up this add-on within the UI. I strongly believe that more pointers need to be built into the manual process since I was unable to get things to work.
More importantly, why does the discover still fail?
And lastly, what do I need to do to get this to work? I see a note about making sure that the EV is not “connected” to anything else. What does that mean? I can connect to it via port 80 and my Vera is configured to “connect” to it as well. Does it have a limitation that I am unaware of?
I am committed to making OH better. Let me know what I can do to help improve the product and process.