13 minutes ago, Mark said:

Current Situation with Ecobee API

Ecobee has ceased support for new developer accounts, which directly impacts integrations like Polisy Universal Devices. This means that new users cannot obtain API keys necessary for integration.

A few weeks ago Ecobee stopped communicating

Message in PG3............Ecobee Nodeserver with API, or Homekit backends. (API is currently blocked by Ecobee)

Like others was using Ecobee with PG3.........If anyone has a fix or an alternative please post.

As discussed in this thread, install HomekitHub plugin and latest Ecobee plugin connect to HomekitHub. https://forum.universal-devices.com/topic/41709-pg3-ecobee-node-server-production-release/#comment-405393

Edited July 5Jul 5 by Jimbo.Automates

I installed this a while ago and it is working great. I'm very happy to have this working again since I had automated my mini splits to run based on my Ecobee thermostat state. Thanks for providing this fix!

Fan state has stopped working (sometimes).

I have two Ecobee thermostats, and have ISY tell me when the fan state changes to ON so it will run a then statement in my program based on the time of day.

Both work at times, but usually only one is working with the fan state. The other I can see from the ISY Admin Console that it shows the fan state is on, but the program rarely is triggered. I've restarted the three polyglot plugins, and sometimes it starts again, but most of the time it doesn't.

Using Ecobee ver 4.1.10 standard

MQTT ver 0.50.8 free

HomeKitHub ver 2.0.17 Professional

Polisy ISY 6.1.1 (performed the same way on 6.05)

Any others experiencing the same issue, and what did you do to correct it?

If AC is showing proper status then it sounds like a programming or notification issue?

No admin console has showed the same temperature all this time, never changes. Hopefully the debug logs I sent will help.

Ok, I was confused because you said "fan state is on, but the program rarely is triggered". What do you mean by "same temperature"? I thought this was about fan state?

If AC is not showing proper temperature, fan state or ... The please confirm you have checked the Healthy Hub Checklist

Jimbo, that was Peter. I Sent a direct message to you about my issues.

I removed, and reinstalled the plugin again. Repaired the two thermostats this morning, and so far both are reporting correctly when the HVAC fan is on.

Installed the plugin and it works but I am having a small problem when I set it to use Celsius. The temperatures are displaying the Celsius numeric values with the Fahrenheit symbol. Not a big issue but then in programs the behaviour is not consistent: I can set the heat setpoint in Celsius but in the 'If' statement I have to put the Celsius equivalents of the Fahrenheit values. Everything works but I find a little weird, here are two screenshots to better understand my problem:

Cosmin

Edited September 25Sep 25 by CMunteanu

15 hours ago, Cosmin Munteanu said:

Installed the plugin and it works but I am having a small problem when I set it to use Celsius. The temperatures are displaying the Celsius numeric values with the Fahrenheit symbol. Not a big issue but then in programs the behaviour is not consistent: I can set the heat setpoint in Celsius but in the 'If' statement I have to put the Celsius equivalents of the Fahrenheit values. Everything works but I find a little weird, here are two screenshots to better understand my problem:

Cosmin

@Jimbo.Automates I believe I had reported this a few years ago with IoX/ISY. This may not be a new problem, but something in the UoM tables/usage that never got corrected. IIRC it only happens with remote ecobee sensors and not the main stat.

After updating to the latest system releases my ecobee plugin is working again. However I'm getting some errors from the plugin that I don't understand.

I have renamed smart5 and smart6 (see below) to PreCool and EnergySave .

Whenever I set the climate type to either PreCool or EnergySave I get an error, see further below:

I attached text from the debug log

ecobee debug log.txt

On 9/27/2026 at 8:03 PM, photogeek54 said:

After updating to the latest system releases my ecobee plugin is working again. However I'm getting some errors from the plugin that I don't understand.

@photogeek54 Update to 4.1.11 and confirm

On 9/25/2026 at 5:05 AM, Cosmin Munteanu said:

Installed the plugin and it works but I am having a small problem when I set it to use Celsius. The temperatures are displaying the Celsius numeric values with the Fahrenheit symbol. Not a big issue but then in programs the behaviour is not consistent: I can set the heat setpoint in Celsius but in the 'If' statement I have to put the Celsius equivalents of the Fahrenheit values. Everything works but I find a little weird, here are two screenshots to better understand my problem:

@Cosmin Munteanu Update to 4.1.11 and confirm

And everyone, please create a new thread if its a new issue instead of posting on this one.

11 hours ago, Jimbo.Automates said:

@Cosmin Munteanu Update to 4.1.11 and confirm

The last update resolved my issues.

Looks like ecobee pg3 plugin lost my Climate program labels again, I assume it does this each time I upgrade?

Anyway I migrated homekit and ecobee to EisyUI and am not sure where to add these Climate program labels including the heatsetpoint and coolsetpoint like it had in pg3?

[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

On 10/20/2026 at 10:55 PM, photogeek54 said:

[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

I think you need to raise a ticket, I have seen this in other plugins after migration to eisy-ui.

ecobee pg3 has lost my climate programs labels and heat and cool setpoints again. I set them up again after migrating back from the eisyui version. This time I didn't upgrade homekit or ecobee so why do these labels keep getting reset?

I figured out that the

[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

nomenclature when i had migrated to eisy-ui means there is an underlying structure for the labels that eisy-ui doesn't know how to display. if I'm going to migrate again to eisy-ui there has to be a way to set and change these.

also i'm seeing this in the log: mqtt_client:_hello_retry_loop: HomeKit hub MQTT: hello ack not received yet; retrying hello (16). could this have anything to do with my lost climate program labels?

On 11/1/2026 at 4:46 PM, photogeek54 said:

ecobee pg3 has lost my climate programs labels and heat and cool setpoints again. I set them up again after migrating back from the eisyui version. This time I didn't upgrade homekit or ecobee so why do these labels keep getting reset?

I figured out that the

[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

nomenclature when i had migrated to eisy-ui means there is an underlying structure for the labels that eisy-ui doesn't know how to display. if I'm going to migrate again to eisy-ui there has to be a way to set and change these.

This looks like an eisy-ui plugin bug, or difference. I've reported it to UDI so we'll see what needs to be done.

Please everyone, in the future if it's a new issue create a new post in this sub-forum. I can't keep track of every different issue in the same thread.

On 11/4/2026 at 4:40 PM, photogeek54 said:

also i'm seeing this in the log: mqtt_client:_hello_retry_loop: HomeKit hub MQTT: hello ack not received yet; retrying hello (16). could this have anything to do with my lost climate program labels?

Probably a different issue. Looks like it's having an issue talking to the HomeKitHub plugin.

On 11/4/2026 at 4:40 PM, photogeek54 said:

also i'm seeing this in the log: mqtt_client:_hello_retry_loop: HomeKit hub MQTT: hello ack not received yet; retrying hello (16). could this have anything to do with my lost climate program labels?

Expand to Edit

That line means Ecobee is connected to the MQTT broker and has been saying hello, and the HomeKit hub has not answered.
Please check:

1. udi-poly-homekit-hub is running with mqtt_enable true, and its MQTT status is connected (hub GV1 = 2, bridge GV0 = 1).

2. Both sides use the same broker. Ecobee hk_mqtt_host / hk_mqtt_port (normally port 1884) must be the broker the hub is using.

3. hk_mqtt_hub_slug matches the hub mqtt_hub_slug (usually both default). A mismatch puts hello on a topic the hub never subscribes to.

4. hk_mqtt_client_slug is udi-poly-ecobee unless they intentionally set a unique slug. The hub answers on that same slug.

5. Restart the HomeKit Hub node server first, then Ecobee, if both look configured and the count is still climbing.

   
   Until that ack arrives, Ecobee will not load thermostats from the hub.

1. udi-poly-homekit-hub is running with mqtt_enable true, and its MQTT status is connected (hub GV1 = 2, bridge GV0 = 1).

   says homekit hub - connected

   mqtt transport - connected

   bridge status - running

   hub error code - no error

   node server online - connected

2. Both sides use the same broker. Ecobee hk_mqtt_host / hk_mqtt_port (normally port 1884) must be the broker the hub is using.

   ecobee hk_mqtt_host - localhost

   ecobee hk_mqtt_port - 1884

   those parameters not set in homekit

3. hk_mqtt_hub_slug matches the hub mqtt_hub_slug (usually both default). A mismatch puts hello on a topic the hub never subscribes to.

   ecobee sets hk_mqtt_hub_slug to default

   not set in homekit

4. hk_mqtt_client_slug is udi-poly-ecobee unless they intentionally set a unique slug. The hub answers on that same slug.

   in ecobee hk_mgtt_client_slug is udi-poly-ecobee

5. Restart the HomeKit Hub node server first, then Ecobee, if both look configured and the count is still climbing.

after I checked all above I looked at log again and the ack not received is no longer showing! Go figure.

My biggest problem remains how to set the comfort programs and have them stay. They keep resetting to smart1,2,3,4 etc.

Even though I can't view them currently after migrating the plugin to eisy-ui, I'm assuming they would get transferred there if I could set them in pg3 and them migrate?

Thank you, glad it's working.

Benoit will look into fixing eisy-ui issues with the custom parameters not showing up pro next week.

Ignoring the eisy-ui issue

My biggest problem remains how to set the comfort programs and have them stay in PG3. They keep resetting to smart1,2,3,4 etc.

This seems to be a PG3 Ecobee issue

17 hours ago, photogeek54 said:

Ignoring the eisy-ui issue

My biggest problem remains how to set the comfort programs and have them stay in PG3. They keep resetting to smart1,2,3,4 etc.

This seems to be a PG3 Ecobee issue

Do not change the "climateRef" only change the "Display name", if I could make it readonly I would, but not possible. I've confirmed over many restarts that display name doesn't get reset. Again, for new issues please create a new post. Also, read the notes about how comfort programs are now handled in the version I just released, I've given up trying to hack a way to deal with them due to HomeKit not supporting them.