Jump to content

Venstar: Warning nodesetup.zip file needs updating in ISY


ralbright

Recommended Posts

Trying to add NodeLink Server to my ISY, with adding my Venstar thermostat.

Here are the steps I did
1) Installed NodeLink Server v0.9.6 on my server
2) linked ISY Node 1 to NodeLink Server
3) Added Venstar device into NodeLink Server
 

I did get a device in the ISY for the Venstar which is showing data (run time, air temp, set point, etc.), however none of the data appears to be updating.

Here is the log file from NodeLink Server:

2018-02-18 21:03:47 - ISY NodeLink Server v0.9.6 started
2018-02-18 21:03:47 - Web config server started (http://192.168.2.250:8086)
2018-02-18 21:03:47 - ISY resolved to 192.168.2.4
2018-02-18 21:03:47 - ISY Node Server config detected (profile 1)
2018-02-18 21:03:48 - Warning: nodesetup.zip file needs updating in ISY
2018-02-18 21:03:48 - Relay Server: Started on port 2405
2018-02-18 21:04:25 - Venstar Get Error: One or more errors occurred. [ven1]
2018-02-18 21:05:19 - ISY Error: Response status code does not indicate success: 400 (OK). (ns/1/nodes/n001_ven1/add/VenstarF?primary=n001_ven1&name=Venstar&nls=140V)
2018-02-18 21:05:19 - ISY Error: Response status code does not indicate success: 400 (OK). (ns/1/nodes/n001_ven1_run/add/VenstarRuntimes?primary=n001_ven1&name=Runtime&nls=140VR)
2018-02-18 21:05:19 - ISY Error: Response status code does not indicate success: 400 (OK). (ns/1/nodes/n001_ven1_s00/add/VenstarSensorF?primary=n001_ven1&name=Space Temp&nls=140VS)
2018-02-18 21:06:00 - Venstar Get Error: One or more errors occurred. [ven1]
2018-02-18 21:06:53 - Web Request Invalid: /isylink/add/nodes
2018-02-18 21:07:06 - Venstar Get Error: One or more errors occurred. [ven1]
2018-02-18 21:07:41 - Venstar Get Error: One or more errors occurred. [ven1]
2018-02-18 21:08:02 - Venstar Set Error: A task was canceled. [ven1]
2018-02-18 21:08:05 - Venstar Set Error: A task was canceled. [ven1]
2018-02-18 21:08:31 - Venstar Set Error: A task was canceled. [ven1]
2018-02-18 21:08:34 - Venstar Set Error: An error occurred while sending the request. [ven1]
2018-02-18 21:08:34 - Venstar Set Error: A task was canceled. [ven1]
2018-02-18 21:08:35 - Venstar Set Error: An error occurred while sending the request. [ven1]
2018-02-18 21:08:36 - Venstar Set Error: An error occurred while sending the request. [ven1]
2018-02-18 21:08:38 - Venstar Set Error: A task was canceled. [ven1]
2018-02-18 21:08:42 - Venstar Get Error: One or more errors occurred. [ven1]
2018-02-18 21:09:13 - Venstar Get Error: One or more errors occurred. [ven1]
2018-02-18 21:09:14 - Venstar Get Error: One or more errors occurred. [ven1]
2018-02-18 21:09:34 - ISY: ISY node profile nodedef/I_NDEFS.XML updated successfully
 

What do these messages mean? How do I fix them?


 

Link to comment
Share on other sites

Whole bunch of errors there, and a little confusing with the changes made in 0.9.6.

A task was canceled is a web timeout.  Increase the timeout value in the NodeLink Venstar config page.  Are you using SSL (if so, don't)?

The other errors are going need some changes on my code to dig deeper (error handling became a mess with the new http calls).

Upload the nodesetup.zip file to the ISY and reboot the ISY and NodeLink.

 

Link to comment
Share on other sites

2 hours ago, io_guy said:

Whole bunch of errors there, and a little confusing with the changes made in 0.9.6.

A task was canceled is a web timeout.  Increase the timeout value in the NodeLink Venstar config page.  Are you using SSL (if so, don't)?

The other errors are going need some changes on my code to dig deeper (error handling became a mess with the new http calls).

Upload the nodesetup.zip file to the ISY and reboot the ISY and NodeLink.

 

It turns out I think I have a defective Venstar unit. When I sync the NodeLink to the Venstar unit, the thermostat goes offline after a few minutes. The only way to fix this is to physically remove the thermostat and re-seat it. Grrr. And of course, the idiots at Venstar tell me that there cannot be anything wrong with their "infallible" product that it must be my network.... I am about ready to throw this Venstar in the garbage.

 

Link to comment
Share on other sites

So I have added (or am attempting to add) my Brultech GEM to the NodeLink Server. I have selected Auto-Update ISY, I have installed the nodesetup.zip file. (refer to attachment) Yet in NodeLink Server I am still getting the following:

2018-02-20 07:35:02 - ISY NodeLink Server v0.9.7 started
2018-02-20 07:35:02 - Web config server started (http://192.168.2.250:8090)
2018-02-20 07:35:03 - ISY resolved to 192.168.2.4
2018-02-20 07:35:03 - ISY Node Server config detected (profile 1)
2018-02-20 07:35:03 - Warning: nodesetup.zip file needs updating in ISY
2018-02-20 07:35:24 - GEM: Socket Error - Connection refused. [gem1]
2018-02-20 07:35:33 - GEM: Socket Error - Send Data - A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied [gem1]
2018-02-20 07:35:33 - GEM: Reconnected [gem1]
2018-02-20 07:35:54 - GEM: Socket Error - Connection refused. [gem1]
2018-02-20 07:36:03 - GEM: Socket Error - Send Data - A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied [gem1]
2018-02-20 07:36:03 - GEM: Reconnected [gem1]
2018-02-20 07:36:24 - GEM: Socket Error - Connection refused. [gem1]
2018-02-20 07:36:33 - GEM: Socket Error - Send Data - A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied [gem1]
2018-02-20 07:36:33 - GEM: Reconnected [gem1]
2018-02-20 07:36:54 - GEM: Socket Error - Connection refused. [gem1]
2018-02-20 07:37:03 - GEM: Socket Error - Send Data - A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied [gem1]
2018-02-20 07:37:03 - GEM: Reconnected [gem1]

I must be missing something simple. But I cannot figure out what it is.

GEM setup.png

GEM Nodelink setup.png

GEM Nodelink Devices.png

GEM ISY dashboard.png

Link to comment
Share on other sites

io_guy is working on this and expects a fix tonight hopefully.

io_guy made some Ethernet protocol major revisions and it is causing him some grief getting it to function properly. It affects all my NodeLink devices updating and I went back to 0.9.4 for now.

 

I would wait until io_guy get another fix out before tearing your stuff apart.

Link to comment
Share on other sites

3 hours ago, larryllix said:

io_guy is working on this and expects a fix tonight hopefully.

io_guy made some Ethernet protocol major revisions and it is causing him some grief getting it to function properly. It affects all my NodeLink devices updating and I went back to 0.9.4 for now.

 

I would wait until io_guy get another fix out before tearing your stuff apart.

Do you know where to download 0.9.4?

Link to comment
Share on other sites

3 hours ago, ralbright said:

So is this what is causing the "Warning: nodesetup.zip file needs updating in ISY"? I have downloaded and applied it numerous times, with rebooting the NodeLink and ISY still get this message.

The ISY component and NodeLink server versions have to match so that names and parameters co-ordinate.

v0.9.8 should be resolving your problems. Mine are fixed now with no more complaints from the software.

I temporarily check the auto-update when I want to monitor the upgrade but leave the auto-upgrade ISY on permanently as it only functions with the first option, anyway.

 

Link to comment
Share on other sites

So here is my setup. I am hoping I am doing this correctly. Please update me if I am not.

 

NodeLink Server v.0.9.8

System Config page - 
Port: 8090
ISY address: ISY
ISY username: using admin username (will not accept any other user) - Get error message "ISY Error: Login failure (verify ISY user/password on the system config page.)
ISY password: using admin password (will not accept any other user) - 
Use HTTPS: unchecked
Logging Level: Notice
Require password to access NodeLink pages: unchecked
Enable Relay Server: unchecked
Enable daily program update check: unchecked
Enable EmonCMS: unchecked
Request Timeout: 5
Retry Delay: 30
REST Delay: 100
Use HTTP Keep-Alive: checked

Devices page - 

Auto-Update ISY: checked
Installed Devices:
* Nickname: gem1
* ISY Nodename: gem1
* Device Type: Brultech GreenEye Monitor

gem1 page - 

Use Serial instead of TCP: unchecked
GEM Address: 192.168.2.5 (this is the address of the GEM)
GEM Port: 8000
Create Virtual Main from Channels 1 & 2: unchecked
Send Multiplier: 1
Runtime Trigger (watts): 10
Channel Count: 0
Log Level: Notice
Enable Repeater Function: unchecked
Send Data to SEG: unchecked
Site Token: BLANK
SEG Node (No Spaces Allowed): GEM

Main page:

2018-02-20 20:29:27 - ISY NodeLink Server v0.9.8 started
2018-02-20 20:29:27 - Web config server started (http://192.168.2.250:8090)
2018-02-20 20:29:27 - ISY resolved to 192.168.2.4
2018-02-20 20:29:27 - ISY Node Server config detected (profile 1)
2018-02-20 20:29:28 - Warning: nodesetup.zip file needs updating in ISY
2018-02-20 20:29:49 - GEM: Socket Error - Connection refused. [gem1]
2018-02-20 20:29:58 - GEM: Socket Error - Send Data - A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied [gem1]
2018-02-20 20:29:58 - GEM: Reconnected [gem1]

ISY Node Server Configuration - 

Profile Name: isylink
User ID: BLANK
Password: BLANK
Base URL: isylink
Host Name: 192.168.2.250 (This is the IP of where NodeLink is running from)
SSL: unchecked
Port: 8090
Timeout: 10
Isy User: 0

 

What am I missing here? I think I have EVERYTHING setup correctly. Firewall is turned off on the computer running the NodeLink Server. Please help me understand what I am missing.

Link to comment
Share on other sites

5 minutes ago, io_guy said:

Try opening port 8000 to the GEM with putty and a raw socket.  You should see data coming in.  

Nope nothing on port 8000, after about 10 seconds get "Network Error: Connection timed out".

 

While this was malfunctioning, I did setup (successfully) SmartEnergyGroups.com and they are monitoring the power and getting data correctly. I can log into the Setup mode of the webpage, and still see live data. But I did set this up with the free Community stream, so I am surpassing the amount of free streams.... (Will be deleting the account soon.)

Link to comment
Share on other sites

Well.... this is interesting. Using the GEM Network utility. I changed the local port from 80 to 8000. The main page of NodeLink Server v.0.9.8 is looking different

2018-02-20 21:31:55 - ISY NodeLink Server v0.9.8 started
2018-02-20 21:31:55 - Web config server started (http://192.168.2.250:8090)
2018-02-20 21:31:55 - ISY resolved to 192.168.2.4
2018-02-20 21:31:55 - ISY Node Server config detected (profile 1)
2018-02-20 21:31:56 - Warning: nodesetup.zip file needs updating in ISY
2018-02-20 21:32:26 - GEM: Socket Error - Send Data - Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'. [gem1]
2018-02-20 21:32:26 - GEM: Reconnected [gem1]

This is new.

Link to comment
Share on other sites

However I am still getting the error message:

2018-02-20 21:44:53 - GEM: Socket Error - Send Data - Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'. [gem1]
2018-02-20 21:44:53 - GEM: Reconnected [gem1]

But other things are populating on the dashboard. :):):):):):) 

Link to comment
Share on other sites

Archived

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


×
×
  • Create New...