homeassistant

14387 readers

3 users here now

Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io

founded 2 years ago

MODERATORS

GreatAlbatross@feddit.uk

greatalbatross@lemmy.world

334

Voice control is dangerous (infosec.pub)

submitted 2 weeks ago by Dave@lemmy.nz to c/homeassistant@lemmy.world

36 comments fedilink hide all child comments

This morning my kid asked the voice assistant to "Turn off the computers in this house".

I heard it, thought well that's a strange request but seems harmless because how is home assistant gonna turn off computers.

Me a little while later, "why is shit broken? What's happening!"

Turns out dumb me had adguard exposed to the voice assistant, it switched off all the adguard settings including the DNS rewriting that is the cornerstone of many of my self-hosted services.

I've since revoked that access.

you are viewing a single comment's thread
view the rest of the comments

[–] AlternateRoute@lemmy.ca 28 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

I’ve since revoked that access.

A few releases ago they made it so you can DEFAULT new entities NOT to be controlled by the VA.. I cleared ALL entities and changed the setting. I only add things one at a time to voice control now.

SO many integrations ad switches it is a high risk to default the VA to have access to all new ones.

[–] Dave@lemmy.nz 3 points 2 weeks ago

I think that setting has been there as long as I've had a voice assistant (since I got my HA Voice Preview in January). I knew it existed but I let it expose them. I probably shouldn't, because I always have to review it after adding anything new since it normally doesn't get what I wanted exposed/not exposed.