I'm running V5.0.13D firmware on my ISY, and Nodelink V0.9.19 on a VM.  As of a couple of days ago, I can read settings and data from the thermostats via the ISY admin console, but I cannot send any commands to change anything on the thermostats.  Similarly, I have a few programs that send commands to the thermostats and those commands no longer seem to have any effect. 

I have the log level set to "debug" on the thermostat screen, but am not seeing anything showing up in the web display for Nodelink except a message along the lines of "TCC Get StatusError - Forbidden [hwstat2]" maybe once or twice a day.  I know that Honeywell was working to fix some things re: communications with their servers recently, but is anyone else experiencing any issues with controlling Honeywell thermostats?  

 

 

Lesson number 1 ... when in doubt, reboot.  I restarted the machine and VM running Nodelink, and the thermostats appear to be responding again.  Not sure what happened, but if I'll repost if it occurs again.  Sorry for the false alarm ....

 

 

I am seeing this issue on and off as well. Reboot works then after some time it errors out. Make sure your MONO is updated though. I was thinking maybe a CRON reboot but that’s not a real fix.

EDIT: Related link here 

 

Edited August 31, 20187 yr by Scottmichaelj

16 hours ago, Scottmichaelj said:

Reboot works then after some time it errors out.

Yes ... this is what I'm seeing.  Things worked for a while after I rebooted yesterday, but today it's back in the same state.  The ISY seems to be reading data from the thermostats, but I can't make changes from the ISY to the thermostats.  I'm running Mono 5.10.0.160.  Will try updating to see if that helps.

Yes ... this is what I'm seeing.  Things worked for a while after I rebooted yesterday, but today it's back in the same state.  The ISY seems to be reading data from the thermostats, but I can't make changes from the ISY to the thermostats.  I'm running Mono 5.10.0.160.  Will try updating to see if that helps.

I am on the newest version of Mono and it didn’t help but always good to keep up to date.

Same is true for me Scott

I have an ISY program that runs a few times a week and calls a network resource to Nodelink's relay server. I use it's REBOOT command a few times a week to restart the pi. Not as elegant as setting up process monitoring on the pi, but easy for me to do.

Edited September 1, 20187 yr by paulbates

The problem with TCC is it's a webscrape.  The Honeywell server could be doing a dozen different things to recognize that I'm cheating the system vs. a proper API (which they won't release).  

Every time you tell me it doesn't work it's a different error in the log (Forbidden vs Timeout vs Nameserver).  

I don't own a Honeywell stat so I can't really play much.  

Honestly wish I never made a driver for it.  It's more pain than it's worth. 

The problem with TCC is it's a webscrape.  The Honeywell server could be doing a dozen different things to recognize that I'm cheating the system vs. a proper API (which they won't release).   Every time you tell me it doesn't work it's a different error in the log (Forbidden vs Timeout vs Nameserver).  

I don't own a Honeywell stat so I can't really play much.  

Honestly wish I never made a driver for it.  It's more pain than it's worth. 

 

 

Well we all are grateful and understand your position. Since you do have my account info still could you run it for a bit on your side and I will stop running NodeLink on my end? Maybe you will find something that way?

 

Edit: Another thought is, could you build in a check within NodeLink that if you get two of any TCC error to auto reboot? The only issue would be is if someone is using NL for two things?

 

You don't need to stop using, both can be connected.  I'll start it up tomorrow and keep it running, see what happens.

Auto-reboot would be a last resort, that's a pretty big band-aid.

Been running your TCC on my system since Saturday, 3 timeouts and no issues.  But that was on Win10.

I've moved it over to a Pi now and will watch again.

On 8/31/2018 at 5:02 PM, dwengrovitz said:

Will try updating to see if that helps.

I updated Mono to 5.14.0.177 on my Mac.  Things seemed to work okay for a few days but then hung up again.  Rebooted the machine and I'm back online.  

Any v5 mono is fine, that's not the issue.

On 8/31/2018 at 8:18 PM, paulbates said:

Same is true for me Scott

I have an ISY program that runs a few times a week and calls a network resource to Nodelink's relay server. I use it's REBOOT command a few times a week to restart the pi. Not as elegant as setting up process monitoring on the pi, but easy for me to do.

You might want to see if the latest version resolves your issue too.  Some of the changes affected Venstar as well.  

On 9/11/2018 at 12:09 AM, io_guy said:

You might want to see if the latest version resolves your issue too.  Some of the changes affected Venstar as well.  

Thanks. Functionality has always been fine, its been a slow increase in memory allocation over time by Mono until it crashes. 

I did look initially and it still seemed to be doing it a little, but TBH I didn't watch closely over a few days.  I'll monitor this weekend and see how it does over time

Paul

On 9/11/2018 at 12:09 AM, io_guy said:

You might want to see if the latest version resolves your issue too.  Some of the changes affected Venstar as well.  

io_guy, that did address it. I backed off how frequently my pi restart was needed until not restarting at all.  Thanks!

Paul