Hi @ifMike
Tested on version 1.1.8, and now the Covers buttons work all in the correct way.
Thank you a lot.
Hi @ifMike
Tested on version 1.1.8, and now the Covers buttons work all in the correct way.
Thank you a lot.
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
titlefields 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_titlesservice 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_shuffleandspeaker_repeatcapabilities (SHUFFLE_SET, REPEAT_SET features)- Binary sensor alarm types: Added device classes for
alarm_vibration,alarm_occupancy, andalarm_presence- Device class mappings: Added
heater,switch, andvacuumcleanerto central device class mapping for correct type detectionChanged
- 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_reportfrom 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
Hi Mike,
Greate work, was looking for this!
Unfortunately i keep getting “cannot_fetch_devices“
Any ideas how to solve my problem?
André
Hi Andre,
Did you follow instructions @ post 1 of this topic?
Yeah, step by step
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
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é
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.
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
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
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.
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:
Don’t have screenshot for this one. I’m in the smartphone.
Bur this one breaks all my Energy dashboard. ![]()
2 Partial Device unavailable:
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
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.