Jump to content

Missing setup info


johnnyt

Recommended Posts

Posted

Am upgrading from a 4.7.3 configuration to 5.x on 2nd "lab" ISY and installed/configure NodeLink okay but am missing some setup info around adding devices and getting errors.

1. I tried to setup a Venstar device and configured it on the new tab that was created on NodeLink web page, making sure to enter the correct IP address for it. I don't see anything on the ISY and get the following error each time the NodeLink does it's polling:

2019-05-11 09:32:52 - Venstar: Get Error - Invalid URI: The hostname could not be parsed. [ven1]

So I tried on the ISY to Add Node -> Venstar Thermostat. I got prompted for Node Address and Primary Node Address. I assumed that I needed to enter my Venstar IP address for both and it took it (no error) but see nothing added. I tried putting in address of NodeLink computer instead but still nothing to see on ISY. Should I see something? What are Node Address and Node Primary Address supposed to be?

2. I then tried to add my DSC Alarm Panel and configured it on the new tab that was created on Nodelink web page. Again, I don't see anything on the ISY and I get the following errors:

2019-05-11 11:06:53 - ISY Error: Web Error (NODE_ALREADY_EXISTS) - BadRequest (ns/1/nodes/n001_dsc1/add/DSC?primary=n001_dsc1&name=DSC Alarm&nls=102D)
2019-05-11 11:06:53 - ISY Error: Web Error (NODE_ALREADY_EXISTS) - BadRequest (ns/1/nodes/n001_dsc1_part1/add/DSCPartition?primary=n001_dsc1&name=Partition 1&nls=102DP)
2019-05-11 11:06:53 - ISY Error: Web Error (NODE_ALREADY_EXISTS) - BadRequest (ns/1/nodes/n001_dsc1_z01/add/DSCZone?primary=n001_dsc1&name=Zone 01&nls=102Z)
2019-05-11 11:06:53 - ISY Error: Web Error (NODE_ALREADY_EXISTS) - BadRequest (ns/1/nodes/n001_dsc1_z02/add/DSCZone?primary=n001_dsc1&name=Zone 02&nls=102Z)
2019-05-11 11:06:53 - ISY Error: Web Error (NODE_ALREADY_EXISTS) - BadRequest (ns/1/nodes/n001_dsc1_z03/add/DSCZone?primary=n001_dsc1&name=Zone 03&nls=102Z)
2019-05-11 11:06:53 - ISY Error: Web Error (NODE_ALREADY_EXISTS) - BadRequest (ns/1/nodes/n001_dsc1_z04/add/DSCZone?primary=n001_dsc1&name=Zone 04&nls=102Z)
2019-05-11 11:06:53 - ISY Error: Web Error (NODE_ALREADY_EXISTS) - BadRequest (ns/1/nodes/n001_dsc1_z05/add/DSCZone?primary=n001_dsc1&name=Zone 05&nls=102Z)
2019-05-11 11:06:53 - ISY Error: Web Error (NODE_ALREADY_EXISTS) - BadRequest (ns/1/nodes/n001_dsc1_z06/add/DSCZone?primary=n001_dsc1&name=Zone 06&nls=102Z)
2019-05-11 11:06:53 - ISY Error: Web Error (NODE_ALREADY_EXISTS) - BadRequest (ns/1/nodes/n001_dsc1_z07/add/DSCZone?primary=n001_dsc1&name=Zone 07&nls=102Z)
2019-05-11 11:06:53 - ISY Error: Web Error (NODE_ALREADY_EXISTS) - BadRequest (ns/1/nodes/n001_dsc1_z08/add/DSCZone?primary=n001_dsc1&name=Zone 08&nls=102Z)

For giggles I tried to add the node in ISY as I did for venstar but ran into the same issues as with the Venstar.

What am I missing?

Finally, I'm getting the message "2019-05-11 09:03:21 - ISY Warning: Duplicate node names exist on the ISY (Workshop Lights)" at NodeLink startup but can't find more than one device on my ISY that's called "Workshop Lights", nor is there a program or variable named that, though some have that in a portion of their names, e.g. I have a "Workshop Lights Off" program. Where do I need to look for this duplicate and what is the impact of having a duplicate (in case I'm not able to find it)

Below is the status info I get at NodeLink startup: I'm definitely pointing to the lab ISY, not the prod one and NodeLink is on a separate machine from the VenLink and DSCLink programs running for my prod ISY.

2019-05-11 09:03:18 - ISY NodeLink Server v0.9.31 started
2019-05-11 09:03:18 - OS: Microsoft Windows NT 6.1.7601 Service Pack 1
2019-05-11 09:03:18 - Web config server started (http://192.168.0.6:8090)
2019-05-11 09:03:19 - ISY resolved to 192.168.0.251 (5.0.13D)
2019-05-11 09:03:19 - ISY Node Server config detected (profile 1)
 

Any help would be appreciated.

 

Posted

 

4 hours ago, johnnyt said:

 I don't see anything on the ISY 

Okay so I do see devices now in the root of "My Lighting", but there's no data for either venstar or DSC alarm. (I was looking under Node Servers menu for something before)

Posted

Venstar should just be an IP address.  

Never add nodes from Inside the ISY.  

Reboot NodeLink and paste a log.  

Posted
1 hour ago, io_guy said:

Reboot NodeLink and paste a log.  

here you go:

2019-05-11 19:20:15 - ISY NodeLink Server v0.9.31 started
2019-05-11 19:20:15 - OS: Microsoft Windows NT 6.1.7601 Service Pack 1
2019-05-11 19:20:15 - Web config server started (http://192.168.0.6:8090)
2019-05-11 19:20:15 - ISY resolved to 192.168.0.251 (5.0.13D)
2019-05-11 19:20:15 - ISY Node Server config detected (profile 1)
2019-05-11 19:20:17 - ISY Warning: Duplicate node names exist on the ISY (Workshop Lights)
2019-05-11 19:20:18 - DSC: Repeater started on port 4025 [dsc1]
2019-05-11 19:20:18 - DSC Error: Connected - An existing connection was forcibly closed by the remote host [dsc1]
2019-05-11 19:20:18 - Relay Server: Started on port 2405

 

Posted

Not long enough to show any Venstar.  

I'm guessing the DSC closes cause you're still running DSCLink.  The EVL only supports a single connection (hence why I added the repeater).  

Posted

Venstar works after the restart - would be good to mention this in setup guide - along with info about configuring devices after adding them.

I do have the repeater check box checked for DSC alarm.

I shut down DSCLink and rebooted again. Here's what came up now:

2019-05-11 19:32:55 - ISY NodeLink Server v0.9.31 started
2019-05-11 19:32:55 - OS: Microsoft Windows NT 6.1.7601 Service Pack 1
2019-05-11 19:32:55 - Web config server started (http://192.168.0.6:8090)
2019-05-11 19:32:57 - ISY resolved to 192.168.0.251 (5.0.13D)
2019-05-11 19:32:57 - ISY Node Server config detected (profile 1)
2019-05-11 19:32:58 - ISY Warning: Duplicate node names exist on the ISY (Workshop Lights)
2019-05-11 19:32:59 - DSC: Repeater started on port 4025 [dsc1]
2019-05-11 19:32:59 - Relay Server: Started on port 2405
2019-05-11 19:32:59 - DSC Error: Data Arrival - StartIndex cannot be less than zero.
Parameter name: startIndex [dsc1]
2019-05-11 19:34:29 - DSC TCP: No poll response, attempting to reconnect to alarm [dsc1]
2019-05-11 19:34:29 - DSC: Reconnecting To Server [dsc1]
2019-05-11 19:34:29 - DSC Error: Data Arrival - StartIndex cannot be less than zero.
Parameter name: startIndex [dsc1]
 

 

 

Posted

Redid everything without DSCLink running and things are working now. (VenLink running doesn't cause any problems)

Only outstanding item is:  ISY Warning: Duplicate node names exist on the ISY (Workshop Lights)

Does "node" = device, or something else? or could it be anything, i.e. device, program, variable, network resource, etc. Is it a case of only looking at the first 15 chars in a name, meaning "Workshop Lights 2" would be reported as a duplicate of "Workshop Lights"?

Posted

You can ignore it, it's just a warning, warning that two things have the same same.  Could be node, variable or program.   

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...