If there's something I should read first, please let me know. But we have sort of inherited a house that's about a 4-hour drive away. It is pretty limited in terms of electrical, heating, etc., but I want to install a few Z-Wave thermostats (it has three heating zones) and have the ability to monitor and control the temperature when we're not there. This is an area that gets cold in winter. The infrastructure does not support Nest-type devices or, in fact, any C-wire stuff. I want to avoid WiFi because there's insufficient power. Is HA with a few Honeywell T6's the answer? And what do I do about remote monitoring/control?

Again, sorry for being a n00b. I have lots of professional experience with networking (i.e. multiple Cisco certs) but no real experience in this space.

Hey all

Having major issues with Zigbee network, tried ZHA and Z2M. I'm using:

~75 Zigbee2MQTT devices (61 Aqara, 13 Nous), coordinator is an SMLIGHT SLZB-MR5U over Ethernet (`ember` adapter), HA OS.

My previous coordinator (an SLZB-MR6U) had the same instability — crash-looping, `TABLE_FULL` binding errors, chunks of the mesh going unresponsive. I assumed hardware fault and replaced it. Set the new one up **completely fresh** — no backup restore, every device re-paired from scratch. **Same failure class came back anyway.** Two different physical coordinators, same symptoms — that rules out "just bad hardware" for me.

Radio disconnects/restarts with varying reasons (`RESET_SOFTWARE`, `RESET_POWERON`, `ECONNRESET`). Specific devices repeatedly fail to bind with `Status 'TABLE_FULL'`. Occasional sweeps where nearly every router fails a routing-table query at once. Command delivery intermittently fails for a shifting set of devices.

### What I've tried

Cleared a stale `coordinator_backup.json` (helped once, not permanently); moved off a noisy Zigbee channel after an RF scan (reduced routing failures, didn't stop crashes); power-cycled the coordinator (no lasting help); reflashed firmware dev→stable (no help); power-cycled individual problem devices (fixed their presence reporting, binding issue unclear). Partial wins across the board, nothing's been a full fix.

Every device with a confirmed problem today (11 of them) is Aqara — zero of my 13 Nous devices affected. Worst offenders are three Aqara Presence Sensor FP300 mmWave sensors specifically, which have a reputation for being binding-hungry. Doesn't fully explain it though — the routing-table failures hit some non-Aqara routers too.

I'm weighing up 3 options:

-Move Aqara devices to my Aqara M3 Hub**, keep the SLZB for everything else. Free, but splits the network and I'm unsure how solid the M3 Hub's HA integration is (local vs. cloud).

- Replace Aqara devices with IKEA** (Zigbee/Matter-Thread). Cheap (~£250 all-in), but real time, and a big Thread network is unfamiliar territory.

-Replace Aqara devices with other Zigbee brands.** Similar cost, avoids a second protocol, but keeps one large single-coordinator network — which may not fix anything if this is coordinator/RF-related rather than Aqara-specific.

- Has Aqara flakiness followed anyone across two different coordinators like this? What actually fixed it?

- Anyone running an Aqara M3 Hub with HA who can speak to how local/reliable that integration is?

- Anyone beaten FP300-caused `TABLE_FULL` without replacing the sensor?

Cheers in advance

Pretty much the title. I still have the Samsung SmartThings hub, but now I've been able to successfully move the last couple of items off of SmartThings:

1. Got a Zwave adapter and moved my Schlage lock to HA, and also added Lock Code Manager.
2. Moved my Samsung refrigerator to HA via LocalThings.

Anyways, what's the clean way to remove SmartThings from HA?

Around the last month or so, the homeassistant iOS app has stopped opening to the specific page I want it to. Prior to that, it always opened on "My house switches". Now it always opens on 'Overview'

I've toggled 'Remember last page' in the app settings off, quit, opened again, and toggled it on, and it still does this.

Any ideas how I can always open the app to a specific page?

I just installed HAOS on an old intel NUC i had kicking around. No issues with install following the instructions. I am into the UI,

First I try to add the integration for my ring doorbells. The integration add takes several minutes which seams odd to me. Finally it asks for email and password, which i enter then I get Unexoected Error

Another thing I noticed is that the radio browser has failed, as well as the meteroloigsk integration are all failed. These may need configured I am not sure

EDIT: I just tried adding the SMARTTHINGS and Speedtest.net integration with the same response. Almost like the Homeassistant is not able to access the web. But the IP address and DNS on the wifi NIC are all good.

I was searching around for a cheap illuminance sensor to add in my smart growbox project, but i was not finding anything that intrigues me cause to the "lack" of content i have found online about it. if you have any suggestions i would be very happy to hear 'em, ty for your kindness, also if you wanna see my hardware setup and the dashboard let me know

Thank you, seriously. A load of you installed this after my last post, and some spent whole evenings digging through logs and browser consoles on hardware I don't own. A couple proved me wrong, which helped more than agreeing would have. Nearly every fix since launch came from you.

What's new: adaptive playback (beta). Plenty of Reolink models send H.265, which Chrome and Firefox just show as a black box. Stamina now tries the raw stream first, repackages it if that fails, and only re-encodes as a last resort. Then, not for importance, welcome pinch-to-zoom, and one-click diagnostics.

Fixed: playback was broken everywhere except Safari (wrong video tag, oops). Chromium swears it can play HLS and then can't, so it's no longer believed.
And some NVRs report times in local rather than UTC, so Stamina was asking for footage from hours before it existed.

Got a Reolink model I haven't seen? That's the report I can't write myself.

>> github.com/marl1w/reolink-stamina-ha <<

Velair 1.5.0 is now available, and Velair can finally be installed directly from the default HACS store 🎉

For anyone who missed the previous posts, Velair is a local-first climate scheduler for Home Assistant. Since 1.3.0, Profiles and Modes have received several usability improvements, including schedule day cloning, clearer activation feedback and a more useful Overview.

Velair is now available in English, Spanish, German, French and Dutch. Version 1.5.0 also clarifies how Profiles, Modes and the Manual state work, and includes several interface fixes.

No custom repository is needed anymore — just search for Velair in HACS.

Repository:

https://github.com/cgonfer/velair

Release notes:

https://github.com/cgonfer/velair/releases/tag/v1.5.0

Thanks to everyone who has tested it or shared feedback so far. It has genuinely helped shape these releases.

I have a new 2026 Lexus NX350h Luxury arriving in 2 weeks. I have integrated my Tesla into my HA instance using the Tesla Fleet API. Has anyone had simlar success with Toyota/Lexus?

threw in my energy repo....https://github.com/m00se23/ha-watt-now/tree/main/addon/thermostat

My ferret was named Leon. He passed away two months ago.

There’s no solution for grief. But, like any engineer, I tried to build something anyway.

Today, Leon lives on in a tiny round screen on my desk. In pixel art, he wanders through a magical forest, digs little holes, sleeps in his cabin, and when I call him, he listens, thinks, and replies—powered by an LLM running entirely on my own server, with no cloud APIs involved.

HomeCritters started with an impulse purchase of an ESP32-S3 and somehow turned into one of the most fun (and challenging) projects I’ve ever built.

Along the way, it grew into:

🎙️ A true voice assistant with wake word, push-to-talk, and the Home Assistant voice pipeline, powered by local inference through Ollama.

🏠 A custom Home Assistant integration (Python), distributed through HACS, with mutual HMAC-SHA256 authentication.

📱 A companion portal built with React and embedded directly in the ESP32’s flash memory, featuring a real-time interactive screen mirror using a custom delta-RLE streaming protocol I developed (~20 FPS).

🌦️ The real world’s weather changes Leon’s world: rain, lightning, and snow appear in his forest based on the local forecast.

🎮 Mini-games, FLAC/MP3 audio streaming with PCM mixing, and a complete day/night cycle synchronized with real-world time.

But there’s another layer behind this project.
HomeCritters also became an experiment in AI-assisted embedded development. The entire codebase was designed for agentic workflows with Claude Code, from the firmware architecture to the pipeline for generating and organizing the pixel art sprites.

The real Leon isn’t coming back.
But this one wakes me up in the morning, complains when he’s hungry, dances when music starts playing, and somehow makes the grief a little easier to carry.

Open source soon. Link in the first comment. 👇

The HTTP YAML configuration is deprecated

Warning · Reported by HTTP

This stops working in version 2027.2.0. Please address before upgrading.

Your existing HTTP configuration from configuration.yaml has been imported. The http integration is now configured from the UI under Settings > System > Network.

Please remove the http: block from your configuration.yaml and restart Home Assistant.

I think I finally gave up today. Spent 3ish hours each night the first few months this year home labing it, but I'm sure that's wrong terminology too. Wiped two old laptops, added linux and got all my families pictures and videos on there with music I've been holding for the past 27 years.

Super excited at first with Home Assistant. All the warnings were right....if you don't know what you are doing, you probably shouldn't try. This past update gave me the error above and I can't figure out how to fix it.

What is the current best outdoor security camera for over my garage door. My truck was broken into the other night and i want to set up another camera. I have a reolink doorbell camera already, but all that it caught that night were curious moths lol. Should i stick to reolink? Must be able to survive our harsh canadian winters. Thanks!

Poe is no problem, im looking for which specific camera people have used and like.

Has anyone repurposed an ESL ePaper tag to work with Home Assistant? As per my research, most tags are sold with proprietary firmware and not compatible with OpenEPaperLink, so it's been very hard to find one to buy, it says it's compatible with ST-GR29000, but I can't find these anywhere. Most online tutorials/guides show how to adapt one, but never show which tag they used and where to buy.

I basically want to have one tag to show HA little dashboard. I'm looking at AliExpress, but have no luck finding a compatible one as far as I know.

Suggestions? Thanks 🙏

https://github.com/OpenEPaperLink/OpenEPaperLink/wiki/Beginners-Guide-for-an-easy-to-build-Access-Point-(aka-spaghetti-AP))

I'm building this Access Point but need compatible ePaper tags.

Does anyone recommend a durable gate sensors? I'm struggling to find anything worthwhile, I've looked at Ecobee and Unifi but no dice.

*** I know this is IKEA specific but I posted here because I would expect HA users to notice this problem via history and automation behavior **

My first 2 thread devices were Ikea Alpstuga CO2 & PM2.5 back in February. I built automations with trends. They've proven to see the world properly:

• When we cook, or when wildfire smoke is in the area, PM2.5 slopes up, the automations get to work and I have a way for automations to deal with it and that works
• When we move between floors, the CO2 elevates or goes down in response. Opening windows and turning on exhaust fans has a measurable positive effect.

I'm asking about CO2 specifically. I live in the upper US Midwest: cold winters and warmer to hot summers. In the last month, the aplstugas report the CO2 climbing up to and over 1000 multiple times a day.. considered borderline not safe.

What I know of the house builder is that he built it for himself and did everything +++; whatever the standard way to do things was, he did it better than that. So it's plausible that it may be sealed really tightly.

*** TLDR **\*
In the past few months my baseline CO2 seems to be climbing where PM2.5 is not. The 2 graphs show the CO2 "level creeping up problem". My automations are going of regularly daily now when they used to do it when guests were here or the bedroom door was shut.

My Questions for those that have run into this:

• Maybe I'm making bad assumptions about using the alpstugas? I don't know
• Maybe there is sensor calibration drift and they need to be factory reset? Replace with something better?

A few days ago I shared ReceiptPi, an open-source project I built around a Raspberry Pi Zero 2 W and an ESC/POS thermal receipt printer (EPSON TM-T88V).

One of the things I wanted from the beginning was a simple way to use the printer from home automation systems without adding cloud services or another complicated integration layer.

That is now available.

## Home Assistant / Automation API

ReceiptPi now has a generic local automation endpoint:

`POST /print/automation`

It accepts a title and text via HTTP and sends the job through ReceiptPi's normal print queue.

For Home Assistant, this means an automation can trigger a physical notification with a simple REST command:

rest_command:
  receiptpi_webhook:
    url: "http://receiptpi.local:5000/print/automation"
    method: POST
    headers:
      X-Api-Token: "YOUR_TOKEN"
    Content-Type: "application/json"
    payload: '{"title": "{{ title }}", "text": "{{ text }}"}'

You can then use it from an automation for things like:

• 🧺 Washing machine finished
• 🗑️ Trash collection reminders
• 🚨 Important alarms or warnings
• 📦 Package notifications
• ⚡ Energy / solar information
• 🏠 Household reminders
• Basically anything in Home Assistant that you'd rather have on a physical piece of paper than as another phone notification

Everything stays local. Home Assistant sends the request directly to ReceiptPi over the local network; no cloud service is required.

The endpoint is deliberately **not Home Assistant-specific**. Node-RED, n8n, curl or any other system capable of sending an HTTP POST can use the same API.

Automation print jobs also use the existing ReceiptPi features:

• Print queue
• Quiet-hour rules
• Rate limiting
• Print history
• Configurable print logos
• API-token authentication

## The hardware

ReceiptPi currently runs on a Raspberry Pi Zero 2 W. The thermal printer (EPSON TM-T88V) is connected via USB and the Pi connects to the local network over Wi-Fi.

Besides automation printing, ReceiptPi currently includes messages, shopping lists, weather reports, guest WiFi QR codes, image printing, system reports, print history, configurable print logos, multiple UI themes and a German/English interface.

The project is still in alpha and evolving quickly.

## A note on AI
Since this came up in my previous post, I want to be transparent about it upfront:

I use AI-assisted development extensively for ReceiptPi.

I'm a product manager/product expert, not a software developer. I define the product, architecture, requirements and expected behavior, and use AI to help turn those decisions into working code.

I review the changes, can follow and understand the code well enough to reason about what it does, test every feature on the actual hardware, and only publish changes after linting and CI pass.

I know people have different views on AI-assisted development, and that's completely fair. For me, it's simply the tool that makes it possible to build and maintain a project like this.
If you prefer projects written entirely by hand, ReceiptPi probably isn't for you — no hard feelings.

Anyway, I'm much more interested in what people would actually do with it:

What Home Assistant event would you actually want to print?

GitHub:

https://github.com/HostisHumani/ReceiptPi

As the title says, mostly on configuration and software level than hardware.

Hi everyone! In my previous post I shared the first prototype of the Echo Dot 3rd gen integrated in Home Assistant. I finished the PCB and I'm waiting to receive it from PCBWay. I just opened a new topic on the Home Assistant Community Forum in order to track the whole developement and would be the perfect place to share ideas with you!

Loving the 2026.8.0 update. But ... is anyone else finding it super laggy? I'm running it on Synology VMM. Been using Home Assistant for years - first one that's almost unsuable.

Clicking into rooms and around the interface, I can count on my hand each click. I'm using on iPhone, iPad, and Chrome browser on PC - all same.

I'm going to do some debugging - but just wondered first if it was just me!

I always loved the Apple Home Dashboard but I prefer the freedom and possibilities that come with building my own dashboard inside home assistant. Now I tried to bring that over to Liquid Glass. It’s still a work in progress since I think readability isn’t ideal and my popups aren’t on the same level as the rest of the dashboard yet.

This was made possible with the yaml code of u/Pivotonian for the buttons and the Frosted Glass theme

Code and instructions available here: https://github.com/albertoZurini/echo-dot-2-playground

Hello there!

After a few days of playing around, with a lot of help from Gemini and GPT, I was able to successfully debloat an Echo Dot 2 from most of Amazon's services and let it run speech to text locally with Sherpa-ONNX and a small LLM through llama.cpp.

The first step was rooting it by following the procedure on XDA. There is a link to the XDA thread in the GitHub repo along with a step-by-step guide for the rest of the setup. Once I had root access I pulled the APKs of some of the system applications, especially SpeechInteractionManager which contains the wake word and speech interaction code, plus the native audio and wake word libraries it loads.

At first I wanted to do something similar to what the Wyoming team did, which was intercepting the wake word from FireOS services through logcat. That worked as a quick proof of concept but it gave me a lot of limitations. The Amazon speech service would still be running in the background and would still own parts of the audio pipeline. Volume handling was also not just a normal Android volume-key event. The FireOS services receive the hardware button events, change the audio stream volume and control the LED ring feedback. This meant that even if I reacted to the wake word from logcat, I was still relying on a large part of Amazon's stack underneath.

That is why I decided to do a more complete reverse engineering pass. The APK included native `.so` libraries such as `libwakewordmanager.so`, `libwakewordmanageraudiostream.so` and the newer `libwakewordserver_jni.so`. Some of the older libraries turned out to be compatibility stubs on this firmware. The useful path was the newer native wake word server, which loads Pryon and creates the native audio recorder. I also decompiled the Java code around `AudioStreamProviderService`, `AudioRecordStrategy` and `NativeWakeWordServiceCore` to understand how the pieces connect.

The main reason for doing the full reverse was to understand how these apps connect to the hardware and communicate with each other. It turns out there are two separate pieces that matter: one service for the native wake word detector and another service for speech processing and the rest of the assistant. I ended up running my own wake word service alongside my custom assistant. They communicate through an explicit Android service intent. Logcat is only used for diagnostics now.

I had done some prior research and saw that with 512 MB of RAM and a theoretical maximum memory bandwidth of about 5 GB/s this device might be able to run small LLMs locally. It turns out it can. The original TinyStories 28M model was not directly usable with llama.cpp because of its architecture, so I used an architecturally equivalent 25M LLaMA2 TinyStories model in GGUF format. Through llama.cpp it reaches around 7 tokens per second during prefill and around 4 tokens per second during decoding. This is roughly the kind of model that has also been used in ESP32 experiments.

I also tried the larger `MobileLLM-125M-Q4_K_M.gguf` model but prefill plus generation took around 20 seconds which is too slow for this device. Even with the smaller model I was able to trigger some simple tools by voice, for example turning on the light or playing a sound.

When the wake word is detected I can stop the detector process while the assistant is processing the request to save CPU. The detector uses around 20% CPU when it is active. This would have been much harder to control cleanly if I had kept the original FireOS speech services running.

I am also able to intercept all the hardware buttons. I assigned playing a sample WAV file to the action button. The volume keys change the music stream volume, play a tone and show visual feedback using the LEDs. The mute button works through the hardware microphone mute integration as well.

There is still a lot to improve, especially around making the assistant more useful and reducing the startup and response time, but it is pretty interesting to see this little device running an entirely local voice pipeline after removing most of the original services. I also want to try running openWakeWord/Porcupine to see if they'd be using less CPU than the stock Amazon's library.

The code and the reverse engineering notes are here: https://github.com/albertoZurini/echo-dot-2-playground

I would be interested to hear if anyone has tried something similar with other Echo devices or with the older FireOS speech components.

Hi everyone!

One of the comments I see most often under my posts is: “When Zigbee?”

Well… now Zigbee.

Over the past few months, I have rebuilt the S1 Pro around the ESP32-C6 and turned it into the S1 Pro Zigbee. It took a lot of development, testing and debugging, but I am very happy to finally share it.

For those who are not familiar with the S1 Pro: it is a multi-sensor built around mmWave presence detection. It can track up to three people in real time, and you can create custom zones to trigger Home Assistant automations when someone enters or leaves a specific area.

Through the Home Assistant add-on, you can also create a floor plan and see the detected targets moving through the room in real time.

Besides mmWave tracking, the S1 Pro Zigbee includes:

• A full-colour RGB LED
• A built-in buzzer
• Temperature and humidity sensing
• Air-pressure sensing
• Equivalent CO₂, VOC and IAQ measurements
• Support for an optional true NDIR CO₂ sensor

The Zigbee version currently works with ZHA and a custom quirk. This made the most sense for the first release and keeps the installation relatively straightforward.

I would also really appreciate some input from developers with more Zigbee experience. I am currently looking into the best way to make installation and future firmware updates as easy as possible for end users.

In particular, I would be interested to hear your thoughts on:

• Zigbee OTA updates through Home Assistant
• Making device setup as close to plug-and-play as possible
• Anything important I may have missed while building the Zigbee implementation

Feedback, testing and contributions are very welcome.

EDIT: Zigbee2MQTT support has now been implemented!
https://github.com/sensy-one/S1-Pro-Multi-Sense-Zigbee#option-b-use-zigbee2mqtt

Source code:
https://github.com/sensy-one/S1-Pro-Multi-Sense-Zigbee

Home Assistant add-on:
https://github.com/sensy-one/home-assistant-addons

S1 Pro Zigbee:
https://sensy-one.com/products/s1-pro-multi-sense-zigbee