I am using both HA and Homey.
I have been a long time Homey user but have always struggled with the dashboarding capabilities.
I wanted a wall mounted dashboard that provided me with insights and easy access to devices such as lights etc.
For years I have used the Node Red/ MQTT solution as provided in an excellent way by Satoer (Node Red: A widget based dashboard working with Homey trough MQTT).
But (styling)capabilities are still limited and since a few years I now use HA for dashboarding.
Homey is in the lead and ‘owns’ all the devices (zWave and Zigbee, Solaredge, Gardena etc ) and controls all the automations via flows.
HA runs on a Pi4 and is connected to Homey via MQTT and discovers all Homey devices automaticaly. In HA I have created a custom dashboard that fits all my needs (displayed in kiosk mode on an old iPad)
In HA I have also added many other integrations and datafeeds that I like on my dashbord (such as weather data, Unifi data, carbage collection data, camera integrations etc).
I think that in this way I use the strongest point of both platforms:
-
Homey for easy device management, out of the box Zwave and Zigbee connectivity, a good looking app with remote access & notification capabilities (helps in the WAF…
) and easy automations with flows. Things that HA is not delivering yet.
-
And HA for advanced dashboarding and tons of usefull and fun integrations that homey is not delivering yet . These Integrations are realy easy to set up via the GUI, but the dashboarding I wanted still requires a lot of yaml.
And as MQTT works both ways I am really flexible going forward.
For example I can start creating automations in HA if I think that would be usefull. Currently I am not yet doing this, but with pressing buttons on the dashboard to control lights I am in fact already feeding commands into Homey.
Just my 2 cents…