Hi!
It’s not in the HACS store yet. Will add that at a later, more stable, stage.
Did your situation improve? Can you also check the logs?
→ Settings → System → Logs → “Show raw logs”
Hello @ifMike I’d like to try your integration, but I still have a question. All my ZigBee and Zwave devices are already on HAS, and I want to keep them that way. Can I choose which devices will be copied to HAS?
To answer this, yes it’s there:
Home Assistant community app
This app adds your (selected) H.A. devices to Homey
Yes, you can see this for yourself as you configure the integration.
Once downloaded through HACS, go to “Devices and Services” and “Add new integration”. Then search for “Homey”.
Once you have entered the IP of your Homey, and given it the API key (with correct permissions), you will be prompted with a list of all your devices. Here you can deselect them. You can even do this after if you accidentally added something you did not want.
Nothing will be added until you press “Add”. So you can see that before you go all the way 
The beta version isn’t working. The error message is “setup error, import error”.
@ifMike Thanks for your quick reply. I’ll give it a try.
Logger: homeassistant.loader
Quelle: loader.py:1275
Erstmals aufgetreten: 21:31:23 (5 Vorkommnisse)
Zuletzt protokolliert: 21:34:18
Unexpected exception importing platform custom_components.homey.config_flow
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/loader.py”, line 1275, in _load_platform
cache\[full_name\] = self.\_import_platform(platform_name)
\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/loader.py”, line 1307, in _import_platform
return importlib.import_module(f"{self.pkg_path}.{platform_name}")
\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/util/loop.py”, line 201, in protected_loop_func
return func(\*args, \*\*kwargs)
File “/usr/local/lib/python3.13/importlib/_init_.py”, line 88, in import_module
return \_bootstrap.\_gcd_import(name\[level:\], package, level)
\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “<frozen importlib._bootstrap>”, line 1387, in _gcd_import
File “<frozen importlib._bootstrap>”, line 1360, in _find_and_load
File “<frozen importlib._bootstrap>”, line 1331, in _find_and_load_unlocked
File “<frozen importlib._bootstrap>”, line 935, in _load_unlocked
File “<frozen importlib._bootstrap_external>”, line 1027, in exec_module
File “<frozen importlib._bootstrap>”, line 488, in _call_with_frames_removed
File “/config/custom_components/homey/config_flow.py”, line 20, in
from .device_info import get_device_type
File “/config/custom_components/homey/device_info.py”, line 69
return "light"
IndentationError: expected an indented block after ‘if’ statement on line 67
I know. I just saw it. It was an indentation error.
Redownload the newest BETA from HACS, restart HA and all should be good.
Also, please try to create issues on the GitHub instead.
Also, they are not really “copied”. Because if you remove the integration they will be removed again.
And if you create a “dashboard” with these devices and remove the integration they will offcourse not work, and the dashboard will look “broken”.
But if you re-install the integration again, the dashboard will just return to it’s working state with the same Homey devices..
1 Like
After reinstalling the beta version, the import error no longer occurs. Importing individual roller shutters is successful. However, when I import all roller shutters at once, the entity is not created correctly and it becomes uncontrollable. A strange error…
@Undertaker , Thanks, I’ve found the app and it works likes a charm. 
If anyone wants to try it. I actually managed to get Socket.IO working for real-time updates.
No more “polling every 5 seconds” (I still use that as a fallback)
From Homey to HA it could take a second.. But from HA to Homey - that’s milliseconds.
Build: v1.1.5-beta.4
Added
- Real-Time Updates: Full support for real-time device updates via Socket.IO
- Integration now uses Socket.IO for instant device state updates when available
- Device changes in Homey (via app, physical switches, or automations) appear in Home Assistant immediately (< 1 second)
- Socket.IO provides bidirectional communication for instant feedback on control commands
- Automatic fallback to polling (every 5 seconds) if Socket.IO connection fails or disconnects
- Seamless reconnection: Socket.IO automatically reconnects if connection is lost
- Connection status clearly logged: INFO when Socket.IO connects, WARNING when it disconnects and polling takes over
- Polling continues as backup even when Socket.IO is active, ensuring updates are never missed
- Works with both local Homey devices and self-hosted Homey servers
Fallback mechanism:
- If Socket.IO fails or disconnects, fall back to HTTP polling every 5 seconds
- Polling continues as a backup even when Socket.IO is active
- Clear logging indicates when Socket.IO is active vs when polling is used
I’ll keep it in the beta for now until everything has been tested, as there will probably be more issues to fix from 1.1.5 (main) as they are reported (but not many so far).
This is a beta version - Use at your own risk. Report issues on GitHub.
2 Likes
I deactivated the MQTT hub today. I will observe whether the hub devices are really no longer necessary.
So far, I have only noticed that warnings from the DWD weather warnings app (text) are not being transmitted. However, before I report an error, I need to take another close look at it.
@Peter_Kawa , Thanks I already use this app. I have an Orcon MVS at home. To connect it to Homey, I used tips from this forum to install the OrconWifiController in the MVS, after which I was able to connect it to HA. To make the MVS visible in Homey, I installed the Home Assistant community app. At the time, I couldn’t install the Sonoff button SNZB-01P in Homey. Therefore, I installed it in HA. Then I had the button’s functionality available in Homey. Apparently, several Sonoff products are now supported through a Homey app, so I only need HA to access the Orcon from Homey. Great work and thanks to these developers.
1 Like
Well it disconnected again, had to reconfigure to add all the devices again (see gap in screenshot)
Will try to find some Logs from that period if possible.
Here is a log:
Logger: custom_components.homey.homey_api
Bron: custom_components/homey/homey_api.py:163
integratie: Homey (documentatie, problemen)
Eerst voorgekomen: 13 januari 2026 om 21:09:59 (1 gebeurtenis)
Laatst gelogd: 13 januari 2026 om 21:09:59Failed to get devices from any endpoint
Hi!
Are you on the 1.1.5 (e.g. not beta or dev)?
What device version of Homey are you using?
How is HA installed?
Is there nothing else in the log? (Please check the “raw” log if you have that). In Log → Click the three dots to show it.
Share as much information as you can as this could be caused by a thousand different external causes.
Just wanted to add this, as it’s super important and will arrive in the next stable release (this is currently in the BETA if you already want to try it):
You will need to update your API key in the future. If you have already just set “all permissions” you’re all set. But for the upcoming release your will need the “System” as well (homey.system.readonly).
The reason is below, and I promise that this is a game changer!
Major Real-Time Updates Release
Build: v1.1.5-beta.5
This is a significant update that transforms the integration from polling-based to real-time event-driven updates. Device state changes in Homey now appear in Home Assistant instantly (< 1 second) instead of waiting for the next poll cycle (previously 10 seconds).
IMPORTANT: API Key Requirement
-
This feature requires a new API key with the
homey.system.readonlypermission enabled -
Go to Homey Settings → API Keys and create a new API key
-
Enable the System → View System permission (
homey.system.readonly) -
After creating the new API key, update your Home Assistant integration configuration with the new key and restart Home Assistant or reload the Homey integration
-
Without this permission, Socket.IO real-time updates will not work and the integration will fall back to polling
-
The integration will continue to work with polling if the permission is missing, but you won’t get instant updates
What This Really Means:
- Before: When you turned on a light in Homey, Home Assistant would show the old state until the next poll (up to 10 seconds later)
- After: When you turn on a light in Homey, Home Assistant updates instantly (< 1 second) - the UI reflects reality in real-time
- Bidirectional: Commands sent from Home Assistant to Homey also get instant feedback
- Seamless: If Socket.IO connection fails, the integration automatically falls back to polling (5-10 seconds)
- Efficient: When Socket.IO is active, polling reduces to 60 seconds (safety net)
3 Likes
It’s 1.1.5 stable release.
HA runs in a virtual machine on a Unraid server as Home Assistand OS. Which is the latest version.
This is the only logs I see when pressing the 3 dots regarding the homey integration
2026-01-15 00:44:08.962 ERROR (MainThread) \[custom_components.homey.homey_api\] Failed to get devices from any endpoint
2026-01-15 00:44:30.786 ERROR (MainThread) \[custom_components.homey.homey_api\] Failed to get devices from any endpoint
2026-01-15 00:44:52.738 ERROR (MainThread) \[custom_components.homey.homey_api\] Failed to get devices from any endpoint
2026-01-15 00:45:14.754 ERROR (MainThread) \[custom_components.homey.homey_api\] Failed to get devices from any endpoint
2026-01-15 00:45:36.770 ERROR (MainThread) \[custom_components.homey.homey_api\] Failed to get devices from any endpoint
2026-01-15 00:45:58.786 ERROR (MainThread) \[custom_components.homey.homey_api\] Failed to get devices from any endpoint
2026-01-15 12:30:38.991 ERROR (MainThread) \[custom_components.homey.homey_api\] Failed to get devices from any endpoint
2026-01-15 12:30:49.475 ERROR (MainThread) \[custom_components.homey.homey_api\] Failed to get devices from any endpoint
I did notice some other hiccups to a Hue bridge. So will have a look at possible network issues.
Thanks for the report - this helps a lot
The error:
“Failed to get devices from any endpoint”
This means Home Assistant temporarily could not reach any of Homey’s local REST endpoints (devices, zones, apps, etc.).
This is almost always caused by network reachability issues, not by the integration logic itself.
What you can try
Please try / check the following:
1. Use a fixed IP for Homey (recommended)
You already noticed DNS → IP helped initially
Please make sure:
- Homey has a static IP (either set in your router or DHCP reservation)
- You use that IP in the integration config (not hostname)
Homey mDNS/hostnames are known to “disappear” temporarily on some networks.
2 Check network isolation / VLANs (very common on Unraid)
Since HA runs:
- in Home Assistant OS
- inside a VM on Unraid
Please verify:
- HA VM and Homey are on the same LAN
- No VLAN, firewall rule, or “IoT isolation” blocks traffic
- Multicast and local traffic are allowed
Hue issues at the same time strongly suggest a local network problem, not Homey-specific.
3. Test Homey API reachability when it happens 
When the error occurs, try this from the HA VM:
curl -H "Authorization: Bearer YOUR_API_KEY" http://HOMEY_IP/api/manager/devices/device
If that fails or hangs → it’s 100% network / connectivity related.
4. Increase Homey API logging (optional but very helpful)
Add this to configuration.yaml:
logger:
default: info
logs:
custom_components.homey: debug
Then restart HA and send the logs from the time it disconnects again.
What’s happening internally:
- The code tries multiple endpoints:
- /api/manager/devices/device
- /api/manager/zones/zone
- etc.
- When all fail → we logFailed to get devices from any endpoint
- That almost always means:
- TCP connection timeout
- DNS resolution failure
- ARP issue
- brief Homey network drop
The fact that:
- Hue bridge also had issues
- DNS → IP helped temporarily
- HA is inside a VM
…points strongly to Unraid networking, not the integration.
Hope this helps! 
Hi Mike, the heat pump isn’t being configured correctly with the sensors. Also, the lamps that have color and temperature settings aren’t being configured correctly in the system. I can only control the color of the lamps. Otherwise, the new system is running very well and switching perfectly! Great work, Mike.
1 Like
