Ecobee PIN request error

[Basenji]

My Nodelink was not talking to Ecobee, so I requested a new PIN and keep getting this:

 

NodeLink Server v0.9.16 started
2018-07-07 15:27:36 - OS: Linux raspberrypi 4.4.11-v7+ #888 SMP Mon May 23 20:10:33 BST 2016 armv7l GNU/Linux
2018-07-07 15:27:36 - Mono version: 3.2.8 (Debian 3.2.8+dfsg-10)
2018-07-07 15:27:36 - Mono version: Recommend moving to >= 4.6 (see latest how-to)
2018-07-07 15:27:36 - Web config server started (http://192.168.1.7:8090)
2018-07-07 15:27:36 - ISY resolved to 192.168.1.9
2018-07-07 15:27:37 - ISY Node Server config detected (profile 1)
2018-07-07 15:27:37 - ISY Warning: Duplicate node names exist on the ISY (Fan High Button)
2018-07-07 15:27:37 - ISY Warning: Duplicate node names exist on the ISY (Fan Low Button)
2018-07-07 15:27:37 - ISY Warning: Duplicate node names exist on the ISY (Fan Off Button)
2018-07-07 15:27:37 - ISY Warning: Duplicate node names exist on the ISY (Closet Light)
2018-07-07 15:27:45 - Ecobee Get Error - Invalid certificate received from server. Error code: 0xffffffff800b010a [ecobee1]
2018-07-07 15:27:45 - Ecobee Timer Error - Expected element was 'root', but the actual input element was '' in namespace '' [ecobee1]
2018-07-07 15:28:38 - Ecobee Get Error - Invalid certificate received from server. Error code: 0xffffffff800b010a [ecobee1]
2018-07-07 15:28:38 - Ecobee Timer Error - Expected element was 'root', but the actual input element was '' in namespace '' [ecobee1

 

I deleted the node and reinstalled with no luck, any help please!
 

[larryllix]

22 minutes ago, Basenji said:

My Nodelink was not talking to Ecobee, so I requested a new PIN and keep getting this:

 

NodeLink Server v0.9.16 started
2018-07-07 15:27:36 - OS: Linux raspberrypi 4.4.11-v7+ #888 SMP Mon May 23 20:10:33 BST 2016 armv7l GNU/Linux
2018-07-07 15:27:36 - Mono version: 3.2.8 (Debian 3.2.8+dfsg-10)
2018-07-07 15:27:36 - Mono version: Recommend moving to >= 4.6 (see latest how-to)
2018-07-07 15:27:36 - Web config server started (http://192.168.1.7:8090)
2018-07-07 15:27:36 - ISY resolved to 192.168.1.9
2018-07-07 15:27:37 - ISY Node Server config detected (profile 1)
2018-07-07 15:27:37 - ISY Warning: Duplicate node names exist on the ISY (Fan High Button)
2018-07-07 15:27:37 - ISY Warning: Duplicate node names exist on the ISY (Fan Low Button)
2018-07-07 15:27:37 - ISY Warning: Duplicate node names exist on the ISY (Fan Off Button)
2018-07-07 15:27:37 - ISY Warning: Duplicate node names exist on the ISY (Closet Light)
2018-07-07 15:27:45 - Ecobee Get Error - Invalid certificate received from server. Error code: 0xffffffff800b010a [ecobee1]
2018-07-07 15:27:45 - Ecobee Timer Error - Expected element was 'root', but the actual input element was '' in namespace '' [ecobee1]
2018-07-07 15:28:38 - Ecobee Get Error - Invalid certificate received from server. Error code: 0xffffffff800b010a [ecobee1]
2018-07-07 15:28:38 - Ecobee Timer Error - Expected element was 'root', but the actual input element was '' in namespace '' [ecobee1

 

I deleted the node and reinstalled with no luck, any help please!
 

Did you insert the PIN approval number into your ecobee account successfully first?

[Basenji]

Never got the pin number that usually dhows up in the history when you click the request PIN button.  I just get the invalid cert error as above

 

[larryllix]

48 minutes ago, Basenji said:

Never got the pin number that usually dhows up in the history when you click the request PIN button.  I just get the invalid cert error as above

 

You are running an old version of mono. There may be compatibility problems there but io_guy would be the one to know about that. The error messages have recommendations in them.

What RPi version are you running? I had trouble with mono v5.0.?? installing on my RPi 1.

However  mono  installed no problems this week, on  the same RPi with the latest mono version install.

[larryllix]

The last few days I had symptoms that NodeLink wasn't working with my ecobees on ISY HVAC things that didn't seem to function. My logger was reporting my HVAC ran 24 hours the previous day etc...

Looking at NodeLink web page I discovered the ecobee Nodes were blank. I got a comm failure a few days before  but ignored it as I thought it corrected at that time. (Need better repetitive notification program in ISY).

I entered the ecobee web app and deleted the current PIN and then generated a new pin in Nodelink. Looking in the NodeLink main tab logging, I could not find the newly generated PIN. I repeated the "generate new PIN" several times but could not find any occurrence of a reported new PIN. Checked the config.xml file and  nothing PIN related found. Then I changed the logging level to debug but it didn't help, either. Eventually I found a line further up with mention of a four char PIN embedded in a line. Not like it reported  before at all, and very obscure.

Anyway, I think when I signed up for an ecobee stat purchase rebate, there was mention of giving access to my stats for utility access. Since the process was really jumping from page to page I am not sure what transpired exactly but thought I can always straighten it out later. I found two apps installed into the ecobee setup which I deleted both but this is right about the same time my ecobee access via NodeLink stopped. The second app was not apparent or visible until the NodeLink app access was deleted.

My conclusion is that ecobee has more problems sharing their API and can destroy the existing setup with NodeLink for users when they add in a new app PIN.