# Homey integration for Home Assistant - Now Available! 🎉

**URL:** <https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786>\
**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:** 8

<div class="post-metadata">

**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:** [February 21, 2026, 12:29am UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/143 "2026-02-21T00:29:32Z")

</div>

Just letting everyone know that I have released 1.1.9.

I got some comments regarding the reporting of capabilities to GitHub issues, so I fixed that. It should now report exactly what I need to know.

I’m really looking forward to the Device Database that HA is creating. Having a direct connection to that will make things a whole lot easier for everyone. And for me to create a script that would check that regularly would be fantastic.

What I’m talking about: [How we'll build the device database, together - Home Assistant](https://www.home-assistant.io/blog/2026/02/02/about-device-database/)

Some release notes for 1.1.9:

> ## 1.1.9 (2026-02-18)
> 
> ### Added
> 
> - **Opt-in capability title naming** : Homey apps can provide human-readable `title` fields for capabilities (e.g., “Temperature”, “Target Temperature”). By default, entity names use the capability ID (e.g., “Living Room measure\_temperature”). Enable this option in integration settings to use the app-provided titles instead (e.g., “Living Room Temperature”) for cleaner names in the UI.
> - **Rename entities service** : `homey.rename_entities_to_titles` service to bulk-update existing entity display names to capability titles without changing entity\_ids. Use this after enabling title naming to update entities that were created before the option was turned on.
> - **Media player shuffle/repeat** : Full support for `speaker_shuffle` and `speaker_repeat` capabilities (SHUFFLE\_SET, REPEAT\_SET features)
> - **Binary sensor alarm types** : Added device classes for `alarm_vibration`, `alarm_occupancy`, and `alarm_presence`
> - **Device class mappings** : Added `heater`, `switch`, and `vacuumcleaner` to central device class mapping for correct type detection
> 
> ### Changed
> 
> - **Device info** : Expanded Homey device class mapping for more reliable classification
> 
> ### Fixed
> 
> - **Capability reporting** : When new Homey capabilities are detected (e.g., after an app update), the integration now shows a persistent notification with device and capability details plus a prefilled GitHub issue link. Call `homey.test_capability_report` from Developer Tools → Actions to try the report flow and see the format. Reports include device class, driver, type, setable/getable flags, and suggested platform for unknown capabilities.

_(Note, for new installs the title naming will be managed by default. But I did not want to f\*\*k up your current installs so I made it optional for existing users)_

As always, if you have any feedback or feature-requests. Please let me know!

Yours truly,  
Mike

---

<div class="post-metadata">

**Author:** ![Andre\_van\_de\_Werken](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andre_van_de_werken/32/12462_2.png) [@Andre\_van\_de\_Werken](https://community.homey.app/u/Andre_van_de_Werken)\
**Post date:** [February 27, 2026, 1:28pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/144 "2026-02-27T13:28:29Z")

</div>

Hi Mike,

Greate work, was looking for this!

Unfortunately i keep getting “cannot\_fetch\_devices“

Any ideas how to solve my problem?

André

---

<div class="post-metadata">

**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:** [February 27, 2026, 8:22pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/145 "2026-02-27T20:22:57Z")

</div>

Hi Andre,

Did you follow instructions @ post 1 of this topic?

---

<div class="post-metadata">

**Author:** ![Andre\_van\_de\_Werken](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andre_van_de_werken/32/12462_2.png) [@Andre\_van\_de\_Werken](https://community.homey.app/u/Andre_van_de_Werken)\
**Post date:** [February 27, 2026, 8:48pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/146 "2026-02-27T20:48:37Z")

</div>

Yeah, step by step

---

<div class="post-metadata">

**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:** [February 27, 2026, 8:55pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/147 "2026-02-27T20:55:45Z")

</div>

Sounds like a connection issue. You use Pro 2023 or newer?  
Any network influencing tool(s)? (AdGuard/PiHole/vLANs etc)

Here’s an extended howto

> **[GitHub - ifMike/homeyHASS: A Homey integration for Home Assistant that...](https://github.com/ifMike/homeyHASS)**
>
> A Homey integration for Home Assistant that automatically discovers and connects all your Homey devices, making them available natively in Home Assistant.

---

<div class="post-metadata">

**Author:** ![Andre\_van\_de\_Werken](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andre_van_de_werken/32/12462_2.png) [@Andre\_van\_de\_Werken](https://community.homey.app/u/Andre_van_de_Werken)\
**Post date:** [February 28, 2026, 9:18am UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/148 "2026-02-28T09:18:51Z")

</div>

I feel really stupid but you got me on track Peter.  
Thanks. I found out I used the IP-Address of my HASS to connect the integration to ☹

Works like a charm now (offcourse)

André

---

<div class="post-metadata">

**Author:** ![JeroenD](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroend/32/14297_2.png) [@JeroenD](https://community.homey.app/u/JeroenD)\
**Post date:** [March 10, 2026, 8:27pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/149 "2026-03-10T20:27:25Z")

</div>

Does it work with Homey Bridge as well? That way it can be used as hub for all the radios it contains. That can be useful for a lot of HA users. Tomorrow I receive my Homey Brige then I will try out my self. I now have connected with Homey self-hosted server and that also works.

---

<div class="post-metadata">

**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 10, 2026, 8:36pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/150 "2026-03-10T20:36:44Z")

</div>

Homey bridge is just a piece of hardware.  
Did you perhaps mean Homey Cloud + Bridge?  
Then it’s a negative, Jeroen.  
It only works for Homey types with the local API feature.

To connect HA to Homey Cloud you’ll need this app  
[https://homey.app/a/io.home-assistant/](https://homey.app/a/io.home-assistant/)  
Only that works the other way round: it adds HA devices to Homey.

I don’t know anything which can add Homey Cloud devices to HA, besides by using webhooks

---

<div class="post-metadata">

**Author:** ![JeroenD](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroend/32/14297_2.png) [@JeroenD](https://community.homey.app/u/JeroenD)\
**Post date:** [March 10, 2026, 8:52pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/151 "2026-03-10T20:52:19Z")

</div>

I don’t know how Homey bridge works, that I will found out tomorrow.  
I was expecting that it has a kind of interface for setup the devices.  
But from your reaction it needs Homey-cloud or Self-hosted sever (the bridge I mean)

I can confirm this app works with Homey Self-hosted sever

---

<div class="post-metadata">

**Author:** ![Daniel\_Cruz](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daniel_cruz/32/81875_2.png) [@Daniel\_Cruz](https://community.homey.app/u/Daniel_Cruz)\
**Post date:** [March 10, 2026, 9:19pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/152 "2026-03-10T21:19:21Z")

</div>

Hi @ifMike

After updating today to v1.2.0, I have 2 points.

1 - It appears a new “Homey”, when I already have the integration with 50 devices.

 ![imagem](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/9/097274f17d84753af406ca1d8ffa5fbdb01dc740.jpeg)

2 - From the 50 devices, 3 become “Unavailable”. 2 are full and 2 are partial. I remove them, and added again with success, but some minutes, they become unavailable again.

2 Full Device unavailable:

- Shelly H&T Gen3

 ![imagem](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/0/30b16a92423b671658806e748a4d7b12a3d2b774.png)

- Shelly EM

Don’t have screenshot for this one. I’m in the smartphone.

Bur this one breaks all my Energy dashboard. 😕

2 Partial Device unavailable:

- Shelly BLU Motion

 ![imagem](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/6/064803ca5022aa8505f5ccb3b6b599aa5409ab7b.png)

- Shelly BLU Door Window

 ![imagem](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/4/740d9396ae76f1d50e0284447e7712996274c683.png)

---

<div class="post-metadata">

**Author:** ![Daniel\_Cruz](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daniel_cruz/32/81875_2.png) [@Daniel\_Cruz](https://community.homey.app/u/Daniel_Cruz)\
**Post date:** [March 10, 2026, 10:15pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/153 "2026-03-10T22:15:45Z")

</div>

@ifMike

After checking all the devices, the issue is not only in some, but in all of them.

Some parts working, some don’t.

Mostly sensors are all off.

**Example** - Shelly 1PM: The buttons to power ON/OFF work, but sensors are all down

 ![imagem](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/9/f9187338d39bd30f43b441f9f7eeae5e7988e0c7.png)

---

<div class="post-metadata">

**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 11, 2026, 10:55am UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/154 "2026-03-11T10:55:53Z")

</div>

It now can have 3 different roles:  
1st:  
as extension to Homey Cloud, by adding local radios (zigbee, z-wave, IR etc.)

2nd:  
as satellite, adding bridged-over-wifi possibilities for IR/Bluetooth/433MHz signals, and acting as ordinary zigbee and z-wave router (like any mains powered zigbee z-wave device);  
Multiple bridges can be added as satellite.

3rd:  
as extension to Homey SHS, by adding zigbee and z-wave controllers, and additional local radios IR, Bluetooth and 433MHz.

The bridge is not needed for cloud-2-cloud connections, or in case of SHS, not needed for LAN-2-LAN and LAN-2-cloud connections.

---

<div class="post-metadata">

**Author:** ![Andre\_van\_de\_Werken](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andre_van_de_werken/32/12462_2.png) [@Andre\_van\_de\_Werken](https://community.homey.app/u/Andre_van_de_Werken)\
**Post date:** [March 12, 2026, 2:02pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/155 "2026-03-12T14:02:10Z")

</div>

Yeah, same problem here. I think i’m returning to version 1.1.9 for now.

I can confirm a downgrade makes all work again.

Grx, André

---

<div class="post-metadata">

**Author:** ![Daniel\_Cruz](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daniel_cruz/32/81875_2.png) [@Daniel\_Cruz](https://community.homey.app/u/Daniel_Cruz)\
**Post date:** [March 12, 2026, 5:17pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/156 "2026-03-12T17:17:03Z")

</div>

Exactly. In the previous version all is good.

---

<div class="post-metadata">

**Author:** ![Davy\_B](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/davy_b/32/120935_2.png) [@Davy\_B](https://community.homey.app/u/Davy_B)\
**Post date:** [March 13, 2026, 9:36pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/157 "2026-03-13T21:36:41Z")

</div>

Does this work with the energy dongle?

I cant make an API key anywhere, I only have local API

---

<div class="post-metadata">

**Author:** ![Paul\_Nassif](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paul_nassif/32/79361_2.png) [@Paul\_Nassif](https://community.homey.app/u/Paul_Nassif)\
**Post date:** [March 14, 2026, 10:55am UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/158 "2026-03-14T10:55:31Z")

</div>

hello , i have the same problem I downgrade to 1.1.9

---

<div class="post-metadata">

**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 14, 2026, 8:01pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/159 "2026-03-14T20:01:52Z")

</div>

Thank you for reporting this.

**Edit:**  
In v1.2.0 I added a filter that skipped sensors that were already in the entity registry. That caused those sensors to stop receiving updates and show as Unavailable, while switches and other controls kept working. I’ve removed that filter.

I also fixed the “Discovered” Homey showing when you’ve already configured it manually. Discovery was using different identifiers than manual setup, so it didn’t recognize the hub as already configured. I’ve added a check so discovery is suppressed when an existing config entry points to the same host.

Both fixes are in the dev release (v1.2.0-dev.1).

**If anybody wants to test and report back:**  
Press “Redownload” on the integration in HACS, then switch the integration to the dev branch and update. If everything looks good, I’ll include these fixes in the next stable release.

Sorry for the trouble.

---

<div class="post-metadata">

**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 14, 2026, 9:18pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/160 "2026-03-14T21:18:24Z")

</div>

Hello,

dev-Update installed, the issue with non-working / unavailable sensors is solved.

Thx for the fast solution!

Edit: The not existing „second Homey“ is still found.

---

<div class="post-metadata">

**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 14, 2026, 11:25pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/161 "2026-03-14T23:25:38Z")

</div>

Thank you for testing!

I think this has something to do with DHCP vs zeroconf discovery. I think I need to resolve by IP, not just string.

I will try fix it by:

1. For each existing config entry, take its host and resolve it to an IP (if it’s a hostname).
2. For the discovered host, resolve it to an IP if it’s a hostname.
3. If any entry’s resolved IP equals the discovered IP, treat it as the same hub and abort discovery.

Will update dev as soon as I can 🙂 Thanks again for testing!

---

<div class="post-metadata">

**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 15, 2026, 4:05pm UTC](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786/162 "2026-03-15T16:05:57Z")

</div>

Hi Mike!

Just FYI, v1.2.0-dev1: it still shows discovered Homeys, details:  
[https://github.com/ifMike/homeyHASS/issues/22](https://github.com/ifMike/homeyHASS/issues/22)

And, the missing entity values are back again, that seems to be solved.

[Previous page](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786.md?page=7)

[Next page](https://community.homey.app/t/homey-integration-for-home-assistant-now-available/148786.md?page=9)
