My main use case for voice is for things that I haven’t been able to (reasonably) automate. For a couple of examples:
It’s all fairly trivial stuff to do manually but I think that’s probably true for the vast majority of home automation.
VSCode in HA is primarily useful for editing config files and with all the latest pushes towards config in the UI it’s not as useful as it used to be. That said, it does integrate with HA to provide completion for entities and some basic yaml validation.
I also use it to work on ESPhome configs as well as some simple file management. I never got SSH working correctly on the HA VM and VSCode has been a convenient workaround.
This is the answer. I have a handful of notifications setup this way. My routing logic tends to be much simpler but that’s what “choose” is for.
The only tricky one may be to hold the notifications until later. I probably wouldn’t bother with that personally. Instead I use the do not disturb functionality on the phone.
https://companion.home-assistant.io/docs/notifications/actionable-notifications/
There is a custom integration available for Dreame devices. It’s what I use for my L10SU
I believe so. They keep the method pretty secret so it can keep working as long as possible. There are also rumors that new methods may be announced in a month or so.
I believe it is still rootable but via a non-public method. There is a system called VAERS that you request help from. I went through it for one of mine (I had 4 before Dreame lost one during warranty work) and the response was fast and helpful.
You have exactly summed up my views. I currently have a 2020 MY and it convinced me that I probably won’t buy another ICE vehicle. With all the crap coming out of Tesla and Musk lately, I also can’t imagine getting another Tesla.
I’m just waiting for NACS to be built in and hoping today’s layoff news doesn’t ruin that as well…