Homey integration for Home Assistant - Now Available! 🎉

ifMike · July 22, 2026, 5:41pm

Fixed in both legacy and new v2 release!

Doekse · July 22, 2026, 6:46pm

Awesome to see your progress, congratulations on getting your integration on HACS. Cool to see you are bringing the platforms closer together through code.

zuur · July 26, 2026, 11:03am

Hi there,

Thanks a lot for all the energy and effort you’ve put into this.

It is greatly appreciated, and it makes usage much easier for less technical users. I set it up right away and am very impressed by how simple it is to use.

I’ve also developed some apps myself that run via MQTT.

I notice that your app allows other apps to be viewed and edited via the API key.
Is it possible to make my app visible through yours as well? These are primarily dashboard widget apps.

I assume only if a device with a status is linked to it?

ifMike · July 26, 2026, 2:04pm

Hi, and thank you! Really glad it’s working well for you.

Short answer: dashboard widgets don’t show up in Home Assistant by themselves. This integration exposes what Homey knows as devices, flows, scenes/moods, and logic variables - not the dashboard UI.

So yes, your guess is mostly right: for something to appear in HA, it usually needs to be exposed through Homey as a device with capabilities (often a virtual device), or via flows or logic variables.

If your MQTT apps already do that, they should work here too. If they’re only dashboard widgets without devices/flows/logic behind them, they won’t appear in Home Assistant.

Feel free to share how your apps expose their data in Homey, and we can check whether they fit.

Thanks again for the kind feedback - it means a lot.

zuur · July 26, 2026, 6:53pm

Thanks for your feedback. In the meantime, I’ve created a device with status indicators and buttons, and it all seems to be working fine.

ifMike · August 11, 2026, 12:16pm

Homey integration 2.1.0 - guided migration from 1.x is here

I’ve released v2.1.0 of the Homey integration for Home Assistant, with a guided migration assistant that makes upgrading from 1.x much easier than before.

What changed

From 2.0.0 onward, the integration uses domain homey_hass (folder custom_components/homey_hass/, services homey_hass.*). That was required for the official HACS catalog, but migrating was manual and easy to get wrong.

2.1.0 fixes that. If you still have Homey 1.x configured, the setup flow now offers Migrate from Homey 1.x so you can:

Copy your connection settings from 1.x
Keep entity IDs (dashboards and many automations keep working)
Restore device areas
Optionally remove the old 1.x integration when done

Migration screens only appear when 1.x is still installed - new installations are unchanged (add Homey 2.x, enter host + API key, done).

Who should do what

You are…	What to do
On 1.x and ready to upgrade	Backup HA → update to 2.1.0 → Add integration → Homey 2.x → Migrate from Homey 1.x. Full guide: Migrating from 1.x
On 2.0.x already	Update to 2.1.0 and restart. No migration steps.
New user	Install Homey 2.x from HACS (search “Homey”). No migration needed.
Happy on 1.x, not upgrading yet	Stay on the legacy HACS repo `ifMike/homeyHASS-legacy` (1.2.x only). Don’t install 2.x from the main repo until you’re ready.

While both versions are installed: you may see Homey (1.x) and Homey 2.x in Add integration — pick Homey 2.x for migration.

After migration

Confirm devices work under Homey 2.x
Delete custom_components/homey/ and restart
If any automations/scripts call homey.* services (e.g. homey.trigger_flow), change them to homey_hass.* - automations that only use entity states usually need no changes if entity IDs were preserved
Ignore any Homey (IP unknown) discovery card (don’t add a second entry)

Release & docs

Release: v2.1.0
Repository: github.com/ifMike/homeyHASS
Issues / feedback: GitHub Issues

If you tried migrating on earlier dev builds and hit errors, 2.1.0 includes fixes for newer Home Assistant versions and more resilient migration handling - worth retrying after a backup if you’re still on 1.x.

Thanks for your patience while I got this right!

All the best,
Mike

Robinjo · August 21, 2026, 5:12pm

Thanks for making this app, an easy way of controlling homey devices from HA I was looking for a long time! I want to play with the AI voice assistant from HA to control homey. Now I can do that in an easy way!

MGrosni · October 6, 2026, 11:43am

Thank you very much for this integration. I use Homey as my primary Smarthome Hub, but I like the dashboards from HA and the Tuya Cloud integration ist working more stable than in Homey.
I read your setup guide and installed the integration. My Homey (Pro 2016) is found with the right ip. I created the API key as you recommend, but if I want to add my Homey. The log shows warning, main thread homey_hass_config, could not reach homey at right ip adress.
I could not figure out the problem. The only thing that I assume, it is a problem because my HA installation runs in a Docker Pod (Network = Host). Any suggestions? Thanks.

ifMike · October 12, 2026, 11:43am

Hi!

Your Docker “network_mode: host” setup is usually fine for this integration.

The more likely cause is the Homey model: Homey Pro 2016 (and 2019) do not support API Keys / the Local API, which this integration requires.
The hub can still be discovered with the correct IP, but Home Assistant cannot talk to it the way Pro 2023+ can - that matches the “could not reach Homey” warning.

So this is a Homey hardware limitation, not something you can fix with Docker networking. Supported hubs are Homey Pro 2023 or later (and Homey Pro mini / SHS where Local API is available).

If you later move to a supported Homey, your host-network HA install should work with an API key created under Homey → Settings → API Keys.

MGrosni · October 12, 2026, 12:05pm

Hi!

Thank you very much. I thought it was because of Docker. Anyway, then I can stop my troubleshooting.

Fredrik_Edenlind · October 15, 2026, 7:03pm

Hej ifMike

I just setup a new HA and added HACs + Homey Integration and then a Homey Self hoster server.

But my problem is that I cant add the SHS device, it just asks for host and API key, I cant add the host:4859 anywhere to add the SHS server as per the installation manual.

What am I doing wrong?

It has also found my to homeys but if I click add it still asks for API key which I dont have in my Homey Cloud and Home SHS

PLease help anyone

Peter_Kawa · October 15, 2026, 8:52pm

Homey SHS has the possibility to create an API Key just like Homey Pro;
Screenshot of SHS:

I just installed a Homey SHS instance to HA, started it, activated it per Homey Mobile app.
Then I created an API Key, as per manual

in post # 1

In the HA Integrations screen, the SHS instance should pop up as discovered device;
If not:
I added Homey SHS to HA per Homey Integration, by tapping on the Homey integration entry.
Then tap “Add hub”

enter
http://[HA.ip.adress]:4859
and the aforementioned API Key.

Here it was found, and I could add a Homey SHS device to HA.

Homey Cloud hasn’t got the API Key feature as it can’t connect to local network devices .

The_cure_Bob · October 16, 2026, 1:56pm

Hello,

great work, bravo:waving_hand:

all my homey devices are well up, except my 2 aeotec wallmote quad switches,

Do you have an idea?

Thank you

Yann

Fredrik_Edenlind · October 16, 2026, 5:50pm

Okej, so I add the :4859 and the API key?

I found a way to create a key but did not ad

d the port at the end.

Another question, what gui is it were you add the hub above?

Fredrik_Edenlind · October 17, 2026, 11:39am

got it too work, used the port and the API key I finally found

Fredrik_Edenlind · October 17, 2026, 11:40am

my problem now is that all my devices are in my Homey Cloud and not the SHS server, so I guess I need to remove and add all devices again

Peter_Kawa · October 17, 2026, 1:15pm

Ah, yes Homey Cloud can’t connect to H.A. with this app, plus it doesn’t have de API functionality.
(and the Pro 2016-2019 models can connect, but also don’t have de API functionality).

Unfortunately there’s no migration functionality (I know of) from Homey Cloud to any other Homey model.

ifMike · October 19, 2026, 11:30am

Hi!

The Aeotec Wallmote Quad usually won’t show up as switches in Home Assistant, and that’s expected with how Homey exposes it.

It’s a remote (tap / hold / swipe), not a normal on/off switch. In Homey those presses are handled as Flow triggers, not as switch entities with a lasting on/off state. This integration only creates switch/button entities when Homey exposes a settable capability (like onoff or a settable button). The Wallmote typically doesn’t, so Home Assistant has nothing solid to map.

Aeotec Wallmote Switch Tech Spec

What you can do:

Create Homey Flows for the Wallmote button presses you care about
Make sure those Flows are enabled
They should then appear in Home Assistant as Homey Flow buttons

You may also see a battery sensor if Homey reports one. Also double-check that the Wallmote isn’t excluded in the integration’s device filter.

If you still see nothing at all for that device, send me the Homey device capability list (or a screenshot of the device info), and I’ll take a look.
You can do that by going to Gather Device Information on my GitHub.