Fixed in both legacy and new v2 release!
Awesome to see your progress, congratulations on getting your integration on HACS. Cool to see you are bringing the platforms closer together through code.
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?
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.
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. 
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 tohomey_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
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!
