Home Assistant

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.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/objektiver_Dritter on 2026-05-19 10:57:07+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Creisel on 2026-05-19 08:45:58+00:00.

Had the feeling quite a bunch are using Grafana and should be aware of this

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/datkenny on 2026-05-19 08:26:06+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/infantkicker_v2 on 2026-05-19 00:50:32+00:00.

I've been using HA green since the beginning of the year and like all things automation and assistant I couldn't leave it be. Over the weekend I migrated to a mini PC with some decent but not crazy specs and set up a VM with proxmox. Not nearly as complicated as I thought it would be but holy smokes does it work FAST. I have a bunch of dumb dashboard things and I made a card that uses my cameras to track my dog around the house so he's easier to find so I believe the HA green was just running full tilt all the time and got laggy. now that I've upgraded I wish I started here. I appreciate all you guys for posting your own setups and experiences, it certainly pushed me to try newer and better things with my own setup.

keep it weird!

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/OkPop8490 on 2026-05-18 20:29:52+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Spare_Conclusion_579 on 2026-05-18 17:57:55+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Taggytech on 2026-05-18 16:51:55+00:00.

I noticed some of the automations I use the most now are actually the really simple ones I almost didn’t bother setting up. Meanwhile some of the more complex stuff barely gets used anymore. Curious what ended up being unexpectedly useful in your setup.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Drunk_Panda_456 on 2026-05-18 13:03:55+00:00.

I spent several days debugging what I thought was a code issue with my Home Assistant thermostat automation and finally figured out what was happening. Posting in case anyone else runs into this.

If you’re seeing a cryptic error like:

“Provided temperature X is not valid. Accepted range is X to X”

Here’s what’s going on. Matter communicates in Celsius internally. When HA sends a Fahrenheit setpoint to a Matter thermostat, it converts it to Celsius and your value may land right at or just over the device’s ceiling due to floating point rounding. The action then fails or behaves unexpectedly.

What made it so hard to diagnose was that it didn’t always throw an error. Sometimes it just set the wrong mode, or heat would update correctly but cool wouldn’t. All of it traced back to Matter’s unit conversion hitting that ceiling.

The fix: Back your cool setpoint off by a fraction of a degree until it converts cleanly under your device’s ceiling. The exact value will depend on your thermostat’s deadband and temperature limits.

My setup:

• Honeywell Home X8S connected via Matter

• Home Assistant

• climate.set_temperature action

Hope this saves someone else the headache.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/kreatifcocuk on 2026-05-18 09:02:22+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/mrruss3ll on 2026-05-18 05:51:39+00:00.

https://preview.redd.it/xbzyin9m4u1h1.png?width=1024&format=png&auto=webp&s=b654b34e9ea9990167283a9956c5d5a7dab2e723

I got tired of handing guests my phone every time they wanted to turn a light on, so I built a proper guest access system for Home Assistant.

Gatekeeper HA is a custom integration that lets you generate time-limited, scoped guest links. No app install for guests, no HA account creation, no handing over your phone.

The workflow is: open the Gatekeeper card on your dashboard, tap "+ New Token", pick which entities the guest can touch (light., lock.front_door, climate., whatever you want), set how long the link should live, and it spits out a unique URL. A QR code renders right there on the card. Laminate it for the guest room, text it to them, whatever works.

Guest opens the link on their phone. They get a stripped-down page with exactly the controls you allowed. That's it. No login, no app, no account. The link expires after X hours or X uses. You can kill it early from the same card.

There's also a guest mode toggle that disables your automations (alarm scheduling, away mode, night lights), snaps a restore point, and revokes every active token when you flip it back off.

Why I didn't use the existing workarounds:

HA-Pass runs as a separate proxy app you need to maintain. Manual HA user accounts work but you're setting up credentials for every guest. Template-switch "guest mode" toggles exist but don't handle scoped tokens or automated cleanup.

This is a standard custom_component. It spawns its own lightweight HTTP server for the guest page, plus a Lovelace card for administration. One install, no Docker containers.

Tech stack: Python asyncio + aiohttp for the guest proxy, LitElement for the card, bcrypt for token hashing. QR codes render locally in the browser — no calls to an external API. About 2000 lines.

Code is on GitHub if you want to kick the tyres:

https://github.com/rusty4444/gatekeeper-ha

Feedback, bug reports, and feature ideas welcome. If there's enough interest I'll submit it to HACS.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/bf3247 on 2026-05-18 00:19:29+00:00.

A few weeks back, I posted Wrist Assistant, a native Apple Watch app for Home Assistant. A bunch of you (way more than I expected) tried it and sent feedback, which was super helpful for finding issues and figuring out what to improve. Thank you all so much!

Version 2 is available today with tons of updates, new features, bug fixes, and a bunch of speed and reliability improvements across the board.

The goal is still the same: to create the fastest and most intuitive way to control Home Assistant. Still looking for feedback and feature requests. Join the Discord if you want to chat: https://discord.gg/NZCghTQmZ

Here's the app if you want to check it out: https://apps.apple.com/us/app/wrist-assistant/id6759152098

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/stijnley on 2026-05-17 10:27:03+00:00.

Hi all

New to HA and diving into the amazing rabbit hole!

I'm having trouble to show who is home, since this is important to start automations.

My wife and I have both iPhones with the HA-app running, location always on, Nabu Casa for remote access, geocoded location shared. Home location is set up in HA as in the app itself.

My wife is added as person and the device_trackers are selected.

But how does it goes from here? When I open the maps both phones show in the "home" area, but this is not the current position, it's not live. It show "1 day ago" or 2 days" ago. I don't have any clue how to scan for the live location.

How does it go from here?

Do i setup a card? Do I forst have add "helpers"?

It feels like I missed a thing. Anyone who can show me the steps?

Thanks!

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/sz_ag on 2026-05-17 14:54:56+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/cdelaet on 2026-05-17 18:00:08+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/hutchet on 2026-05-17 08:52:03+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/mrruss3ll on 2026-05-17 05:57:53+00:00.

This is an automated archive made by the Lemmit Bot.

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

I found a good deal on some Yoolax Zigbee-based smart blinds. Saved a few hundred dollars cheaper over the closest Z-Wave based equivalents I could find.

Nearly every Zigbee-based blind also comes with an accompanying remote, so I thought (naively) that their remotes would also be Zigbee-based and function via direct device binding - like the Z-Wave blinds I saw and the single Zigbee blind I already own (Ikea Fyrtur). Direct binding at the protocol level for a device installed into my home has real appeal - the device keeps basic functionality even if I move out, all while not being tied to a proprietary remote that may eventually get lost or broken.

However, I found out the remote for my Yoolax blinds (like many cheap-to-mid-range Zigbee blinds) is actually an old 433hz RF remote - and more than that, the Zigbee protocol is particular about how blinds should be controlled.

A window covering device following the spec ought to implement the window covering cluster to communicate it's state and take commands. This sounds fine, but it also means the device won't communicate via the on/off cluster or the level control clusters, which is what 99% of Zigbee remotes expose as an interface (since those are used to control lights, switches & dimmers). There are Zigbee blinds out there that can receive commands via the on/off & level control clusters to workaround this incompatibility, but this doesn't appear to be a widely adopted convention.

For my use case, I was dismayed to only find 3 Zigbee remotes that actually act as a client of the window covering cluster:

• now-unobtainable Ikea E1766 remotes for the Fyrtur blinds

• remotes from Somfy (expensive)

• remotes from Profalux (expensive and impossible to find in North America)

So, if you're out there thinking about Zigbee smart blinds, and you care about direct binding their remote controls, I strongly recommend some close research of the device you're buying, or just getting Z-Wave motors instead.

(Z-Wave handles this better at the protocol level, all cover devices are required by the spec to respond to the equivalents of the on/off binding & level control binding.)

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Mihonarium on 2026-05-17 12:35:27+00:00.

This is an automated archive made by the Lemmit Bot.

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