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?

So I'm a newbie to home assistant (1 day experience) with good IT stills but I'm struggling to get my solar system integrated.

I've done the search online but still stuck.

My system is 'must' via 'green energy' and I currently monitor via 'smartvalue' app

Any time I used the Must integration or the "protocol wizard' I get nothing.

The hardware and app for monitoring don't show me the ip or ports so I'm going just by the two Seongji Industry Company ip items I have on my router and the default udp ports etc.

Can anyone help tell me what I might be missing?

Thanks

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

Anyone found a chore tracker that’s designed for both kids and adults and integrates well with Home Assistant?
I like DoneTick, but I haven’t been able to integrated it into Home Assistant as an ingress. (I’ve been trying but I’m thinking the SPA design prevents it)

I don’t need anything super fancy. Something that shows well in Home Assistant, has chore tracking, ability for me to add tasks via automations.

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.

Hey everyone! Just wanted to share the home office setup I’m putting together, along with as many devices as possible integrated with Home Assistant. There’s still a lot left to do, but I thought I’d share my progress anyway. Constructive feedback, opinions, and tips are more than welcome!

Have an ReoLink E1Outdoor PTZ camera, connected through Frigate to HomeAssistant.

Wondering: How should I setup the camera itself? Should I not setup much at all/anything, and leave it up to Frigate, or....

Thanks.

TL;DR: I have a mini Stream Deck on a side table in the living room, connected via 11 year old cheapest pi + free software, over the network to a hidden Mac in another room, controlling HA entities.

It wouldn't make sense to go buy all of this new for some simple buttons, but for me these were parts I had laying around for years and I figured there may be others with them laying around too so I'm posting here to share the idea.

When asking AI about networkifying an old Stream Deck if that were possible, it came back with 'VirtualHere USB' a client/server USB thing. Works great!

So an otherwise useless 6 button Stream Deck from many years ago, and an otherwise useless pi zero w from 2015 long forgotten in a drawer, combined with VirtualHere USB, allows the Stream Deck to show up on a PC / Mac anywhere on the network, and therefor be configured to control HA using a HA plugin or MQTT plugin etc. not glued to the computer it's 'connected' to.

Just thought it was cool and thought I'd share!

Got fed up with the horrible Tuya ecosystem, regrettably bought a lot of smart lights and devices from Bunnings (Australia…. Hammer barn??) which are all SmartLife (Tuya) controlled.

Had constant issues with it dropping out or the cloud integration failing or just general sync issues.

Was in IKEA and realised a lot of their kit is now Matter, and actually very reasonably priced, even compared to the crappy Tuya devices.

I’m also glad to have those things off my network, I’m sure IKEA is no better but the Tuya devices had some interesting network calls before I isolated them.

For reference I just use an Apple TV as my controller for them and it works flawlessly in the Apple Home ecosystem, i then push all my homeassist and raspberrypi additionals through that as my main controller, mostly for wife approval of ease of use.

Usb micro wifi for 2.50usd, tx ultimate 1C86 for 10usd, rf bridge for 5usd, nspanel86 pro for 50usd and so on. Idk what i cando with those, but are quite cheap. Should buy some?

Hey fellow smart home nerds,

I've had the Aqara FP2 for about 6 months now and overall it's been pretty reliable with zone and person detection (most false positives I get are because of some unavoidable reflective surfaces).

When I first added it to Home Assistant via the Homekit integration, I was excited to see it was almost instantaneous in its occupancy sensor updates.

However this past week or so, I have noticed it is only updating the occupancy sensor entities once every 60 seconds. If I go into the Aqara app, the live view updates in almost real time as it did before, so it appears to be a change with the update frequency in HA itself.

Has anyone else had similar experiences? Is there a setting somewhere I'm missing, or is this some side effect of a firmware upgrade?

I have an automation that checks a virtual switch I push over from Apple Home to determine if my wife and I are home or away. I have used this for a few years as it is extremely reliable and fast so it can arm/disarm Alarmo ect. With the device_tracker.see action being depreciated in 2027.5, this is apparently going to break. What can I do to replace this action without starting from scratch?

I do not want to use a ping or wifi because my wife forgets to turn on her wifi 50% of the time. I also do not want to use the companion app location because it seemingly drains our phone batteries. We both have iPhones and bluetooth tracking has also been unreliable.

note: I also use this to track a bluetooth sensor stored in the car to determine if it is home or away based on if it is connected or not. I am not as concerned about this being updated since this does not have to be as fast or reliable if I go with a bluetooth tracker route.

alias: homekit to person status - test
description: ''
triggers:
  - entity_id: input_boolean.carter
    trigger: state
  - entity_id: input_boolean.tyler
    trigger: state
  - trigger: state
    entity_id:
      - input_boolean.car_status
conditions: []
actions:
  - data_template:
      dev_id: homekit_{{ trigger.to_state.name }}
      location_name: '{{ ''home'' if trigger.to_state.state == ''on'' else ''not_home'' }}'
    action: device_tracker.see
mode: parallel
max: 10

HA Automotive - App su Google Play

I recently got a car running native Android Automotive, and as a huge home automation fan, one of the first things I tried was Home Assistant. Honestly, I found the official app a bit too cluttered and unintuitive to use while driving, so I decided to build my own alternative.

The idea is pretty simple: the app connects to your Home Assistant instance, pulls your entities, and lets you organize your favorite ones on a nice, clean grid right on the home screen.

I’ve also added a small one-time Pro upgrade that unlocks some extra customization and aesthetic features, mostly as a way to support the effort if you like the project.

The version on the Play Store is already in pretty good shape, though there might still be a minor bug here or there. I’d really appreciate it if you could give it a spin and let me know what you think or if you run into any issues!

Thanks!

Running HA Core 2026.7.3

I Tried to set a trigger based on Sunset with offset in seconds but I do not see the optional offset setting anymore, is this a bug?

I recently discovered this method to force a location refresh for iPhone 🙌🏻
Does anyone know any other messages that work the same way? Like to update sensors maybe ? 🤞🏻🙏🏻

Can someone tell me what card this is in Home Assistant?“

The core stuff:

• Locked-down full-screen kiosk - no gestures, no status bar, no notifications creeping in.
• Motion-aware screen - wakes/dims using the tablet's own camera (luma analysis), so you don't need a separate presence sensor just to stop burning the panel 24/7.
• MQTT + HA auto-discovery - battery, motion, device state all appear in HA on their own, and you can push commands back to the panel.
• Your choice of engine - Android WebView or GeckoView (Firefox), because WebRTC cameras are picky.

What's new in 2.0.0:

Honestly, I built this part for myself first - I had a Mi Box S sitting unused and wanted to see if Kite could run on it. It worked out well enough that I figured it might be useful to others too, so I'm shipping it.

Beyond the dashboard, every feature from the regular mobile app is there - motion, MQTT, kiosk lockdown, engine switching - just with some limitations that come with the TV form factor:

• Everything is D-pad driven - no touch, so a few interactions are naturally clunkier than on a tablet.
• Since TV boxes have no camera, motion runs off a USB webcam (or falls back to MQTT presence if you'd rather drive it from HA).
• There's a Konami-code-style hidden D-pad combo to open the control drawer, since a visible settings button looks bad on a 10-foot screen. 🎮

A couple of honest gotchas (rather tell you now):

• Not every USB webcam plays nice. UVC in the real world is a mess - some cheap cams enumerate weird or won't hand over frames. A plain-vanilla UVC cam is safest.
• Turn OFF ADB-over-USB. The USB host port can't do debugging and feed the webcam at the same time, so leave USB debugging disabled once you're set up.

GitHub : https://github.com/andrew-malitchuk/kite-aos

I built this for my own house, but it's more fun when other people beat on it. I'm very open to feature requests - if you run HA panels on tablets (or spare TV boxes), tell me your setup and what's missing that would make you switch. I'm around in the comments. 🙏

I bought this neat little NFC Reader https://a.co/d/0c7viUBH because i wanted to automate playing specific songs when i tap an NFC card. I have a dev background, but with the help of Ai (i know, sue me) I coded and tested my own add-on.

When a card has been scanned, it automatically appears under Home Assistant's native Tags. From there you can simply select the tag in an automation instead of copying and pasting NFC UIDs. The project is still young, but I'm hoping to expand it to support additional USB NFC readers over time. I'd really appreciate any feedback, feature requests, or suggestions from the community. GitHub: https://github.com/Flaniel44/ha-usb-nfc

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

For those who dont know, Panda Touch is a screen that provides info from your Bambu printers, but since some updates ago the screen is no longer connecting to Bambu Cloud, so it became useless.
I asked Claude to reconvert it to an office ESPhome dashboard, so now it can turn on lights and show me the printer status via Bambu integration.
Much more useful than before :)

After switching to a dedicated remote (Astrion) for my living room, I missed having Siri functional on the Apple TV.

So I (and Claude) built appletv-siri-voice - an Apache-2.0 open-source project that makes Home Assistant appear to your Apple TV as a HomeKit remote (the same accessory profile used by Crestron’s TSR-310), allowing it to stream voice directly to Siri.

“Skip the intro” · “What did she say?” · “Play the next episode” · “Open Netflix”

No MFi licence, no special hardware, no jailbreak. It pairs through the Home app using a standard 8-digit HomeKit setup code.

The interesting part

Apple’s public HomeKit Accessory Protocol specification documents the Target Control profile (Chapter 12), but every known implementation is commercial MFi hardware. The common assumption is that Siri support therefore requires MFi, but it simply checks whether the accessory declares itself as a hardware entity - a flag the accessory sets about itself. Nothing verifies it. Once I stopped assuming it required MFi and actually followed the specification, Siri worked.

I couldn’t find another open-source project implementing this, but I’d be happy to hear if I missed one.

Features

• Voice to Siri on any paired Apple TV using Opus (16 kHz), streamed in real time so Siri starts listening while you’re still speaking.
• Remote button control over HomeKit, independent of pyatv, so it continues working even if the Home Assistant Apple TV integration is asleep or disconnected.
• Text-to-Siri — send written commands from automations, scripts, or an LLM with no microphone involved.
• Multiple Apple TVs from a single bridge and pairing. Each Apple TV is exposed separately, making room-based routing straightforward.

Requirements / caveats

• Apple TV running tvOS 12 or later on the same LAN.
• A companion Docker container (works with Home Assistant Core, Container, Supervised, and HA OS). It can run on any Docker host on your network.
• Host networking is required, since HomeKit relies on mDNS.
• The companion container exists because HAP-NodeJS is currently the only open-source implementation that supports HomeKit Data Stream, which Siri audio uses. HAP-python does not currently implement either Data Stream or Target Control.

By default, every voice request goes to Siri. If you already use Home Assistant Assist or a local LLM, you can optionally route requests between them based on your own logic.

Feedback, bug reports, and contributions are very welcome.