Home Assistant

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

The original was posted on /r/homeassistant by /u/erichernandez91 on 2026-02-25 22:04:20+00:00.

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

The original was posted on /r/homeassistant by /u/Hto005 on 2026-02-25 21:29:41+00:00.

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

The original was posted on /r/homeassistant by /u/miket2872 on 2026-02-25 16:46:34+00:00.


Hey everyone,

I need to share something that’s been going on behind the scenes.

As some of you know, TOMMY is a self-hosted project for Wi-Fi-based motion and presence detection where you own your data. It’s grown into something I’m really proud of, largely thanks to this community.

Recently, I received a cease-and-desist letter from a company in the United States alleging that TOMMY infringes one of their U.S. patents and requesting that I stop distributing TOMMY in the United States, including both paid and free versions.

I’ve reviewed the situation and the patent with legal counsel, and based on that review, I do not believe TOMMY infringes the patent identified in the letter.

Without accepting any of their claims, I have voluntarily taken steps to make TOMMY unavailable for purchase and distribution in the United States in order to avoid unnecessary dispute and expense. As a solo developer, I don’t have the resources to engage in prolonged and expensive litigation in the United States.

Development of TOMMY continues as normal, and I’ll share updates if anything materially changes.

Thanks for all the support around this project. It really means a lot.

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

The original was posted on /r/homeassistant by /u/skotman01 on 2026-02-25 15:16:25+00:00.


I know we've seen a few posts about people using public MQ Servers, but I wanted to share this article as an example the kind of data that is sent via MQ.

https://www.theverge.com/tech/879088/dji-romo-hack-vulnerability-remote-control-camera-access-mqtt

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

The original was posted on /r/homeassistant by /u/LightBrightLeftRight on 2026-02-25 14:33:53+00:00.


For any ESPHome tinkerers out there, the unofficial ESPHome library to use HomeKey with a PN532 NFC reader is working! Thanks rednblkx!

I've really wanted to set up HomeKey readers in my house to disarm the alarm and to open my garage. Tried this library last year, but it was too finnicky for actual use so my prototype boards have been collecting dust. With the recent update to the crypto library it works like a charm now!

I really hope that we see some open source projects with this! Right now I'm just planning to 3d print a case to put the reader on top of an S3 box as an entry reader.

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

The original was posted on /r/homeassistant by /u/imkangmin on 2026-02-25 14:29:27+00:00.

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

The original was posted on /r/homeassistant by /u/MsbS on 2026-02-25 08:29:08+00:00.


I started considering a full reinstall of my Home Assistant (running on the same NUC since 2019/2020). I thought I might at the same time replace my Zigbee dongle (using a Conbee 2, which is sometimes a bit wonky).

What other options do I have? Anything that would also support other protocols?

My setup uses a mixture of Zigbee and Wifi, from IKEA, Philips, Shelly, Sonoff, etc. so a proprietary gateway is not an option for me.

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

The original was posted on /r/homeassistant by /u/CurrentPast3481 on 2026-02-25 05:40:48+00:00.


Hi!

I'm back with a new update for ha-wa-bridge - Check the first reddit post about this one

I released the v1.4.0 with polls support

If you are using the Home Assistant Add-on, you can configure the following options in the add-on configuration tab:

  • detect_own_messages: Set to true to allow the bridge to detect and broadcast messages sent by your own authenticated WhatsApp account (e.g., messages sent from WhatsApp Web, your phone, or voice assistants like Ray-Ban Meta glasses). Note: This feature only works for messages sent in WhatsApp groups. Default is false.

Docker Compose Configuration

If you are using Docker Compose, you can enable this feature using an environment variable (Note: This feature only works for messages sent in WhatsApp groups):

    environment:
      - DETECT_OWN_MESSAGES=true

Thank you!

For any bugs or enhancements you’d like to suggest for this project, please open an issue here. It’s easier to keep track of them this way.

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

The original was posted on /r/homeassistant by /u/jbmc00 on 2026-02-25 01:17:02+00:00.

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

The original was posted on /r/homeassistant by /u/Forsaken_Shopping481 on 2026-02-25 08:39:28+00:00.


Hey guys,

I wanted to share a small project I've been working on to solve a personal pain point: TinyTTS.

We all love our massive 70B+ LLMs, but when building local voice assistants, running a heavy TTS framework alongside them often eats up way too much precious VRAM and compute. I wanted something absurdly small and fast that "just works" locally.

TL;DR Specs:

  • Size: ~9 Million parameters
  • Disk footprint: ~20 MB checkpoint (G.pth)
  • Speed (CPU): ~0.45s to generate 3.7s of audio (~8x faster than real-time)
  • Speed (GPU - RTX 4060): ~0.056s (~67x faster than real-time)
  • Peak VRAM: ~126 MB
  • License: Apache 2.0 (Open Weights)

Why TinyTTS? It is designed specifically for edge devices, CPU-only setups, or situations where your GPU is entirely occupied by your LLM. It's fully self-contained, meaning you don't need to run a complex pipeline of multiple models just to get audio out.

How to use it? I made sure it’s completely plug-and-play with a simple Python API. Even better, on your first run, it will automatically download the tiny 20MB model from Hugging Face into your cache for you.

pip install git+https://github.com/tronghieuit/tiny-tts.git

Python API:

from tiny_tts import TinyTTS

# Auto-detects device (CPU/CUDA) and downloads the 20MB checkpoint

tts = TinyTTS()

tts.speak("The weather is nice today, and I feel very relaxed.", output_path="output.wav")

CLI:

tiny-tts --text "Local AI is the future" --device cpu

Links:

What's next? I plan to clean up and publish the training code soon so the community can fine-tune it easily. I am also looking into adding ultra-lightweight zero-shot voice cloning.

Would love to hear your feedback or see if anyone manages to run this on a literal potato! Let me know what you think.

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

The original was posted on /r/homeassistant by /u/mellowbalmyleafy on 2026-02-24 23:19:13+00:00.

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

The original was posted on /r/homeassistant by /u/smarthomecompared on 2026-02-24 23:17:37+00:00.


Hey everyone! I’ve been building a Home Assistant add-on (now app) called Smart Home Planner. The goal is simple: keep a clean, visual, and searchable inventory of your physical smart home devices.

https://preview.redd.it/mqny6rq5zilg1.jpg?width=1239&format=pjpg&auto=webp&s=d8c87b16c134f99a867df1e7aa5df0564c797f82

What it does:

  • Builds a complete device inventory (brand, type, labels, areas, floors, networks, power, warranties, etc.)
  • Syncs devices, labels, areas, and floors with Home Assistant
  • Device diagram with floor-plan background support (upload a house plan and pin devices)
  • Bulk edit for fast updates
  • Files per device (manuals, invoices, photos)
  • Dashboard for batteries, connectivity, and maintenance views

Why it exists:

Home Assistant is amazing for control, but I wanted a dedicated place to document everything about the physical devices themselves, especially for large installs.

If this sounds useful, I’d love feedback from the community.

Let me know what you think or what you’d want added.

https://github.com/smarthomecompared/smart-home-planner

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

The original was posted on /r/homeassistant by /u/Due_Capital_9249 on 2026-02-25 00:13:55+00:00.

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

The original was posted on /r/homeassistant by /u/bdery on 2026-02-24 18:55:50+00:00.


I have an Equinox EV car which can be remotely started. As can be expected, the Chevrolet app is average at best: slow to connect, asks for credentials every other day, slow to send commands to the car, does not always update State of Charge, etc.

One thing which truly bothers me is how convoluted it is to program remote start. The only easy way to schedule it is in the car, and it's linked to the charging status. Not convenient.

Someone created an integration for Chevrolet's OnStar (thanks!). HA can now send commands to the car. So I set up the Time Picker card and a switch helper. If the switch is on, the Time Picker appears on the dashboard and the next time time equals the picked time, an automation sends a command to the car to start it, then turns off the switch so that the car doesn't start by accident the next day. I also get a notification.

Commands via HA reach the car faster than via the Chevrolet app, and I can schedule things easily.

Setting that up took me about 10 minutes including choosing the colors for the cards.

Gotta love HA.

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

The original was posted on /r/homeassistant by /u/j0nnymofo on 2026-02-24 18:46:59+00:00.

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

The original was posted on /r/homeassistant by /u/jdlnewborn on 2026-02-24 15:26:32+00:00.


Ive been using HA now for many years, and it continues to be amazing to me, and the automations Im using really help me and my household. Love it.

But my dashboard - sucks. Its a cobbled together view of stuff, some from day one, and whenever I added something I wanted, but its just that...added. Its far from pretty.

I am getting to the point where I am thinking of getting a tablet of some kind and mounting it for the family, but in its current form, Im embarassed.

Ive been playing with the MCP server with Claude, and have been working on automations and such, works great for that. But a designer of a dashboard, it is not. Maybe its the guy prompting it (me) but frankly, Im gaining no ground.

Can anyone point me in the direction of what has worked for them? Im not looking for fully automated system to do all the work, but I obviously need help where I am at right now to get where I am to something better.

Any help/direction/tips would be appreciated.

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

The original was posted on /r/homeassistant by /u/Far_Set7950 on 2026-02-24 13:50:23+00:00.


turn old Android devices (Android 7+) into dedicated smart home control panels and BLE proxy gateways. Instead of letting tablets and phones rot in drawers, we can turn them into purpose-built infrastructure.

Over the past few months, I’ve deeply optimized the Bluetooth proxy layer.

Ava can now run a BLE proxy 24/7 without degrading WiFi performance, avoiding the common 2.4GHz congestion issues seen with ESPHome proxies.

On my A64 smart clock speaker and Samsung tablets, it has been running continuously and stably.

But here’s the bottleneck.

To better support Bermuda (room-level presence detection), I reworked the BLE scanning logic, especially targeting an old Android issue where low-end chipsets silently stop scanning.

The problem is: I don’t own enough BLE 4.0 devices.

Most of my hardware is BLE 5.0, which works almost perfectly.

If Ava is going to truly support older 2016-2018 era devices, I need more real-world validation.

If you have an Android 7+ device with BLE 4.0, preferably from 2016-2018

Requirements:

  • Root access preferred (most old devices can be rooted)
  • Shizuku also works if root isn’t available
  • Install the APK
  • Enable BLE proxy with Bermuda
  • Let it run and report whether scanning stops or disconnects

Your feedback directly impacts low-level stability improvements and chipset compatibility.

If you’re using BLE 5.0, the experience is already very smooth.

But if we can make BLE 4.0 stable, Ava becomes viable on a much wider range of “obsolete” hardware.

Let’s see how far we can push old Android hardware.

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

The original was posted on /r/homeassistant by /u/Impossible_Spray_842 on 2026-02-24 15:01:29+00:00.

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

The original was posted on /r/homeassistant by /u/automaticbam on 2026-02-24 14:18:05+00:00.

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

The original was posted on /r/homeassistant by /u/objektiver_Dritter on 2026-02-24 12:52:54+00:00.

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

The original was posted on /r/homeassistant by /u/XcOM987 on 2026-02-24 09:13:43+00:00.


So someone somehow managed to take control of thousands of cleaners accidently.....

User accidentally gains control of over 6,700 robot vacuums while tinkering with their own device to enable control with a PlayStation controller — security flaw reveals floor plans and live video feeds | Tom's Hardware

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

The original was posted on /r/homeassistant by /u/WalnutApple on 2026-02-23 23:25:37+00:00.

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

The original was posted on /r/homeassistant by /u/Mrsaintj on 2026-02-23 21:50:35+00:00.

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

The original was posted on /r/homeassistant by /u/ConsistentScratch640 on 2026-02-23 17:42:17+00:00.

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

The original was posted on /r/homeassistant by /u/CarsAlcoholSmokes on 2026-02-23 15:56:40+00:00.

view more: next ›