It depends on what your use case is, I have both homebridge and homeassistant setup for different devices. But I also use HomeKit as the main hub of my home automation not home assistant.
For me both services are primarily for things that don't natively support HomeKit (my vacuum, logitech harmony, the receiver for my sound system, and a couple other things).
I also use home assistant to expose a couple of fake accessories for state tracking for some automation, and I do a little bit of more advanced automation in home assistant.
I use both though since some plugins in the home assistant side are way to complex (and causes issues due to that complexity) for what I need to just expose controls to homekit, or don't work as well as the homebridge version.
I haven't used homebridge, but have used HA in the past when I had lights and things hooked up. The UX and configuration surface always felt janky to me. So many little paper cut annoyances across every control / window / menu that you touch. The screenshots of homebridge seem much better at a cursory glance - if so, that's a net gain.
The discussion about Claude always omit the important context - which language/platform you’re using it for. It is best trained for web languages and has most up to date knowledge for that.
If you use it for Swift it is trained on whole landfill of code and that gives you strong bias towards pre-Swift 6 coding output. Imagine you would give Claude a requirements for a web app, and it implements it all in JQuery. That’s what happens with other platforms.
The author of website will be flooded with submissions about almost every known brand.
Instead of ledger of bad brands it should track brands that remain, - it will be a lot easier and less work.
reply