Before y'all get the pitchforks out and exclaim this has nothing to do with Seattle, it does and let me tell you why.

After hearing about this vulnerability a couple weeks ago I wanted to see if I could find the flaw and recreate the researchers' findings, they are going to be disclosing the details this week at DefCon, and after a few days of research I was able to verify this is indeed real and there are vulnerable vehicles in the Seattle area.

The worse part about this is that some people are completely in the dark about this issue, because even if you don't pay the up-charge to "activate" the system it remains installed and still "active", just not to the vehicle owner :(. The linked article provides details for how someone can go about updating the system that should address this flaw.

I'm posting this in the hopes of getting the word out before this gets into the hands of the wrong individuals, and I'd be naive to think that someone else has not already figured it out. I'd post this on reddit to get some more exposure but alas those privileges have been revoked for the time being, so please feel free to spread the word there if you so desire.

P.S. I developed an Android application that can scan and detect these devices out in the wild. It does not contain the exploit, cannot connect to or control these systems and only scans the airwaves for their broadcasts. https://github.com/0xD34D/KARR_Scan

Cross posted from: https://sh.itjust.works/post/29828353

I recently worked on a personal project where I wanted to trigger a sound board using a custom wake word. I had been keeping a keen eye on the work being done for local wake word detection in ESPHome and wondered if I could make use of it in this project. While ESPHome is an amazing project, I actually have a few devices flashed with it in my HA setup, it was more than I needed. This repository is the result of my efforts to make micro wake word a standalone component I could use in my own projects.

If you happen to find this useful make sure to send your thanks to those that did all the real work over at ESPHome, especially Kevin Ahrendt 😉.

And of course, here's a little video of it in action https://youtube.com/shorts/dRHSXZUriEs bqvEoKjWCEACqld0

Made sure the stock firmware printed the example gcode that came on the SD card and then immediately embarked on my journey to get klipper running on this guy.

I didn't finish until the wee hours this morning so I've yet to really give it a go but all the essentials are operational.

Here's the GitHub link to the config I created: https://github.com/0xD34D/ender3-v3-se-klipper-config