Thursday, October 4, 2018

2018-10-04 17:05:10 - Ecobee Web StatusError - BadRequest [ecobee1]

Still non-operational. Ecobee.com admits they are doing maintenance.

Edited October 5, 20187 yr by larryllix

 

18 hours ago, larryllix said:

Thursday, October 4, 2018

2018-10-04 17:05:10 - Ecobee Web StatusError - BadRequest [ecobee1]

Still non-operational. Ecobee.com admits they are doing maintenance.

Friday, October 5, 2018

It seems NodeLink caved and issued a new pin so data could never resume.
Reboot, new pin obtained, found, and installed into ecobee.com, back up and running.

9 minutes ago, larryllix said:

 

Friday, October 5, 2018

It seems NodeLink caved and issued a new pin so data could never resume.
Reboot, new pin obtained, found, and installed into ecobee.com, back up and running.

Yeah, I noticed it was failing last night and did the same drill with the new PIN, but it was still failing.  It looks like it's working now.

8 minutes ago, rccoleman said:

Yeah, I noticed it was failing last night and did the same drill with the new PIN, but it was still failing.  It looks like it's working now.

I understand that NodeLink wants to try everything it can to get the connection back but I am not sure "giving up on the old pin" is the best idea  that point. The new pin is really hard to find when requested now. I had to request a new one about 5-6 times. Maybe it  only shows up with "Debug" level?

 

Another issue I just discovered: A logfile is not created every day. This may be due to nothing to log using  "Notice" mode and be related to the errors I still get, complaining at 23:59:45 most nights.... No events to write to the file and an error is reported. Very minor, with no apparent effect, and I have been ignoring it lately.

Edited October 5, 20187 yr by larryllix

Nodelink doesn't "give up" for a new pin.  This would have been forced by some sort of reset on ecobee's servers. 

Tuesday, October  23, 2018

   ---- Ecobee webpage access is refusing connection at this time.

2018-10-23 17:01:34 - Ecobee Post Error - Timeout [ecobee1]
2018-10-23 17:04:38 - Ecobee Web StatusError - ServiceUnavailable [ecobee1]
2018-10-23 17:07:53 - Ecobee Get Error - Timeout [ecobee1]

Nodelink has been unable to connect to Ecobee for a couple of days now, and is currently giving me the following error:

Quote

2018-11-17 11:37:22 - Ecobee: New tokens received from ecobee.com [dnecobee]
2018-11-17 11:37:22 - Ecobee Web StatusError - InternalServerError [dnecobee]

I was hoping that it would just get better on its own, but it hasn't, and removing and re-adding the NodeLink app on the Ecobee site isn't helping.

I have a program that runs when my home/away trigger tries to change the thermostats to home/away, and then tells me if it doesn't succeed.  It looks like it started to fail on Nov 15 at around 11:30am PST.

Same thing happening to others?

Edited November 17, 20187 yr by rccoleman

1 hour ago, rccoleman said:

Nodelink has been unable to connect to Ecobee for a couple of days now, and is currently giving me the following error:

I was hoping that it would just get better on its own, but it hasn't, and removing and re-adding the NodeLink app on the Ecobee site isn't helping.

I have a program that runs when my home/away trigger tries to change the thermostats to home/away, and then tells me if it doesn't succeed.  It looks like it started to fail on Nov 15 at around 11:30am PST.

Same thing happening to others?

I have also had a lot of problems with ecobee3&4 / NodeLink over the last few days. 

I suspect an elusive problem yet with NodeLink/mono/RPi working together. It seems once I get an error or two reported, the errors seems to increase for days until the system sometimes fails.
I have noticed when errors seem to get out of control, rebooting NodeLink can make the problem go away. Sometimes rebooting Nodelink can make the problem get worse until it is rebooted or the whole RPi is rebooted again. This would tend to indicate  some initialisation problem with the system. Mostly it works very well and is quite impressive but once problems start they seem to escalate.

IMHO, ecobee is also making changes unannounced to anybody. Ecobee has demonstrated this poor attitude in the past, many times.  However, this should be showing up with PolyGlot testers also,  and I don't hear many  rumblings there.... yet.

Mine ecobee/NodeLink is working quite well again today after rebooting several times yesterday. 

2018-11-16 09:08:07 - ISY NodeLink Server v0.9.21 started
2018-11-16 09:08:28 - OS: Linux rpi3 4.9.59-v7+ #1047 SMP Sun Oct 29 12:19:23 GMT 2017 armv7l GNU/Linux
2018-11-16 09:08:28 - Mono version: 5.8.0.108 (tarball Fri Jan 19 18:55:10 UTC 2018)
2018-11-16 09:08:28 - Web config server started (http://192.168.0.175:8090)
2018-11-16 09:08:28 - ISY resolved to 192.168.0.161
2018-11-16 09:08:29 - ISY Node Server config detected (profile 1)
2018-11-17 12:19:54 - Ecobee Web StatusError - ServiceUnavailable [ecobee1]

Edited November 17, 20187 yr by larryllix

Finally working again.  Reboots didn't do anything & manual "apt-get update & upgrade" didn't help, but I noticed that Mono was held back at 5.12.xx.  I decided to try the installation script that io_guy recently posted, which updates to 5.16.xx and updates the launch script to match and I was still getting the same "InternalServerError".  Several attempts to remove NodeLink at ecobee.com and re-add it with a new app code didn't help, but I rebooted the rpi3 again, saw that Nodelink had given yet another app code, and that worked.  Now it seems like it's in sync and I'm getting data.  Hard to pin down exactly what was wrong, what fixed it, or even if it was anything I did.

11 minutes ago, rccoleman said:

Finally working again.  Reboots didn't do anything & manual "apt-get update & upgrade" didn't help, but I noticed that Mono was held back at 5.12.xx.  I decided to try the installation script that io_guy recently posted, which updates to 5.16.xx and updates the launch script to match and I was still getting the same "InternalServerError".  Several attempts to remove NodeLink at ecobee.com and re-add it with a new app code didn't help, but I rebooted the rpi3 again, saw that Nodelink had given yet another app code, and that worked.  Now it seems like it's in sync and I'm getting data.  Hard to pin down exactly what was wrong, what fixed it, or even if it was anything I did.

After hearing some of the snags, I have stuck with mono 5.8.xx so far.

2019-01-07 05:52:13 - Ecobee Web StatusError: ServiceUnavailable [ecobee1]
2019-01-07 05:55:13 - Ecobee Web StatusError: ServiceUnavailable [ecobee1]
2019-01-07 06:16:17 - Ecobee Web StatusError: ServiceUnavailable [ecobee1]
2019-01-07 06:19:32 - Ecobee Get Error: Timeout [ecobee1]
2019-01-07 06:22:47 - Ecobee Get Error: Timeout [ecobee1]
2019-01-07 06:26:02 - Ecobee Get Error: Timeout [ecobee1]
2019-01-07 06:29:17 - Ecobee Get Error: Timeout [ecobee1]
2019-01-07 06:32:32 - Ecobee Get Error: Timeout [ecobee1]
2019-01-07 06:35:47 - Ecobee Get Error: Timeout [ecobee1]
2019-01-07 06:39:02 - Ecobee Get Error: Timeout [ecobee1]
2019-01-07 06:42:17 - Ecobee Get Error: Timeout [ecobee1]
2019-01-07 06:45:32 - Ecobee Get Error: Timeout [ecobee1]
2019-01-07 06:48:47 - Ecobee Get Error: Timeout [ecobee1]
2019-01-07 06:52:02 - Ecobee Get Error: Timeout [ecobee1

 

They reported it this time!

ecobee.com will bee back soon!

We’re working on some improvements at the moment.
Don’t worry, we’ll be back up and running in no time!

---

Need help? Call us at 1 877 932 6233 or email support@ecobee.com