Home Assistant

259 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 2 years ago
MODERATORS
1
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/ElementZoom on 2026-02-11 17:42:14+00:00.

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

The original was posted on /r/homeassistant by /u/imkangmin on 2026-02-11 13:16:42+00:00.

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

The original was posted on /r/homeassistant by /u/ElementZoom on 2026-02-11 10:41:22+00:00.


Hey everyone!

I'm thrilled to release v5.0.0 of the MDI 3 Dashboard. This is a major quality-of-life update that I think you'll really enjoy!

What's New:

  • 🎨 Smooth animations throughout - Every interaction feels polished and responsive
  • 🏠 Redesigned room navigation - Switched from pop-up cards to section-based layouts with clean headers (back button, room title, more options)
  • 📱 Streamlined room selector - Now in a pop-up card for better navigation
  • 🎵 Spotify integration - Quick link to open the Spotify app from the notification panel
  • Performance improvements - Under-the-hood optimizations for smoother operation

A Big Thank You:

This release wouldn't be possible without the continuous contributions from all of you in the forums and discussion panels. Your feedback, suggestions, and testing have been invaluable in shaping this update. The community here is what makes projects like this thrive! 🙌

Get It Now:

The full code has been updated on GitHub - check it out and let me know what you think!

Need Help?

Don't have time to implement it yourself? I'm open for hire to set this up for you. Feel free to DM me!

As always, I'm open to feedback and suggestions for future updates. Let's keep making this dashboard better together!

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

The original was posted on /r/homeassistant by /u/Secret_Friend on 2026-02-11 06:45:41+00:00.

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

The original was posted on /r/homeassistant by /u/2442929161 on 2026-02-11 06:14:22+00:00.


Hi everyone,

I’m a developer from Shenzhen Heiman. I’ve been developing Matter since 2022, at that time, The Alliance was conducting test events, The Alliance conducted nine test events and two final Specification Validation Event (SVE) prior to the launch of Matter. and two final Specification Validation Event (SVE) prior to the launch of Matter.

I am wondering how you have been feeling about the stability and overall experience of Matter over Thread. I’ve received feedback regarding several different issues; the major one being that users are often unable to commission, pair, or onboard their devices. Others are encountering "unresponsive" or "unavailable" status errors.

I’m not sure if most of you are facing these same hurdles. Have you run into any issues with Matter over Thread devices lately—for example, with the recent IKEA Matter series? How has your experience been with these brands? Let’s discuss it here."

I’ve been testing Matter over Thread devices for years, including our own Heiman Matter products. To start this topic, I’d like to share some of my experiences and test results below, I am also very curious to hear: what do your Matter setups look like?"

Test Setup 1: Apple Home Only.

  • Matter Hubs: Apple HomePod Mini, HomePod (2nd Gen), Apple TV 4K.
  • Matter Devices: Heiman Motion sensor(M1-M), Heiman Smoke Sensor(S1-M, HS1SA-M, S1-TM), Heiman Co Sensor(C1-M, HS720ES-M, HS725ES-M), Heiman temperature & humidity sensor(H1-M), Heiman Door Sensor(D1-M) and Heiman Water Leakage Sensor(L1-M).
  • Version: Hubs are running HomePod Software 26; iPhone 15 Pro Max is on iOS 18.5.
  • Result: We commissioned 25 battery-powered devices with no issues. However, when we increased the count to 50, devices began going offline due to high network traffic (congestion), especially during active commissioning.
  • Recommendation: For larger setups, adding Full Thread Device (FTD) routers (mains-powered Matter devices) is highly recommended to improve system robustness.
  • Known Issue: Apple Home currently does not support the Self-Test feature for Smoke and CO alarms.

Test Setup 2: Google Home Only.

  • Matter Hubs: Google Nest Hub (Gen 2), Google TV Streamer 4K.
  • Matter Devices: Heiman Motion sensor(M1-M), Heiman Smoke Sensor(S1-M, HS1SA-M, S1-TM), Heiman Co Sensor(C1-M, HS720ES-M, HS725ES-M), Heiman temperature & humidity sensor(H1-M), Heiman Door Sensor(D1-M) and Heiman Water Leakage Sensor(L1-M).
  • Result: 25 devices commissioned successfully with no issues. We did not add more "Sleepy End Devices" (SEDs) here, as we recommend adding FTD routers to the mesh first to ensure stability.
  • Known Issues (Pending Google Fix): 1. Battery status always shows as "Unavailable" for Smoke and CO alarms. 2. Hardware status always shows as "Unavailable" for Smoke and CO alarms.

Test Setups 3 & 4: SmartThings / Homey Pro Only.

  • Matter Hubs: SmartThings Hub v3 / Homey Pro.
  • Matter Devices: Full range including M1-M, S1-M, S1-TM, C1-M, HS1SA-M, HS720ES-M, HS725ES-M, H1-M, L1-M and D1-M.
  • Result: 25 devices commissioned with no issues. As with other platforms, we recommend adding FTD routers if you plan to expand the number of battery-powered sensors.

Test Setup 5: Home Assistant (HAOS) Only

  • Matter Hub: Home Assistant Green/ Heiman thread dongle.
  • Matter Devices: Full range including M1-M, S1-M, S1-TM, C1-M, HS1SA-M, HS720ES-M, HS725ES-M, H1-M, L1-M and D1-M.
  • Result: 48 devices commissioned (mixture of battery and AC-powered). We use this daily for automations with great success.
  • Observation: Without an FTD router in the system, we noticed very brief "drop-offs" or latency. Adding a Matter-compatible Thread router is highly recommended.

Test Setups 6–9: Multi-Admin (Mixed Ecosystems)

  • Setups: Apple + HA, Google + HA, Homey + HA, SmartThings + HA.
  • Matter Devices: Full range including M1-M, S1-M, S1-TM, C1-M, HS1SA-M, HS720ES-M, HS725ES-M, H1-M, L1-M and D1-M.
  • Result: We tested 15 to 20 devices in these multi-admin configurations. All worked without issue. We still suggest FTD routers for any network with many sleepy devices.

Developer Tips for Matter over Thread:

  1. OTA Updates: We found that SmartThings, Google Home, and Home Assistant currently handle OTA (Over-the-Air) firmware updates most easily.
  2. Firmware Version: For Heiman Matter devices, we highly recommend using Version 1.5.
  3. Mesh Robustness: Always include at least one or two Full Thread Devices (FTDs)—like a smart plug or light switch—to act as routers for your battery-powered sensors.
  4. Wireless Interference: Check your Wi-Fi channel against your Thread (802.15.4) channel. Ensure they do not overlap to prevent signal interference, Thread and Wi-Fi both use the 2.4 GHz frequency. For the most stable connection, manually set your Wi-Fi to Channel 1. This stays far away from Thread Channel 25, which many Matter hubs (like Apple’s) use by default and cannot change.
  5. Network Unity: When using multiple hubs, ensure they are all on the same Local Area Network (LAN).
  6. Border Router Support: Ensure your chosen hub officially supports OTBR (OpenThread Border Router) functionality.
  7. Troubleshooting Unavailable: If a device drops off, try moving it closer to the hub or a router to check for range issues.
  8. IPv6 Configuration: Double-check your router's IPv6 configuration, as it is critical for Matter over Thread stability, Ensure your Wi-Fi router has mDNS or Multicast enabled. Matter uses these to "find" devices on your network. If your router blocks multicast, your devices will show as "Unavailable" even if the Thread signal is strong.

what do your Matter setups look like? please leave comments below.

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

The original was posted on /r/homeassistant by /u/GeekifiedSocialite on 2026-02-11 00:12:19+00:00.

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

The original was posted on /r/homeassistant by /u/momo1822 on 2026-02-10 15:06:20+00:00.


Hi everyone!

I'm excited to share a collection of Voice Assistant Blueprints I've been working on.

Full GitHub URL: luuquangvu/tutorials: Exclusive Blueprints and Tutorials for Home Assistant

I built these based on my own frustrations and daily needs. I wanted my VA to be more than just a fancy speaker and truly act as a personal or family assistant. I figured if they solved problems for me, they'll likely solve problems for many of you too!

The best part is they're compatible with both local and cloud LLMs

I've put the most effort into two blueprints I think will be game changers for your setup:

Hope you check them out and find them useful for your smart homes. Let me know what you think in the comments below. Thanks a lot!

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

The original was posted on /r/homeassistant by /u/mrded on 2026-02-11 00:51:47+00:00.


I made an Air Comfort Card that visualises indoor air comfort using temperature and humidity sensors. It displays a circular “comfort dial” with a moving dot indicator showing whether conditions are cold, warm, dry, humid, or comfortable - plus 24-hour history charts for temperature, humidity, and CO2.

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

The original was posted on /r/homeassistant by /u/AndyDigger123 on 2026-02-10 21:35:02+00:00.

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

The original was posted on /r/homeassistant by /u/Sensitive-Remove-714 on 2026-02-10 20:13:58+00:00.

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

The original was posted on /r/homeassistant by /u/ApolloAutomation on 2026-02-10 19:46:21+00:00.

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

The original was posted on /r/homeassistant by /u/CD_at_Galaxy on 2026-02-10 17:35:13+00:00.

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

The original was posted on /r/homeassistant by /u/CurrentPast3481 on 2026-02-10 16:59:47+00:00.


Hi!

Yesterday I released the first version of Home Assistant WhatsApp Integration - A custom integration to send WhatsApp messages in Home Assistant and to run triggers/automations based on received messages.

Thanks to the overwhelming support from you guys and because some people asked for group support, today I released the version 1.1.0 which includes group support.

Here are some examples on how to use this new update:

Sending a Messsage

You can send messages to any number using the service:

service: whatsapp.send_message
data:
  number: "40741234567" # Country code + Number (no "+" symbol) 
  message: "Hello from Home Assistant! 🏠"

Sending to a Group

You can send messages to a group by its exact name:

service: whatsapp.send_message
data:
  group: "Family Group" # Exact name of the group
  message: "Dinner is ready! 🍽️"

Automation Trigger

Trigger actions when a specific message is received:

trigger:
  - platform: whatsapp
    from_number: "40741234567"
    contains_text: "Turn on lights" # Optional
action:
  - service: light.turn_on
    target:
      entity_id: light.living_room

Group Message Trigger

To trigger an automation from a group message, use from_group with the exact group name:

trigger:
  - platform: whatsapp
    from_group: "Family Group"
    contains_text: "Dinner" # Optional
action:
  - service: notify.persistent_notification
    data:
      message: "Dinner time!"

Thank you!

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

The original was posted on /r/homeassistant by /u/denzoka on 2026-02-10 14:14:22+00:00.


just saw that how-to geek wrote a whole article about HAGHS. seeing the project featured there is wild but super cool. link:https://www.howtogeek.com/this-tool-gave-my-home-assistant-server-a-rating-and-told-me-how-to-improve-it/

honestly, i am just happy the score is helping so many of you clean up your instances and optimize your hardware. that was exactly the goal from day one.

quick update: v2.2 is currently cooking and will be ready soon. also, we are very close to hitting the official HACS store, so you wont have to deal with manual custom repository links for much longer.

check out the repo if you didnt already: https://github.com/D-N91/home-assistant-global-health-score

huge thanks to this community for all the feedback and support. stay stable and keep killing those zombie entities.

cheers.

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

The original was posted on /r/homeassistant by /u/crua9 on 2026-02-10 15:09:21+00:00.


I figure I might as well share this because I'm sure others will get some use out of this. Something to note is I use my bathroom door sensor to tell if I'm up because I don't have a motion in my room. This can be replaced with pretty much anything you want.

Anyways I based this on science and pretty much all my automations in the description I list the rules and other bits because I have bad memory at times, and if someone else works on it or I might need to mess with it down the road. I can easily see what is going on. I figure I might as well share the rules first so if you can see if you want it.

______

Rules:

  1. At 2:30 AM this grabs the next alarm that will happen on my phone. It then subtracts 60 minutes.
  2. If no time is set or out of bounds if it is a school day base on the calendar, then it will default to 6AM. If not then 8am. In bounds is 3:30 AM - 11 AM
  3. If the event is running, and I go to the bathroom. Assume I am up and end the lock/event.
  4. If the event has ran, don't run it again that day.
  5. If the event has ran, lock other events which might overwrite the lights for this room.
  6. If my protection toggle is on (my bedroom motion) then don't trigger this event. (sick or whatever and I need my rest)

The lighting events are as follows:

  1. Ignition (T+0m to T+10m): Ramps to deep Red/Brown (RGB 68, 28, 0) at 25% brightness.
  2. Dawn (T+10m to T+20m): Ramps to warm Salmon/Orange (RGB 160, 85, 68) at 51% brightness.
  3. Rise (T+20m to T+30m): Switches to Kelvin; ramps to Neutral White (4239K) at 75% brightness.
  4. Peak (T+30m to T+40m): Ramps to Cool Daylight (6500K) at 100% brightness.
  5. Soak (T+40m+): Maintains max brightness for 30 minutes (plus an optional 20m post-alarm buffer).

Scientific Basis:

  1. The Curve (Weber-Fechner Law): Uses a segmented ramp to counter the eye's logarithmic perception of brightness. By stepping intensity alongside color temperature, it creates a "perceptually linear" dawn rather than a sudden glare, mimicking the changing angle of solar elevation.
  2. Start (Melatonin Sparing via Rayleigh Scattering): Begins with long-wavelength Red/Amber (>600nm). This mimics the atmospheric scattering of early dawn. Crucially, this wavelength is invisible to Melanopsin (the protein in your eye that tracks time), allowing you to drift out of deep sleep without prematurely crushing melatonin, preventing "sleep inertia" (grogginess).
  3. End (Cortisol Awakening Response): Ramps to blue-enriched 6500K (simulating zenith daylight). This targets the ipRGC receptors (peak sensitivity ~480nm) to signal the Suprachiasmatic Nucleus. This hard-stop suppresses melatonin and triggers the natural Cortisol Awakening Response (CAR) required for alertness and circadian alignment.

_______

alias: My Bedroom Sunrise
description: >
  60-min lead: Deep Red start, Gamma ramp to 6500K, 20-min pre-alarm soak, plus
  post-alarm soak. 

  Rules: 

  1. At 2:30 AM this grabs the next alarm that will happen on my phone. It then
  subtracts 60 minutes.

  2. If no time is set or out of bounds if it is a school day base on the
  calendar, then it will default to 6AM. If not then 8am. In bounds is 3:30 AM -
  11 AM 

  3. If the event is running, and I go to the bathroom. Assume I am up and end
  the lock/event.

  4. If the event has ran, don't run it again that day. 

  5. If the event has ran, lock other events which might overwrite the lights
  for this room.

  6. If my protection toggle is on (my bedroom motion) then don't trigger this
  event. (sick or whatever and I need my rest)

  The lighting events are as follows:

  1. Ignition (T+0m to T+10m): Ramps to deep Red/Brown (RGB 68, 28, 0) at 25%
  brightness.  

  2. Dawn (T+10m to T+20m): Ramps to warm Salmon/Orange (RGB 160, 85, 68) at 51%
  brightness.  

  3. Rise (T+20m to T+30m): Switches to Kelvin; ramps to Neutral White (4239K)
  at 75% brightness.  

  4. Peak (T+30m to T+40m): Ramps to Cool Daylight (6500K) at 100% brightness.  

  5. Soak (T+40m+): Maintains max brightness for 30 minutes (plus an optional
  20m post-alarm buffer).
  6. If I haven't waked by that point or I'm not home then the lights turn off.

  Scientific Basis: 

  1. The Curve (Weber-Fechner Law): Uses a segmented ramp to counter the eye's
  logarithmic perception of brightness. By stepping intensity alongside color
  temperature, it creates a "perceptually linear" dawn rather than a sudden
  glare, mimicking the changing angle of solar elevation.

  2. Start (Melatonin Sparing via Rayleigh Scattering): Begins with
  long-wavelength Red/Amber (>600nm). This mimics the atmospheric scattering of
  early dawn. Crucially, this wavelength is invisible to Melanopsin (the protein
  in your eye that tracks time), allowing you to drift out of deep sleep without
  prematurely crushing melatonin, preventing "sleep inertia" (grogginess).

  3. End (Cortisol Awakening Response): Ramps to blue-enriched 6500K (simulating
  zenith daylight). This targets the ipRGC receptors (peak sensitivity ~480nm)
  to signal the Suprachiasmatic Nucleus. This hard-stop suppresses melatonin and
  triggers the natural Cortisol Awakening Response (CAR) required for alertness
  and circadian alignment.
triggers:
  - trigger: time
    at: "02:30:00"
    id: calculate
  - trigger: template
    id: start_sunrise
    value_template: >-
      {{ now().strftime('%H:%M') ==
      states('input_datetime.sunrise_start_time')[:5] }}
  - trigger: state
    entity_id:
      - binary_sensor.bathroom_door_sensor
    id: bathroom_trip
    to:
      - "off"
  - trigger: time
    at: "10:00:00"
    id: reset
conditions:
  - condition: state
    entity_id: input_boolean.smoke_or_co_detected
    state: "off"
  - condition: time
    after: "02:00:00"
    before: "11:00:00"
actions:
  - alias: Main logic
    choose:
      - conditions:
          - condition: trigger
            id: calculate
          - condition: state
            entity_id: input_boolean.my_bedroom_motion
            state: "off"
        sequence:
          - action: input_datetime.set_datetime
            target:
              entity_id: input_datetime.sunrise_start_time
            data:
              time: >-
                {% set alarm = states('sensor.pixel_10_pro_next_alarm') %}

                {% set t = as_datetime(alarm) %}

                {# 1. Check if alarm is valid, is set for TODAY, and is between
                5am-8am #}

                {% if alarm not in ['unavailable', 'unknown', 'none'] and t is
                not none and t.date() == now().date() and 5 <= t.hour < 8 %}
                  {% set wake = t %}
                {# 2. Fallback: School Days (6am) #}

                {% elif is_state('calendar.school_days', 'on') %}
                  {% set wake = today_at("06:00") %}
                {# 3. Fallback: Weekends (8am) #}

                {% else %}
                  {% set wake = today_at("08:00") %}
                {% endif %} 

                {# 4. Subtract 80 minutes and output #}

                {{ (wake - timedelta(minutes=60)).strftime('%H:%M:%S') }}
        alias: 2:30 AM get the alarm data
      - conditions:
          - condition: trigger
            id: start_sunrise
          - condition: state
            entity_id: input_boolean.my_bedroom_motion
            state: "off"
          - condition: state
            entity_id: input_boolean.sunrise_has_run
            state: "off"
        sequence:
          - action: input_boolean.turn_on
            target:
              entity_id:
                - input_boolean.sunrise_has_run
                - input_boolean.sunrise_active_lock
          - action: light.turn_off
            metadata: {}
            target:
              entity_id: light.my_bedroom
            data: {}
          - delay:
              hours: 0
              minutes: 0
              seconds: 2
              milliseconds: 0
          - action: light.turn_on
            target:
              entity_id: light.my_bedroom
            data:
              brightness: 65
              rgb_color:
                - 68
                - 28
                - 0
              transition: 600
          - delay: "00:10:00"
          - action: light.turn_on
            target:
              entity_id: light.my_bedroom
            data:
              brightness: 130
              rgb_color:
                - 160
                - 85
                - 68
              transition: 600
          - delay: "00:10:00"
          - action: light.turn_on
            target:
              entity_id: light.my_bedroom
            data:
              brightness: 190
              transition: 600
              color_temp_kelvin: 4239
          - delay: "00:10:00"
          - action: light.turn_on
            target:
              entity_id: light.my_bedroom
            data:
              brightness: 255
              transition: 600
              color_temp_kelvin: 6500
          - delay: "00:30:00"
          - if:
              - condition: state
                entity_id: input_boolean.sunrise_active_lock
                state: "on"
            then:
              - delay:
                  hours: 0
                  minutes: 20
                  seconds: 0
                  milliseconds: 0
              - action: light.turn_off
                target:
                  entity_id: light.my_bedroom
              - action: input_boolean.turn_off
                target:
                  ...
***
Content cut off. Read original on https://old.reddit.com/r/homeassistant/comments/1r139se/i_made_an_artificial_sunrise_that_uses_science_to/
16
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/dfGobBluth on 2026-02-10 14:05:33+00:00.


Let me preface. I have cameras. lots of them. I have 12 exterior cameras. I have 2 cameras in my storage units on my property. I have 1 camera that could be considered "indoor" in the house. It points at my 3D printer and is framed to only show the inside of the printer and the feed. some of the wall behind it.

I have several dashboards around the house, hundreds of smart home sensors, automations etc. We have tracking on myself and my wife's phones and vehicles displayed on the select dashboards. My wife and I have full access to each others phones. Nothing malicious. Just to prep for meals and for FYI etc.

I see a lot of dashboards posted here. A lot of them have cameras all over the inside of the house.

I have 4 kids. they range from 3 to 19 years old. I would never put cameras in the house. My family, my kids deserve privacy in their home. In their entire home. My kids, my teens deserve to have an expectation of privacy and I would want to raise them to have that expectation in any private situation they are in.

We had baby monitors in the kids rooms when they were babies, but there was a clear limit at around 1.5- 2 years old where that was removed from the rooms.

I don't think pets need constant surveillance. If they do they either aren't trained properly or you are leaving them home alone far too much.

This is my opinion. I understand it won't be shared by everyone. As someone who integrates tech into just about everything am I the only one who thinks this way?

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

The original was posted on /r/homeassistant by /u/eyes_are_real on 2026-02-10 12:55:50+00:00.

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

The original was posted on /r/homeassistant by /u/Secret_Friend on 2026-02-10 09:25:00+00:00.

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

The original was posted on /r/homeassistant by /u/One-Astronomer-8171 on 2026-02-10 03:34:50+00:00.

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

The original was posted on /r/homeassistant by /u/Red_Con_ on 2026-02-09 19:28:26+00:00.


Hey,

I struggle to make a neat looking dashboard and while I found several dashboards for inspiration, it seems like a lot of people use 3rd party themes, cards etc. which I'd prefer to avoid as I'd like to rely on 3rd party/unofficial stuff as little as possible (even if it means my dashboard won't be the fanciest).

Did anyone here manage to make a nice looking dashboard only using the stock components Home Assistant offers? If yes I'd appreciate it if you could post a picture.

Thanks!

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

The original was posted on /r/homeassistant by /u/ChipSalt on 2026-02-10 01:49:31+00:00.

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

The original was posted on /r/homeassistant by /u/Mtrain on 2026-02-10 02:30:19+00:00.

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

The original was posted on /r/homeassistant by /u/AnonFartsALot on 2026-02-09 20:48:35+00:00.


I’m looking to kick Amazon and Alexa out of my house, especially now that Ring is working with Flock. I just don’t support that. I was looking at Home Assistant green, but I want to know more about it before I make the investment. I’m NOT tech savvy. I’m looking mostly for assistive-device type tasks, as I have ADHD and Alexa has been the only thing that’s worked. Tasks I typically use:

  • Playing music (unimportant)

  • Alarms

  • Timers

  • Announcements for reminders

  • Reminders (although the way Alexa does it isn’t as useful)

  • Turning on/off my living room lights (not as important)

  • Travel times

  • Shopping lists (perhaps the most important task)

  • Integration with a home security system (nice but not needed)

From everything I’ve read, it sounds like getting the HA to do these tasks is going to require a lot of set up, as they’re not preprogrammed and might involve coding? I don’t think I can do that.

Would it be a good fit? If not, any recommendations for something that would work better for me?

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

The original was posted on /r/homeassistant by /u/4Face on 2026-02-09 22:30:20+00:00.

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

The original was posted on /r/homeassistant by /u/YogurtclosetGlad9512 on 2026-02-09 14:42:44+00:00.


Hey folks,

Over the past few months I built a dedicated Home Assistant smart display for our kitchen. It started as a side project, but it’s now fully working and my family uses it every day, so I figured it might be useful beyond just our house.

It combines:

• Voice add/edit calendar

• Tasks / todos

• Meal planning + groceries

• Full-screen family dashboard

• Home Assistant controls

The main idea was simple: something the whole family can walk up to and use without opening apps or touching their phones.

Some real-life examples from our house:

– “add soccer practice tomorrow 5pm”

– “what’s on today?” while making coffee

– kids checking “what’s for dinner”

– adding groceries while cooking

– turning off lights / locking doors before bed

– quick glance at the day’s schedule on the counter

So it feels more like a small household appliance than a DIY tablet dashboard.

At this point it’s pretty stable. Before polishing it further, I’d love feedback from other HA users.

If anyone’s curious to try the prototype or help test, I’m happy to share it with a few folks and hear what you think.

view more: next ›