Home Assistant

281 readers
2 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/CharAznableLoNZ on 2026-07-22 10:34:06+00:00.

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

The original was posted on /r/homeassistant by /u/thaifighter on 2026-07-22 00:12:48+00:00.


So I went a little overboard after seeing some basic wifi filtering buttons on here and spent a few weeks working to build out a family defcon panel that integrates fully with adguard.

Disclamer, a lot of code outside of the base structure was generated with ai help.

I wanted something fun that would also help promote my kids being nicer to each other. Nothing like the threat of mutual destruction of the internet for everyone that day if they cant get along. (You can exclude or include parents in the fun)

There is a lot of options such as sound triggers, lights, etc that you can trigger as I exposed a lot of status entities. I had originally built this with the idea of using the cheap esp32 s3 screens with a light and key system but I havent had time to finish it. Sharing this with the intent to see what others can come up with.

I had chatgpt create a readme and instructions so I could share this. Most features are working but there may be some bugs as I stopped playing with it once I had a working model. I am hoping some others will enjoy this and keep going with it. There may be other things it could be used for as the integration with adguard is really useful as it comments out and isolates the rules it generates instantly and will leave all other custom filters alone.

https://github.com/guitar82/family_defcon/tree/main

Here are some photos of the dashboard, all buttons change colors as they are used and as pin is approved.

https://i.imgur.com/7Bu5RXp.jpeg https://i.imgur.com/ajRJ6PN.jpeg https://i.imgur.com/0EzKDzl.jpeg

For the interface a target has to be selected then a pin has to be entered and confirmed prior to hitting the launch button. All of the keypads work with pin verification as a “real” launch pad would. You can arm and disarm the system from the admin panel and clear out the defcon status if needed.

I have sample dashboards in the example file that work. One known issue is I need to update the target entity buttons to regenerate on a reboot. I believe they only generate properly on initial load right now.

Fyi, I am not 100% sure the hacs installer works, but a sideload of the zip file does. As a dad of three, this isnt something I havent had time to troubleshoot. Anyhow I wanted to share as this has brought some fun diplomacy to my house and maybe others will enjoy it to.

Edit: I just updated the code and fixed the Hacs install compatibility and the names/button entities update and load automatically now. There is a beta release when you install as a custom repository in Hacs. So far it seems to be working well compared the the base files in github now.

I also forgot to add you need the button-card and auto-entities dashboard plugins for the example dashboards to work.

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

The original was posted on /r/homeassistant by /u/Creepy-Ad8688 on 2026-07-21 22:06:05+00:00.


Hi community,

Need your advice on how to proceed.

I got my hands on a minisforum m1 pro to replace my old intel NUC that currently host my home assistant running HAOS on bare betal. I run esphome with a lot of devices and takes some time to build, also now running scrypted and want to run frigate as well and perhaps small model LLM in ollama.

Initially I Just wanted to go bare metal route again and just install frigate and ollama inside HA as I’ve always done, but from what I can find while googleing there is a lot mentioning running proxmox on the mini pc instead and HAOS in a VM and then scrypted, frigate and ollama in their own containers on the side. Besides obvious better seperation and control is there another good reason to go the proxmox way instead of keeping bare metal HAOS?.

I have no experience with proxmox, but want to learn if it will make my setup so much better. I just love the simplicity of the current bare metal setup and let HA handle it.

What is your experience, what would you do in my case :)

Thanks.

EDIT:

Thank you so much for all the feedback. A good mix of both worlds I can see, and of course depending on different use cases. I am really happy with the current setup, been hosting HAOS for years and rock solid. But I am adding more and more stuff to it and I just wanted to future proff it a bit with a newer mini pc, also considering I wanted to play around with Frigate, LLM vision etc.

What got me started reading about if I should do another type of install is that I’ve read that passing the iGPU/NPU and driver setup for Frigate could be difficult on bare metal. But if I am running HAOS on proxmox I guess that would be the exact same issue just inside a vm. I want to keep the HAOS no matter what as it’s always worked best for me.

As several mentioned I could try and start by using proxmox and setup frigate etc and experiment while I still keep HA on my old NUC or even keep HA on the NUC after I migrate services over to the other one. I still need to read up some more or perhaps just try it out before making the right decision, right now I am just lucky I have a new machine to test on while HA lives on :)

Thanks again for all the ideas.

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

The original was posted on /r/homeassistant by /u/First-Quail-2691 on 2026-07-21 21:23:59+00:00.

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

The original was posted on /r/homeassistant by /u/GenericUser104 on 2026-07-21 22:59:06+00:00.

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

The original was posted on /r/homeassistant by /u/ChasmyrSS on 2026-07-21 22:59:00+00:00.

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

The original was posted on /r/homeassistant by /u/Strange_Inspector_10 on 2026-07-21 19:40:48+00:00.

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

The original was posted on /r/homeassistant by /u/daniel5151 on 2026-07-21 17:07:49+00:00.

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

The original was posted on /r/homeassistant by /u/steelavian on 2026-07-21 14:49:47+00:00.

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

The original was posted on /r/homeassistant by /u/CacheMeIfYouCan_07 on 2026-07-20 21:31:12+00:00.


I want to create a Home Assistant user who can only see one dashboard in the Android app and cannot access anything else (Settings, other dashboards, devices, entities, etc.).

I'm running the latest Home Assistant and using the official Android Companion app.

Is this possible with built-in features, or do I need something like Kiosk Mode? If so, what's the recommended setup to completely lock the user to a single dashboard?

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

The original was posted on /r/homeassistant by /u/larsjarred9 on 2026-07-21 05:35:11+00:00.


Today i received a mail saying:

For Non-Commercial, Individual Developers: We remain deeply committed to our developer community. For those using our APIs for personal smart home configurations, we are introducing a dedicated $4.99-per-month paid plan starting in October 2026, specifically tailored to individual needs—more details to follow

Is there a way to be able to know when the dryer or washmachine finished locally without passing by the samsung cloud?

I was never happy to share my data with samsung but it was free so i guess it was a good deal.

No i will pay to share my data with them? Are you kidding me?! 😆

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

The original was posted on /r/homeassistant by /u/ElementZoom on 2026-07-21 07:59:07+00:00.

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

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


https://blog.smartthings.com/smartthings-updates/a-new-enhanced-smartthings-api-experience/

Samsung is getting rid of free API access and moving to a paid-only model later this year.

Free Access Through September 2026: Free API access will remain fully available throughout September 2026.

New usage limits and the phase-out of free access will not begin until October 2026.

Of course, they're giving you the ability pay them for the privilege of accessing your own devices. Yay.

For those using our APIs for personal smart home configurations, we are introducing a dedicated $4.99-per-month paid plan starting in October 2026

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

The original was posted on /r/homeassistant by /u/rdehuyss on 2026-07-20 21:45:46+00:00.


Disclaimer: written by hand, without any AI 😄

I was about to give up on a local LLM using Home Assistant and Voice Assistant on my Mac Mini M4 Pro with 24GB ram.

Since Home LLM had the most stars on GitHub, I was trying to use that together with Qwen 3.6 or the recent Gemma 4 update. I switched from Ollama to LMStudio, to Llama.cpp. I used different versions of Gemma 12B, Gemma 26bA4b, different quants, ...

Nothing worked... it either was way too slow to respond (due to Home LLM adding a lot of tools which polluted the context to > 6000 tokens) for a simple hello or if I used legacy tool calling, it was fast enough but tool calling failed. I had copilot with claude try to fix it but nothing worked.

My final attempt was to switch integrations. The other actively developed local LLM integration I tried was Local OpenAI LLM by skye-harris - and bam, everything worked out of the box. It was fast, responsive, and felt much closer to using ChatGPT or Gemini (except for the first call).

We often focus on finding the best model, but perhaps we should also be asking which integration provides the best experience.

That is not to say Home LLM is a bad project. I’m sure it works well for many users and has its own strengths. In my case, though, I simply couldn’t get it working reliably.

My setup:

Yes, all on this Mac Mini M4 with only 24GB ram.

This is how I start llama.cpp:

llama serve \
   --hf-repo ggml-org/gemma-4-12B-it-GGUF \
   --hf-file gemma-4-12B-it-Q4_0.gguf \
   --alias gemma-4-12b-ha \
   --host 0.0.0.0 \
   --port 6543 \
   --ctx-size 16384 \
   --parallel 1 \
   --n-gpu-layers 999 \
   --flash-attn auto \
   --reasoning off \
   --cache-type-k q8_0 \
   --cache-type-v q8_0 \
   --jinja \
   --api-key "redacted"  

If you think the llama.cpp startup / config can be improved, feel free to comment. I'm new to this scene.

And to prove it, here a screenshot (the light is on/off after about 1 sec after the question). I added the asjeblieft so it would get routed to the LLM.

voice assistant

And it even works with Music Assistant!

Music Assistant integration

I normally don't post much but I thought this was worth sharing...

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

The original was posted on /r/homeassistant by /u/GalusPeres on 2026-07-20 12:19:54+00:00.

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

The original was posted on /r/homeassistant by /u/jrmgx on 2026-07-20 12:01:40+00:00.


The main goal is to monitor the outdoor temperature, bearing in mind that my balcony gets full sun; so, I need something suitable for that scenario.

It needs to run on batteries or operate without an external power cable (solar?), as I cannot plug it in; there is no outdoor power supply

And (of course) it must be compatible with Home Assistant. Any candidate you would recommend?

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

The original was posted on /r/homeassistant by /u/GenericUser104 on 2026-07-20 09:14:25+00:00.

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

The original was posted on /r/homeassistant by /u/Double_Ad9555 on 2026-07-20 08:31:16+00:00.


So this kept happening to me: restart HA (update, whatever), glance at a dashboard afterward, and do a double-take ? everything says "2 seconds ago" even though nothing's actually touched those devices in days. I know it's just how HA handles last_changed on restart, but it bugged me every single time, especially when I'd actually go check history thinking something triggered.

Turns out the recorder already has the real answer ? HA just resets last_changed to the restart time internally. So I wrote an integration that fixes it right at startup: it looks up the true last-change timestamp from the recorder and writes it back onto the entity itself. No extra sensors, nothing to change in your automations or dashboards.

Quick rundown:

Runs on startup, basically no overhead the rest of the time

Also catches Zigbee/Z-Wave devices that take a bit to come back online (rechecks at +30/90/180s)

You pick what it touches ? domains, specific entities, labels, areas, an exclude list, plus a grace window

restore_now service if you want to trigger it manually

Been running clean on my own instance for weeks now, figured it's worth putting out there.

GitHub: https://github.com/hiSweid/last_changed_keeper

Not in the HACS default store yet (PR's open), so add it via that button or manually as a custom repository for now. Happy to hear feedback, bug reports, or just "yep works for me too."

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

The original was posted on /r/homeassistant by /u/KiKuo05 on 2026-07-20 02:21:33+00:00.

20
 
 
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.

21
 
 
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.

22
 
 
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?

23
 
 
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.

24
 
 
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! 🚀

25
 
 
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

view more: next ›