# Home Assistant Home Assistant is an open source home automation system that puts local control and privacy first. It is powered by a worldwide community of tinkerers and DIY enthusiasts, perfectly suited to run on a Raspberry Pi or a local server. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Turn Arduino® UNO™ Q into your local 3D printing watchdog DevFeed: [Turn Arduino® UNO™ Q into your local 3D printing watchdog]() Original publisher: [Read original article]() Author: Arduino Team Published: 2026-09-14T18:03:45Z Content type: article Language: en Sources: [Arduino Blog]() Topics: [Arduino](), [Hardware](), [webcam](), [MQTT](), [Home Assistant](), [API](), [Security]() Tags: [3d-printer](), [3d-printer-watchdog](), [3d-printing](), [3d-printing-watchdog](), [anomaly-detection](), [api](), [arduino](), [cameras](), [edge-ai](), [hardware](), [mqtt](), [privacy](), [security](), [uno-q]() ### AI overview This Arduino Blog article presents a local 3D-printing watchdog built with an Arduino UNO Q, a camera, and the FOMO-AD anomaly model through Arduino App Lab. It trains on images of normal prints, flags deviations, and can automatically pause a print through the Moonraker API after repeated anomaly detections. The system can also integrate with OctoPrint, send MQTT notifications to Home Assistant, and operate entirely on the local network for privacy and security. ### Source excerpt A lot of newer 3D printers incorporate sophisticated sensor suites and cameras to detect problems with print jobs, like the dreaded "spaghetti failure." Those work pretty well and prevent wasted time, wasted filament, and even damage to the printer. But what if you don't have a printer with those features? Or if you want to [...] The post Turn Arduino® UNO™ Q into your local 3D printing watchdog appeared first on Arduino Blog. ## Home Hardware, Part 1: My Control4 Revenge Arc DevFeed: [Home Hardware, Part 1: My Control4 Revenge Arc]() Original publisher: [Read original article]() Published: 2026-09-08T00:34:58Z Content type: opinion Language: en Sources: [Jessie Frazelle]() Topics: [Home Assistant](), [Hardware](), [Bluetooth](), [Homekit](), [codex]() Tags: [api](), [bluetooth](), [codex](), [connect](), [hardware](), [home-assistant](), [homekit](), [sensor](), [sensors]() ### AI overview The author describes designing consumer hardware for a Home Assistant-based smart home, including a Bluetooth sensor hub and a maintenance display. The post discusses Bluetooth proxy range, regulatory constraints, testing considerations, and the use of NFC stickers for maintenance tracking, while reflecting on using Codex during the project. ### Source excerpt Fuck1 it, we're doing consumer hardware for ourselves now and getting fucked by economies of scale, I guess. This all started with me buying some Olimex Bluetooth proxies for Home Assistant. Then I started looking at the components and wondering if I could get better range. Now I'm designing boards, displays, and enclosures, and emailing manufacturers because their bezels are enormous. I've ordered the first two boards: a Bluetooth sensor hub and a little maintenance display. I've been working on this in Codex, and this post is going to go through what it was good at, where it got stuck or got things wrong, and where I had to step in. Why build this? Honestly, Control4, Savant, and the rest of these fucking systems seem built for rich people who don't know how to turn on their TV and would rather call someone. I want to program the fucking thing. Control4 puts HomeKit integration in its paid Connect tier.2 Why am I paying a recurring fee to connect things I already bought? I don't want to call a Control4 or Savant dealer, either, just because I want to change how something works. Give me API access or give me death. Source works too. I'll pick the hardware and connect it to Home Assistant, HomeKit, or my own code. If I want another sensor or some weird maintenance reminder, I can write that. It's my fucking house.31 Back to the Bluetooth proxies With a Bluetooth proxy, I can put the BLE radio near the sensors and get back to Home Assistant over the network.4 The machine running Home Assistant doesn't have to be within range of every sensor. When I mentioned my plans to Paul (paultag) over Slack, he pointed out that Olimex might be constrained by what the FCC allows, not just the components it picked. A radio supporting more transmit power doesn't mean you can use all of it.5 I hadn't thought about that. These are boards for my house. I'm not selling them. Fuck it, I'll build them and test them. I still have to measure the range; a bigger number on the radio's datash ## Home Assistant 2026.9 Adds Security Alerts and Removes the VLC Integration DevFeed: [Home Assistant 2026.9 Adds Security Alerts and Removes the VLC Integration]() Original publisher: [Read original article]() Author: Christian Rakoot Published: 2026-09-03T06:30:38Z Content type: article Language: en Sources: [Self Host Lab]() Topics: [Home Assistant](), [dashboards](), [Security](), [Accessibility](), [VLC]() Tags: [accessibility](), [home-assistant-2026-9](), [home-automation](), [home-automation-news](), [integrations](), [news](), [release](), [security](), [september-2026](), [update]() ### AI overview Home Assistant 2026.9 is a stable release that adds conditional security alerts, favorites, shared filtering for History and Activity, accessibility improvements for charts, and a shared-bus Modbus foundation. The release also includes breaking changes, including removal of the VLC integration. ### Source excerpt Home Assistant 2026.9, "There's room on this bus," is now the stable release. The Security dashboard gains an Active alerts section that only appears when something needs attention, History and Activity share a new Sources panel, and Modbus gets a shared-bus rework. Several breaking changes deserve a read first, starting with the removal of the VLC integration. ## Home Assistant 2026.9 adds Modbus device integrations, Cloud voice processing, and Matter network mapping DevFeed: [Home Assistant 2026.9 adds Modbus device integrations, Cloud voice processing, and Matter network mapping]() Original publisher: [Read original article]() Author: Franck Nijhof Published: 2026-09-02T00:00:00Z Content type: release Language: en Sources: [Home Assistant]() Topics: [Home Assistant](), [Release notes](), [Modbus](), [Cloud](), [Matter](), [asr]() Tags: [cloud](), [core](), [home-assistant](), [matter](), [modbus](), [release](), [release-notes](), [security](), [speech](), [ui]() ### AI overview Home Assistant 2026.9 introduces Modbus integrations that can share a connection, new Cloud voice processing focused on speech-to-text, Security dashboard alerts and favorites, shared sources for History and Activity, a Matter network map, keyboard and sound navigation for charts, and 13 new integrations. ### Source excerpt Home Assistant 2026.9! 🎉 I'll be honest: Modbus has never been the flashiest part of Home Assistant. It quietly powers solar inverters, heat pumps, and energy meters, but only if you're comfortable hand-writing your own register map in YAML, a real wall that's kept a huge category of devices out of reach. This release finally makes room on the bus: integrations that already know how a device talks over Modbus, sharing a single connection instead of fighting over it, so you simply pick your device in the UI like anything else in Home Assistant. It won't show up in a screenshot, but modernizing Modbus is hands-down my favorite change this release. 🔧 I'm also really looking forward to jumping on the new Cloud voice processing myself and putting it through its paces. We're a household with a non-English main language, and if you've ever run a private voice assistant in one, you know exactly how fast accents and background noise trip things up. This new speech-to-text engine specifically targets those pain points, so I'm very curious to see how it holds up against my own accent. 😉 And there's plenty more: active alerts and favorites for the Security dashboard, a shared Sources panel for History and Activity, Activity that finally explains why something changed, a brand new network map for Matter, charts you can now navigate by keyboard and sound, and 13 new integrations! 🚀 One more thing before you dive in: we're at IFA Berlin this weekend! It's one of the largest consumer electronics expos out there, running September 4 to 8, 2026, and the Open Home Foundation has its own booth in the Smart Home hall: Hall 1.2, stand 1.2-153. If you're around, come find us and say hi. 👋 Enjoy the release! ../Frenck Home Assistant Cloud Seeing through the Cloud Test the new voice processing Float in to be a Cloud subscriber Active alerts and favorites for the Security dashboard A new Sources pane for History and Activity From what changed to why it changed Insights into your Matter world ## Anonymous and open to all: The Home Assistant survey dataset DevFeed: [Anonymous and open to all: The Home Assistant survey dataset]() Original publisher: [Read original article]() Author: Annika Schulz; Idil Bostan Published: 2026-08-26T00:00:01Z Content type: article Language: en Sources: [Home Assistant]() Topics: [Home Assistant](), [dataset](), [data](), [Open Source](), [GitHub]() Tags: [customization](), [data](), [devices](), [open-source](), [privacy](), [research](), [smart-home](), [survey]() ### AI overview This article announces the free publication of anonymized results from Home Assistant's first community survey, conducted in December 2024 and completed by 8,616 respondents. It describes the survey's purpose, anonymization and privacy safeguards, findings about smart-home users, and how the data will support product work and further research. ### Source excerpt Our why as an organization is clear: to fight for privacy, choice, and sustainability for smart homes, and for every person who lives in one. But who does live in them? In December 2024, we launched the first Home Assistant survey to find out. Our goal was simple: to make Home Assistant more inclusive and approachable by listening directly to the diverse community of people who use it. In the spirit of building in the open, today we're thrilled to announce the anonymized results of that survey are now freely available. In this post, we'll run you through what the survey covered, why and how we're publishing this data, what the data is not (read: identifiable), how we're using this information to improve what we do, and opportunities for further understanding and research. ## My Home Lab, V2 DevFeed: [My Home Lab, V2]() Original publisher: [Read original article]() Author: EduuhMuraya Published: 2026-08-17T00:00:00Z Content type: article Language: en Sources: [EduuhMuraya]() Topics: [Homelab](), [Home Assistant](), [Network](), [Firewall](), [Internet of things](), [MQTT](), [Server](), [Kubernetes]() Tags: [firewall](), [home-lab](), [infrastructure](), [kubernetes](), [network](), [networks](), [proxmox](), [smart-home](), [usb]() ### AI overview An updated home lab replaces a multi-node Kubernetes setup with one mini PC running Proxmox. The article covers segmented networks enforced by OPNsense, firewall testing from within each segment, and a solar-power system integrated with Home Assistant through USB and MQTT. It also describes load-shedding and shutdown safeguards during battery depletion. ### Source excerpt The Kubernetes cluster is gone. One mini PC runs the whole house now: four network segments, a solar inverter Home Assistant can act on, and a guard that shuts the servers down before the battery does. ## Wiring Home Assistant Into My Solar Inverter DevFeed: [Wiring Home Assistant Into My Solar Inverter]() Original publisher: [Read original article]() Author: EduuhMuraya Published: 2026-08-14T00:00:00Z Content type: article Language: en Sources: [EduuhMuraya]() Topics: [Home Assistant](), [MQTT](), [data](), [Document Object Model (DOM)](), [phoenix](), [servers]() Tags: [data](), [firewall](), [infrastructure](), [proxmox](), [raspberry-pi](), [smart-home](), [telemetry]() ### AI overview This article explains how to connect a Growatt solar inverter to Home Assistant through Solar Assistant and MQTT. It covers running Home Assistant as a Proxmox VM, troubleshooting Phoenix LiveView form state and an inactive MQTT publisher, and keeping the integration read-only. ### Source excerpt A Growatt inverter, a Raspberry Pi running Solar Assistant, and Home Assistant on Proxmox. Bridging them took an MQTT broker, a form that silently discarded everything I typed, and a decision to keep the link read-only. Then it stopped watching the house and started switching it off. ## Community Day 2026: Save the date! DevFeed: [Community Day 2026: Save the date!]() Original publisher: [Read original article]() Author: Missy Quarry Published: 2026-08-13T00:00:01Z Content type: article Language: en Sources: [Home Assistant]() Topics: [Home Assistant](), [hosting](), [Discord]() Tags: [2026](), [blog](), [community](), [discord](), [events](), [hosting](), [sustainability]() ### AI overview The article announces that Home Assistant Community Day 2026 will take place on Saturday, November 7. It describes changes based on the first event, including more planning time, broader participation from Open Home Foundation projects such as ESPHome and Music Assistant, updated branding centered on sustainability, and additional support for meetup hosts through Discord and a planned dynamic website. ### Source excerpt You've been asking all year, and the wait is over... Mark your calendars, because Community Day 2026 will be held on Saturday, November 7! 🎉 ## Community Day 2026: Save the date! DevFeed: [Community Day 2026: Save the date!]() Original publisher: [Read original article]() Author: Missy Quarry Published: 2026-08-13T00:00:00Z Content type: news Language: en Sources: [ESPHome - Smart Home Made Simple - Blog]() Topics: [Home Assistant](), [esphome](), [hosting](), [Website]() Tags: [2026](), [announcements](), [blog](), [community](), [discord](), [esphome](), [event](), [events](), [home-assistant](), [hosting](), [music]() ### AI overview Community Day 2026 will take place on Saturday, November 7. The event is expanding beyond Home Assistant to include communities from other Open Home Foundation projects, including ESPHome and Music Assistant, with earlier planning and updated support for meetup hosts. ### Source excerpt You've been asking all year, and the wait is over... Mark your calendars, because Community Day 2026 will be held on Saturday, November 7! 🎉 ## ESPHome launches a Starter Kit with four modules and an ESP32-C6 microcontroller DevFeed: [ESPHome launches a Starter Kit with four modules and an ESP32-C6 microcontroller]() Original publisher: [Read original article]() Author: Paulus Schoutsen Published: 2026-08-12T00:00:00Z Content type: release Language: en Sources: [ESPHome - Smart Home Made Simple - Blog](), [Home Assistant]() Topics: [Home Assistant](), [ESP32](), [Microcontroller](), [Hardware](), [Automation]() Tags: [announcements](), [automation](), [electronics](), [esp32](), [esp32-c6](), [esphome](), [home-assistant](), [product](), [sensor](), [smart-home](), [usb]() ### AI overview ESPHome has launched its first official product, a Starter Kit produced by Apollo Automation. It includes four modules--motion, temperature and humidity, notification, and button--built around an ESP32-C6 microcontroller and designed to work with Home Assistant. ### Source excerpt Back in April during State of the Open Home 2026, we gave you a sneak peek of ESPHome's very first official product... And after months of hard work alongside the community, the ESPHome Starter Kit is here! 🎉 ## 2026.8: Approachable by design DevFeed: [2026.8: Approachable by design]() Original publisher: [Read original article]() Author: Ashley Abbott Published: 2026-08-05T00:00:00Z Content type: release Language: en Sources: [Home Assistant]() Topics: [Home Assistant](), [releases](), [Operating system](), [YAML](), [Cloud](), [Template]() Tags: [2026](), [core](), [esphome](), [live-stream](), [os](), [release-notes](), [releases](), [smart-home](), [youtube]() ### AI overview Home Assistant 2026.8 is a release focused on making the platform more approachable for users without technical expertise. It introduces improvements to installation, configuration, device handling, cloud exploration, entity IDs, templates, triggers, conditions, media search, and integrations. ### Source excerpt Tip Don't forget to join our release party live stream on YouTube on August 5, 2026, at 20:00 GMT / 12:00 PT / 21:00 CET! Tip There's more to look forward to next week: the ESPHome Starter Kit is launching, and you're invited to the official launch party! 🚀 Join the ESPHome team and their partners at Apollo Automation on the ESPHome YouTube channel on August 12 at 21:00 CEST. Familiar faces are dropping by to celebrate lift-off, too: Reed from Smart Home Solver, Simon from Simon Says Home Assistant, and Gavin from HomeTech.fm. Home Assistant 2026.8! 🎉 Hi, I'm Ashley, the Technical Program Manager at the Open Home Foundation. With Frenck taking a well-deserved break, Bram and I are teaming up to handle things this time around. We have been working on a lot over the past few weeks, and I'm excited to share some of what we have done for this release! If there's one thread tying this release together, it's a direction we care about: making Home Assistant something you don't need to be technical to use. This release is another step along that path. Enjoy the release! - Ashley Making Home Assistant more approachable The same Home Assistant, minus the magic number Your current setup keeps working Want to change the port? We've got you covered What this means for YAML Less "advanced", more approachable Describing the feature, not the user Just Tools, no developer required Home Assistant Cloud, now easier to explore Your entity IDs, your choice A cleaner way to handle your devices We can't stop adding triggers and conditions Integrations New integrations Noteworthy improvements to existing integrations Integration quality scale achievements Now available to set up from the UI Farewell to the following Other noteworthy changes Tell us how setup went A roomier template editor Taps that land where you mean them A combined battery level you can trust Search your media Find your favorite cards faster Z-Wave lock credentials, properly managed And a few more Patch releases 2026.8.1 ## Home Assistant: domótica autoalojada DevFeed: [Home Assistant: domótica autoalojada]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-03T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Home Assistant](), [Proxmox](), [Open Source](), [USB](), [Kernel]() Tags: [home-assistant](), [hub](), [kvm](), [lxc](), [os](), [proxmox](), [usb](), [vlan]() ### AI overview A Spanish tutorial explains how to self-host Home Assistant OS as a virtual machine on Proxmox. It recommends a full VM rather than LXC, discusses the Supervisor and add-ons, warns users to inspect community scripts, and covers updates, USB passthrough, dashboard access, and network isolation. ### Source excerpt Instala Home Assistant OS como VM en Proxmox, por qué conviene evitar el LXC, primeros pasos con el dashboard y cómo aislar tu domótica en su propia VLAN. ## A big win for Android interoperability DevFeed: [A big win for Android interoperability]() Original publisher: [Read original article]() Author: Timothy Nibeaudeau Published: 2026-07-31T00:00:01Z Content type: article Language: en Sources: [Home Assistant]() Topics: [Android](), [interoperability](), [Home Assistant](), [Automation](), [Google]() Tags: [2026](), [android](), [automation](), [developer](), [eu](), [gemini](), [google](), [interoperability](), [news](), [privacy](), [self-hosted](), [voice]() ### AI overview The article describes the European Commission's July 16, 2026 decision under the Digital Markets Act requiring Alphabet to open eleven Android features to all assistants on equal terms. It presents the decision as a result of advocacy by the Open Home Foundation and a significant step toward Android interoperability, enabling capabilities such as always-on wake word detection, ambient sensor access, and screen automation for Home Assistant and other assistants. ### Source excerpt Something big just happened. As the Open Home Foundation's Android developer for Home Assistant, I was invited by the European Commission to consult on Android interoperability. On July 16, 2026, the Commission adopted a decision requiring Alphabet to open up eleven Android features -- including always-on wake word detection, ambient sensor access, and screen automation -- to all assistants, on equal terms. ## FireAvert joins Works with Home Assistant DevFeed: [FireAvert joins Works with Home Assistant]() Original publisher: [Read original article]() Author: Miranda Bishop Published: 2026-07-28T00:00:01Z Content type: article Language: en Sources: [Home Assistant]() Topics: [Home Assistant](), [Protocol (disambiguation)](), [Network]() Tags: [community](), [devices](), [ecosystem](), [heat](), [homes](), [innovation](), [launch](), [local](), [mesh](), [network](), [open](), [partner](), [product](), [smart-home](), [works-with-home-assistant]() ### AI overview FireAvert has joined the Works with Home Assistant program with fire-safety devices that automatically shut off electric and gas stoves and other small appliances when a smoke alarm sounds. Its Z-Wave models support local Home Assistant integration through an open smart home protocol and mesh network. ### Source excerpt Sound the alarm, because Works with Home Assistant just welcomed our newest partner to the program: FireAvert! 🎉 Specialists in fire safety, FireAvert are on a mission to keep you and your home out of harm's way. They bring the very first gas and electric appliance shutoff devices to the program, and with them, a whole lot of peace of mind. Where there's smoke, there's FireAvert As ex-firefighter Peter Thorpe knows too well, a moment of forgetfulness is all it takes for a kitchen to end up in flames. And after close to twenty years of service witnessing the same devastating scenario repeat itself, he knew something had to be done. So he founded FireAvert, launching with the Auto Stove Shutoff for electric stovetops. The device was already gaining momentum before FireAvert's pitch caught the attention of Shark Tank, and for good reason. They say there's no smoke without fire, but years on the job taught Thorpe that in the kitchen, that isn't always the case. Smoke can build well before a flame takes hold - and that's the window FireAvert's shutoff works in. By listening for your standard smoke alarm, the device automatically shuts off your stove when the alarm sounds - cutting the heat at the source before a fire can catch. "Excited to see FireAvert join the Home Assistant community. Smart homes shouldn't just be convenient - they should help keep families safer too. This is exactly the kind of innovation the ecosystem needs." - Chasen Tolbert, FireAvert Since their launch, FireAvert's range has expanded to include gas stove and small appliance shutoffs (think microwaves, air fryers, hot plates), so whatever's most likely to be left on in your kitchen, there's a shutoff for it. And with Z-Wave units now among them, it's easier than ever to bring that protection straight into your Home Assistant setup. On the same frequency The FireAvert shutoffs joining the program run on Z-Wave. For anyone unfamiliar, here's a quick rundown: Z-Wave is an open smart home protocol tha ## Building the device database together: Public preview now live DevFeed: [Building the device database together: Public preview now live]() Original publisher: [Read original article]() Author: Matthias Kerstner Published: 2026-07-23T00:00:01Z Content type: article Language: en Sources: [Home Assistant]() Topics: [Home Assistant](), [Database](), [data](), [Discord](), [Internet]() Tags: [2025](), [bugs](), [building](), [community](), [data](), [database](), [devices](), [discord](), [integrations](), [launch](), [open](), [smart](), [smart-home]() ### AI overview The Open Home Foundation has launched a public preview of a community-powered device database for Home Assistant. It presents anonymous, aggregated data contributed voluntarily by users and supports browsing, searching, and filtering devices by characteristics such as internet requirements, protocols, and integrations. The preview is intentionally limited and unpolished, with community feedback helping shape its later official launch. ### Source excerpt Ever since we introduced the idea of a community-powered device database at State of the Open Home 2025, our goal has been clear: create a "Wikipedia of smart home devices" based on real-world usage. In February, we took the first step by inviting Home Assistant users to voluntarily share anonymized device data to help us build it. ## Remotely access Home Assistant via Tailscale for free DevFeed: [Remotely access Home Assistant via Tailscale for free]() Original publisher: [Read original article]() Author: Kevin Purdy Published: 2026-07-16T20:00:00Z Content type: tutorial Language: en Sources: [Blog on Tailscale]() Topics: [Home Assistant]() Tags: [app](), [devices](), [dns](), [open-source](), [remote](), [tutorial](), [update](), [video](), [web]() ### AI overview A tutorial for installing and configuring the Tailscale app in Home Assistant to enable remote access to home controls and dashboards without opening ports or setting up proxies. ### Source excerpt Take Home Assistant beyond your home network with Tailscale. ## IoTorero joins Works with Home Assistant DevFeed: [IoTorero joins Works with Home Assistant]() Original publisher: [Read original article]() Author: Miranda Bishop Published: 2026-07-09T00:00:01Z Content type: news Language: en Sources: [Home Assistant]() Topics: [Home Assistant](), [Internet of things](), [Hardware](), [Open Source](), [Code](), [GitHub]() Tags: [community](), [customers](), [devices](), [firmware](), [github](), [hardware](), [internet-of-things](), [iot](), [manufacturing](), [open-source](), [products](), [remote-access](), [research-development](), [smart-home](), [works-with-home-assistant]() ### AI overview IoTorero joins the Works with Home Assistant program with seven certified devices pre-flashed with ESPHome. The company focuses on open source smart home hardware, including smart plugs and relays, and publishes device configuration files on GitHub. ### Source excerpt The Works with Home Assistant program powers up this month as we welcome our new partner, IoTorero! 🎉 Experts in pre-flashed smart home hardware, IoTorero bring the very first ESPHome-ready smart plugs and relays to the program (and that's not all). IoTorero enters the ring If you've spent any time browsing pre-flashed smart home tech online, there's a good chance you've come across IoTorero. And if you haven't, let us introduce you! Founded in 2020, the company (formerly Athom Technology) was tinkering with ESPHome right out of the gate. Their new name is a nod to the Internet of Things (IoT), but unlike standard IoT gadgets that stop working if your internet drops or a company closes its servers, IoTorero champion open source firmware. Other smart devices run manufacturer-written software, which is tuned to work well with Home Assistant for certification to the program. IoTorero go a step further to make sure their tech is accessible for all: all seven of their certified devices are pre-flashed with ESPHome, meaning there's no installation required - the devices will integrate into your Home Assistant setup straight out of the box. And because their devices are genuinely open, you can always tweak and customize them if you want to. "Since inception in 2020, IoTorero (Athom Technology) has been dedicated to the research, development, and manufacturing of open source smart home hardware products. We provide Home Assistant users with high-quality devices pre-flashed with ESPHome firmware. By joining the Works with Home Assistant program, we ensure that customers can select and purchase our products with complete confidence." - Aiden Tang, CTO and Co-Founder, IoTorero That same spirit of openness carried over to last year's Community Day, where IoTorero donated a stack of samples for attendees to try - a gesture we loved to see, and one that speaks to how seriously they take supporting our community 💪. It shows up in their approach to code, too: IoTorero maintain a pu ## Home Assistant timezone and configuration override issues DevFeed: [Home Assistant timezone and configuration override issues]() Original publisher: [Read original article]() Author: Nicolas Fränkel Published: 2026-07-05T00:00:00Z Content type: opinion Language: en Sources: [Nicolas Fränkel]() Topics: [Home Assistant](), [timezone](), [Automation](), [bug](), [configuration](), [YAML]() Tags: [automation](), [bugs](), [config](), [home-assistant](), [locale](), [technical](), [timezone](), [user-experience](), [yaml]() ### AI overview The author describes Home Assistant shutter automations that ran an hour late during summer time because the instance timezone appeared as Paris/+1. Overriding the timezone in configuration removed UI-set settings, requiring all settings to be specified again in YAML. ### Source excerpt Last year, I motorized the rolling shutters on the southern façade of my apartment. My idea was to manage them via Home Assistant. I had a couple of automations in mind: In the evening, roll down the shutters of my bedroomIn the morning:If it's too hot outside, roll down all shuttersIf it's too cold outside, roll down all shuttersIn other cases, roll up all shutters but my bedroom's Living in France, I added the official Météo France integration. ## 2026.7: Automations that speak your language DevFeed: [2026.7: Automations that speak your language]() Original publisher: [Read original article]() Author: Franck Nijhof Published: 2026-07-01T00:00:00Z Content type: release Language: en Sources: [Home Assistant]() Topics: [Home Assistant](), [Automation](), [YAML](), [releases](), [User interface design]() Tags: [2026](), [automation](), [community](), [complexity](), [core](), [documentation](), [examples](), [release](), [release-notes](), [ui](), [zigbee]() ### AI overview Home Assistant 2026.7 makes purpose-specific automation triggers and conditions the default, aiming to provide more power with less complexity through both the user interface and YAML. The release also rebuilds Activity into a timeline, adds update-all and infrared/radio-frequency panels, improves ZHA Zigbee device management, and introduces 10 community integrations. ### Source excerpt Tip Don't forget to join our release party live stream on YouTube on July 1, 2026, at 20:00 GMT / 12:00 PT / 21:00 CET! Home Assistant 2026.7! 🎉 This is one of those releases I've been looking forward to for a long time. My favorite by far is what we've done with automations. Purpose-specific triggers and conditions graduate from Labs and become the new default for everyone. 🎉 It comes down to something we've been chasing for years: more power, less complexity. Instead of starting from Home Assistant's internals, which entity, which state, which kind of trigger, you start from what you actually want your home to do. When the bedroom drops below 18°C, turn on the heating. That's it. No technical traps, no quirks to memorize. And because integrations can teach the automation engine their own triggers and conditions, it only gets better from here. All of it right there in our beautiful user interface. The nice thing is, nothing breaks. All your existing automations keep working, worry-free. We've also written tons of great documentation explaining every single trigger, condition, and action, with examples to learn from. And if you're one of those people who prefers writing automations in YAML instead of the UI, you're in for an amazing experience too. User experience is not a synonym for "the UI". YAML users deserve good user experience too. But honestly? I've got a second favorite this release, and that surprised me a little. Activity, what many of you still know as the logbook, has been rebuilt into a slick and clean timeline. 😍 It reads top to bottom like a feed, groups entries by day, and finally speaks the same language as the rest of Home Assistant. I keep opening it just to look at it. And that's just the start. There's a new update-all button, dedicated panels for infrared and radio frequency, an overhauled ZHA Zigbee device management, and 10 new integrations from our community. One more thing before you dive in: the Open Home Foundation is exhibiting at IFA B ## Walking Pad, Controlled by Code: BLE, FTMS, and a Phone Button That Tracks Every Step DevFeed: [Walking Pad, Controlled by Code: BLE, FTMS, and a Phone Button That Tracks Every Step]() Original publisher: [Read original article]() Author: Ivan Morgillo Published: 2026-06-24T08:00:00Z Content type: tutorial Language: en Sources: [Ivan Morgillo]() Topics: [Home Assistant](), [Bluetooth](), [Python](), [Code]() Tags: [ble](), [bluetooth](), [code](), [home-assistant](), [python]() ### AI overview A developer connects a Mobvoi Home walking pad to Home Assistant using Bluetooth Low Energy and the Fitness Machine Service standard. A Python-based setup uses the device's control point and notifications to start and stop the pad and record session data, while the article also documents challenges with rolling-code remotes, BLE scanning, and BlueZ connections. ### Source excerpt I have a Mobvoi Home walking pad under my standing desk. BLE, FTMS, Python, and a Home Assistant button: one tap to start, one to stop, every session logged. ## The Matter upgrade you've been waiting for DevFeed: [The Matter upgrade you've been waiting for]() Original publisher: [Read original article]() Author: Ingo Fischer Published: 2026-06-23T00:00:00Z Content type: article Language: en Sources: [Home Assistant]() Topics: [Matter](), [Home Assistant](), [TypeScript](), [Open Source](), [Network](), [Homebridge]() Tags: [2026](), [announcements](), [border-router](), [bugs](), [hardware](), [homebridge](), [matter](), [open-source](), [recovery](), [speed](), [standards](), [thread](), [typescript](), [upgrade](), [visualization]() ### AI overview Home Assistant introduces a new Matter implementation built on matter.js, an open source TypeScript implementation of the Matter standard. After beta testing and community contributions, the update aims to improve stability, reduce bugs, and accelerate startup and recovery. It also adds network visualization, upgrades to Matter 1.5.1, and updates the OpenThread Border Router app for Thread 1.4 support. ### Source excerpt It started as a passion project. Yet in a few years matter.js has grown beyond my wildest expectations, becoming the backbone of the open source Matter ecosystem, and powering everything from Homebridge to openHAB, and even some commercial products. Ten months ago, I joined forces with the Open Home Foundation to work full time as Lead Developer of Matter. Shortly after, I donated matter.js to the foundation - giving it a new home where it would be safeguarded for the future. Together we announced our plans to take Matter support in Home Assistant in a completely new direction: we set out to rebuild the Open Home Foundation Matter Server - the engine that powers Matter in Home Assistant - on matter.js. After four months of beta testing, with our community fixing bugs and contributing new features along the way, today we're thrilled to present the newest version of Matter for Home Assistant! 🎉 The Open Home Foundation invests in important technology to make open alternatives possible, and our work is funded in part by everyone who subscribes to Home Assistant Cloud and buys official hardware from our commercial partners. The launch of a new Matter experience in Home Assistant shows what's possible with your support. 💪 Presenting the matter.js plans at the Connectivity Standards Alliance (CSA) Member Meeting in November 2025 (right), and returning in March 2026 as an Outstanding Contributor Award recipient (left). Serving up more with matter.js For those new to matter.js, it's an open source TypeScript implementation of the Matter standard. I built it to give developers and power users more speed and flexibility, and to make Matter better suited for open source development across the millions of homes that use Home Assistant. By running Matter in Home Assistant on matter.js, all of those benefits now flow directly into the platform. This major update brings greater stability for Matter in Home Assistant, fewer bugs, and faster start-up and recovery. It also comes with ## Proxy all the things: no device left behind DevFeed: [Proxy all the things: no device left behind]() Original publisher: [Read original article]() Author: Paulus Schoutsen Published: 2026-06-18T00:00:01Z Content type: article Language: en Sources: [Home Assistant]() Topics: [Home Assistant](), [Network](), [Hardware]() Tags: [devices](), [diy](), [hardware](), [integrations](), [network](), [smart-home]() ### AI overview The Open Home Foundation describes how recent Home Assistant and ESPHome releases use generic proxying to connect older, offline devices to modern smart homes. Small microcontrollers can act as bridges for infrared, radio frequency, and serial communication, alongside existing Bluetooth and Z-Wave proxies, allowing devices such as older receivers and air conditioners to be controlled over the home network. ### Source excerpt Every smart home has them: the older devices that still work perfectly well but no longer fit neatly into a modern setup. Instead of letting them gather dust in a drawer, the Open Home Foundation's projects can help you bring them back into the fold. Here's how a little proxying can give your beloved old gear a new lease of life, and keep your smart home that bit more sustainable. ## 2026.6: Pick a card, any card DevFeed: [2026.6: Pick a card, any card]() Original publisher: [Read original article]() Author: Franck Nijhof Published: 2026-06-03T00:00:00Z Content type: release Language: en Sources: [Home Assistant]() Topics: [Home Assistant](), [dashboards](), [Automation](), [dialog](), [Matter]() Tags: [2026](), [apps](), [automation](), [core](), [custom-dashboard](), [dialog](), [features](), [integrations](), [matter](), [release](), [release-notes]() ### AI overview Home Assistant 2026.6 introduces a new card picker that recommends dashboard cards based on the device or entity users want to display, with live previews using their data. The release also adds zone triggers and conditions, live condition-test indicators, target counts, step notes, new tile card features, improved smart-lock support, a friendlier Apps page, and additional community integrations. ### Source excerpt Home Assistant 2026.6! 🎉 I'm going to put my hand up right away: ✋ I am not a dashboard person. Not because I don't like them; I love seeing what you all build. But designing a beautiful one is a kind of visual creativity I just don't have. That's a big part of why I love the built-in Home dashboard so much, it does the designing for me. But when I do build a custom dashboard, I usually stare at that "add a card" dialog for way too long, picking cards almost at random just to see if they look good with the data I have. So you can imagine my excitement for my personal favorite of this release: the new card picker. Instead of asking "which card type do I want?", it now asks "which thing in your home do you want to show?", and then suggests cards that actually make sense for it, with live previews using your own data. For someone like me, that's not just easier; it's genuinely inspiring. It nudges me towards combinations I would not have thought of on my own. 💡 This fits into a bigger direction I keep getting more excited about: Home Assistant getting better at starting from the thing you want to do, instead of asking you to first learn the building blocks. The same idea is what makes purpose-specific triggers and conditions in Home Assistant Labs feel so right, and this release brings them a big step closer to graduating out of Labs with brand new zone triggers and conditions. 📍 A close second favorite for me this release is everything happening around that in the automation editor: live test indicators on your conditions, target counts on every device, area, floor, and label, and proper notes you can attach to any step. Individually they are small quality-of-life touches; together, they make building automations feel a whole lot more transparent. ✨ And there is plenty more to love in this release: new tile card features, Z-Wave smart locks catching up with their Matter siblings, a friendlier Apps page, and another big batch of new integrations from our community. 🚀 E ## Sensereo joins Works with Home Assistant DevFeed: [Sensereo joins Works with Home Assistant]() Original publisher: [Read original article]() Author: Miranda Bishop Published: 2026-05-28T00:00:01Z Content type: news Language: en Sources: [Home Assistant]() Topics: [Home Assistant](), [Matter](), [Network]() Tags: [2026](), [battery](), [ecosystem](), [matter](), [products](), [safety](), [sensors](), [smart-home](), [thread](), [wireless](), [works-with-home-assistant]() ### AI overview Sensereo has joined the Works with Home Assistant program with Matter-based MS-1 smoke alarms and MSC-1 smoke and carbon monoxide alarms. The article explains how Matter and Thread support open, interoperable, energy-efficient smart-home devices while the alarms continue operating as regular alarms if the Thread network fails. Sensereo also plans to develop air quality sensors and other environmental sensing devices. ### Source excerpt We're sensing a change in the air this month as we welcome Sensereo to the Works with Home Assistant program 🎉. Specialists in environmental sensing, Sensereo brings Matter smoke and carbon monoxide (CO) alarms into the Home Assistant ecosystem - meaning more ways to keep your home open, safe, and sound. Built from a burning question... What happens if your smoke alarm goes off, but you're not there to hear it? It's an unsettling question, and one that led Roy Chen to found Sensereo in 2024. Driven to create safety devices that were equal parts reliable and resilient, Sensereo built the Matter-based MS-1 Smoke Alarm and MSC-1 Smoke and Carbon Monoxide Alarm, because as they put it: "every home deserves a system that will not fall silent when it matters most." It's just good sense For anyone unfamiliar, Matter is an open standard that lets smart home devices from different brands work together, regardless of who made them - no lock-in, no closed ecosystems. It's exactly the kind of open, interoperable technology the Open Home Foundation exists to champion. Thread operates on the same principle: it's an energy-efficient, wireless mesh network that connects devices directly to one another and can automatically reroute around disruptions. And for battery-powered alarms like Sensereo's, Thread's low-power design means fewer battery changes for devices that are always on duty. While we're talking about safety, it's important to note that if your Thread network did for any reason drop out, Sensereo's smoke and CO alarms will keep working as a "regular" alarm would - no smart home required. That peace of mind is central to how Sensereo thinks about their products, and having caught up with the team at CES 2026 earlier this year, we can tell you it's just the beginning. Air quality sensors and more are on the horizon, all building toward the same vision: to build an environmental intelligence system for the home that helps users understand and respond to their surroundings. "J [Next page]()