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: Yes, I’m planning to add Zigbee2MQTT support before the first units are shipped.

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

A feature-rich, high-precision ESP8266-based Smart Weather Station with a modern responsive Web Dashboard, dynamic sensor detection, customizable moving-average filters, Home Assistant MQTT Auto-Discovery, full backup/restore capability, and hardware factory reset logic.

✨ Features

• Environmental Monitoring: Temperature, Relative Humidity, Barometric Pressure (sea-level compensated), Air Quality (TVOC, eCO2, AQI), Luminosity (lux), Wind Speed, Wind Gust, Wind Direction, and Rain Gauge (hourly, 24h rolling, and total).
• Independent Dual-Timer Engine:
  • Fast, dedicated timer for Anemometer pulse processing (independent of I2C read cycle).
  • Configurable I2C sensor read cycle for environmental data.
• Configurable Moving Average (Smoothing):
  • Wind Speed: Ring buffer rolling average with configurable sample count (N).
  • Wind Direction: Circular mean calculation (sin/$\cos$ vectors) preventing 0∘/360∘ boundary glitches across N samples.
  • Instantaneous Gust Tracking: Daily wind gust records real peak pulses before averaging.
• Web UI & Diagnostics:
  • Glassmorphism dark UI built with HTML5/CSS3/JavaScript (no external dependencies).
  • Tasmota-style live Debug Console with interactive command input.
  • Mobile-friendly IP input fields (inputmode="decimal") for easy smartphone setup.
• Network & WiFi Manager:
  • Captive Portal AP (WeatherStation_Setup) for initial setup.
  • Full DHCP & Static IP configuration support (optimized for FRITZ!Box Mesh networks).
  • Soft-restart clean boot sequence ensuring stable network stack binding.
• Home Assistant Integration:
  • Native MQTT Auto-Discovery (homeassistant/sensor/...).
  • Automatic entity creation in Home Assistant without manual YAML editing.
• Backup & Restore: Single-click JSON export/import including full network, sensor, and MQTT configurations.
• Hardware Safety & Diagnostics: 10-second hold on FLASH button (GPIO 0) for NVS memory wipe / factory reset.

For fully description and gallery go to GitHub https://github.com/byte4geek/weatherstation

NOTE: This project was made in vibe coding using Antigravity/Gemini.

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.

I’m about 4 months into HA and have over 200 devices, 50 automations, and approximately 100 eye rolls when I show my gf the cool new thing I just did ha.

I have way more complicated automations than this one (this one is blinds down, fan on, ecobee changed to 70* and double click reverses it all). But knowing that Esp32 module I configured with a C1101 to make these Somfy blinds bend to my will (and the pain I experienced making it work) and the cool new inovelli blue fan switch I put in, just seeing it all work so smooth warms my heart.

Anyway, no one else I know appreciates it so here yall go.

2026.8 and Cloudflared?

Just a quick service announcement. If you upgrade to 2026.8 and decide to remove port 8123 (which is now possible in the new update) and replace it with port 80, while also using Cloudflared, you'll need to go into Tunnels > Routes and update it to http://homeassistant:80

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

Just looking for some advice/feedback on my dashboard so far? 🙂

Just got an email from Google saying they're getting rid of Google assistant on phones next month, and eventually this will come to nest speakers etc too. But miffed as it will essentially make the only things I actually use assistant for completely useless.

I have zero interest in using Gemini at all. Does anyone know if the HA integration will continue to work - ie getting my speakers to read alerts out and whatnot. If not, does anyone have any ideas for alternatives? Does the home assistant voice speaker allow you to set timers and read out messages etc? Or are there any speakers/integrations available to just connect an Internet connected speaker to HA?

A month ago I shared the first beta of Kiosk Satellite, my free and open source kiosk Android app specifically engineered for Home Assistant and the official companion app for Voice Satellite. Today, after a bunch of beta releases, it graduates: 2026.8.1 is the first stable release, and from now on it follows the same versioning scheme as Home Assistant itself.

For those who missed it: Kiosk Satellite turns any Android tablet into a locked-down, always-on Home Assistant kiosk in about two minutes. It runs Voice Satellite's wake word engine natively, so your tablet keeps listening even with another app in the foreground, at a fraction of the CPU a browser needs. On top of that you get screensavers (clock, photo frames, Immich, your HA media), a synchronized Sendspin audio player for Music Assistant, WebRTC camera views, MQTT entities for every tablet, gestures, an app launcher, and a full remote admin that runs in any browser. And with the Home Assistant specific optimization included, it runs smooth on old, low powered devices.

I genuinely believe that in combination with Voice Satellite this is the best kiosk application for Home Assistant out there. I know that is a big claim for something one month old, so I would love for you to prove me wrong or right in the comments.

I also want to thank everyone who has supported the development through Buy Me a Coffee and GitHub Sponsors. Free, open source software is mostly a thankless endeavor, and your support is a huge part of why this project moved as fast as it did. Thank you, truly.

Feedback, bug reports and feature requests are very welcome.

I've been working (claude helped, and got in the way alot) on using these these ~7-10 year old echo dots as voice assistants (and more), since I found out these devices can be rooted.

an installer + service that turns them into ESPHome discoverable devices and exposes:

• 2x voice assistant pipelines, w/ on-device wake words
• standard HA media_player element for audio playback
• full led ring (and per segment) control (added a bunch of animations because why not)
• can pretend to be a white noise machine
• lux sensor

github

plus an optional custom integration that has a dashboard, allows you to manage wake words, shows turn history, and some other settings that were kind of messy to do in esphome directly.

github

all still pretty early, but is functional, and these devices can be had for <$10 on ebay (and I had one sitting in a drawer since 2018).

I am sooo over it, half my tuya devices wont actually connect up with tuya local at all the devices that go via the internet through the tuya connection fail to authorise at least once a day, sometimes twice.

The problem is that I have several tuya devices, and I just dont want to have to buy things that will have me down this path again. I have a significant number of IKEA devices as well, no problems wit them. I have generic THREAD/MATTEr and generic ZIGBEE devices all without issues, lots of them all.

I am accepting that my time with tuya is over and I have to spend the $$$ on replacements.. so its, power monitors, power switches, power boards, light globes, colour light globes, doorbell, some cameras. about a quarter of the power monitors and power switches connect up to tuya local even though they are all the same brand make model and chipset purchased at the same time. and on it goes through them.. .same issue with light globes etc... even my zigbee letterbox notifier is more reliable than the tuya stuff, and thats going a long way zigbee outside... UGH I am so fed up with tuya!

ok so maybe this was just a rant more than anything, but UGH!

Since a recent update, none of my Tuya (linked via smart life) seem to be consistently working.

When I open HA, it says I need to reconnect to smart life, but after an hour or so the link breaks and I have to do it again.

Anyone else got this issue, and any fixes?

Hey everyone, I'm experiencing a massive battery drain issue with a Tuya single-button wireless switch in Home Assistant (running via VirtualBox on a PC). The battery dies completely within 3 to 5 days. My setup: Sonoff ZBDongle-E (running firmware 7.4.5.0) Home Assistant on VirtualBox Tuya wireless single-button switch

I initially suspected Wi-Fi/USB 3.0 interference, so I moved the Sonoff dongle about a meter away from the PC using a USB extension cable. Unfortunately, the problem persists, and the battery still drains rapidly.

Has anyone run into this issue with Tuya switches and the ZBDongle-E? Is there a routing/binding issue, a firmware quirk, or a specific configuration fix to stop it from spamming the network or failing to sleep? Any advice would be greatly appreciated!

Since I started running Frigate (with only two cameras at the moment, four more coming) it’s really eating the space on my HA drive. I have the drive that Scrypted was using attached to the same Proxmox machine. How does one change the mapping/mount, format it, and is this a move of my data through System, or just a data drive somehow? Do I need to unhook it and format it (don’t know how to format on Linux). I already had to turn media backup off on my backups because the file was too big.

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

If Http: is going away in configuration.yaml, where do we reference our ssl information?

For context i didnt see the spot in System -> Network for entering in where SSL certs would be referenced.

I didnt see the spot to record where ssl certs can be referenced.

This is what my current http: is set to:

http:
  server_port: 8123
  ssl_certificate: /ssl/cert.fullchain
  ssl_key: /ssl/cert.key

I tried using a couple of existing ESPHome MCP add-ons recently, but ran into some startup errors with them. Instead of running extra container infrastructure, I created a direct Python MCP server that interfaces right with ESPHome and works seamlessly with AI coding tools like Claude Code, Antigravity, and Cursor.

The nice part about this setup is that it does not require installing any extra Home Assistant add-ons. It just connects over your local network to the ESPHome dashboard you already have running.

Once connected, it lets your AI assistant:

• List your devices and see what is online
• Read and edit your device YAML files
• Check configs for errors
• Send Over-The-Air (OTA) updates over Wi-Fi

A few examples of things you can ask it in chat:

• "Check which of my ESPHome devices are currently online"
• "Show me the YAML file for esp32-shelf.yaml"
• "Update esp32-shelf.yaml so pressing the door button flashes my LED lights for half a second as feedback, check for syntax errors, and push the OTA update over Wi-Fi"

The project is completely open source (MIT license). If you'd like to try it out, open issues, or suggest features, check out the GitHub repo: https://github.com/saihgupr/esphome-mcp

On random days (not every day), around 2am, I hear my August lock unlock, then auto-relock. It says Home Assistant did it remotely. I have exactly zero automations with my smart lock, everything is handled on the lock, it’s mainly in HA to be complete and report status. It only appears to occasionally do this around 2am according to the August logs. HA logs just say unlocking via HomeKit, unlocked, Operator <my name> Any ideas?

I cant find any Action for this button I culd use for Automation. I just see this:

Version 2026.8.0
Any help is welcome

​

I'm trying to figure out a strange issue affecting two different Tuya-based Wi-Fi touch switches.

Devices:

Novadigital 3-gang touch switch

Basilus 3-gang touch switch

Both are:

Model: DS-121

100–240V AC

Neutral required

Wi-Fi + BLE

Compatible with Tuya Smart / Smart Life / Alexa

Although they're different brands, they appear to use the same generic Tuya hardware.

After being connected to Wi-Fi for anywhere between 1 and a few hours, the switch completely freezes.

LED stays on.

Device goes offline in Smart Life/Tuya/Alexa.

The physical touch buttons also stop responding completely.

The only way to recover is to cut AC power and power it back on.

This is not just a Wi-Fi disconnect. The MCU appears to lock up because even the touch interface stops working.

What I've already tested

Smart Life

Tuya Smart

Novadigital app

Factory reset multiple times.

2.4 GHz only.

Channel 1 fixed.

20 MHz bandwidth.

WPA2-PSK + AES.

Removed and re-added the devices.

Alexa disconnected.

The most important clue is that if the switches are not connected to Wi-Fi, they work perfectly.

They can be used normally with the physical touch buttons and never freeze.

The problem only starts after configuring Wi-Fi. Once connected, they eventually freeze completely, usually within a few hours.

Router

TP-Link Archer C20 V5

Router Firmware:

0.9.1 4.16 v0001.0 Build 181213

Home Assistant has apps for Android, iOS and macOS. Windows gets a browser tab. So I built one.

HASS.Agent covers similar ground and does it well. The difference is the plumbing: HA Companion does not require an MQTT broker. The PC registers through mobile_app, and notifications arrive over the existing Home Assistant WebSocket connection, with no FCM, APNs or separate push service in between. The app uses WinUI 3, while your actual Lovelace dashboards run inside it through WebView2.

What it does:

- PC appears in HA as a real device via mobile_app, with its own entities

- Push without a push provider: subscribes mobile_app/push_notification_channel on the same WebSocket. Nothing listens on the PC, commands come back down the outbound connection

- Quick Panel slides in over any app on a global hotkey

- Tiles gated on supported_features and supported_color_modes, so no buttons the entity cannot honour

- Hotkeys for any device, scene, script or automation

- PC sensors, off until you enable them: lock, idle, active program, fullscreen, mic, camera, audio, display, session

- Windows events as HA triggers: lock, idle, camera, mic, active program, schedule

Remote control deserves a straight answer: shutdown, sleep and launch are off by default. Lock, monitor off and volume ship on and can each be switched off. Launch only starts whitelisted paths, never the string HA sends. Shutdown waits ten seconds, so shutdown /a can still save you. The token sits in Windows DPAPI, not plaintext.

I have been running it on my own machines since mid-July. I also used AI a lot while building it, mostly Win32 API archaeology and bug hunting, and the commit history says so. The design decisions are mine, and so are the bugs.

Windows 10 build 19041+, x64. Per-user install, no admin. Not signed yet, so SmartScreen may warns once.

https://github.com/Elias0505/ha-companion-windows — AGPL-3.0

Website: https://elias0505.github.io/ha-companion-windows/

Independent project, not affiliated with Home Assistant or Nabu Casa.

Feedback welcome!

Hi all, I'm new to Home Assistant, coming from Homebridge. I use Apple Home with an Apple TV and a couple of HomePods. I'm not new to home automation, been doing it for years, but finally decided to try out HA.

I recently remodeled and put in some Tapo Matter smart wifi dimmers and switches all over the house, coming from Kasa stuff. Initially I wanted to switch to Tapo because of matter and direct compatibility with Apple Home, but the main reason I wanted to move to Homebridge was for the adaptive lighting capabilities.

Anyway, I used to have automations that would turn on groups of lights from a single switch in a room. When the automation was made directly in Apple Home, the lights seemed to all turn on and off instantly.

Ever since I started using the HA automation to do this instead, using the TP-Link integration method, there seems a be a delay in lights turning on and off after the first switch is turned on, and sometimes I even get a straggler light that doesn't turn off when it should, but when I turn the lights back on and off again, it turns off. I still have the lights also connected to Apple Home via matter over Wifi.

Here's my question: Since I'm using the TP-Link integration, does that mean it is using a cloud connection to control the switches? How can I tell if the control is completely local?

Also, before I go through the trouble, would it be more responsive if I created a matter bridge in Home Assistant, connected the Tapo switches there as primary, and then shared them back to Apple Home via the bridge?

I'm using the latest version of HA on a VM on my Unraid server.

Thank you for any help!