Earlier quoted context omitted.
Nice! What languages do you support? (for STT & TTS)
Thanks! STT is "just" a very heavily optimized (beyond even faster-whisper) Whisper implementation, so all of those languages[0]. For TTS we now use Coqui, which has a wide range of models with various voices, languages, etc. It even supports Meta MMS which has support for 1,100 languages[1]. [0] - https://github.com/openai/whisper#available-models-and-langu... [1] - https://about.fb.com/news/2023/05/ai-massively-mul…
Home Assistant 2023.11
181–190 of 195 posts
Re: Home Assistant 2023.11
#182As much as I love ha it still it pretty high maintenance
Re: Home Assistant 2023.11
#183Earlier quoted context omitted.
I don't think you'll find much software that touches the day-to-day life of the average user as much as Home Assistant does. Living through breaking backwards compatibility and deprecations I think is the paint point- just continued paper cuts for the grumpy here. it's easy to lose sight of how great a piece of software it is
My Samsung, Google, Wyze, and car charger integrations slowly stopped working. I'm replacing everything with dumb stuff again, because the breakage (not usually HA's fault) is just too annoying. This stuff needs to be an appliance, or managed by someone else, to make sense.
Though such an approach doesn't work with many other integrations.
Re: Home Assistant 2023.11
#184The only negative thing I can say about HASS is that getting it running in Kubernetes with a USB Zigbee/Zwave adapter is a real pain. I've got a local cluster and had it working once, but had to rebuild everything for some unrelated reason, and haven't been able to get it consistently working since. There are too many in-built assumptions about how you're running it and the USB access. Documentation assumes that _may…
I'm using zigbee2mqtt in K8s and just pinning the deployment to a node and mapping the device as a volume: https://github.com/LukeChannings/kube-config/blob/3b61c7607c...
Should work the same for Home Assistant, but I don't use HA for Zigbee directly, instead using z2m -> MQTT -> HA, which I've found to be very robust.
I'm waiting for a new K8s cluster (based on CM4) and when I re-implement all of this I'll get a network-based PoE Zigbee device (https://smlight.tech/manual/slzb-06/), that way I can un-pin the deployment and look at high availability Zigbee via MQTT (something Home Assistant doesn't support)
Re: Home Assistant 2023.11
#185Earlier quoted context omitted.
I don’t understand the negativity at all. HA rivals or exceeds commercial automation systems like crestron, RTI, etc. clearly those people don’t have any industry experience. I’ve generally never had an issue with HA beyond my own fault, like a buggy integration.
I’ve never seen Crestron or RTI used for commercial building automation, aside from Crestron lighting controls on a rare occasion. Crestron is mostly an A/V company with a lighting controls line as far as I’m aware. Building automation is owned by Johnson Controls, Carrier, Siemens, and Honeywell. There are some smaller manufacturers around, but those four plus Trane sell the vast majority of commercial building auto…
Re: Home Assistant 2023.11
#186With this in mind, I am surprised by the fact that people complain about HA. Software that uses words such as YAML, Integration etc. is obviously not a TV that requires a remote with 5 buttons. I would not complain about my TV not making coffee.
I use HA for many years now and I had it breaking exactly once, at a key change. I had automated updates at that time and it just taught me to upgrade manually and read the release notes. This is the "price" you pay for a dynamic, complex system.
I found it getting simpler (and more obscure) with time and overall I think it is a good thing. I used to have everything in YAML files and getting frustrated by the UI. Now I changed my mind and do not care anymore about renaming a device directly in the UI, even though I do not know where the change is (actually I know but this is not the place you want to dig in). It just works and I like home automation but it is not my full time job either.
The learning curve is not smooth. It starts pretty much flat and then there are cliffs you climb through "eureka!" moments when you understand what is what and how it is connected. It takes some time.
The automations went a great way (very great) from the time they were completely crazy all in YAML to today where you can do most of the things in th eUI. I used the YAML version for a short time, wrote my own, discovered AppDaemon, discovered pyscript and finally (the trip above lasted a few years) I am back to the built-in solution. Nothing beats a toggle switch to disable an automation at 4am in the morning from your bed.
The documentation is a bit weird. It is very complete, but quite difficult to master. There are still things I do not understand, I see them in the documentation but still do not understand after reading it.
Fortunately there is the community which is awesome. I think all the questions I ever had were answered. There is a big "but" though: it is very helpful when you are a beginner or an intermediate user, but you are mostly on your own for more advanced things. It is not that someone does not want to help, it is rather that there are so many possibilities with HA that you are likely to hit unchartered territory at some point if you want to become an advanced user. Otherise you will be fine.
In conclusion: THANK YOU VERY MUCH HOME ASSISTANT (but my wife hates you because everything works only 90% of the time, but when it works it is awesome :))
Re: Home Assistant 2023.11
#187I used it initially because when my kids were toddlers they would get up and turn on the lights in the middle of the night and play or leave them on. I set up some rules so it would block turning on the light between 8 and 6 but let the bathroom come on for 5 minutes at a dim level.
WAF = Wife acceptance factor KAF = Kid acceptance factor
Re: Home Assistant 2023.11
#188Earlier quoted context omitted.
My Samsung, Google, Wyze, and car charger integrations slowly stopped working. I'm replacing everything with dumb stuff again, because the breakage (not usually HA's fault) is just too annoying. This stuff needs to be an appliance, or managed by someone else, to make sense.
I just took the ZigBee approach. A vendor can't (usually) remove or break the features available and it'll just work for years and years. Though such an approach doesn't work with many other integrations.
Re: Home Assistant 2023.11
#189Earlier quoted context omitted.
I’ve never seen Crestron or RTI used for commercial building automation, aside from Crestron lighting controls on a rare occasion. Crestron is mostly an A/V company with a lighting controls line as far as I’m aware. Building automation is owned by Johnson Controls, Carrier, Siemens, and Honeywell. There are some smaller manufacturers around, but those four plus Trane sell the vast majority of commercial building auto…
Nope incorrect. Crestron and rti offer end to end solutions for whole home automation including the commercial space. Clearly you don’t care and/or get home automation, no skin off my back. It’s not for everyone
Re: Home Assistant 2023.11
#190I love HA but hate how manufacturers are going all-in on preventing people from integrating their devices into the platform without an alternative. Chamberlain MyQ did this by turning on CloudFlare Super Bot Fight and 429'ing anything that doesn't look like it came from their app. That's fine and reasonable, but I can't even pay to create an OAuth client, even though I am paying for their Tesla integration, and they…