I see that Ecobee has shut down the integration we were using and now it has to be accessed indirectly. When I try to pair my ecobee so that I can use the homekit hub I'm stuck because I'm android.

Is there a workaround for this?

There's are threads about this in the ecobee section of the forum. The updated plugin is using the HomeKit Accessory Protocol (HAP). Apple (unusually) made HAP an open, public spec. No apple devices are required on your network to get it to work.

Go to the ecobee section of the forum and you'll find the posts. One's a little long, and I think there are others where jimbo makes the steps more brief. I think there is both a new ecobee plugin as well as a HomeKit plugin and both are needed

Thanks - I'll go look. I've been working so far just from the install instructions in the details area of the homekit pg plugin

Well that was easy...... all connected and working. Turns out all I had to do was install homekit hub then enter the pairing code for my ecobee into the config. Nice. Now if only my Chamberlain GDO would allow access outside of their stupid MyQ app - grrrrr

Thanks!

Edited Wednesday at 02:34 PM4 days by MarkJames

4 hours ago, MarkJames said:

Now if only my Chamberlain GDO would allow access outside of their stupid MyQ app - grrrrr

Can't help there.. that was a total and complete rug pull by Chamberlain:

• First Chamberlain had an API for solutions like eisy to integrate.

• Then they rug pulled that support.

• Then Ratgo, Meross (et al) made WiFi controllable add on boards.

• Then Chamberlain introduced a new security standard that the controllers downloaded and that effectively locked those alternatives out... the final rug pull.

Hard to believe GDOs is where things are raging... 🤪 Remembering the simpler time at my old house were an iolinc did a good job. My current house has 2 chamberlains and one needs to be replaced. Even though they're not automated, I'll be going with something else.

Well, there's still the ole workaround of wiring a dry contact unit like a IOlinc across the button contacts of a physical remote.

...or if the GDO has a wired button for the wall, across its hardware switch (I've done this myself, but via Lutron, not Insteon). Either approach will probably require soldering wires to the pads on the circuit board, though. Or alligator clips if you're lucky and there are accessible leads on the button/switch (not likely these days).

-Tom

On 8/12/2026 at 4:57 PM, xlurkr said:

...or if the GDO has a wired button for the wall, across its hardware switch (I've done this myself, but via Lutron, not Insteon). Either approach will probably require soldering wires to the pads on the circuit board, though. Or alligator clips if you're lucky and there are accessible leads on the button/switch (not likely these days).

-Tom

I had a couple of PLMs that would throw ALL ON commands once in a while and light up the whole place. Pretty jarring when it happens at night lol. IOLincs would all go ON with this too. I had/have an ElkM1 system so I just wired the GDO opener switch like you said to an output relay on the Elk. The Elk is far more robust than the Insteon system so it will absolutely not 'accidentally' open the door. I just had the ISY run the automation task associated with it and have that trigger the relay. That kept it completely separate from any stray signals.

It was probably overkill but I already had the output board as I use that for my fireplace - and for the same reasons too.

I have two Chamberlin LiftMaster side mount openers which are great, so quiet, and the work perfectly with Konnected BLAQ. I'll be releasing the plugin for these very soon.

fd

1 minute ago, Jimbo.Automates said:

I have two Chamberlin LiftMaster side mount openers which are great, so quiet, and the work perfectly with Konnected BLAQ. I'll be releasing the plugin for these very soon.

That would be very nice. Looking forward to it.