DSC Envisalink

[io_guy]

There is no way in the API to tell when the output turned off.  Right now I set the outputs off when the alarm panel sends back a "Ready" state.

[apostolakisl]

57 minutes ago, io_guy said:

There is no way in the API to tell when the output turned off.  Right now I set the outputs off when the alarm panel sends back a "Ready" state.

That is what I am saying.  Not only is there no way to tell when it is off, there is no way to tell when it is on.   "command output" doesn't mean the output is on or off.  "command output" just means someone commanded the output to do something.  It means they hit *7x (where x is the output number) on the keypad.  Depending on how the panel is programmed that could mean it was toggled or that it was turned on for a period of time between 1 and 255 seconds.

So what I am saying here is that you shouldn't list the output state since you it doesn't appear that envisalink shares that info.  "command control" isn't a state, it is the panel broadcasting that someone hit *7x on a keypad.  It would be good to leave it in the node as a trigger event.  This would allow someone to trigger an ISY event by hitting the *7x on the keypad.

More importantly, it would be useful to send a "command control" to the panel so that you can, from ISY, initiate a *7x event on the panel.  I believe this is possible based on my experience with the polyglot node, but I haven't tested it.

[io_guy]

I can change the command output to a "command triggered" and put it on a 5s timer or something like that.

I don't currently support keypad entry in NodeLink.  People have been doing this:

 

[apostolakisl]

@io_guyIt's doing this again.  I have had nodelink running on this computer for a couple years and it never did this until now.  Two things are different, updating to 0.10.x and adding dsc link.  There is nothing wrong with my network and the PC nodelink is running on is working just fine accessing ISY, envisalink, cai, the internet, everything.  In fact, I'm posting this from the same computer that nodelink can't get to ISY from.

2019-11-17 21:36:27 - DSC: 50000025[C][L] [dsc1]
2019-11-17 21:36:27 - DSC: 500 - Command Acknowledge (000) [dsc1]
2019-11-17 21:36:28 - ISY Error: Web Error (FAILED) - NotFound (ns/1/nodes/n001_dsc1/report/status/GV1/09/70)
2019-11-17 21:37:01 - ISY Error: Web Error (FAILED) - NotFound (ns/1/nodes/n001_dsc1/report/status/GV1/09/70)
2019-11-17 21:37:27 - DSC TCP: Polling DSC [dsc1]
2019-11-17 21:37:27 - DSC: 50000025[C][L] [dsc1]
2019-11-17 21:37:27 - DSC: 500 - Command Acknowledge (000) [dsc1]
2019-11-17 21:37:34 - ISY Error: Web Error (FAILED) - NotFound (ns/1/nodes/n001_dsc1/report/status/GV1/09/70)
2019-11-17 21:38:07 - ISY Error: Web Error (FAILED) - NotFound (ns/1/nodes/n001_dsc1/report/status/GV1/09/70)
2019-11-17 21:38:27 - DSC TCP: Polling DSC [dsc1]
2019-11-17 21:38:27 - DSC: 50000025[C][L] [dsc1]
2019-11-17 21:38:27 - DSC: 500 - Command Acknowledge (000) [dsc1]
2019-11-17 21:38:40 - ISY Error: Web Error (FAILED) - NotFound (ns/1/nodes/n001_dsc1/report/status/GV1/09/70)
2019-11-17 21:39:13 - ISY Error: Web Error (FAILED) - NotFound (ns/1/nodes/n001_dsc1/report/status/GV1/09/70)
2019-11-17 21:39:27 - DSC TCP: Polling DSC [dsc1]
2019-11-17 21:39:27 - DSC: 50000025[C][L] [dsc1]
2019-11-17 21:39:27 - DSC: 500 - Command Acknowledge (000) [dsc1]
2019-11-17 21:39:45 - ISY Error: Web Error (FAILED) - NotFound (ns/1/nodes/n001_dsc1/report/status/GV1/09/70)
2019-11-17 21:40:19 - ISY Error: Web Error (FAILED) - NotFound (ns/1/nodes/n001_dsc1/report/status/GV1/09/70)
2019-11-17 21:40:27 - DSC TCP: Polling DSC [dsc1]
2019-11-17 21:40:27 - DSC: 50000025[C][L] [dsc1]
2019-11-17 21:40:27 - DSC: 500 - Command Acknowledge (000) [dsc1]

 

[io_guy]

Can you see if anything is showing up in the ISY logs that matches the time?  Not found is a 404 error so kind of odd.  

The ISY V5 has a knack of sending non-relevant error codes for errors so something else might be happening.  

For giggles you can also try sending ns/1/nodes/n001_dsc1/report/status/GV1/09/70 via a web browser to makes sure it's a valid send.  

[apostolakisl]

1 hour ago, io_guy said:

Can you see if anything is showing up in the ISY logs that matches the time?  Not found is a 404 error so kind of odd.  

The ISY V5 has a knack of sending non-relevant error codes for errors so something else might be happening.  

For giggles you can also try sending ns/1/nodes/n001_dsc1/report/status/GV1/09/70 via a web browser to makes sure it's a valid send.  

1) Looking at ISY log, it just stops reporting anything about nodelink during the time period where nodelink is showing the above error.

2) I sent http://192.168.1.9/ns/1/nodes/n001_dsc1/report/status/GV1/09/70 via a browser, and it replied   (my isy is at that lan address)

/ns/1/nodes/n001_dsc1/report/status/GV1/09/70 not found

I don't know what this means.  Is nodelink asking for the status of something in isy that does not exist in isy?  Is this causing nodelink to hang?

[io_guy]

NodeLink is setting it, or trying to and failing.  NodeLink has a buffer of all it's current sends.  If it fails (which this one is doing), it will retry every 30s.

The url should be:

http://192.168.1.9/rest/ns/1/nodes/n001_dsc1/report/status/GV1/09/70

[apostolakisl]

2 hours ago, io_guy said:

NodeLink is setting it, or trying to and failing.  NodeLink has a buffer of all it's current sends.  If it fails (which this one is doing), it will retry every 30s.

The url should be:

http://192.168.1.9/rest/ns/1/nodes/n001_dsc1/report/status/GV1/09/70

Response to that URL:

<RestResponse succeeded="false">
<status>404</status>
<reason code="1"/>
</RestResponse>

  ISY admin console was up and running on that very same computer and working properly while NL was stuck on that error.  NL was stuck on that for ~12 hours before I restarted NL from its config page and then it immediately had no issues and continues to have no issues now for about another 12 hours.  If everything else works, and the only thing it took to fix the problem (at least for a while) is restarting NL, then it has to be something within NL  Or maybe the .net framework?  I have no idea what role that plays.  As part of updating to 0.10.x NL, I had to install .net as it was not previously installed on that computer.

In addition to NL and the admin console, that computer runs Blue Iris 24/7.  Blue Iris is linked to polisy's blue iris node server.  That also works fine.  It has never hung up.

[io_guy]

It's the disarming user.  The ISY will not accept a value of 09.  I need to format the string to be 9 (no leading zero).

[apostolakisl]

1 hour ago, io_guy said:

It's the disarming user.  The ISY will not accept a value of 09.  I need to format the string to be 9 (no leading zero).

Great that you figured it out.  User 9 is my cleaning person.  I should have figured that out since I knew the one time that it immediately started when he showed up.  I guess the 1-8 already didn't have a leading "0"?

I got the network resource working for toggling the valve.  Thanks for that link.  Since Envisalink doesn't report valve state, hopefully we won't have any missed commands since the valve will be out of sync with the expected state.  I think I'm going to have to use a zone to monitor that valve state.

 

EDIT: And for anyone wanting to know, this is the network resource for sending a *72    

0711*72# 9F\r\n

 

[apostolakisl]

@io_guy

I'm trying to arm/disarm the system, but ISY says "request failed".  The log on nodelink does not show that anything happened at all.  Just the heartbeat and other stuff.  The log below covers the time period when I tried to arm the system to away and stay several times and nothing popped up.  ISY is accurately tracking the status of zones and armed state.  And I am using a network resource to trigger the outputs successfully.  Seems like there is a breakdown in communication between ISY and nodeserver regarding those commands.

2019-12-11 12:46:51 - DSC: 510 - Full LED Status Update [dsc1]
2019-12-11 12:46:51 - DSC: 6531CF[C][L] [dsc1]
2019-12-11 12:46:51 - DSC: 653 - Partition in Ready to Force Arm (Partition 1) [dsc1]
2019-12-11 12:46:51 - DSC: System Status - Ready to Force Arm (Partition 1) [dsc1]
2019-12-11 12:47:07 - DSC TCP: Polling DSC [dsc1]
2019-12-11 12:47:07 - DSC: 50000025[C][L] [dsc1]
2019-12-11 12:47:07 - DSC: 500 - Command Acknowledge (000) [dsc1]
2019-12-11 12:48:07 - DSC TCP: Polling DSC [dsc1]
2019-12-11 12:48:07 - DSC: 50000025[C][L] [dsc1]
2019-12-11 12:48:07 - DSC: 500 - Command Acknowledge (000) [dsc1]
2019-12-11 12:49:07 - DSC TCP: Polling DSC [dsc1]
2019-12-11 12:49:07 - DSC: 50000025[C][L] [dsc1]
2019-12-11 12:49:07 - DSC: 500 - Command Acknowledge (000) [dsc1]
2019-12-11 12:50:07 - DSC TCP: Polling DSC [dsc1]
2019-12-11 12:50:07 - DSC: 50000025[C][L] [dsc1]
2019-12-11 12:50:07 - DSC: 500 - Command Acknowledge (000) [dsc1]
2019-12-11 12:51:07 - DSC TCP: Polling DSC [dsc1]

 

[io_guy]

Enable debug on NodeLink's log window and on NodeLink's System Config tab.  You should see the request from the ISY?

[apostolakisl]

5 hours ago, io_guy said:

Enable debug on NodeLink's log window and on NodeLink's System Config tab.  You should see the request from the ISY?

No, ISY node can't find nodelink.  Other direction works fine.  Same result with either of my two partitions and all arm/disarm buttons.

EDIT:  Also, same thing with my Webcontrol 8.  ISY sees the input states fine, but can't control the outputs.

 

[apostolakisl]

Tried to update node def files and this is what the log says:

 

2019-12-12 09:11:27 - DSC: 653 - Partition in Ready to Force Arm (Partition 1) [dsc1]
2019-12-12 09:11:27 - DSC: System Status - Ready to Force Arm (Partition 1) [dsc1]
2019-12-12 09:11:35 - ISY Receive: ISY node profile nls/EN_US.TXT updated successfully
2019-12-12 09:11:35 - ISY Error: REST Post Error: The response ended prematurely.

 

[io_guy]

You likely have some sort of windows firewall issue.

[apostolakisl]

2 hours ago, io_guy said:

You likely have some sort of windows firewall issue.

only using windows built-in firewall.  Turned it off and the problem didn't change.  Perhaps unrelated, but I also noticed that the program no longer runs as administrator.  If I run as admin, a command window pops up for a split second and closes.  I have to run as regular user.  But I also don't get the message in the opening log about whatever it was the made you need to run as admin.  Running windows 10 pro 64 ver 1903.  I opened port 8090 on the computer, and now I can get to the console from other computers, but ISY still gives me error.

EDIT: Also tried adding an windows firewall inbound rule that opened everything up from my ISY IP address.  Still no go.

EDIT 2: Also, Event Ghost is running on that PC.  ISY sends commands to EG and those work. 

[nathagt]

On 12/11/2019 at 1:02 PM, apostolakisl said:

@io_guy

I'm trying to arm/disarm the system, but ISY says "request failed".  The log on nodelink does not show that anything happened at all.  Just the heartbeat and other stuff.  The log below covers the time period when I tried to arm the system to away and stay several times and nothing popped up.  ISY is accurately tracking the status of zones and armed state.  And I am using a network resource to trigger the outputs successfully.  Seems like there is a breakdown in communication between ISY and nodeserver regarding those commands.

2019-12-11 12:46:51 - DSC: 510 - Full LED Status Update [dsc1]
2019-12-11 12:46:51 - DSC: 6531CF[C][L] [dsc1]
2019-12-11 12:46:51 - DSC: 653 - Partition in Ready to Force Arm (Partition 1) [dsc1]
2019-12-11 12:46:51 - DSC: System Status - Ready to Force Arm (Partition 1) [dsc1]
2019-12-11 12:47:07 - DSC TCP: Polling DSC [dsc1]
2019-12-11 12:47:07 - DSC: 50000025[C][L] [dsc1]
2019-12-11 12:47:07 - DSC: 500 - Command Acknowledge (000) [dsc1]
2019-12-11 12:48:07 - DSC TCP: Polling DSC [dsc1]
2019-12-11 12:48:07 - DSC: 50000025[C][L] [dsc1]
2019-12-11 12:48:07 - DSC: 500 - Command Acknowledge (000) [dsc1]
2019-12-11 12:49:07 - DSC TCP: Polling DSC [dsc1]
2019-12-11 12:49:07 - DSC: 50000025[C][L] [dsc1]
2019-12-11 12:49:07 - DSC: 500 - Command Acknowledge (000) [dsc1]
2019-12-11 12:50:07 - DSC TCP: Polling DSC [dsc1]
2019-12-11 12:50:07 - DSC: 50000025[C][L] [dsc1]
2019-12-11 12:50:07 - DSC: 500 - Command Acknowledge (000) [dsc1]
2019-12-11 12:51:07 - DSC TCP: Polling DSC [dsc1]

 

So I just found this thread and it's basically exactly the issue I am having on Polisy. I posted about it a few days ago here. 

[apostolakisl]

1 minute ago, nathagt said:

So I just found this thread and it's basically exactly the issue I am having on Polisy. I posted about it a few days ago here. 

I believe IoGuy did some updates to fix this issue.  There were several updates in there that revolved around observations I had while implementing his NS so I don't recall what was what anymore.  I would check to make sure you are running the most up to date version.  There was also an issue where I was using the default user/pass on my envisalink and then the envisalink did a firmware update which disabled the default user/pass.  So make sure you are using a custom user/pass combo on envisalink.

[nathagt]

I'm running on Polisy so not sure I have the option of running a different version other than what is on the Polyglot Store. I did change my password because I read about the issue with the default one. 

[apostolakisl]

Just now, nathagt said:

I'm running on Polisy so not sure I have the option of running a different version other than what is on the Polyglot Store. I did change my password because I read about the issue with the default one. 

I don't think you are using IOGuy's nodeserver.  Nodelink doesn't run on Polisy.  There is a different DSC nodeserver that is part of polyglot.  Polyglot runs on Polisy.  Nodelink only runs on a pc or RPi.  According to Ioguy, he is working on getting nodelink to run on Polisy.  

[nathagt]

I agree it isn't Nodelink but I thought the code for connecting to DSC systems was pretty similar and your issue of one-way communication was the same as mine. I can see status of DSC but can't arm or disarm. Just the bad rad request error.

[apostolakisl]

4 hours ago, nathagt said:

I agree it isn't Nodelink but I thought the code for connecting to DSC systems was pretty similar and your issue of one-way communication was the same as mine. I can see status of DSC but can't arm or disarm. Just the bad rad request error.

Hard to say.  I am pretty sure this particular issue was the user/password problem.  Envisalink slipped the firmware update in on me.  Never asked or informed me that it wasn't updating firmware so I was at a complete loss when things just stopped working.