I've switch over to v5.0.10 on my ISY994 and also transitioned over to Nodelink v0.6.10 from DSCLink. I have the DSC alarm panel setup and working as it should but I am having problems with my Ecobee4. 

 

I've resquested the 3rd party pin and added the apps on the Ecobee website. It is not updating the information in the NodeLink Server. The following error message is in the log:

 

Ecobee Web Error - The request timed out [ecobee1]

Ecobee Timer Error - Expecting element 'root' from namespace ''.. Encountered 'None'  with name '', namespace ''. [ecobee1]

 

It is showing up at roughly 3 minute intervals.

 

Any help to get this resolved would be appreciated.

 

Thanks io_guy,

 

Adding the ability to manual set the web time out in the ecobee settings of the NodeLink server has resolved the error I was receiving.

Hi

I just recently bought the ecobee4. Is the ecobee device in Nodelink compatible with ecobee4? I am getting this error. I hope anyone can help.

2017-07-30 15:50:12 - Ecobee Web Error - The remote server returned an error: (401) Unauthorized. [ecobee1]
2017-07-30 15:50:13 - Ecobee Web Error - The remote server returned an error: (400) Bad Request. [ecobee1]
2017-07-30 15:50:13 - Ecobee: Error refreshing tokens - if this continues try setting a new app pin [ecobee1]
2017-07-30 15:50:57 - Ecobee Web Error - The remote server returned an error: (401) Unauthorized. [ecobee1]
2017-07-30 15:50:57 - Ecobee Web Error - The remote server returned an error: (400) Bad Request. [ecobee1]
2017-07-30 15:50:57 - Ecobee: Error refreshing tokens - if this continues try setting a new app pin [ecobee1]
2017-07-30 15:52:05 - Ecobee Web Error - The remote server returned an error: (401) Unauthorized. [ecobee1]
2017-07-30 15:52:05 - Ecobee Web Error - The remote server returned an error: (400) Bad Request. [ecobee1]
2017-07-30 15:52:05 - Ecobee: Error refreshing tokens - if this continues try setting a new app pin [ecobee1]

I have an Ecobee 4 working with the newest update of NodeLink, I was receiving an error on a timeout issue due to my satellite internet. Your error is different from the one I was getting and it may be from the request to the server are to frequent. Believe Ecobee only allows polling to the servers every 3 minutes.

Hi,

I turned on verbose logging and getting this error. I hope someone can guide me on how to fix this.

 

Thanks.

2017-07-30 22:26:31 - Ecobee Web Error - The remote server returned an error: (401) Unauthorized. [ecobee1]
2017-07-30 22:26:32 - Ecobee Web Error - The remote server returned an error: (400) Bad Request. [ecobee1]
2017-07-30 22:26:32 - Ecobee: Error refreshing tokens - if this continues try setting a new app pin [ecobee1]
2017-07-30 22:29:33 - Ecobee Web Error - The remote server returned an error: (401) Unauthorized. [ecobee1]
2017-07-30 22:29:33 - Ecobee Web Error - The remote server returned an error: (400) Bad Request. [ecobee1]
2017-07-30 22:29:33 - Ecobee: Error refreshing tokens - if this continues try setting a new app pin [ecobee1]
2017-07-30 22:31:13 - Ecobee Web Error - The remote server returned an error: (401) Unauthorized. [ecobee1]
2017-07-30 22:31:14 - Ecobee Web Error - The remote server returned an error: (400) Bad Request. [ecobee1]
2017-07-30 22:31:14 - Ecobee: Error refreshing tokens - if this continues try setting a new app pin [ecobee1]
2017-07-30 22:34:15 - Ecobee Web Error - The remote server returned an error: (401) Unauthorized. [ecobee1]
2017-07-30 22:34:15 - Ecobee Web Error - The remote server returned an error: (400) Bad Request. [ecobee1]
2017-07-30 22:34:15 - Ecobee: Error refreshing tokens - if this continues try setting a new app pin [ecobee1]
2017-07-30 22:37:16 - Ecobee Web Error - The remote server returned an error: (401) Unauthorized. [ecobee1]
2017-07-30 22:37:16 - Ecobee Web Error - The remote server returned an error: (400) Bad Request. [ecobee1]
2017-07-30 22:37:16 - Ecobee: Error refreshing tokens - if this continues try setting a new app pin [ecobee1]

Did you generate an app PIN and allow/enter it on the ecobee website?

 

It's kind of a backward process to other methods for security.

Hi larryllix,

Thank you for that tip. I did generate a pin and entered it in My Apps in ecobee website. Everything seems to be working now. However, I am not sure if this is normal, but the 'Schedule Type' is always showing as N/A. Is there no notification whether the schedule type is in 'HOME', 'AWAY' or 'SLEEP'?

 

Thanks

Hi larryllix,

Thank you for that tip. I did generate a pin and entered it in My Apps in ecobee website. Everything seems to be working now. However, I am not sure if this is normal, but the 'Schedule Type' is always showing as N/A. Is there no notification whether the schedule type is in 'HOME', 'AWAY' or 'SLEEP'?

 

Thanks

Did you check the NodeLink maintenance webpage to see what Nodeink has found?

 

This will tell you if the probem is between NL and ecobee's website ot between NL and your ISY. Perhaps it will take some time to update in ISY or the next schedule change. IIRC mine didn't have to wait but the updates can be very slow.

I typically find that Ecobee updates fairly quickly when something changes.  N/A for schedule type is definitely odd....granted I have a 3, but it always shows the correct schedule type.  Perhaps they did change something with 4? (Although that would be a curious action, unless they added more types or something.)

Oh there's nothing quick about it.  Their API requires a minimum 3 minute wait between polls (no data is updated quicker than that).  Excluding this "runtime" data, the other stuff is on a 15 minute cycle.

 

Ecobee 2/3/4 use the API and rate.