Home Assistant

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Big-Edge2297 on 2026-05-23 05:00:51+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/elhouso on 2026-05-23 01:49:59+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/pREDDITcation on 2026-05-22 21:18:30+00:00.

I bought two mmwave sensors from switchbot and one of them was terrible. I left a bad review. I got an email from a third party service that switchbot hires to keep their reviews high. The rep offered to reimburse me (through paypal) if i order another switchbot item if i changed my review to 5 stars on the original product, and leave a good review on the next one.

Some may argue that it’s a company trying to do right by their customers - I see it as buying good reviews for poor quality products.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Ajpaxson on 2026-05-22 17:13:13+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Johann_VR on 2026-05-22 12:04:41+00:00.

Hey! A while ago I released an Addon for Home Assistant that turns your HA Host into an Airplay 2 receiver. I'm happy to announce that it has now been updated to the latest version of shairport-sync (the underlying Airplay 2 receiver program).

It still has all the same great functionality but in a much smaller footprint, thanks to changing the image base to Alpine.

It also lets you turn on the MQTT integration built-in to shairport-sync to use in automations, like turning on your speaker when you connect to Airplay! Feel free to check out the code and request changes/improvements, and I'll see what I can do 😄

Here's the link to the Repo: Airplay 2 for Home Assistant

*edit*:

If you missed my original post, here is a quick breakdown of how it works:

The Core Concept: This add-on makes the hardware you run Home Assistant on (like a Raspberry Pi) show up on your iPhone, iPad, or Mac as a native AirPlay device.

Audio Only: You can stream any music, podcasts, or audio straight from Apple devices to your HA host (note: video streaming is not supported). 

Hardware Setup: You can route the sound through your host's built-in audio jack, or use any standard USB sound card recognized by Home Assistant.

Just plug your Home Assistant host or USB sound card into a speaker, and you have a brand-new smart AirPlay speaker ready to go!

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Dazzling-Stable-3452 on 2026-05-22 01:00:02+00:00.

I am a software engineer and observe supply chain attacks on software (trivy, axios) happening more frequently. With use of AI for development, this may happen in HACS integrations & even HA, for me, I have started to delay the version upgrades for at least a week if my current setup is working fine and even started looking at source code for HACS integration

I am still new to open source software so happy to hear your thoughts on this especially experts in this area. Cheers!

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/bradcrc on 2026-05-21 23:12:50+00:00.

Been playing around with the voice assistant stuff, and it's so neat that it's possible with HA to have EVERYTHING run locally if you want. Voice recognition, tts, even been playing around with ollama to get local AI, which is wild that it's all running right in the same room and not some mystery cloud somewhere. just neat stuff. Having some weird ESPHome issues with the device, but still a lot of fun to play with.

STL files: https://www.thingiverse.com/thing:7357076

YAML: https://github.com/bradcrc/voice_assistant_circle_led

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/mrruss3ll on 2026-05-21 21:37:50+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Reikan-Ysora on 2026-05-21 20:04:11+00:00.

Hi everyone (again :D),

A quick word of context first: Helios is my Home Assistant card (a Lovelace card for HA) that I released a few days ago. I've had a lot of feedback since then, and I wanted to offer you a solution to a problem quite a few of you ran into.

I hesitated a lot before posting yet another message, because for the past week I've really felt like I've been flooding the subreddit, and that's not like me. But given the announcement I had to make about Helios, I wanted to give it a dedicated post. I get a lot of support messages, and I think I can finally show you a solution that should make everyone happy. So, sorry in advance for cluttering your feed a little more.

About Helios: I've been pleasantly surprised by the enthusiasm and the feedback on my card, but I also picked up on a lot of frustration on your side. For many of you, you weren't in a LiDAR zone covered by Helios.

Unfortunately, after spending many hours trying to find compatible providers for the majority of you, I hit a serious wall. Between the data formats, the incomplete websites, and the APIs that work whenever they feel like it, I tried to find a way for as many people as possible to get access to this feature. And that's when a certain u/jourdant suggested adding a feature to my card: the ability to import a homemade LiDAR map, along with all the tools to do it.

So I decided to recycle my little OVH VPS to offer you an alternative, and above all community-driven, solution: https://helios-lidar.org/.

It's an automatic conversion pipeline that supports the majority of LiDAR formats available in each country. Anyone can head to the site, convert their map, and receive a ready-to-use LiDAR map along with the YAML configuration that goes with it. I wanted this tool to be simple, free (of course), and practical. The data is only kept for 10 minutes, both to preserve everyone's anonymity and to avoid overloading my server's storage.

If any of you finds a working API for a country, all you have to do is submit a pull request on the site's GitHub repository, in the "LIDAR_SOURCES.md" file, and the whole community can benefit from that link.

It's simple, community-driven, practical, and, for now, maybe a little slow given the computing power I have :X, but I wanted to share it with you. I'm convinced that with LiDAR data, Helios's predictions are much finer and more relevant than with other forecasts.

So I'm going to stop flooding for good and let you breathe a little with this project. I'll do the same myself: I've spent a lot of hours on it recently and I'm going to ease off a bit. I plan to bring you a 1.7.0 with plenty of new features, but it'll come when it comes. I want to take the time to do things right, and above all to do my best to give you a quality card.

Hoping this card brings you as much joy as I had designing it.

Don't hesitate to keep reaching out to me by DM; I'll do my best to help you and reply as quickly as possible. I was very busy wrapping up 1.6.0, which means quite a few of you had to wait a few days before getting an answer. If that's the case, feel free to open a discussion thread on the Helios GitHub: most of the issues you've run into have probably also been hit by other users.

And for the curious, here are all the links. Everything is open source, even the site:

• The site: https://helios-lidar.org/
• The site's repository: https://github.com/ReikanYsora/Helios-Lidar
• The card's repository: https://github.com/ReikanYsora/Helios
• The page to edit to add a LiDAR coverage link: https://github.com/ReikanYsora/Helios-Lidar/blob/main/LIDAR_SOURCES.md

Please don't hesitate to send me your feedback, I strongly encourage it: that's how this tool will keep growing and improving.

And if you feel like it, feel free to drop a little GitHub star on both repos (or buy me a coffee sometime if you can). It's always nice to see that the project sparks some interest :)

Feel free to share the link too: I'm afraid the HACS integration request might take longer than expected (I'm guessing around 1 to 2 months).

And sorry for the length of this message, but the topic is a little complex and deserves, I think, to be explained properly.

Thanks everyone, and see you soon :)

ReikanYsora / Jérôme

Sorry, I deleted the previous post because it sorely lacked clarity.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/bsnel76 on 2026-05-21 06:17:20+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/TechTechno57 on 2026-05-21 03:32:49+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Virtual-Path1704 on 2026-05-21 02:05:22+00:00.

I originally got into smart home stuff for the fun side of it, but some devices genuinely ended up changing my day to day habits more than I expected.

Robot vacuums might be the biggest example for me, because I stopped having to constantly think about the floors being dirty.

Curious what devices ended up becoming background infrastructure in your home instead of just a cool gadget.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Rude-News-8416 on 2026-05-21 15:08:51+00:00.

I will start with two of mine at opposite ends of the spectrum.

The first is extremely simple. When I put my smartwatch on its charger in the evening, the house knows I am winding down. The lighting shifts to evening tones. The shades close. The whole house mode flips to sleep-ready. It is one of my least technically impressive automations and one of my most loved. The trigger is dumb. The effect is everything.

The second is more involved. The shades in my main living space are managed by an automation I call "Do Not Cook the Fish". It has four template sensors and two state triggers. It tracks LUX levels going up and down, the TV being turned on or off, and whether any windows are opened or closed. The west-facing dining room windows take full afternoon sun, which both bakes the room and causes a lot of glare.

The automation closes the shades when LUX crosses a sustained threshold, or faster when the LUX spikes high enough to be painful (cloud-and-sun afternoons in Loja are dramatic). It does not fully close the shades when a window is open, so if someone closes the window it re-evaluates and adjusts. Same for the TV. Turning it on triggers a lower LUX threshold because glare on a screen is more annoying than direct sun on a face. And the shades open all the way at the start of sunset, because the sunset over the Andes is the actual reason we live in this house and no automation gets to hide it.

The bedtime one is extremely simple but satisfying. The shades automation is more complex and impressive. Both earn their place because they make the house feel like it is paying attention.

What is yours?

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/nutstobutts on 2026-05-21 13:54:41+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/sydpermres on 2026-05-21 04:45:17+00:00.

I've been thinking of scenarios where HA might be used for my Roborock, but I'm not able to find out what HA can do better/automate which I can currently do in its own app. I understand the need of centralising usage, but this is something which I'm not able to fully creative.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/smallbaconfry on 2026-05-21 10:48:52+00:00.

Been involved in this community forever! (over 12 years I think judging by my son's age, my first project was baby monitoring.) I've never taken time to say how awesome I find you all here, every single one. Although I don't fit what seems to be the stereotypical active user from the forums, tech inclined 50+ yo male, I always feel welcome and supported. So many things have changed through the years and seriously I feel old saying it but you never to the scene guys have no idea how much easier it is now and how good you've got it, but I wouldn't trade the learning curve or experience for anything! I can only laugh at what once took maybe days or weeks to figure out comparably being solved in moments. I'm so grateful you're all here to share your knowledge and I never thought I'd find a bond with a community like this. Keep getting excited over tracking those kitty poops or whatever project it is thats getting you excited this week you silly old men, I love you all! 🩷 Xx

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Dfes1989 on 2026-05-20 23:04:19+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Chrono_Constant3 on 2026-05-20 18:00:49+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Tuxabyte on 2026-05-20 17:52:28+00:00.

Hi everyone,

I wanted to share a fun project I recently finished. Like many of you with toddlers, my daughter has developed a fascination with standing about two inches away from the TV screen. To protect her eyes and teach her to keep her distance, I decided to automate the parenting.

Whenever she gets too close (< 240cm), the TV automatically pauses. Once she steps back, it resumes. She actually adapted to it immediately and now stays behind the "invisible line" on her own!

Hardware

• Sensor: Hi-Link HLK-LD2410C (24GHz mmWave Radar)
• Board: M5Stack Atom Lite (ESP32)
• Mounted directly under the TV edge (I initially hid it inside my wooden TV cabinet, but the wood density messed with the radar scattering).

The Netflix Hurdle: Everything works perfectly for apps like SmartTube and my local TV provider app, but the official Netflix app actively blocks state updates (playing/paused) via the Android TV integration. I had to build a bypass in Node-RED to ignore Netflix so the flow doesn't get stuck.

Demo & Code:

• YouTube Demo: [https://youtu.be/AO/_Pd3kCA3k]](https://youtu.be/AO_Pd3kCA3k%5D)
• GitHub Repo with ESPHome config & Node-RED export: https://github.com/digira1n-tuxabyte/Homelab/tree/master/home-automation/tv-proximity-sensor (it's in Dutch)

Has anyone else found a reliable workaround for reading the play/pause state of the Netflix app on Android TV?

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Praline_Choice on 2026-05-19 22:49:17+00:00.

Hey everyone,

I built an open-source ESP32 LED clock ("Led'o'clock") because commercial ones lack proper smart home integrations.

My son's clock has 3 states: 🔴 Sleep 🟠 Play quietly (Time-based trigger) 🟢 Free to leave the room

(Bonus feature: the LEDs can turn off one by one as a time block progresses, acting as a visual countdown: super helpful for bedtime routines!)

In my use case, the transition to green isn't a timer! When his sister wakes up and turns on her bedroom light, an HA automation hits the ESP32 API to instantly turn his clock green. It perfectly syncs their mornings so they don't wake each other up too early.

https://preview.redd.it/ow2hk05b962h1.jpg?width=600&format=pjpg&auto=webp&s=c70dac756a88059797b2ede706915e9bbed97089

https://preview.redd.it/ucgog5si962h1.png?width=775&format=png&auto=webp&s=4404d93ea2846d377ef1f8425b5143a06c467b92

https://preview.redd.it/0sw4n6si962h1.png?width=775&format=png&auto=webp&s=244a301e7c356671cf50f2925222c5db9d8a570d

https://preview.redd.it/9p10e6si962h1.png?width=788&format=png&auto=webp&s=b5ae543f23fc633d8482aac5459ce25c7933aeca

The project (firmware, custom PCB, 3D enclosure) is fully open-source: https://github.com/denouche/led-o-clock

It also features OTA updates, fetching the latest firmware directly from GitHub.

Feel free to build it for yourself, or if you don't have the time and want to get one let me know, I have a few fully assembled units ready to ship!

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/damani112 on 2026-05-19 15:59:57+00:00.

I need to upgrade some new thermostats in my house. I have some older nest thermostats. I am looking at the Honeywell x8s, ecobee premium, and aqara W200. We are a apple house so homekit and home assistant are most important. I have upgraded my network and cameras to Unifi and and removing all my amazon/ring items.

I would love to get the best thermostat that will continue to incorporate into the home assistant space. I am leaning towards the ecobee or Honeywell. I am leery of utilizing anything from aqara, but realize that that i can limit its access to networks potentially.

Does anyone have any idea which route would be best to go? Thanks.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Reikan-Ysora on 2026-05-19 17:22:48+00:00.

Hey r/homeassistant, some of you saw the v1.5 post a few days ago and helped me clear out a long list of bugs. Today it's v1.6, big update and a clearer direction for what comes next.

For those discovering Helios: it's a custom Lovelace card that visualises live solar conditions at your home on a 3D MapLibre map. The sun arc, cloud cover, real cast shadows from buildings and vegetation (where LiDAR data is available), an optional PV production overlay with forecast, an optional battery overlay, and a scrubbable 5-day timeline that drives the whole scene through time. No API key, no signup, no cloud: tiles come from OpenFreeMap (OSM) and the weather from Open-Meteo.

Getting to this 1.6 took over 40 alpha versions and around ten betas. The card is now robust, functional, and I hope as user-friendly as possible. The goal: install it and use it fast, no headaches. I've put a huge amount of time into polishing the details to deliver the best possible experience.

What's new since v1.5.1

• Forecast calibration, Helios learns from your last 5 days of actual production and surfaces a refined kWh estimate alongside the raw model. Catches biases the model can't see (cloud forecast skew, panel soiling, install drift).
• Multi-orientation PV layouts, the editor accepts a list of arrays, each with its own tilt, azimuth, share, and optional GPS coordinates (for installs where panels sit elsewhere than the home).
• GPU-rendered LiDAR overlay, toggle the dot cloud on top of the map to see exactly which aerial scan data Helios is using.
• Architecture refactor, the two ~5k-line monoliths split into focused modules. Zero user-visible change, but the next LiDAR provider takes 30 minutes to add instead of 3 hours.
• External solar-radiation sensor input, pyranometer or any W/m² sensor? Helios uses it for live + historical data, and falls back to Open-Meteo for the forecast portion.
• 4 new LiDAR providers, Poland (national), Canada (national, via NRCan HRDEM), Germany Brandenburg + Berlin (one WCS covers both), and Vermont USA (first native US state). Helios now ships with 10 native LiDAR integrations.

Plus a long tail of fixes (PV chart quantization spike, dashboard polish on smartphone, battery cap rendering, freeze on solar-radiation sensor selection, etc., all in the changelog).

Thanks

This release wouldn't be where it is without external help:

• @jourdant (Jourdan Templeton) contributed the entire BYO local nDSM provider (PR #5), originally for NSW Australia, but the design unlocks shadows in any region where raw local LiDAR data is available. He also wrote the Python preparation toolchain (PR #11). Original idea credit: @stephenwq.
• @i6media (Frank Boon) contributed the home-latitude / home-longitude override (PR #9, useful for shared HA installs, holiday homes, or privacy) and the multi-orientation PV layout (PR #10).
• Everyone who filed clean bug reports or ideas since the 1.5 release.

If you want to contribute, the door is wide open, the codebase is now structured enough that a focused contribution doesn't have to wrestle with the rest of it.

LiDAR coverage, the priority now

The card is stable. The dashboard is finally done. The next direction is clear: extend LiDAR coverage to as many people as possible.

I've published a worldwide LiDAR provider registry: https://reikanysora.github.io/Helios/LIDAR/_PROVIDERS.html

Every public elevation API I've inspected is there, with its status (integrated, verified compatible, partially blocked, incompatible), the actual endpoint, and a curl-verified example URL. There's also a world map of the integrated providers' coverage.

If you're in a covered region, you get real LiDAR shadows. If not, two options:

1. Use the BYO local nDSM path (a GeoTIFF prepared from your country's open data, 6 config keys in Helios).
2. Request your region here or on GitHub.

The next iterations attack the "verified compatible but pending" tier of the registry: Baden-Württemberg, Austria (Steiermark + Tirol), Switzerland (swissSURFACE3D), New Zealand (LINZ), Denmark (Dataforsyningen), and a few more. Each is a provider file to write once I add the projection helper it needs. Suggestions, code contributions, or even just "here's the WCS URL for my region", all of it is useful.

Install

In HACS:

1. Add the custom repo https://github.com/ReikanYsora/Helios, category Dashboard
2. Install Helios
3. Add type: custom:helios-card to your dashboard
4. The visual editor exposes every option, no YAML needed

Repo + full release notes: https://github.com/ReikanYsora/Helios

All feedback is welcome, bugs, ideas, region requests.

And if you enjoy Helios, a little star on the repo (or a coffee for those who want) really helps me keep going with my efforts to "map" the world.

Thanks again for all the feedback, encouragement, and DMs, it really means the world.

ReikanYsora / Jérôme ;)

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/momo1822 on 2026-05-19 16:52:04+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/_insomnautik on 2026-05-19 14:22:20+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/degeneratedVirginApe on 2026-05-19 13:06:00+00:00.