NodeLink: Honeywell TCC - Can't change values in A.C.

[memphis2k]

Running ISY v5.15A and just installed NodeLink on a Windows 2019 Server.  On the main page ISY Admin Console, I get all of the Honeywell Thermostat info, and then in the HEAT dropdown, say I set it 68 and it goes right back to 67.  I opened 2405 (TCP/UDP) outgoing in my firewall.  Relay server is enabled.

 

Any thoughts?

 

log.txt

[io_guy]

Verify your node server settings in the ISY (address and port).   

If they're correct enable debug on the NodeLink system config page and on the main page to see if Nodelink is actually getting the request from the ISY.  

[memphis2k]

2019-05-03 15:41:10 - Web Request: /config.htm
2019-05-03 15:41:24 - Web Request: /isylink/nodes/n001_hwstat1/cmd/CLISPH/71/14
2019-05-03 15:41:24 - TCC Set StatusError: OK [hwstat1]
2019-05-03 15:41:26 - Web Request: /isylink/nodes/n001_hwstat1/cmd/CLISPH/76/14
2019-05-03 15:41:26 - TCC Set StatusError: OK [hwstat1]
2019-05-03 15:41:27 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><climate enabled="true" locationId="MID_MN098" rss="http://wx.hamweather.com/?pands=MID_MN098" lastUpdatedTS="2019/05/03 15:31:37"><Temperature>55 °F</Temperature><Temperature_High>55 °F</Temperature_High><Temperature_Low>39 °F</Temperature_Low><Feels_Like>55 °F</Feels_Like><Temperature_Average>44.1 °F</Temperature_Average><Humidity>69 %</Humidity><Pressure>200.02 inHg</Pressure><Dew_Point>45 °F</Dew_Point><Wind_Speed>4 mph</Wind_Speed><Wind_Direction>SW</Wind_Direction><Gust_Speed>9 mph</Gust_Speed><Total_Rain_Today>0 inches</Total_Rain_Today><Light>88 %</Light><Evapotranspiration>0 inches/day</Evapotranspiration><Irrigation_Requirement>0 inches</Irrigation_Requirement><Water_Deficit_Yesterday>0 inches</Water_Deficit_Yesterday><Elevation>909 </Elevation><Coverage>0</Coverage><Intensity>0</Intensity><Weather_Condition>0</Weather_Condition><Cloud_Condition>1</Cloud_Condition><Average_Temperature_Tomorrow>48 °F</Average_Temperature_Tomorrow><High_Temperature_Tomorrow>58 °F</High_Temperature_Tomorrow><Low_Temperature_Tomorrow>37 °F</Low_Temperature_Tomorrow><Humidity_Tomorrow>49 %</Humidity_Tomorrow><Wind_Speed_Tomorrow>10 mph</Wind_Speed_Tomorrow><Gust_Speed_Tomorrow>15 mph</Gust_Speed_Tomorrow><Rain_Tomorrow>0 inches</Rain_Tomorrow><Snow_Tomorrow>0 inches</Snow_Tomorrow><Coverage_Tomorrow>13</Coverage_Tomorrow><Intensity_Tomorrow>2</Intensity_Tomorrow><Weather_Condition_Tomorrow>14</Weather_Condition_Tomorrow><Cloud_Condition_Tomorrow>3</Cloud_Condition_Tomorrow><Forecast_Average_Temperature>52 °F</Forecast_Average_Temperature><Forecast_High_Temperature>62 °F</Forecast_High_Temperature><Forecast_Low_Temperature>41 °F</Forecast_Low_Temperature><Forecast_Humidity>61 %</Forecast_Humidity><Forecast_Rain>0 inches</Forecast_Rain><Forecast_Snow>0 inches</Forecast_Snow><Forecast_Coverage>3</Forecast_Coverage><Forecast_Intensity>2</Forecast_Intensity><Forecast_Weather_Condition>15</Forecast_Weather_Condition><Forecast_Cloud_Condition>4</Forecast_Cloud_Condition></climate> (climate)
2019-05-03 15:41:41 - Web Request: /isylink/nodes/n001_hwstat1/cmd/CLISPH/83/14
2019-05-03 15:41:41 - TCC Set StatusError: OK [hwstat1]
2019-05-03 15:43:22 - Web Request: /index.htm

Like a fool, I had put the wrong IP address in the ISY for NodeLink.  Now I'm seeing the requests.  Still no change.  Verifying by the app on my phone.

[paulbates]

if you made changes to your node config, you might want to reboot the ISY.  

Also, you mentioned firewall rules between LAN devices, you sure everything's opened between the 3 participants:

ISY <> Nodeserver <> device

Paul

[io_guy]

Turn off the "System Config" debug and turn on debug on the honeywell tab now.  The send is happening but failing, need to see why.

2019-05-03 15:41:24 - TCC Set StatusError: OK [hwstat1]

[memphis2k]

On 5/3/2019 at 4:39 PM, paulbates said:

if you made changes to your node config, you might want to reboot the ISY.  

Also, you mentioned firewall rules between LAN devices, you sure everything's opened between the 3 participants:

ISY <> Nodeserver <> device

Paul

Thanks Paul, It was an internal port blocking issue.  I fiddled with a couple settings in my UTM and I can change the values.