I am running the Ecobee plugin in API mode and it has been running rock solid in PG3 since @Jimbo.Automates released the current version with API, or Homekit backends.

I have been working on migrating this plugin (using API configuration) from PG3 into EISY-ui and having issues. A fair amount of my programs appear to run, but there are issues where programs evaluate thermostat temperatures and errors in the log files are present.

On this first post I don’t want to distract you with the specifics of the issues I am seeing, but whether the UDI community users have migrated their Ecobee API configured plugin into EISY-ui and everything is working as you expect and your log files show no concerns.

I know your issue is related to using your own Developer Key which I'll try to look into soon.

But for everyone else's info, I have migrated all of mine to Plugins and everything worked perfectly. But I am on the staging repo and don't recommend everyone use that but wait for eisy-ui 1.4.9 and PG3x 3.4.28 to be released to beta or production, although I'm not sure if that makes a difference.

I just want to be clear... all of the comments below ONLY apply to users who are using the Ecobee Plugin in the cloud/API mode. Users who are using the default HomeKit mode should not have issues migrating the Ecobee plugin to eisyui and do not need to read this.

The main problem seen with v4.1.11 of the ecobee plugin after migration to eisyui was failure to be able to read current values/parameters from the ecobee API server due to authentication issues. With work by @Jimbo.Automates and ecobee plugin update to v4.1.13, issues are resolved, but users with their ecobee configuration in cloud/API mode will still have some extra steps that have to be preformed to have everything working on eisyui after migration.

Ecobee plugin has been updated to v4.1.13 and addresses issues related to authentication with Ecobee. Here are the recommended steps... and again, this is ONLY for users that work in the cloud/API configuration mode.

1) Update the Ecobee Plugin to v 4.1.13. It was recommended to update this on PG3 before migration and confirm all is OK

2) Migrate the Ecobee plugin to eisyui. Due to the way that Ecobee handles the authorization of the API using the xxxx-xxxx PIN handshaking, this new instance of the plugin running on eisyui will be seen as a new instance of the plugin by the API Serves too and it will not be able to use the old auth codes. To resolve this, the xxxx-xxxx PIN or User ID has to be communicated to ecobee. This does not happen automatically during the migration and the user has to manually trigger the xxxx-xxxx PIN handshaking process.

3) To manually trigger the handshaking process, you have to know what the new xxxx-xxxx PIN is. The method I used is as follows... and this is done after migration... 1) On the eisyui plugin view in the Configuration Tab, remove your API String from the API Key field in the configuration. 2) Save the change you just made. 3) This will trigger a pop-up blue notification in the Overview tab, but it will not have a xxxx-xxxx PIN in it because the API was removed. 4) Now, go back to the configuration tab in the eisyui plugin view and re-enter the same API String into the API Key field (this is your own personal developer API String), 5) Now, save the configuration changes again. 6) You will see an updated blue notification in the Overview tab and within the lower blue notification box you will see your new xxxx-xxxx PIN. 7) Now, log in at the Ecobee web site → Profile → My Apps → Add Application → enter the PIN and click Validate. The website will popup a verification of what you just submitted... verify and then click validate in that popup. Ecobee will then tell you the process worked and will probably send you an email saying essentially the same thing. 8) Back in the eisyui plugins view in the Overview tab... the blue notification boxes will disappear within 2 minutes. AFTER those blue notification boxes have disappeared, re-submission of the xxxx-xxxx PIN handshaking process is finished.

4) With the xxxx-xxxx PIN process completed, the plugin is still looking at the old validation that it did on startup. To refresh everything with the new authentication code, go to the eisyui plugin view and in the Overview Tab and STOP the plugin and then START the plugin ( I suspect a RESTART will to the same, but I did not test that). At this point everything should be running as it should.