Homey integration for Home Assistant - Now Available! šŸŽ‰

Developers
143

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

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

144

Hi Mike,

Greate work, was looking for this!

Unfortunately i keep getting ā€œcannot_fetch_devicesā€œ

Any ideas how to solve my problem?

AndrƩ

145

Hi Andre,

Did you follow instructions @ post 1 of this topic?

146

Yeah, step by step

147

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

148

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 :frowning:

Works like a charm now (offcourse)

AndrƩ

149

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.

150

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/
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

151

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

152

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
imagem1106Ɨ1012 78.1 KB

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
imagem653Ɨ376 27.6 KB

  • Shelly EM

Donā€™t have screenshot for this one. Iā€™m in the smartphone.

Bur this one breaks all my Energy dashboard. :confused:

2 Partial Device unavailable:

  • Shelly BLU Motion

imagem
imagem697Ɨ445 31.7 KB

  • Shelly BLU Door Window

imagem
imagem681Ɨ431 31.6 KB

153

@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
imagem690Ɨ822 56.8 KB

154

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.

155

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Ʃ

156

Exactly. In the previous version all is good.

157

Does this work with the energy dongle?

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

158

hello , i have the same problem I downgrade to 1.1.9

159

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.

160

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.

161

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 :slight_smile: Thanks again for testing!

162

Hi Mike!

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

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