Completed the setup/integration of a new VeraEdge (version 1.7.1018) and DSC/Envisalink using DSC alarm panel plugin (version .40). After installation, all my zones were showing under my devices reporting the proper state
My problems started after attempting to change the parameter ?EnabelRemoteArm? to disarm, according to the wiki. After this change no matter what I do I get ?DSCAlarmPanel Can't Detect Device? and ?EnabelRemoteArm Parametr must be either blank, false or value from wiki?. :'(
Once I get on this mode I cant get out even if I try to go back to the default (false). It appears that the value is updated, because after reset/reloads or reboots the value appears to be correct under the advance variables tab. I have try to remove the device, uninstall the plugin and total reset of the vera with no luck.
On my current configuration DSC alarm panel plugin, is my only plugin, please help!!!
I had this exact same problem as well. I am not sure if it will work in your case, but I can tell you what I did to fix it.
I started with a clean slate. I removed everything created by the plug-in and uninstalled it.
After reinstalling the plugin, open up the panel and click “Envisalink”
Restart your Vera
When changing the values below, press “tab” after you are done filling out the textbox and then move on to the next one.
4) Under “Params”
– enter the IP of your envisalink
5) Under “Variables”
– I put all door and window zones under “DoorZones”. If you have motions, obviously put those in “MotionZones”. Mine looks like this “1,2,3,4,5,6,7,8,9,10,11,12,13”
– Set “EnableRemoteArm” to “disarm” as you did before
6) Reboot your Vera again
At this point, everything worked for me. I think the key is setting all the values once and then rebooting the Vera without changing the same value multiple times.
Thanks for your help, it is working!!, it took 2 attempts, but it is working. I had to do a reload engine (New Service tab) between step 4 and 5, in order to get access to the variables.
Thanks for this post, just suffered the same problem, followed these instructions and back to normal. Problem is, why did it happen? Don’t like that I don’t know the cause, but at least there is a path back to normal!
I have tried this Over and over and over. As soon as I modify any value under variable, I lose connection to the panel. At this point, I don’t even care if the zones are correct, I just want to be able to arm it remotely.
Does anybody have any suggestions?
I’ve tried arm, disarm, Arm, Disarm (with capitals). I’ve tried every combination of removing the app and rebooting and reinstalling that I can think of. Noting works. As soon as I touch that remote arm variable, it kills it. I’ve tried my IP with just the IP and I’ve tried it with port 4925 appended.
What am I missing?
It works fine from the eyeson site. I don’t get it.
If I leave everything default (except for IP) it will report status. As soon as I touch any zones or the remote arm variable, all of the zones toss red “can’t connect” errors. I have been trying win “arm” mostly. I’ve only tried “disarm” once or twice but received the same result. I will try the uninstall-reboot-reinstall method with “disarm” to see if I have luck.
I installed and configured the DSC in UI7.
I had to manually force a reboot after setting to EVL.
I set zone and set to disarm, it initially did not save data.
Verified Userdata was correct after successful saving
http://ip_address:3480/data_request?id=user_data&output_format=xml
Tested, after a luup restart but unable to Disarm.
Tested after reboot but unable to Disarm.
I could confirm I experienced the same issues but unable to do anymore as I had to leave.
I will follow up later tonight (currently morning here) when I return home.
Thank you for checking. Making any changes in the variable screen causes panel disconnect for me. I’ve had rebooted the Vera (power cycle) between steps. I am at a loss. Even changing the value back to “false” will not cause a reconnect.
As soon as I change any variables, I get a red error message above the panel device as well as above all zones added that says “cannot detect device”. I did NOT put in the MAC address.
Log directly on to your EVL3, not via Envisalink, go to the Network tab and the bottom contain the section on TPI connection and its MAC address. Two things:
Place your MAC information in your Vera, below the IP and remove your IP address.
You can verify there if your Vera is connecting. This may take a few minutes before it does
I have just returned home and tested, both arm and disarm are now working fine which indicatives, that there were other things still ongoing in the back ground when I first set this up this morning.
The main problem identified when users have reported reported drop out or disconnection of the TPI, both here on and the Envisalink forum have traditionally been local network issues.
Try and remove the MAC address and set your ip address.
WRT to the EVL3, have you set the ip address to manual and out of the range of the DHCP range of your router?
If not, it may be a good idea to do this now. This is done on the EVL3 driectly in the network tab.
You can also raise a ticket to Envisalink if you do not resolve the issue and they can load customized firmware which enables them to conduct traces.
It is also worth verify the firmware of the EVL3 which I believe should be Remote 135 currently.
If it isnt, this is a setting on their site against your profile and I cannot remember much more than that; otherwise, you can raise a ticket with them to upgrade it.
If the connection is good you should not be seeing “Undefined” either in the MAC or IP.
Just a quick update:
The latest firmware update for the Vera edge fixed whatever it was causing my trouble. Noting else would fix it. I’m a happy camper now!
Best Home Automation shopping experience. Shop at Ezlo!
