# Homey integration for Home Assistant - Now Available! 🎉 **URL:** \ **Category:** Developers\ **Created:** [January 7, 2026, 11:03pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786 "2026-01-07T23:03:50Z")\ **Posts on this page:** 20\ **Page:** 9
**Author:** ![ifMike](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ifmike/32/152149_2.png) [@ifMike](https://community.homey.app/u/ifMike)\ **Post date:** [March 15, 2026, 9:20pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/163 "2026-03-15T21:20:35Z")
A new dev version has been released. If anyone wants to test, please do! 🙂 > [@Peter\_Kawa](#): > > Just FYI, v1.2.0-dev1: it still shows discovered Homeys, details: > [@Steffen\_Schmitt](#): > > Edit: The not existing „second Homey“ is still found. ---
**Author:** ![Steffen\_Schmitt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/steffen_schmitt/32/165968_2.png) [@Steffen\_Schmitt](https://community.homey.app/u/Steffen_Schmitt)\ **Post date:** [March 16, 2026, 5:29am UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/164 "2026-03-16T05:29:26Z")
Hi Mike, dev3 installed: - no second Homey Pro entry ☑ - all sensors active ☑ ---
**Author:** ![ifMike](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ifmike/32/152149_2.png) [@ifMike](https://community.homey.app/u/ifMike)\ **Post date:** [March 16, 2026, 7:47pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/165 "2026-03-16T19:47:52Z")
A new release is out! I kind of had to rush this since a lot of sensors stopped working (and it was my dumb mistake). I also added some new features like better descriptions during setup, better error messages and discovery improvements. # v1.2.1 > ## Critical > > **Sensor unavailability fix** : A registry filter was incorrectly skipping existing sensors, causing them to become orphaned and show Unavailable. Controls (lights, switches, etc.) worked, but sensors did not. This is a critical fix for all users who rely on sensor data—temperature, humidity, presence, distance, and similar capabilities. > > ## Added > > - **Discovery card identification** : Shows IPv4 on discovered cards (e.g. “Homey (192.168.1.32)”) so multiple Homeys can be distinguished. Falls back to “Homey (IP unknown)” when IPv4 cannot be resolved. > - **Setup step descriptions** : Step descriptions explain what to do, required permissions (Devices, Flows, System read), and Pro 2023+ limitation. > - **Translations** : Added translations/en.json for config flow to display step descriptions correctly. > > ## Changed > > - **Discovery host field** : Never show .local hostname or IPv6 in the host field. Resolve to IPv4 when possible; use empty when resolution fails. Default manual host changed from homey.local to empty. > - **Error messages** : Full error messages for invalid\_auth and cannot\_connect with causes and solutions, including Pro 2019 not supported. Passed directly since translation keys may not resolve in custom components. > > ## Fixed > > - **Sensor unavailability** : Removed registry filter that skipped existing sensors, causing them to become orphaned and show Unavailable (controls worked, sensors did not). > - **Discovery suppression** : Suppress discovery when an existing config entry points to the same host. Fixes “Discovered” Homey showing when manually configured (manual uses homeyId, discovery uses MAC/hostname). > - **IPv6 discovery suppression** : When discovered host is IPv6, resolve hostname to IPv4 and compare with existing entries so discovery is correctly suppressed for already-configured hosts. > - **Discovery card fallback** : When title\_placeholders was empty, the card showed “homey” (domain). Now always shows “Homey (IP)” or “Homey (IP unknown)”. ![Added description to setup flow](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/2/0243a71a5906c80179ef7da50ea6be9516e5da70.png) ![Better naming for discovered Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/a/9ae19dfe6cba6629a9b22fe7f7328cd309b3cce3.png) If you encounter any errors or bugs, please report them (preferably on GitHub) or just let me know here! All the best, Mike ---
**Author:** ![Steffen\_Schmitt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/steffen_schmitt/32/165968_2.png) [@Steffen\_Schmitt](https://community.homey.app/u/Steffen_Schmitt)\ **Post date:** [March 17, 2026, 8:31am UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/166 "2026-03-17T08:31:38Z")
Hi Mike, Thx for your work. Sensor are working fine but now I have a „new“ Homey pro again. The integration of the sensors works fine so its ok for me. ---
**Author:** ![ifMike](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ifmike/32/152149_2.png) [@ifMike](https://community.homey.app/u/ifMike)\ **Post date:** [March 17, 2026, 7:06pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/167 "2026-03-17T19:06:31Z")
Glad to hear it! I’m working on a fix for this. I’ve already added it to my dev branch if you want to test (available in my HACS repo) > **[Release dev-1.2 · ifMike/homeyHASS](https://github.com/ifMike/homeyHASS/releases/tag/dev-1.2)** > > Dev release for testing new features before beta/stable release. > This is a dev version - Use at your own risk. Report issues on GitHub. > Build: dev-1.2 > Discovery suppression – The "new" Homey discov... ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [March 17, 2026, 7:37pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/168 "2026-03-17T19:37:19Z")
Hi Mike, The 2019 models are still on the ‘discovered’ devices list, but it’s no biggie of course. We can put it on the ignore list in the devices screen, which makes them disappear in the integration screen as well ![Screenshot_20260317_202036_Home Assistant](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/8/88249ce23a27be99b88443243d8cf05f880badba.jpeg) ![Screenshot_20260317_203649_Home Assistant](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/b/1be156a29d9f047e4a7ded609f40c98d7b5f840c.jpeg) I understand it’s hard to determine the model in the discovery stage. ---
**Author:** ![ifMike](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ifmike/32/152149_2.png) [@ifMike](https://community.homey.app/u/ifMike)\ **Post date:** [March 17, 2026, 8:09pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/169 "2026-03-17T20:09:09Z")
Yeah, I think I need to add a logger in my dev build and have you (or someone) try it. Then see what kind of differentiation we have between different models so that I can suppress them in the discovery. The problem is that before we actually authenticate with our token, we don’t get the full picture. I’ll let you know when I have something 🙂 **EDIT:** It was a minor update to dev. So there is a new dev-1.3. Once it’s installed, reboot and search for **[discovery]** in the logs. There should be a “model” field e.g. `'model': 'homey5q', 'version': '13.0.0'}` So I need to know the model for 2019. I’m expecting it to be “homey2”, “homey2s”, “homey4d” or similar. If someone wants to give me a legacy model ID that don’t have the local API then I can add that to the “Unsupported models” list and we won’t have that problem 🙂 ---
**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\ **Post date:** [March 17, 2026, 10:28pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/170 "2026-03-17T22:28:16Z")
> [@ifMike](#): > > So I need to know the model for 2019. I’m expecting it to be “homey2”, “homey2s”, “homey4d” or similar My Homey 2019 has model number `homey3d` if that helps. Also, this is what I found while reverse engineering Homey SHS: ```auto export const MODELS = { desktop: 'Desktop', homey1s: 'Homey (Early 2016)', homey1d: 'Super Homey (Early 2016)', homey1q: 'Super Homey (Early 2016)', homey2s: 'Homey (Early 2018)', homey2d: 'Super Homey (Early 2018)', homey2q: 'Super Homey (Early 2018)', homey3s: 'Homey (Early 2019)', homey3d: 'Homey Pro (Early 2019)', homey4d: 'Homey Pro (Early 2019)', homey5q: 'Homey Pro (Early 2023)', homey6q: 'Homey Pro mini', homey7q: 'Homey Pro (2026)', cloud: 'Homey Cloud', shs: 'Homey Self-Hosted Server', } as const; ``` ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [March 18, 2026, 1:36am UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/171 "2026-03-18T01:36:09Z")
Hi Mike, I know my Homey 2019 modelIds are homey3d and homey4d. ![Screenshot_20260318_023242_Vivaldi](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/2/52e91f701b7fc5cedf7b37f997e4b08dd7e79ef3.jpeg) ![Screenshot_20260318_023347_Vivaldi](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/2/82a32f801f55f623acd33f80e7448b212ad9a982.jpeg) Unfortunately it’s not in the v1.2.1-dev.3 debug log. I’ll DM you the complete log entry which comes closest to discover specific info (too much data to anonimise). ---
**Author:** ![ifMike](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ifmike/32/152149_2.png) [@ifMike](https://community.homey.app/u/ifMike)\ **Post date:** [March 18, 2026, 8:49am UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/172 "2026-03-18T08:49:59Z")
Thank you both! This is probably what I needed! > [@smarthomesven](#): > > ```auto > export const MODELS = { > desktop: 'Desktop', > homey1s: 'Homey (Early 2016)', > homey1d: 'Super Homey (Early 2016)', > homey1q: 'Super Homey (Early 2016)', > homey2s: 'Homey (Early 2018)', > homey2d: 'Super Homey (Early 2018)', > homey2q: 'Super Homey (Early 2018)', > homey3s: 'Homey (Early 2019)', > homey3d: 'Homey Pro (Early 2019)', > homey4d: 'Homey Pro (Early 2019)', > homey5q: 'Homey Pro (Early 2023)', > homey6q: 'Homey Pro mini', > homey7q: 'Homey Pro (2026)', > cloud: 'Homey Cloud', > shs: 'Homey Self-Hosted Server', > } as const; > > ``` > [@Peter\_Kawa](#): > > I know my Homey 2019 modelIds are homey3d and homey4d. I’ve added a filtering so Homey 2019 and older no longer show up in discovery. From the mDNS logs I see that Pro 2023 sends `model: 'homey5q'` in the discovery properties, while 2019 and older apparently don’t send a `model` at all sometimes. So I now: 1. Ignore devices without `model` - older firmware doesn’t broadcast it, so we treat them as unsupported. 2. Ignore known unsupported models - e.g. homey3d, homey4d, homey2s, etc. 3. Allow supported models - homey5q (Pro 2023), homey6q (Pro mini), homey7q (Pro 2026), and SHS. 4. Allow unknown models - so future devices still show up until we know their IDs. This is in the latest dev build. If you still see your 2019 in discovery, tell me and I can look at the logs again. As always, thank you for testing. Really means a lot! ```auto HOMEY_MODELS_SUPPORTED = frozenset({"homey5q", "homey6q", "homey7q", "shs", "desktop"}) HOMEY_MODELS_UNSUPPORTED = frozenset({ "homey1s", "homey1d", "homey1q", # 2016 "homey2s", "homey2d", "homey2q", # 2018 "homey3s", "homey3d", "homey4d", # 2019 "cloud", }) ``` ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [March 18, 2026, 1:39pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/173 "2026-03-18T13:39:49Z")
My pleasure, Mike. It seems you nailed it, v1.2.1-dev.4 doesn’t show discovered Pro 2019s. Observation: When manually installing & updating the integration, my previous selection was gone, all devices were back. Is this “as expected” with manual updates? To update, I rename the `custom_components/homey` folder and upload the updated `homey` folder to `custom_components`, followed by HA restart. ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [March 18, 2026, 1:41pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/174 "2026-03-18T13:41:16Z")
> [@smarthomesven](#): > > `Super Homey (Early 2018)` Funny, these ‘Super’ models never seem to be sold ---
**Author:** ![ifMike](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ifmike/32/152149_2.png) [@ifMike](https://community.homey.app/u/ifMike)\ **Post date:** [March 18, 2026, 2:16pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/175 "2026-03-18T14:16:43Z")
> [@Peter\_Kawa](#): > > My pleasure, Mike. > It seems you nailed it, v1.2.1-dev.4 doesn’t show discovered Pro 2019s. Great! 🙂 Then I’ll prepare a new main release, but I’ll wait just a bit to make sure I don’t get any other errors with this version first. > [@Peter\_Kawa](#): > > Observation: > When manually installing & updating the integration, my previous selection was gone, all devices were back. Is this “as expected” with manual updates? > To update, I rename the `custom_components/homey` folder and upload the updated `homey` folder to `custom_components`, followed by HA restart. The device selection is stored in the config entry (in Home Assistant’s `.storage/core.config_entries`), not in the `custom_components/homey` folder. So it should actually survive a manual update where you only replace the files and restart. ### Why it might still disappear 1. Removing and re-adding the integration - If you delete the integration in the UI and add it again (instead of just replacing files), you create a new config entry. That new entry starts with no device filter, so all devices are selected again. 2. Integration failing during the update - If you rename/remove the `homey` folder while HA is running, the integration can fail to load. HA may then mark the entry as failed and ask you to reconfigure. Depending on how that reconfigure flow works, it might overwrite the entry and drop the device filter (but this seems unlikely). 3. How you perform the update - Renaming the folder and uploading a new one can leave HA in a state where it treats the integration as needing reconfiguration, which can overwrite the stored config. ### Recommendation Use HACS for updates when possible. HACS updates files in place, so the integration stays loaded and the config entry (including device filter) is preserved. If you must update manually, avoid removing the integration from the UI. Just replace the files, restart HA, and the device selection should remain. ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [March 18, 2026, 6:33pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/176 "2026-03-18T18:33:36Z")
> [@ifMike](#): > > The device selection is stored in the config entry (in Home Assistant’s `.storage/core.config_entries`) Aahhhh, thanks! I knew it’s not in the `custom_components/homey` folder, but I didn’t figure out where it’s actually stored. . > [@ifMike](#): > > Integration failing during the update This probably was what happened in my case. I didn’t disable the integration before renaming the actively used homey folder. . > [@ifMike](#): > > If you must update manually, avoid removing the integration from the UI. Just replace the files, restart HA, and the device selection should remain. It’s a plan to temporary disable the integration I think. . > [@ifMike](#): > > Use HACS for updates when possible I know, and it’s preferred by me as well, but, after I removed it, I couldn’t add the custom repository anymore, no matter what. In a bright moment I thought “what if I restore a backup from when it was added already”, and this brought things to life again. ---
**Author:** ![Martin\_Carangelo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_carangelo/32/121876_2.png) [@Martin\_Carangelo](https://community.homey.app/u/Martin_Carangelo)\ **Post date:** [March 21, 2026, 9:31pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/177 "2026-03-21T21:31:45Z")
You saved my home. I was at my wits end. I wanted to bring all devices in through Homey and then distribute to homeassistant and Alexa. Alexa has the skill built in, that worked right away. I was pulling my hair out trying to find a way to expose to HA. This is perfect. THANK YOU! ---
**Author:** ![Heinz\_Himmel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/heinz_himmel/32/159280_2.png) [@Heinz\_Himmel](https://community.homey.app/u/Heinz_Himmel)\ **Post date:** [May 23, 2026, 11:01am UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/178 "2026-05-23T11:01:27Z")
I can’t integrate Homey into Home Assistant. Homey isn’t being detected. ![Bildschirmfoto 2026-05-23 um 12.43.04](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/5/05275fefe2d788182ec182f53f20d12e3d44dc11.png) ![a19cf2d8acb21b936e1642671b792a248302e05f_2_1380x724](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/f/ef2f54f054f5064a4bed7c1b6fbe08dc34fa88b4.png) ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [May 26, 2026, 12:53am UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/179 "2026-05-26T00:53:57Z")
Hi Heinz, I get the mix-up, but, you ended up at the HACS “Homey” compound addon for the Home Assistant Community app by Ronny Winkler, which is deprecated and unrelated to this “Homey Integration for Home Assistant” app by Mike. In short: Please add the repository by Mike to HACS “Custom repositories” first: ![Screenshot20260526024802Home Assistant](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/d/9da34094bfbb9ad3ae03225726a1e0cd2921f379.jpeg) Next, make sure it’s added correctly: ![Screenshot20260526024719Home Assistant](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/d/6d9baf5c78ab0ccfa780090d32a1b265ff6943a1.jpeg) Now you can look for “Homey Integration” and install it: ![Screenshot20260526024554Home Assistant](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/2/82c46191de41c62f602957da3733fc9ccbd93958.jpeg) Next, goto Settings \> Devices & Integrations \> Integrations; Hit the “Add Integration” button; Select “Homey”: ![Screenshot20260526025651Home Assistant](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/b/9bada29b1edbf6f85a1449953f6446c1b214878c.jpeg) . See this link for the _ **complete and extended instructions** _: > [@ifMike](#): > > For detailed instructions, troubleshooting, and permission requirements, see the GitHub README: > [https://github.com/ifMike/homeyHASS](https://github.com/ifMike/homeyHASS) ---
**Author:** ![ifMike](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ifmike/32/152149_2.png) [@ifMike](https://community.homey.app/u/ifMike)\ **Post date:** [June 4, 2026, 7:58pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/180 "2026-06-04T19:58:43Z")
A quick update as well. This integration will soon be available in the default HACS repo so that if you search for it in HACS it will show up. I’m still waiting for the integration to be reviewed (which I’ve been waiting on since April 2). Once it’s available there I’ll update the guide - and let all of you know! All the best, Mike ---
**Author:** ![Michael\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michael_d/32/16541_2.png) [@Michael\_D](https://community.homey.app/u/Michael_D)\ **Post date:** [July 6, 2026, 3:53pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/181 "2026-07-06T15:53:00Z")
I have a Problem with my Shutterswitches from Fibaro, they doesn´t show up correct in HA. You only see the power Entity not the shutter to control ---
**Author:** ![ifMike](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ifmike/32/152149_2.png) [@ifMike](https://community.homey.app/u/ifMike)\ **Post date:** [July 22, 2026, 5:40pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/182 "2026-07-22T17:40:50Z")
Update time - and this one’s been a long time coming! **The integration is now in the official HACS default catalog 🥳** You can search for **Homey** directly in HACS → Integrations - no custom repository needed. Finally merged in early July! **If you’re a new user:** install **v2.0.1** from HACS and set up as normal. **If you’re already on 1.x and things work:** please read this before updating. Version 2.0.0 renamed the domain from `homey` to `homey_hass`. Updating through HACS without migrating will break your setup. If you want to stay on 1.x, use the separate legacy custom repo **[ifMike/homeyHASS-legacy](https://github.com/ifMike/homeyHASS-legacy)** in HACS - you’ll only get 1.2.x updates, not 2.x notifications. Latest legacy release: **v1.2.8**. 1.x.x versions will only be updated with critical fixes (if any). No new features will be planned for this. | **You are…** | **Do this** | | --- | --- | | New user | → Search **Homey** in HACS → install **2.0.1** | | Happy on 1.x | → Use **homeyHASS-legacy** in HACS, stay on 1.2.x | | Ready to migrate | → Follow the **[migration guide](https://github.com/ifMike/homeyHASS#migrating-from-1x-to-200)** | I’ll update the guide to reflect the default HACS install path. All the best, Mike [Previous page](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786.md?page=8) [Next page](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786.md?page=10)