I have an existing DSC1832 which I have added an EVL-3 to. I can use Eyez-On website or my local IP to control the alarm but I can’t seem to get Vera to work. I am using UI5 and have installed the plug-in - all of the partitions and zones are showing up but I get the following in the message area: DSCAlarmPanel : Invalid Password for the EnvisaLink 2DS. I don’t see anywhere to enter a password? Also, when I click Set Time there isn’t any response - so I assume this is a connection issue. Does anyone have a recommended direction for me to proceed? Is there additonal information I need to post?
Thanks in advance.
Hello jarvis16,
When you log on to to your EVL-3 locally, I gather you changed the default password.
You have two options:
[ul][li]Log on to the EVL-3 and reset the password back to the default “user” - This is done in the Network tab.[/li]
[li]Follow instructions to add a variable. Instructions can be found here
[/li][/ul]
I would suggest option one and then once you have the device communicating with your Vera and set up fully, then attempt to set the time.
Thanks you, that worked. Vera can talk to the unit, as I can arm/disarm, but the set time still doesn’t respond. Seems like it doesn’t matter for me but just wanted to report my situation.
Not sure set time was ever tested for the 2DS/EVL3 as its now a redundant feature seeing that they can both do it automatically.
I take it you did try it with a PIN though?
Yes, I used a pin - no response.
Having the same invalid password problem as well. I did change from the default password so I have tried adding the vairable and clicking add. I see the new variable field for the password, and when I put my password in there it still does not work… Any suggestions?
I would suggest reverting back to default. As @guessed and others have pointed out several times it is not secure.
I just reverted back to default and it works now. I am somewhat surprised that something like this is so difficult to get to work correctly. Seems like it should be a minor programming issue as many others have had a similar problem and I would think it woudl be addressed by now in a more user friendly GUI kind of way… I would still rather have my own password instead of the default password.
I stopped adding major changes to the code some time back to allow the documentation to catch up. There’s a lot of knowledge in the DSC and Alarm threads (including basic setup) that, when read and followed in sequence , works correctly as many newbie’s before you have found.
Time is needed to let the core [wiki] doc catch up with what’s in these threads. The folks that work that are incredibly tied up with work commitments, so we don’t have a timeframe as to when that will be done.
Seems like it should be a minor programming issue as many others have had a similar problem and I would think it woudl be addressed by now in a more user friendly GUI kind of way... I would still rather have my own password instead of the default password.When you'd like to contribute those changes (complete code, UI, documentation diffs, screenshots, UI4 & UI5 Testing etc) [royalty free] just let us know, or post the fully tested/documented code differences [once] to the main code/plugin development thread.
Roger all that! Don’t get me wrong here but I was just telling it like I see it, as you did too. I certainly appreciate all the knowledgable members and coders on here and the support in the forum is second to none.
This is all very new to me - Z-Wave - but I am wanting to learn as much as I can about it. I am a “techie” but with other techie stuff, and so the learning curve here is a bit steep, but it’s moving along nicely for me.
I have read through the entire DSC Security thread, to get as familiar as I can with everything relating to the DSC and the Vera but, again, my attempts were less than fruitful with the solutions I read and tried.
Silly as it sounds, right now I am working on learning how to do scenes, triggers and such and I am certain that will lead to Luup commands and such. So far, the “User Guide” from MCV is less than accurate and lacking in the “how to” department. Now I would expect, that since they are a business and created the UI5 that there would be a much better “handbook” of how to do things and explinations but it appears so dated that it dosent even apply to UI5 much anymore. The WIKI is very helpful and so is this forum, but I guess I was expecting a better “guide” from the manufacturer.
Again, thank you for all your effort and time in this world and especially on this forum! 
Don’t call me Roger… Jokes - Acknowledged your comments.
The concern is that details contained as a password in your Vera is not protected in anyway and therefore completely insecure, and potentially more a security risk then using the default because anyone that has access to you network or Vera has access to this data and what is the consequence of that; especially if you are unaware of they have obtained this? Horses for courses. As far as I am concerned, if you are worried about this level of local access and setting a separate password for this, there are probably greater issues which may need to be addressed. Take my comment lightly as sometimes we can get wrapped up in small thing but miss other core issues.
Now, if you wish to retry:
You really should not have encountered any issues following the instructions as detailed (noting they Must be exact entries and contain no leading or trailing spaces etc.). In the example below, I have Device #133 and set it up using another password but to expose the level of recording of the data, I have used “Admin” as the example.
Refer DSCPassword1.png
ServiceId: urn:micasaverde-com:serviceId:DSCAlarmPanel1
Variable Name: InterfacePassword
Once you click add and save, you can see the ServiceId by hovering your Mouse over the new variable as displayed in HoverOver.png and MouseOver.png. You can also confirm details in your browser.
http://VeraIp/port_3480/data_request?id=user_data&output_format=xml
Either do searches for the Device id (e.g. device id=“133”) or by the new variable (variable=“InterfacePassword”) and you should see an entry like this:
service=“urn:micasaverde-com:serviceId:DSCAlarmPanel1” variable=“InterfacePassword” value=“Admin” id=“12”/>
As indicated, both the entries Must be exact. If you encounter any issues, please post in main thread as this will then be less fragmented which is always a concern and also makes it potentially harder for other that follow that may ask the same questions in the future. Good luck.
@guessed: I am hoping to be taking a few weeks leave next month and will hopefully be able to do some updating…
Thanks for your detailed explination! One thing I do not understand is this:
[quote=“Brientim, post:11, topic:173560”]You can also confirm details in your browser.
http://VeraIp/port_3480/data_request?id=user_data&output_format=xml[/quote]
How do I “confirm” this in my browser?
[quote=“SpaGuru, post:12, topic:173560”]Thanks for your detailed explination! One thing I do not understand is this:
[quote=“Brientim, post:11, topic:173560”]You can also confirm details in your browser.
http://VeraIp/port_3480/data_request?id=user_data&output_format=xml[/quote]
How do I “confirm” this in my browser?[/quote]
First point = use Google Chrome or firefox as they have xml viewers. I also believe Safari does also have an add on xml viewer.
Change /VeraIp to the ip address of your Vera
e.g. http://192.168.1.100/port_3480/data_request?id=user_data&output_format=xml
Copy the details established above in to the browser and you see the next part of the answer…
Now continue with either do searches for the Device id (e.g. device id=“133”) or by the new variable (variable=“InterfacePassword”) and you should see an entry like this:
service=“urn:micasaverde-com:serviceId:DSCAlarmPanel1” variable=“InterfacePassword” value=“Admin” id=“12”/>
I hope this explains enough for you to get the concept.
Copy that, I understand now. Will work on it a bit and check back! Thanks again for all your help!
Hi Folks, I just fired up my Vera lite and got it all set up with latest firmware etc. I also have a DSC 1832 with the EVL-3. I changed the default password of the EVL-3 and can log in and out of the EVL-3 no problems. I followed this thread to a T, and I still get the "Invalid password for the Envisalink 2DS please reconfigure message. Here is my xml line per the instructions above:
The “-” is the password I assigned bleeped out. So I still get the invalid password message. Am I missing anything new about this module and MIOS? I realize I’m responding to a thread that is a little old.
I’m running IU5, envisalink firmware 01.10.118, DSC plugin version 0.38.
BTW should the settings in the advanced tab be EVL-3 instead of 2DS? I noticed also that the commUse variable says rs232.
Is there some sort of debug logging I can see from the vera that might shed some light on why I can get this working? Thanks so much, any feedback would be appreciated.
I will keep it simple: return to default password.
The app shows 2DS this is used for the EVL3 as well and the commUse will update to be 2DS.
I guess to get it working and thats going to be my option, but seriously using the default for password for anything is really not the way to go. I’ll give it a shot report back.
ah ha! I got it working (evil grin) The first password i chose had alpha numeric characters, so I changed the EVL-3 password to be just letters and it worked. I’m guessing the password variable-add doesn’t support alphanumeric (yet?). So anyone else having this problem change your EVL-3 password to be just letters only and try again. It worked for me. ;D
The password is stored in clear text on your Vera and is sent across your network that way. Most people use a single type of password for most things and therefore, if they do this and store it is there Vera is potentially exposing a lot more then the password for this device.
true. I can see the password is clear text by looking at the xml file. Therefore, choose a password completely unique from your other devices to prevent a single password breach exposing more that your RVL-3.