Home Assistant

281 readers
1 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...

founded 3 years ago
MODERATORS
1
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/_Thyraz on 2026-07-19 22:12:33+00:00.

2
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/carrot_gg on 2026-07-19 18:16:45+00:00.

3
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/government--agent on 2026-07-19 18:08:38+00:00.


Looking to improve my smart home to be more hands-off with automations.

One that I set up recently is to have certain lights flash when someone is detected at the front door.

Another one I like is to have the TV's bias/ambient lighting to turn on and off with the TV.

But these do seem a little basic for what HA is capable of.

What are some of your coolest, or most favourite, or most used automations?

4
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Squanchy2112 on 2026-07-19 16:01:51+00:00.

5
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/d4t4_kr4k3n on 2026-07-19 20:47:16+00:00.


Hey everyone,

A while back I posted here about ANS, my custom notification hub for Home Assistant. Since then I've kept using it and pushed a bunch of improvements based on that real-world use – v0.2.0 is now out. 🎉

Quick recap for anyone new: ANS replaces scattered notify.* calls in every automation with one ans.send_notification call. ANS then handles recipient routing, channel selection, criticality-based escalation, Do Not Disturb, rate limiting, retries, deduplication, and TTS volume – all configured once via the UI, not per-automation.

What's new in v0.2.0:

  • See what actually happens to your notifications: Automations can now react in real time to whether a notification was delivered, filtered out, failed, or rate-limited, and get notified once everything is settled.
  • Know when a notification was actually seen: ANS now tracks whether you tapped or dismissed a notification, so you can build automations around real acknowledgement, not just delivery.
  • Tap-to-respond buttons on mobile: notifications can now include up to 3 action buttons you can react to directly from your phone.
  • Self-healing channel detection: if a notification channel (app or media player) goes missing, ANS raises a clear warning in Settings → Repairs and clears it automatically once the channel is back.
  • Simplified, consistent media support: attaching images, videos, files, and links to a notification is simpler now and renders properly and consistently across every channel.
  • TTS now works on speakers in standby: media players that were previously skipped while "off" (like Google Nest speakers in standby) now receive spoken announcements correctly.
  • More resilient under heavy notification load: a safety limit keeps the delivery queue from growing unbounded if a lot of notifications fire at once.

A few internal settings were also adjusted.

A note on stability: Everything migrates automatically on upgrade, so moving from v0.1.x should be a non-event. As always, this remains a personal project I maintain for my own setup. Nevertheless, feedback and bug reports are very welcome.

What's next: I'm continuing to refine ANS based on real-world use and whatever comes up from community feedback.

Get started:

If you're upgrading from v0.1.x, questions or issues are always welcome. And if you want to contribute a new channel adapter or a translation, I'd love the help.

Happy automating! 🚀

6
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Reikan-Ysora on 2026-07-19 19:09:08+00:00.


Good evening everyone :)

It has been a little while!

I am happy to announce that I have just released, ahead of schedule, version 2026.8.0 of Helios, by far the most complete version of both my card and my forecast (both are available right now).

I will be honest with you: these last three weeks have been one of the biggest marathons of my life as a developer. I tried, and I hope I managed, to answer every one of your messages, whether they were support requests or words of encouragement, and they helped me step back and rethink what my card should really offer.

I believe this version finally strikes the right balance between performance and readability. And my Forecast has become considerably more accurate too.

But first, two questions and answers:

What are Helios and Helios Forecast?

Quite simply: a card and an integration for Home Assistant. The card started out dedicated to solar (hence the name), but it has grown, and it is now useful to anyone who wants to understand, analyse and improve the way they consume energy, whether you produce your own or not.

My goal from the start was to make energy "tangible" and "understandable", so that you can actually act on it, either to save money or to reduce your footprint.

Helios Forecast, on the other hand, is still entirely dedicated to solar, and works differently from other forecasts with a "local data" approach.

Why the August version on 19 July?

Well, as I said above, I have spent several hundred hours on this version, polishing every feature, every pixels, and above all making sense of 100% of the Home Assistant Energy dashboard, so that Helios works out of the box, stays simple to use, privacy, and can still be made entirely your own down to the smallest detail.

To celebrate this release, I decided to go all out:

  • A trailer, which you can see above this post, and which also marks the start of the content I will be publishing on YouTube around Helios (and not only Helios).
  • A brand new website that explains EVERYTHING: every configuration detail of Helios, how it works, how transparent it is with your data, and how my forecast actually operates. There is also a section answering the questions I have been asked most often, to help you go further with the card. You will find the full roadmap there too, along with the support I have received and the feedback from the community.

Anyway, I really do hope you will like all of this. Without getting too personal, I have been through a rather difficult period recently, and I want to thank every one of you, because working on this project gave me a purpose again, and slowly helped me rebuild my confidence.

Thank you to those who installed it, to those who starred it on GitHub, to those who sent me an email or a direct message, to those who bought me a coffee (and God knows I drank plenty of them :p), and even to those who gave me negative feedback.

It is thanks to all of you that this version ships today, and that I am, after all, a little proud of myself :)

In short, here is what this new version brings:

  • An even lighter engine.
  • A fully configurable basemap: every detail, roads, zones, woodland, water areas, everything can be themed so you can make the map your own.
  • Full support for EVERY entity configured in your Energy dashboard: multiple grids, multiple solar arrays, multiple batteries. All of your entities can be spread across four groups, with no limit on how many, so you can keep an eye on your car charging, your water heater, your oven, and really your whole home.
  • The ability to show or hide every area, every reading, every chip, so you can turn it into a wall tablet, or simply keep it readable on your phone.
  • A completely rethought curve mode. No more "modes": everything is now built in. A click on a chip shows its consumption in the timeline, a double tap wraps that same curve around your home, and by dragging the cursor along the timeline you can pinpoint instantly, and precisely, what consumed energy and when, so you can act on it and improve the way you use it.

Anyway, those of you who have read my previous posts know they are always very long, and I will not insult you by apologizing, because I am simply incapable of being brief.

I will let you judge for yourselves. And I invite you to explore my new website, still at https://helios-ha.org/.

I am also working on a longer video for my channel, to explain in detail what this new version has to offer.

Thank you all, and see you very soon on GitHub / YouTube or ... whatever :)

Cheers ;)

ReikanYsora / Jérôme

7
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/government--agent on 2026-07-19 04:46:18+00:00.


If you have several users using your HA, do you prefer creating separate dashboards per user, or just use a single dashboard and then use views/subpage visibility to control user access?

I just switched from the former to latter and it seems to be much cleaner this way.

8
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Garper on 2026-07-19 10:06:21+00:00.

9
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Herr_Talvane on 2026-07-19 06:43:53+00:00.


I just uploaded the final version of the Ikea Myggbett mount to Makerworld: Ikea Myggbett - Makerworld

For anyone who missed it, here's the original post:Initial Reddit Post

And here's the original idea: Original idea by u/Gloomy_Independent44

I tried to incorporate as many of your ideas and suggestions as possible. The new design is now fully enclosed and is no longer glued but clamped instead. On top of that, 4 feet can be extended out of the model, which then wedge into the frame.

I couldn't do away with screws entirely, though — all the snap-in variants were too bulky, and this is all about saving space. But well, the M3x6 screws (M3x8 should work too) are standard parts and therefore easy to buy at any hardware store. The 2x threaded inserts are simply better for easy screwing than cutting a thread directly into the plastic. That said, the 4x screws for attaching the cover plate are suitable for screwing directly into the plastic.

There's also an assembly guide on Makerworld.

https://preview.redd.it/6tdowlc0u4eh1.png?width=1025&format=png&auto=webp&s=d04bbd6b64b9ecf213a65a504e2bc75ce2d0d18f

https://preview.redd.it/o4du0tf3u4eh1.jpg?width=3024&format=pjpg&auto=webp&s=86bd09c5d0cda63c349db603797564efff2bdf56

https://preview.redd.it/3ki1dua7u4eh1.jpg?width=6000&format=pjpg&auto=webp&s=dcf74fbb067b85aab79abd7a8cdce1ab93112769

https://preview.redd.it/gfoxhl2gu4eh1.jpg?width=3388&format=pjpg&auto=webp&s=285b0d78fc301a7a819caaa0ae00a7416b0ea65a

https://preview.redd.it/i8irkxzgu4eh1.jpg?width=2646&format=pjpg&auto=webp&s=e55b64835fbda133c1b491cf208de5dac11e8236

I hope you like it and maybe some of you will print a few and give me some feedback here or on Makerworld. I'm now getting started on printing 10+ of them for the whole apartment ;)

10
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/NoviSense on 2026-07-19 05:24:16+00:00.


Hey all - heads up right away that this is my own project, so this is a self-promo-adjacent post. I'm putting it here because you're the people most likely to find the holes in it, and I'd rather hear them now.

Background: I'm an electrical foreman. I've wired up a lot of nice homes - good millwork, tile, stone counters - and then watched a clunky remote or button get slapped on the surface at the very end. It always bugged me. So I built a switch that hides behind the finished surface instead of sitting on top of it.

It's a capacitive sensor that mounts on the back of the material, so there's nothing visible on the surface at all. On my prototypes it reliably registers a touch through up to ~60mm of drywall, tile, glass, wood and any non-metallic surface. You tap the material and it fires.

The part I figured this sub would care about most - it's local-first:

  • Reports into Home Assistant over MQTT with auto-discovery, so entities show up on their own.
  • Also speaks Matter.
  • No cloud account required, no subscription, no app-in-the-middle. If your internet's down it still talks to your local broker / HA instance.

Honest caveats, because I'd rather you hear them from me than catch me on them:

  • It is not ESPHome. It runs custom ESP-Matter firmware, and the HA hook is MQTT auto-discovery rather than the native ESPHome API.
  • Still prototype stage - validated on the bench, not a shipping product.
  • Through-material sensing needs a short guided calibration per install (material and thickness vary), which the device walks you through with audio prompts.
  • I can't call it "Works with Home Assistant" - that's a formal certification I can only pursue later - so I'm describing the actual integration, not claiming the badge.

What I'd genuinely like feedback on:

  • Would you put a no-moving-parts capacitive pad behind your wall in place of a physical switch? If not, what's the dealbreaker?
  • Does the firmware choice (MQTT auto-discovery vs. ESPHome) matter to you as an HA user?
  • Failure modes I should be stress-testing before I commit to a production run - false triggers, humidity, something heavy leaning against the wall, kids, pets, etc.

Happy to get into any of the technical detail in the comments. I'll drop a link to the build and waitlist in a comment rather than the post body so this stays about the feedback, not the sell.

11
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/imbe153 on 2026-07-18 16:26:06+00:00.

12
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/OminousBlack48626 on 2026-07-19 00:45:08+00:00.

13
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/hanumanCT on 2026-07-18 20:33:27+00:00.

14
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/HangarQueen on 2026-07-18 20:08:54+00:00.


I've just started the long process of migrating from a 15-year old Vera system of 200+ ZWave devices to Home Assistant. I have HA installed as a virtual server on my QNAP NAS and it's working fine there. I've installed HACS and a few other goodies as I find my way around this new-to-me product, and have moved over many WiFi-connected devices in my network that HA automatically found for me.

The Aeotec Z-stick 10 Pro arrives tomorrow, and then I'll slowly start the exclude-from-Vera and pair-with-HA process in the coming weeks.

A really useful add-on ("plug-in" in the Vera world) that I had on my Vera system was "DeusExMachinaII". It provided a UI where you could configure any number of switches to randomly turn off and on. For each, you could set a range for length of ON time (randomly) and for the start/stop times for when it would (randomly) be in effect.

I had mine configured for a natural pattern from kitchen to living room to den to bathroom and bedroom as the night progressed, with everything turning off sometime between 11 and midnight (randomly) as we "slept". The plug-in would be automatically enabled when the Vera dashboard was put into "Vacation" mode and disabled when set back to "Home".

I can't find anything that provides the same/similar functionality in the Home Assistant world. I'm sure it's "just a simple matter of automation programming" but there are a LOT of details to get right. The Deus Ex Machina ll plugin did this all very well, and I'm hoping not to have to reinvent it.

Update: THANK YOU for the very quick replies below. Yes, the presence simulation seems that it will suffice for my needs. It's not as clever as the Vera plugin's true randomness, but it'll be "good enough" -- and it seems easy to implement. Thanks again.

15
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Captain_C21H30O2 on 2026-07-18 19:36:10+00:00.

16
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/hometechgeek on 2026-07-18 10:39:44+00:00.

17
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/poldim on 2026-07-17 14:09:53+00:00.


First they forced adding device name Infront of the ESPHome devices. As someone with 50 ESPHome devices, I didn't appreciate this. Now they added areas as another prefix.

Its one thing if they called a best practice, or gave you a system wide option to turn it off. But that's not the case.

Where's them listening to the community? This issue has a few hundred comments and no response.

https://github.com/home-assistant/core/issues/173125

I saw someone suggested having a customizable naming temple which I think is brilliant.

18
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Aluhut on 2026-07-17 21:09:20+00:00.

19
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/dbhagen on 2026-07-17 23:39:45+00:00.

20
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Dazzling-Carpenter on 2026-07-17 19:38:35+00:00.


Hello! I've been ~~daydreaming~~ thinking about a way to point and snap at my devices for years, because I'm lazy and think it's awesome. I finally got around to it and I feel like a Jedi pointing and snapping to turn things on and off around the house. Here's a video of me snapping around and smiling like an idiot. It uses the Apple Watch motion sensors and the metaphor is that you "paint" (or Powerwash Simulator them if that's more your thing) your devices to tell the watch where they are. If people are interested, I'm setting up a TestFlight to gather more data here: https://testflight.apple.com/join/S1rsVDnz

Let me know what you think!

21
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/QuizMasterGary on 2026-07-17 15:47:06+00:00.

22
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/AskDue6927 on 2026-07-17 03:06:09+00:00.

23
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/JoeyJoeJoeJrShab on 2026-07-17 12:37:24+00:00.


When I get a notification on my PC or phone that an upgrade is available, I tend to mindlessly click through and install it. I've realized with HA, that's generally not a good idea since it might create incompatibility issues that will need to be addressed.

I think my philosophy with HA is generally a set-and-forget it configuration. If things work, I will not upgrade anything until I have a specific reason to do so. What's your upgrade philosophy?

24
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Inevitable-Order4193 on 2026-07-17 12:06:16+00:00.


My Shelly Plug S (Gen1) does not pass through the protective earth connection from input to output. Sharing this so other owners can check theirs.

The issue came to light when my washing machine gave me an electric shock. The Shelly Plug S was connected to it to monitor power consumption. A measurement showed approximately 110V on the metal chassis. This is leakage voltage from the Y-capacitors in the washing machine's EMI filter, which should normally be safely dissipated through the protective earth.

A continuity test on the Shelly Plug S confirmed there was no earth connection from input to output. A second Shelly Plug S showed the exact same result. Smart plugs from other brands in the same wall socket all passed earth through correctly.

After opening one of the plugs, two causes became clear: a plastic ridge inside the housing physically prevents the input-side earth contact from making connection with the output-side earth contact, and the metal tube seems to be a bit short. Removing the plastic burr and some of the plastic pipe covering the metal tube immediately restored the earth connection, confirming these as the cause. That said, this isn't something I'd recommend as a fix as there's no guarantee the connection will hold when the plug is in use.

Shelly support was contacted with photos of the defect and measurements. After some back and forth, they forwarded the findings to their engineering team and will replace my two units with Gen3 models. However, they stated that they have no indications of a wider production issue and have not issued any advisory to other Plug S Gen1 owners. Since the Gen1 has been discontinued, they also said they no longer have production units for comparison testing.

So if you own a Shelly Plug S Gen1, it's probably smart to check yours. Set your multimeter to continuity mode, place one probe on one of the earth contacts on the input side (the pins/clips going into the wall) and the other probe on the corresponding earth contact on the output side (where you plug in your device). You should get a clear beep and near-zero resistance. If you get nothing, your plug is also faulty.

Takes 30 seconds and could prevent a dangerous situation.

Photos as proof: https://imgur.com/a/uASSVPR

25
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/edgylukas on 2026-07-17 08:49:22+00:00.

view more: next ›