Honeywell TCC - Thermostat Node visible but empty

[stmrocket]

First, thank you for another WONDERFUL program!  I can't wait to integrate it into my system.  Hopefully someday you will be inspired to add a definition for the Nuvo GC system (I don't think I am talented enough to code the entire nodeserver unfortunately).

 

Anyway, I Set up Nodelink and added it as a node server, added the thermostat and installed the node.  When I look in Admin Console, a device named Honeywell with the correct address shows but there is nothing displayed for it.  Am I doing something wrong?

[io_guy]

Try reloading the zip file and reboot the ISY. Many users are reporting this as a 5.0.2 bug (needing to install a zip multiple times).

[stmrocket]

After a couple reload / reboot cycles, the fields and drop-down menus show up but the fields are blank.  On two thermostats, the current temperature, heat and cool setpoints are visible but nothing else.    Below is my NodeLink log since the last reboot.  I'll keep tinkering with it and see if I can shed more light on what is causing this...

2016-02-09 21:56:47 - ISY NodeLink Server v0.3.3 started
2016-02-09 21:56:47 - Web config server started XXXXXXXXXXXXXXXXX
2016-02-09 21:56:48 - ISY resolved to XXXXXXXXXXXX
2016-02-09 21:56:51 - ISY Error: Duplicate node names exist on the ISY (Dining Room Lamp)
2016-02-09 21:56:51 - ISY Error: Duplicate node names exist on the ISY (Office Lamp)
2016-02-09 21:56:51 - ISY Error: Duplicate node names exist on the ISY (Den Lamps)
2016-02-09 21:56:51 - ISY Error: Duplicate node names exist on the ISY (Den Table Lamp)
2016-02-09 21:56:51 - ISY Error: Duplicate node names exist on the ISY (Guest Closet Light)
2016-02-09 21:56:51 - ISY Error: Duplicate node names exist on the ISY (Popcorn Popper)
2016-02-09 21:56:51 - ISY Error: Duplicate node names exist on the ISY (Shed Porch Light)
2016-02-09 21:56:51 - ISY Error: Duplicate node names exist on the ISY (Den Light)
2016-02-09 21:56:51 - ISY Error: Duplicate node names exist on the ISY (Back Porch Light)
2016-02-09 21:56:51 - ISY Error: Duplicate node names exist on the ISY (Garage Fan)
2016-02-09 21:56:55 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 21:57:28 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 21:58:01 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 21:58:34 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 21:59:06 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 21:59:39 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:00:12 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:00:45 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:01:18 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:01:51 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:02:25 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:02:58 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:03:31 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:04:04 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:04:36 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:05:09 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:05:42 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:06:15 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:06:48 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:07:21 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:07:54 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:08:27 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:09:00 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:09:33 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:10:06 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:10:39 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)
2016-02-09 22:11:12 - ISY Error: The remote server returned an error: (404) Not Found. (ns/1/nodes/n001_z2tstat/report/status/CLIFS/null/68)

[io_guy]

Can you enable the verbose log for the stat (in NodeLink) and post or PM me your log?

Nodelink is failing to find the fan status for your stat so everything after that fails.

If I can get your log I can find out the issue pretty easily since it'll give me your webpage data.

[stmrocket]

PM sent.  mdfstat and z1stst both have no data on the ISY while z2stat and z3stat show the partial data mentioned above.

[lsibarra]

Hi,

Can someone help me how I can correct my outdoor temp for my Honeywell TCC tstat? After updating nodesetup.zip profile in my ISY, i was able to successfully connect my Honeywell TCC tstat. However, I noticed that the outdoor temp and humidity does not match with what is published in the TCC website when logged in. See my screenshot.

 

Thanks.

[paulbates]

Hi

 

Are you also using the most recent version of Nodelink?

 

If yes, 

• Try restarting Nodelink with the button on its System Config page
• If that doesn't do it, restart the ISY.

Paul

[lsibarra]

Hi, I am running Nodelink Server v0.6.7 with ISY firmware 5.0.2.

 

After restarting the Nodelink, I am now getting these error messages

 

2017-02-08 12:22:14 - ISY NodeLink Server v0.6.7 started
2017-02-08 12:22:14 - ISY resolved to <isy_ip_address>
2017-02-08 12:22:14 - Web config server started (http://<rpi_ip_address>)
2017-02-08 12:22:14 - ISY Node Server config detected (profile 1)
2017-02-08 12:22:15 - Warning: nodesetup.zip file needs updating in ISY
2017-02-08 12:22:15 - DSC: Connected to <envisalink_ip_address> [dsc1]
2017-02-08 12:22:15 - DSC: EVL User Login - Password Sent [dsc1]
2017-02-08 12:22:15 - DSC: Status Request Sent [dsc1]
2017-02-08 12:22:15 - DSC: Data Sent - 00191 [dsc1]
2017-02-08 12:22:15 - Relay Server: Started on port 2405
2017-02-08 12:22:16 - DSC: System Status - Disarmed (Set By Status Request - Partition 1) [dsc1]
2017-02-08 12:22:24 - DSC: System Status - Disarmed (Set By Status Request - Partition 1) [dsc1]
2017-02-08 12:22:46 - Subscription Error: Heartbeat timeout, re-subscribing to ISY
2017-02-08 12:23:17 - Subscription Error: Heartbeat timeout, re-subscribing to ISY
2017-02-08 12:23:17 - Subscribed to ISY
 

The nodesetup.zip file I uploaded was from this link:

http://automationshack.com/Files/nodesetup.zip

 

Is this the most recent nodesetup.zip file?

 

Thanks for your help.

[paulbates]

The Nodesetup zip setup should be ok for TCC & DSC, and its a fine line: Nodelink supports many different types of devices including the TCC. If any of them change, a new profile can be issued.. but those changes may not apply to TCC, DSC or you.

 

As an example, I use 2 devices, but their properties haven't changed in a long time. My nodelink tells me to upload the latest profile, but I ignore it because it doesn't apply to me. 

 

I did move from 5.02 to 5.04 about a year ago. I don't think 5.02 is the problem, but can't be sure.

[lsibarra]

Thanks for the explanation.

 

I am also getting this error from time to time. Do you have any idea what causing this error?

 

2017-02-08 13:15:46 - ISY Error: Error getting web response from the ISY (Error getting response stream (ReadDone4): ServerProtocolViolation)

[paulbates]

Nope, unfortunately that's a new one for me.  There's a routine set of messages I get from time to time, but those are based on the 2 device types I have... and things recover or are retried,  I don't have functionality problems.

 

Paul

[lsibarra]

Thanks Paul for your feedback . I will continue to monitor it.

 

Larry