Home Assistant

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Technical_Raisin_246 on 2026-06-12 16:49:23+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/maxi1134 on 2026-06-12 14:04:13+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/thediffi on 2026-06-12 13:32:16+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Leather_Idea_2122 on 2026-06-12 10:56:24+00:00.

Hey all, HA Voice PE user here running local STT on a N100.

I've been frustrated with the long delay between finishing a sentence and hearing the assistant respond and tracked it down to the way wyoming-faster-whisper works: it buffers your entire spoken utterance into a WAV file, then starts inference only after you stop talking.

I added streaming ASR support using sherpa-onnx's OnlineRecognizer. The model now decodes audio chunks as they arrive, so for me on my N100 by the time I stop speaking most of the inference is already done.

In day-to-day use it makes a real difference and the assistant feels much more responsive. In fact, HA assist debug typically reports 0s-0.5s STT time only. In past it took twice the time of the recorded audio after I stopped speaking (3s spoken command -> 6s processing after I stopped speaking before it even went into LLM/local pocessing).

To try it:

Pull the Docker image:

docker pull ghcr.io/pkrahmer/wyoming-faster-whisper:latest

Run it with the streaming English model:

--stt-library sherpa --model sherpa-onnx-streaming-zipformer-en-2023-06-26 --language en

I use this German model at home:

--stt-library sherpa --model sherpa-onnx-streaming-zipformer-de-kroko-2025-08-06 --language de

Fork and details: https://github.com/pkrahmer/wyoming-faster-whisper

Happy to answer questions. Would love to know if others notice the same improvement.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Zealousideal-One5210 on 2026-06-12 08:44:00+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/thewillmiller on 2026-06-12 10:40:08+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/ElementZoom on 2026-06-12 03:42:37+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/KoalaPsychological95 on 2026-06-12 01:43:07+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Kaytzo on 2026-06-11 19:12:31+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/angrycatmeowmeow on 2026-06-11 22:27:42+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/mowdtocqks8 on 2026-06-11 23:59:42+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Rude-News-8416 on 2026-06-11 16:40:25+00:00.

If you rely on home automation for critical tasks like climate control, a single offline sensor can create a precarious situation. Imagine your bedroom heater stays on for hours because your nightstand temperature sensor ran out of battery and went unavailable, leaving your automation blind. Your room becomes a sauna, and you do not realize it until you wake up sweating.

The common way to fix this involves building complex automations loaded with conditions to check if sensors are online. These grow unwieldy, hard to maintain, and a nightmare to debug when things go wrong.

The Sensor Failover blueprint offers a better path.

It wraps your primary sensor and a pool of backups into a single, reliable entity. If your trusted primary sensor goes offline, the blueprint instantly falls back to an average of any backups currently reporting. You can even apply weights if some sensors are more accurate than others.

Your downstream automations never see the underlying connection issues. They simply read one unbreakable sensor that stays online even when the individual parts are acting up.

I've been working on simplifying this in my own setup and think I've come up with a simple and repeatable solution. I've posted the full details, setup instructions, and the import link on the Home Assistant community forum:

https://community.home-assistant.io/t/stop-freezing-in-the-dark-build-unbreakable-sensors-with-the-failover-blueprint/1013598

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/bradcrc on 2026-06-11 15:05:13+00:00.

A couple people had asked for an update after I updated a few things. Bonus second fish. Hopefully someone finds this at least mildly amusing. I'm still giggling like a child when I play with them, but then I'm a dork.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Anxious-Inevitable97 on 2026-06-11 08:50:16+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Gullible_Low_1742 on 2026-06-11 02:35:20+00:00.

Free local license plate recognition for Home Assistant — packaged as a copy-paste template (I built this)

https://i.redd.it/i15pz4e2fk6h1.gif

Normally, getting plate recognition into HA means stitching together Frigate, a separate AI service, and a bunch of YAML/MQTT automations. Instead, this is one self-contained template you just copy — no extra services to wire up.

After copying, a setup wizard walks you through four steps:

1. Camera — USB/CSI, RTSP, or ONVIF (ONVIF is auto-discovered)
2. HA connection — address/port + a long-lived access token
3. Recognition — Fast vs Accurate mode, and plate region (US / EU / KR)
4. Filter — minimum confidence + hold time. By default a plate has to be read consistently for 3 seconds before it reaches HA, so momentary misreads get filtered out.

Every plate it reads shows up in HA as a "License Plate" sensor entity you can automate off — open the gate for known cars, log entries/exits, alert on unknown plates, and so on.

Quick start

1. Install Grablo — runs on a Pi 4/5, Jetson Nano, Windows, or Mac
2. Hit "Copy to my projects" on the gallery template
3. Open the project, and the wizard launches automatically

There's a phone dashboard for the live feed + recent plates too (needs the Grablo app), and settings stay editable later from an Admin menu.

It's free. Link is in the comments — happy to answer any questions.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Andysb123 on 2026-06-10 21:17:57+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/CannonLab-Proxy on 2026-06-10 20:45:48+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/avimakkar on 2026-06-10 19:23:35+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/beanery-bun on 2026-06-10 21:48:17+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/xkrolfo on 2026-06-10 21:41:33+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/ElementZoom on 2026-06-10 20:38:24+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/CantaloupeHeavy996 on 2026-06-10 19:08:30+00:00.

https://preview.redd.it/h6tygllq7i6h1.png?width=2894&format=png&auto=webp&s=3816bf630e8d54f5225575a13950df45337d535b

Hey everyone,

Every time I needed to expand my Home Assistant setup or configure an NVR like Frigate, I hit the same wall. Checking for true ONVIF support, sub-stream resolutions, PoE vs. WiFi, or physical IP ratings meant opening 15 different tabs of scattered retailer specs and vendor PDFs.

To fix this, I compiled a fully queryable database (JSON + CSV) covering 50+ major brands (Hikvision, Dahua, Reolink, Axis, Amcrest, Tapo, UniFi, Ubiquiti, etc.).

What's inside for smart home builders:

• Local Control Check: True ONVIF / RTSP protocol support flag.
• Power & Connection: PoE / WiFi / Battery / 4G filters.
• Hardware Specs: Resolution, sensor size, lens, night vision range.
• Enclosure: IP (weather) and IK (vandal) ratings.
• Audio: Two-way audio support.
• Availability: Regional market tags (handy for filtering what you can actually buy in the US vs. EU/UK).

It's 100% Free, CC0 (Public Domain), no accounts, and no subscriptions. Just clean data to help you pick the right local hardware.

• Browse the web UI: https://ch-bas.github.io/cctv-camera-database/
• GitHub Repo: https://github.com/ch-bas/cctv-camera-database

If you notice a camera model missing from your own setup, there's a simple GitHub issue form to submit it—no git cloning or coding required. Hopefully, this saves you some tab-clutter on your next hardware upgrade!

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Tanner234567 on 2026-06-10 14:49:21+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/ar0v3r on 2026-06-10 04:05:54+00:00.

Hi all! Sharing progress on my E1003 ESPHome project- nothing particularly special on the calendar side, but I think I've worked out the battery optimization with some real world numbers. TL;DR: I'm seeing what looks like 3+ months of battery life at 4hr refreshes. The Github is here with a picture here. Seeed link.

I wanted an e-ink display on the fridge for family scheduling, ideally wireless. Comparing the TRMNL X and the E1003 (same display, same ESP32S3 but a few key differences), I went with Seeed (despite their stated lack of ESPHome support) after seeing this XDA page. $182 shipped to California, arrived from China in under a week. Several mounting options on the back...4 cup magnets and 4 M3x10mm screws later, it's on the fridge.

The device looked great out of the box, good overall build quality with metal enclosure, touchscreen and sensors are nice-to-have. Unfortunately, taking a multimeter to the device showed deep sleep was drawing ~4mA, enough to kill the battery in 20-30 days and turn wake power consumption basically irrelevant. After some digging (Seeed publishing the schematics was a huge help here), I found that the SD card and touchscreen driver pins were floating HIGH during sleep. Properly holding those pins LOW dropped the sleep current to below my meter's detection limit. I'm losing ~1% battery/day (give or take) over 10 days, which projects to roughly 3+ months...good enough that I've shelved the Adafruit TPL5110 hard power cut I had planned (which could potentially triple that number). Overall I'm very happy with the outcome, and I think the time savings + quality of components was worth the cost difference vs going full DIY with the build.

Special thanks to u/averitablerogue for giving this code a test on his project as well.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Original_Might_7711 on 2026-06-10 12:32:37+00:00.