btreinders

@Jimbo.Automates I sent you an API key that I think you can use for your testing.

I had this issue as well before it went down and even when I wrote my own plugin the problem persisted. My plugin is not a polished as @Jimbo.Automates but for now it is getting the job done.

If you have an API key from before they stopped giving them out you can use write you own plugin to get the functionality back. If you do not know how to do that I am making one right now and once I am complete I cam share it.

ratgdo (rage against the garage door opener) is the way to go. You do have to purchase the hardware but there is a plugin for it in the production store.

I'd be willing to pay $20 a year.

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.

@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.

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.

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?

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

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

Sorry, missed this reply. It was the data cable in the gateway. It was just a loosed connection, the connector was not plugged in completely. Yes I have seen the dump calibration too but the app will say it is doing a cal.

Also, anyone else have issues this weekend with solar going to 0 and powerwall 3 saying it was 0% charged when I know it was not and other weirdness with 3rd party apps like Netzero and the PG3 plugin? I was afraid Tesla had changed the API again. I powered off both batteries and back up and it seems to have cured it for now.

I just moved the Insteon dimmers I could where they would not flash and left the Keypadlincs for obvious reasons. They still flash if I am using the dimmer on A but I have not had any electronics die since the Powerwall 3s were installed in Dec 2024. It's not for a lack of electronics either. :) If there was a Keypadlinc alternative I'd replace those too but sadly there is not. At least not with 8 buttons for a reasonable price. Curiously I only see flashing when the Powerwall 3s are the only source, not when solar or the grid is powering the house. I did have a slow UD hub until I upgraded to the EISY from a Polisy. Sorry I am no help.

Watching it boot with the top command and seeing it maxed out at 100%. UD support watched it boot up.