Just throwing my name into the pool. Same story here.

-Xathros

Same here.

I just received an email from ecobee acknowledging UDI access. I stopped the plugin days ago when the trouble started. I restarted it but still only the controller node. Tried discover but no luck.

When I looked in the log there are no errors, the plugin seems to be able to access ecobee, not sure why the thermostats don't populate.

I've been working with Michele and we discovered Ecobee has shut us down. No path forward at this point. Will continue to investigate.

I guess I will not be buying anymore Ecobee sensors if they just bricked them all. I wish I would have not bought so many already because now they are worthless and none of my ceilng fans or other programs work anymore. I really hope they reconsider. If not, then I'll reconsider using ecobee as my thermostat.

I've had my Ecobee for several years and it has been very reliable! I really hate cloud based stuff because this is what can happen and with little to no warning. If there is no path forward my next T-Stat will be local API based, possibly a Venstar CT, not sure on Z-Wave.

The cloud API is returning 500s, during NS discover, which is not a good sign.

https://api.ecobee.com:443 "GET /1/thermostatSummary?json=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx HTTP/1.1" 500 None

Since it looks like Ecobee is on the way out, does anyone have any experience with any of the other thermostat options that work with eisy? One thing I am looking for is one that has the option of remote sensors that will integrate to the thermostat.

1 hour ago, BVincent said:

Since it looks like Ecobee is on the way out, does anyone have any experience with any of the other thermostat options that work with eisy? One thing I am looking for is one that has the option of remote sensors that will integrate to the thermostat.

I've used the Venstar color touch series. It has a local api. It has a cloud service which can be handy, but that is not required for local operation. It can be turned off, but that's how their app gets to the stat.

It has significant HVAC features programmable from the stat. They also sell wireless temperature remotes that are a little bigger and designed to screw to a jbox but can also be put on the wall.

My experience is that the ecobee is more fire-n-forget and has more convenience features. I had many iox programs for the Venstar and only a few for the ecobee. The ecobee looks more friendly, less techy and family members felt more comfortable setting it.

Edit: It's been a few years since I had a color touch. I used their WiFi remotes but I no longer see them on their sales page... No wireless remote. They do have hardwired ones.

Edited 7 hours ago7 hr by paulbates

1 hour ago, BVincent said:

Since it looks like Ecobee is on the way out, does anyone have any experience with any of the other thermostat options that work with eisy? One thing I am looking for is one that has the option of remote sensors that will integrate to the thermostat.

I have YoLink sensors which, via programming, control my Insteon thermostats (no plugin needed and are available on eBay) which control my heat pump.

We are working with Ecobee to find a solution and not be forced to pay a large fee.

Well have to reduce the polling frequency greatly, and probably get rid of forecasts. Hopefully we can get Ecobee to turn our access back on while we investigate.

I figured the collective group using the UDI developer pin were probably exceeding the monthly cloud hits. Thought I saw it was 85,000 hits per month.

2 hours ago, Jimbo.Automates said:

We are working with Ecobee to find a solution and not be forced to pay a large fee.

Well have to reduce the polling frequency greatly, and probably get rid of forecasts. Hopefully we can get Ecobee to turn our access back on while we investigate.

I was not sure the Ecobee forecasting is superior to others, so I use OpenWeather for forecasts... current and future. The user controls the polling by setting the number of times per day the polling occurs and then you have to multiply that by the number of days out you want to forecast. In their current setup you do have post a credit card, but if the polling is low there is no charge... I think it was free below 1000 per day. This is just an example of options, I am sure there are others that will work for forecasting. So if giving that up helps get re-enabled, it is workable.

3 hours ago, Jimbo.Automates said:

We are working with Ecobee to find a solution and not be forced to pay a large fee.

Well have to reduce the polling frequency greatly, and probably get rid of forecasts. Hopefully we can get Ecobee to turn our access back on while we investigate.

Not using forecasts here. Wouldn't miss it. (But certainly do miss not being able to control the thermostat!)

If Ecobee is incurring a cost to provide the forecast, I could understand their position, but otherwise, this seems pretty boneheaded on their part.

If forecasts is the main issue, and if it can be enabled/disabled on Ecobee's end for each key, then maybe split the plug-in up into two versions. One with forecasts that has a higher or recurring cost, and one without that just supports device control.

But like others have said, this may get me looking at other thermostats.

It's not a cost specifically for forecasts, it's a huge cost for polling in general. Removing forecasts will just help reduce the polling. There are options to greatly reduce polling, but at this point it looks like they will not turn us back on unless UDI pays them a large sum. There is another option to use a HomeKit emulator but that is a major effort. Ecobee added Apple Homekit support, but are ignoring thread/matter support so far even though their newer thermostats have the radios which could support it.

I'll be looking into using Matter enabled Nest 4^th Gen ($99) or Meross thermostat ($60) per suggestion from @Michel Kohanim

If we have our API developer key do you think it is possible we could make our own plugin and not be charged or be cutoff due to large amounts of network calls? Thank you.

1 hour ago, Jimbo.Automates said:

There is another option to use a HomeKit emulator but that is a major effort. Ecobee added Apple Homekit support

That's what HA HomeKit Integration uses and is very much limited by HomeKit Accessory Protocol (HAP), which is Apple's definition of a thermostat vs the depth of the Ecobee Developer API. It's a big gap and not apples-to-apples. Adopting that would mean losing capability we have today

1 hour ago, Jimbo.Automates said:

It's not a cost specifically for forecasts, it's a huge cost for polling in general. Removing forecasts will just help reduce the polling. There are options to greatly reduce polling, but at this point it looks like they will not turn us back on unless UDI pays them a large sum. There is another option to use a HomeKit emulator but that is a major effort. Ecobee added Apple Homekit support, but are ignoring thread/matter support so far even though their newer thermostats have the radios which could support it.

I'll be looking into using Matter enabled Nest 4^th Gen ($99) or Meross thermostat ($60) per suggestion from @Michel Kohanim

FWIW, I just spent some time talking with Ecobee tech support and politely but firmly let them know this particular customer wasn't very happy with how they handled this (and that I wasn't the only one).