Well, it depends. But I think it’s more user-friendliness than quality. For example, in HACS you see many integrations with vague names (not the name of the actual brand). This might confuse users.
But Home Assistant integrations also often reference to checking the logs, for example. That’s not very user-friendly, especially for users who don’t even know what “logs“ are in the first place. That is obviously the reason why Homey hides diagnostic reports to users.
In my Homey apps, I try to hide the actual error message to the users, because most likely won’t even understand what is meant by such an error message. Whenever an error occurs that is not supposed to happen, the app will simply use “An unexpected error occured“ or similar instead of the actual error message or stack trace. Any (error) message that looks too confusing to an ordinary user should stay hidden to the user in a Homey app in my opinion. However, this isn’t the case for Home Assistant. In Home Assistant, the people want full control over everything: everything should be visible. While some power users like this full control, it’s definitely not for everyone.
In my opinion:
- Home Assistant = for users who want full control over the code that runs on their devices and want every part of it to be visible, and are willing to debug any issues when they arise.
- Homey = for people who want something that simply works, out of the box, without thinking much about the technical aspect of it.
While I am a power user, I still like the simplicity of Homey with its easy-to-use (advanced) Flows. I also like that Homey uses JS instead of Python, because JS is way easier to understand for me.
For the integrations, I think Home Assistant and Homey have similar integrations. Some integrations are available in HA but not in Homey, and some integrations are only available on Homey and not on HA.
