DSC Alarm Binding

Hi All

I am having challenges getting Envisalink 4 card to work with Openhab 2. I have followed the guide from tutorials but openhab does not seem to connect.
I have enabled logging and the following is what i get,
with or without specifying the password, the binding does not seem to work.

2017-12-17 00:49:36.191 [DEBUG] [rm.handler.DSCAlarmBaseBridgeHandler] - handleIncomingMessage(): Message received: 5050CA - Code: “505”, Name: “Login Interaction”, Description: “505: Login response (failed=0, success=1, time out=2, password request=3).”, Data: 0
2017-12-17 00:49:36.199 [DEBUG] [larm.handler.EnvisalinkBridgeHandler] - read(): Message Received: null
2017-12-17 00:49:41.039 [DEBUG] [rm.handler.DSCAlarmBaseBridgeHandler] - DSC Alarm Polling Task - ‘dscalarm:envisalink:NewBridge’ is OFFLINE
2017-12-17 00:49:41.054 [ERROR] [rm.handler.DSCAlarmBaseBridgeHandler] - Not Connected to the DSC Alarm!
2017-12-17 00:49:41.068 [DEBUG] [larm.handler.EnvisalinkBridgeHandler] - closeConnection(): Closing Socket!
2017-12-17 00:49:41.082 [DEBUG] [larm.handler.EnvisalinkBridgeHandler] - closeConnection(): Closing Output Writer!
2017-12-17 00:49:41.106 [DEBUG] [larm.handler.EnvisalinkBridgeHandler] - closeConnection(): Closing Input Reader!
2017-12-17 00:49:41.120 [DEBUG] [larm.handler.EnvisalinkBridgeHandler] - closeConnection(): Closed TCP Connection!
2017-12-17 00:49:41.130 [DEBUG] [larm.handler.EnvisalinkBridgeHandler] - openConnection(): Connecting to Envisalink
2017-12-17 00:49:41.151 [DEBUG] [larm.handler.EnvisalinkBridgeHandler] - read(): Message Received: 5053CD
2017-12-17 00:49:41.161 [DEBUG] [ng.dscalarm.internal.DSCAlarmMessage] - parseAPIMessage(): Message Received (5053) - Code: 505, Name: Login Interaction, Description: 505: Login response (failed=0, success=1, time out=2, password request=3)., Data: 3

2017-12-17 00:49:41.171 [DEBUG] [rm.handler.DSCAlarmBaseBridgeHandler] - handleIncomingMessage(): Message received: 5053CD - Code: “505”, Name: “Login Interaction”, Description: “505: Login response (failed=0, success=1, time out=2, password request=3).”, Data: 3
2017-12-17 00:49:41.180 [DEBUG] [larm.handler.EnvisalinkBridgeHandler] - write(): Attempting to Send Message: 005user54

2017-12-17 00:49:41.191 [DEBUG] [rm.handler.DSCAlarmBaseBridgeHandler] - sendCommand(): ‘NetworkLogin’ Command Sent - 005user54

2017-12-17 00:49:41.200 [DEBUG] [larm.handler.EnvisalinkBridgeHandler] - read(): Message Received: 5000052A
2017-12-17 00:49:41.210 [DEBUG] [ng.dscalarm.internal.DSCAlarmMessage] - parseAPIMessage(): Message Received (500005) - Code: 500, Name: Command Acknowledge, Description: 500: A command has been received successfully., Data: 005

2017-12-17 00:49:41.220 [DEBUG] [rm.handler.DSCAlarmBaseBridgeHandler] - handleIncomingMessage(): Message received: 5000052A - Code: “500”, Name: “Command Acknowledge”, Description: “500: A command has been received successfully.”, Data: 005
2017-12-17 00:49:41.230 [DEBUG] [rm.handler.DSCAlarmBaseBridgeHandler] - findThing(): Thing Found - org.eclipse.smarthome.core.thing.internal.ThingImpl@1005e881, org.openhab.binding.dscalarm.handler.PanelThingHandler@10b8b4f, PANEL
2017-12-17 00:49:41.241 [DEBUG] [rm.handler.DSCAlarmBaseBridgeHandler] - handleIncomingMessage(): Thing Search - 'org.eclipse.smarthome.core.thing.internal.ThingImpl@1005e881’
2017-12-17 00:49:41.251 [DEBUG] [rm.handler.DSCAlarmBaseBridgeHandler] - handleIncomingMessage(): Thing ‘dscalarm:panel:NewBridge:panel’ Not Refreshed!
2017-12-17 00:49:41.260 [DEBUG] [larm.handler.EnvisalinkBridgeHandler] - read(): Message Received: 5050CA
2017-12-17 00:49:41.270 [DEBUG] [ng.dscalarm.internal.DSCAlarmMessage] - parseAPIMessage(): Message Received (5050) - Code: 505, Name: Login Interaction, Description: 505: Login response (failed=0, success=1, time out=2, password request=3)., Data: 0

2017-12-17 00:49:41.280 [DEBUG] [rm.handler.DSCAlarmBaseBridgeHandler] - handleIncomingMessage(): Message received: 5050CA - Code: “505”, Name: “Login Interaction”, Description: “505: Login response (failed=0, success=1, time out=2, password request=3).”, Data: 0
2017-12-17 00:49:41.295 [DEBUG] [larm.handler.EnvisalinkBridgeHandler] - read(): Message Received: null

I use the EVL-3 and it works great. I’m not sure what they changed in the 4.

Perhaps you can post your things?

Here is my things file, it’s currently the one in tutorial
Bridge dscalarm:envisalink:MyBridgeName [ ipAddress=“192.168.1.200” ]
{
Thing panel panel
Thing partition partition1 [ partitionNumber=1 ]
Thing zone zone1 [ partitionNumber=1, zoneNumber=1 ]
Thing zone zone9 [ partitionNumber=1, zoneNumber=9 ]
Thing zone zone10 [ partitionNumber=1, zoneNumber=10 ]
Thing zone zone11 [ partitionNumber=1, zoneNumber=11 ]
Thing zone zone12 [ partitionNumber=1, zoneNumber=12 ]
Thing zone zone13 [ partitionNumber=1, zoneNumber=13 ]
Thing zone zone14 [ partitionNumber=1, zoneNumber=14 ]
Thing zone zone15 [ partitionNumber=1, zoneNumber=15 ]
Thing zone zone21 [ partitionNumber=1, zoneNumber=21 ]
Thing zone zone22 [ partitionNumber=1, zoneNumber=22 ]
Thing zone zone23 [ partitionNumber=1, zoneNumber=23 ]
Thing zone zone24 [ partitionNumber=1, zoneNumber=24 ]
Thing zone zone25 [ partitionNumber=1, zoneNumber=25 ]
Thing keypad keypad

And you are sure you don’t have a password to connect to your EVL? Can you connect to the web portal of the EVL without a password?

The file otherwise looks fine to me other than the missing password and I assumed you cut off your final } with pasting.

I would see if you could setup a password to the EVL and then modify your things with this:

Bridge dscalarm:envisalink:MyBridgeName [ ipAddress=“192.168.1.200”, password="*****" ]

Hi there
With or without a password, it makes no difference. The only thing I have read while researching this issue is that my password is 7 characters long. Not sure if that matters. I haven’t tested that yet.

Moxified
December 17 |

And you are sure you don’t have a password to connect to your EVL? Can you connect to the web portal of the EVL without a password?

The file otherwise looks fine to me other than the missing password and I assumed you cut off your final } with pasting.

I would see if you could setup a password to the EVL and then modify your things with this:

Bridge dscalarm:envisalink:MyBridgeName [ ipAddress=“192.168.1.200”, password="*****" ]

Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

Well, I’m not sure. The password length might matter. Unfortunately I don’t have the 4 to test against and it may be different.

I know this is a different plugin on a different platform but a quick search found this thread over at homeseer where people say they spoke with envisalink who said the api is the same between the two and forum members reported fully functional with their existing binding. Ours might have an issue with the password or something as you suggest. https://forums.homeseer.com/showthread.php?t=177020

I think @rsstephens wrote it or at least knows a fair bit about it and may have some ideas.

Hello @zizebra,

Looking at the log you provided, the binding is sending the default password to connect to the Envisalink, and then failing on the login. Is this the correct password? As @Moxified suggests if you are not using the default password, you will need to put the correct one in the .things file.

I believe the Envisalink 4 will allow up to 10 characters for a password while the Envisalink 3 will allow up to 6 characters. The binding does check the length of the password, which only allows up to 6 characters for now. So, you will need to keep your password length to a maximum of 6 characters at this point. I will need to look into updating the binding, not sure when though. Hope this helps.

Well that complicates it. My password is 7 characters and that did not work for me and I have envisalink 4. I will shorten my password and try again.

Hi
And there was joy. reducing the number of characters on my password to 6 worked.So not sure if this needs to change on the binding or the Eyezon needs to update the API.

Glad that it is working!!! The binding needs to be changed to allow for more characters for the password. It was updated for the ENV-3 but not for the ENV-4.