Starting a couple days ago my Ecobee thermostats stopped following the programs I have had for a few years. I ended up deleting and reinstalling the PG3 plugin a few times and setting that up. Orriginally it would find the 3 thermostats and other nodes related to the Ecobee but now I can't even get the nodes to populate. When I was able to get the nodes to populate I couldn't get the thermostats to update based on changes made in eisy and eisy would not update based on physical thermostat changes. Any one else having this issue or have advice?

Having the same problem. Started last night. Nodes not updating on IOX, cannot change node values. Restarted plug-in in PG3, had no effect. Restarted Eisy, and this cleared nodes in IOX to no values but not updating from PG3 plug-in. cold see teh node values in ecobee PG3 but could not get them to showup in IOX. Deleted, reinstalled, added key. See one node but thermostats not adding to PG3 now.

Added debug vebose log file with errors

Looks like ecobee changed something

Ecobee_4-17-2026_11623_PM.zip

I am seeing the same problem with my ecobee nodes

Hi @Jimbo.Automates , Same problem here. After reinstalling the plug-in, the plugin acts like it never gets authorized even though ecobee web site indicates success. I just get the controller node. See attached, is the first entry connection status to the thermostats?

Thank you

Same problem here also.

4 hours ago, tazman said:

Same problem here also.

And here. Is Jimbo still listening??

@Jimbo.Automates I am having the same issues as everyone else.

Ah HAH! Problems here too, but I've been having so many other network issues lately, I assumed the problem was mine alone.

Same problem here

Edited Saturday at 04:42 PM1 day by DColegrave

An issue for this has been opened on Github, but I'm not holding my breath. The last time the author posted any activity on Github was the start of June in last year.

Sure hope that is not the case, we paid for this plugin.

Give him a chance, it's the weekend, maybe he's away. He was on the forum yesterday, see attached.

Did you notice that an update was pushed to the thermostat? I've done some poking around and it seems to me, I could be wrong, that Ecobee may be kicking us out like Nest did a while back. I've tried to add Ecobee to Home Assistant and that isn't working out either. The API has probably changed and I found a notice that Ecobee is not allowing any more outside things. Hope I'm wrong about this because the node server has been fairly important to my programming.

I just checked my account on ecobee.com and checked the Developer page. I only see my Home Assistant application listed. Shouldn't Universal Devices (or whatever) be there too? It's been years since I set up the ecobee nodeserver and I don't remember how that all worked.

56 minutes ago, markv58 said:

Did you notice that an update was pushed to the thermostat? I've done some poking around and it seems to me, I could be wrong, that Ecobee may be kicking us out like Nest did a while back. I've tried to add Ecobee to Home Assistant and that isn't working out either. The API has probably changed and I found a notice that Ecobee is not allowing any more outside things. Hope I'm wrong about this because the node server has been fairly important to my programming.

The Home Assistant integration with my Ecobee seems to still be working fine. I sure hope Ecobee recognizes the significant value add from supporting integration with other home automation platforms!

32 minutes ago, carealtor said:

I just checked my account on ecobee.com and checked the Developer page. I only see my Home Assistant application listed. Shouldn't Universal Devices (or whatever) be there too? It's been years since I set up the ecobee nodeserver and I don't remember how that all worked.

After you log into Ecobee, click the user profile icon (top right) and then click My Apps. You should have an app named "UDI Polyglot (PIN)" registered in the list.

Mine stopped working so I deleted the plugin and reinstalled and now it will only find the controller, no nodes under that. Using the PIN worked but seemed to take twice to make the blue message go away. Did this three times and always took twice. When I look at the logs it seems to always be trying to discover. If I hit discover it says Controller:discover: Discovering Ecobee Thermostats already running?

My SmartThings integration to ecobee is still working.

11 minutes ago, bob123 said:

My SmartThings integration to ecobee is still working.

My Home Assistant integration is still working as well and I am not going to remove it and try to install it again to see if would work. I am starting the process of moving all my logic to HA or setting up a ton of variables for HA to send to IoX so the logic can stay in IoX. Either way is going to be a lot of work.

12 minutes ago, btreinders said:

My Home Assistant integration is still working as well and I am not going to remove it and try to install it again to see if would work

That's not necessarily an apples to apples comparison as there are 2 ways to integrate to HA, and one is a dead end:

• If you have your own Ecobee developer API key you can get similar access to the plugin, but Ecobee is no longer handing them out so no one can access it at this time. Ecobee is silent on if they start giving them out again.

• If you use HomeKit Device integration,

  • The good: no Apple brand devices are required, it's HA straight to the thermostat, 100% local (no cloud or internet needed),

  • The bad: a lot thermostat features via the Ecobee API in this plugin are not all presented in the HomeKit Integration. If you're doing more advanced things in iox programs I'd look before leaping.

Edited 16 hours ago16 hr by paulbates

@paulbates I do have a developer API but what I meant was I already have a working integration for Ecobee with HA so I am not about to remove it and see if I can add it again like I did with the EISY because I might have the same issue. Just not taking the chance.

I did just add Homekit to the EISY but I don't understand how the EISY would see the thermostat. It added a bunch of Insteon devices to the Home app but nothing appears in the EISY. I do have the thermostat in the Home app as well. I do use a lot of the thermostat features so even if the thermostat showed up via Homekit I don't think it would suffice.

Thank you.

12 hours ago, ndfan77 said:

After you log into Ecobee, click the user profile icon (top right) and then click My Apps. You should have an app named "UDI Polyglot (PIN)" registered in the list.

Ah yes. UDI is in that list. Thank you.

Edited 14 hours ago14 hr by carealtor

I managed to get Ecobee into HA by adding to Home Kit then deleting it from HK, then HA saw it and integrated it. I have an area with a sensor that needs to be monitored so a program can do its thing and that is back online.

As with others, this is broken for me as well.

I had communicated with Ecobee today and they confirmed that new APIs are not being released, but that the old API that was issued should still work and that all I had to do was to re-link or re-authenticate the API. The agent that helped me, kept thinking I was on Home Assistant where apparently this re-authentication is documented, so I do not know if this is a real fix for a UDI PG3 node.

However, I can't see how to do that and I am hoping someone knows if that is possible. Is there a configuration key that can be added for the Ecobee PG3 that will achieve this re-authentication?

21 minutes ago, ISY4Me said:

The agent that helped me, kept thinking I was on Home Assistant where apparently this re-authentication is documented, so I do not know if this is a real fix for a UDI PG3 node.

However, I can't see how to do that and I am hoping someone knows if that is possible. Is there a configuration key that can be added for the Ecobee PG3 that will achieve this re-authentication?

We'll have to wait for jimbo. In the HA case, each individual user owns the key that the HA Integration uses.

In the eISY plugin case, jimbo owns it and we're behind that when we generate a pin.... which is the actual intent of the developer access. I don't think ecobee intended many individual users using dev access for individual homes.

Everybody needs to standby and wait for jimbo to catch up after the weekend is over.