Earlier quoted context omitted.
So my original comment was not a misunderstanding. They are smart switch drop in replacements.
Yeah, you're right. That is a weird request then, or I don't understand it either. I didn't realize something like [1] goes inside your switch. I was expecting a switch with a faceplate combined. 1: https://us.shelly.com/products/shelly-1-gen3
The era of open voice assistants
251–260 of 290 posts
Re: The era of open voice assistants
#252Earlier quoted context omitted.
As a side note, it always slightly puzzles me when I see "voice interface" and "private" used together. Maybe it takes living alone to issue voice commands and feel some privacy. (Yes, I do understand that "privacy" here is mostly about not sending it for processing to third parties.)
I don't like these interaces because unless they are button activated or something, they must be always listening and sending sound from where you are to a 3rd party server. No thanks. Of course this could be happening with my phone, but at least it have to be a malicious action to record me 24/7
Re: The era of open voice assistants
#253Earlier quoted context omitted.
Do you mean the move away from YAML first configs? I was originally somewhat frustrated, but overall, it's much better (let's be honest, YAML sucks) and more user friendly (by that I mean having a form with pre-filled fields is easier than having to copy paste YAML).
Oh thank got. Just started using HA few months ago and all these yaml is so confusing when I try to code it with ChatGPT , constant syntax or some other random errors.
so don't do that... just rtfm and it's easy
Re: The era of open voice assistants
#254Earlier quoted context omitted.
But like, isn't YAML still available for configuring things? Have they gotten rid of any YAML configs, with things that are now UI only? My understanding was that they've just been building more UI for configuring things and so now default recommend people away from YAML (which seems like the right choice to me).
Yes - for now. I think the ultimate end-goal is to get rid of the YAML config files, which, makes sense for the median user, but not for power users. For example, I have my config on GitHub and share various YAML blueprints with a friend who also has the same Solar+Battery system as I do.
Re: The era of open voice assistants
#255Earlier quoted context omitted.
A group buy for an existing product makes sense. Want to buy a 24TB Western Digital hard drive? It’s $350. But if you and your 1000 closest friends get together the price can be $275. But for a first time unknown product? You get a lot fewer interested parties. Lots of people want to wait for tech reviews and blog posts before committing to it. And group buys being the only way to get them means availability will be…
>> I want 5-20, one for every space in my house. I don't have a small house, but I'm trying to think why I would need even 5 of these, let alone 20. The majority of the time my family spends together is in the open layout on our main floor where the kitchen flows into the living room with an adjacent sun room off the living room. I'm genuinely curious why you need so many of these. I do agree that if you do have a le…
Re: The era of open voice assistants
#256Earlier quoted context omitted.
Kickstarter isn't a group buy.
Kickstarter is often basically a group buy. Project owners make MVPs and market/pitch it, get funding from the public, and then commission a large batch run.
Re: The era of open voice assistants
#257Earlier quoted context omitted.
As a side note, it always slightly puzzles me when I see "voice interface" and "private" used together. Maybe it takes living alone to issue voice commands and feel some privacy. (Yes, I do understand that "privacy" here is mostly about not sending it for processing to third parties.)
I don't like these interaces because unless they are button activated or something, they must be always listening and sending sound from where you are to a 3rd party server. No thanks. Of course this could be happening with my phone, but at least it have to be a malicious action to record me 24/7
You can test this in a couple ways: they'll respond to their wake word when the internet is down (but have an error response). You can also look at the outbound data and see they're not sending continuous traffic.
Not to say with the proprietary products that they couldn't sneakily change this on the fly and record everything, maybe even turning it on for a specific device or account.
Re: The era of open voice assistants
#258Re: The era of open voice assistants
#259Earlier quoted context omitted.
I don't like these interaces because unless they are button activated or something, they must be always listening and sending sound from where you are to a 3rd party server. No thanks. Of course this could be happening with my phone, but at least it have to be a malicious action to record me 24/7
FWIW that's not even how Alexa or Google Assistant work. Both listen locally for the wake word with onboard processing, and only when they recognize it do they send the audio stream to the server to fully interpret. You can test this in a couple ways: they'll respond to their wake word when the internet is down (but have an error response). You can also look at the outbound data and see they're not sending continuous…
Re: The era of open voice assistants
#260Earlier quoted context omitted.
It’s a great project overall, but I’ve been frustrated by how anti-engineer it has been trending.
Install the Node-RED add on. I use that to do the tricky stuff. Install the whole thing on top of stock Debian "supervised" then you get a full OS to use. You get a fully integrated MQTT broker with full provisioning - you don't need a webby API - you have an IoT one instead! This is a madly fast moving project with a lot of different audiences. You still have loads of choice all tied up in the web interface.
I’m currently running, HA, Frigate and pihole on same machine