this post was submitted on 02 Aug 2023

118 points (99.2% liked)

homeassistant

12025 readers

115 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 1 year ago

MODERATORS

GreatAlbatross@feddit.uk

118

2023.8: Translated services, events, and wildcards! (www.home-assistant.io)

submitted 1 year ago by TreeGhost@lemm.ee to c/homeassistant@lemmy.world

20 comments fedilink hide all child comments

all 21 comments

sorted by: hot top controversial new old

[+] cwagner@lemmy.cwagner.me 13 points 1 year ago* (last edited 1 year ago) (2 children)

[deleted]

[–] xtremeownage@lemmyonline.com 11 points 1 year ago (3 children)

Can't wait until we have a device, that is as easy/affordable as picking up a new Alexa..... that works with home assistant.

Once, that problem is solved in a way that doesn't involve soldering and 3d printing.... voice will really start to take off.

[–] TimeSquirrel@kbin.social 1 points 1 year ago (2 children)

I'm surprised these things have been on the market for almost a decade now and nobody has really attempted or figured out how to crack them and put third party firmware on them.

[–] ThePantser@lemmy.world 3 points 1 year ago

There is this but it's replacing almost everything inside. https://hackaday.com/2023/07/23/google-nest-mini-gutted-and-rebuilt-to-run-custom-agents/ I am hoping they sell the boards but most likely won't out of fear of Google lawyers.

[–] xtremeownage@lemmyonline.com 1 points 1 year ago

A year or two back, I think I looked for information on them, and found a few people who disassembled them..... but, the hardware was pretty custom and specific for the application.

That being said, One of these days, I'll take apart one of the ones I have laying around here, and see if it might be possible to solder a esp32 somewhere on the board, to take control over some of the functionality.

[–] DesertCreosote@lemm.ee 1 points 1 year ago (1 children)

Willow looks like it's a decent chunk of the way there, as soon as the hardware is more generally available.

[–] xtremeownage@lemmyonline.com 1 points 1 year ago (1 children)

hardware is more generally available.

Yup, that is the one missing piece.

I have been using the new piper/wyoming stuff, and it actually works extremely nicely. I am very impressed with it.

[–] sylverstream@lemmy.nz 1 points 1 year ago* (last edited 1 year ago) (1 children)

I've tried that, but I couldn't get it to work with the Android app as my instance is on HTTP as it's internal only. Think they solved that. Also, I'm running the docker version, so can't install add-ons.

But, without Home Assistant Cloud, and without 3d printing / custom printing, the only hardware available for voice assist is the mobile app, right? I have a Chromecast with remote, so could use Google Assistant, but I believe that requires HA Cloud.

/edit: just found this doc about GA + HA, it either requires HA Cloud, OR a publicly accessible HA instance with SSL. I have neither :D Will look into HA CLoud.

[–] keyez@lemmy.world 1 points 1 year ago

Yes the latest July release allows for voice assist over HTTP and internal access.

And HA blog has a post with a $13 mic which I bought and works but it needs to be plugged in and press a button to activate so rather limiting.

[–] QHC@kbin.social 1 points 1 year ago

I agree! The pace things are moving has me very excited. I might need to brush the dust off my soldering iron so I can convert my 5+ nest speakers into something that is fully local and open source.

[–] domi@lemmy.secnd.me 4 points 1 year ago

I set it up last month. Local voice control is not quite there yet but it looks promising. Home Assistant's cloud assistant works really well though.

Just needs wake words now and this could be a game changer. Really looking forward to see where this is going.

[–] spitfire@lemmy.world 4 points 1 year ago (2 children)

I am NOT looking forward to the MQTT breaking changes. With Z2M and 80+ Zigbee devices it is going to be awful if there aren’t any good tools to help with naming transition.

[–] sapo_peta@kbin.social 8 points 1 year ago* (last edited 1 year ago)

fyi, just found this PSA: MQTT Name changes in 2023.8.

TL;DR: Once Z2M updates in September, the warnings will go away.

[–] spacemanspiffy@lemmy.world 3 points 1 year ago (1 children)

I am a little confused what is changing here. I set all my device names in Z2M for HASS and let entities name themselves. Its going to rename the entities on me?

[–] spitfire@lemmy.world 0 points 1 year ago

No, it’s throwing names you need to change

[–] AA5B@lemmy.world 4 points 1 year ago (1 children)

I’m excited by the oPower integration! My energy providers are not supported, but at least my gas company is an oPower customer, so hopefully.

I couldn’t find a list of potential customers , nor whether there is a plan to grow them

[–] captainjman2@lemmy.world 1 points 1 year ago

I'm using it now with Comed and it's awesome! So excited!

[–] Unaware7013@kbin.social 4 points 1 year ago* (last edited 1 year ago) (1 children)

Anybody know if it's possible to update to an older version? I'm back on the .4 release, and I'm kinda nervous about upgrading to the latest version without stepping through earlier releases with all the breaking changes I'm aware of since then.

ETA: Figured it out, if you're running HAOS like me, its as simple as opening the console and running

ha core update --version 2023.5.4 --backup

with your version in place of the 5.4 version obv. Interim upgrade seems to be working so far, will give it a few days and start ratcheting forward until I break something. HAOS instructions and HA Core instructions

[–] swm5126@lemmy.world 1 points 1 year ago (1 children)

I just updated from 2022.11 the other day. I took a VM snapshot first but surprisingly everything is working fine. I have a bunch of custom integrations so I was really thinking I’d run into trouble.

Make a backup and give it a shot.

[–] Unaware7013@kbin.social 1 points 1 year ago

Did you update straight to 2023.8.x from 2022.11? If so, glad to hear you didn't break anything!

I actually just figured out how to do an interim upgrade this morning (and dropped in my comment it for future needs) and it seems to be working so far. Planning on ratcheting forward over the next week and seeing if anything breaks. I've got a snap on my machine for my current update, but I don't want to lower the PAF with spending all day futzing with my system because I broke something. Its bad enough I'm having to deal with my one of my docker containers that shat the bed last night when I updated it...

[–] fourohfour@lemmy.fmhy.net 3 points 1 year ago

oPower integration is very welcome. Though pricing isn't working for me.