Prepare to be dazzled, because this month LEDVANCE join the Works with Home Assistant program as our newest partners 🎉 And what’s more, they bring a huge lineup of certified devices (116, to be exact!) to our community, which means plenty of new ways to light up your home 💡

A century of bright ideas

We love welcoming established brands as much as newer names to the Works with Home Assistant program, and LEDVANCE are… well… both! The company was created in 2016 when OSRAM, one of the lighting industry’s oldest and most respected names, spun off its general lighting business as an independent entity. Its name combines “LED” and “advance,” a nod to the shift toward modern LED lighting and the possibilities that came with it.

Since then, LEDVANCE have grown into a global name in their own right, with offices in more than 50 countries and customers in more than 140. They carry forward more than 100 years of lighting experience, and still sell products under the OSRAM brand through a licensing agreement.

But while their heritage is strong, their focus is firmly on the future. Their OSRAM SMART+ range brings that expertise into the modern smart home (and now our program 🎉), embracing Matter to give you more freedom to illuminate your environment around the way you live. With so many devices to choose from, whatever you’re picturing for your home, chances are there’s a LEDVANCE light that can help you make it happen.

Setting the standard

Every LEDVANCE device certified to the program uses Matter with a Wi-Fi connection, making the devices simple to integrate into your existing setup. For any newcomers, Matter is an open standard developed by the Connectivity Standards Alliance. It lets devices from different brands work together locally, so you’re never locked into one company’s ecosystem and your data stays where it should be – in your home.

Since LEDVANCE’s Matter devices use Wi-Fi, you won’t need any extra gear to get started. Just add them to your network and they’ll talk to Home Assistant directly, ensuring an easy setup and the option to create automations with the devices you already have. It’s great to see our new partners prioritizing open standards, showing they care as much as we do about helping our community control their smart homes on their own terms.

Devices

LEDVANCE’s certified devices cover everything from filament-style bulbs, spotlights, and recessed and track downlights, to ceiling and wall lights, floor lamps, and flexible LED strips for adding a glow under kitchen cabinets or behind the TV. In fact, there are so many options that the list is too long to include in this blog, so head to the certified device list to check out all the details!

Set the scene for a comfy night in with LEDVANCE’s smart lights.

To give you a snapshot, most of the range is tunable white or full color, so your lights can go from a cozy evening glow to crisp morning brightness (or a full rainbow, if the mood strikes). There are also IP-rated options for bathrooms and the garden, including floodlights and outdoor spots, so you can automate your lights beyond the back door, for example to turn your security lights on when a sensor detects motion. And if you prefer to use what you already have, the SMART+ Plug can turn any ordinary lamp or appliance into something you can automate, while smart wall switches do the same for your ceiling lights: replace the switch on the wall, keep the bulbs you have.

As with every device certified to the program, LEDVANCE’s products have been rigorously tested by our in-house team to make sure they comply with our core requirements of local control and privacy. LEDVANCE have also committed to providing long-term support for our community, so you can be confident your setup will keep working for the long run.

Lighting that lasts

Sustainability is one of the core principles of the Open Home Foundation, the non-profit organization that runs Works with Home Assistant. A big part of that is making sure devices stay useful for as long as possible. Since LEDVANCE’s devices don’t need a cloud service to function, you don’t have to worry about a far-off server shutdown turning your lights into e-waste.

And because Matter works across platforms, you’ll still be able to use your tech if you ever change smart home systems. Lighting that keeps shining whatever happens to a platform: that’s the kind of partner we love to welcome, and it’s what this program is all about.

All systems glow

We’re thrilled to have LEDVANCE join our community, and can’t wait to see what you light up with their range of devices. Want to see more partners like them on board? A Home Assistant Link (formerly Home Assistant Cloud) subscription gives you secure, remote access to your smart home, and directly supports the Open Home Foundation to expand our program. Because the more brands that join, the more choice you have to design your space exactly the way you like. Here’s to plenty more switched-on homes 💡 Welcome, LEDVANCE!

FAQs

Q: If I have a device that is not listed under Works with Home Assistant does this mean it’s not supported?

A: No! It just means that it hasn’t gone through a testing schedule with our team or doesn’t fit the requirements of the program. It might function perfectly well but be added to the testing schedule later down the road, or it might work under a different connectivity type that we don’t currently test under the program.

Q: OK, so what’s the point of the Works with program?

A: It highlights the devices we know work well with Home Assistant and the brands that make a long-term commitment to keeping support for these devices going. The certification agreement specifies that the devices must have the functionality you would expect within Home Assistant, operate locally without the need for cloud and that they will continue to do so long-term.

Q: How were these devices tested?

A: All of LEDVANCE’s certified devices were tested using Home Assistant over a standard Wi-Fi connection with our certified Matter integration. If you have another setup or integration that’s not a problem, but we test this way as it’s the most effective method for our team to certify within our ecosystem.

Q: Will you be adding more LEDVANCE devices to the program?

A: Why not! We’re thrilled to foster a close relationship with the team at LEDVANCE to work together on any upcoming releases or add in further products that are not yet listed here.

What's Changed

• fix(linux): add a Spanish comment to the desktop entry by @eibidia in #1468
• fix(agent): let a thumb-wheel swipe fire Volume Up/Down more than once by @4ni1ak in #1455
• feat(hid): recognise Powerplay receiver 046d:c53a by @FelipeIzui in #1267
• feat(hid): add G733 battery and power-state support by @d-tatianin in #1601
• fix(i18n): improve Turkish catalog wording by @volkanncicek in #1415
• docs(core): clarify persisted device identifier scope by @yuzi-co in #670
• fix(macos): respect the selected Apple developer directory by @4ni1ak in #1457
• fix(gui): restore the config-error folder action by @4ni1ak in #1458
• fix(core): resolve connection transport from live routes by @4ni1ak in #1367
• feat(gui): add custom actions to the mouse picker by @4ni1ak in #1452
• fix(gui): show friendly names for Windows app profiles by @4ni1ak in #1463
• feat(hidpp): implement pointer motion scaling by @Chernicharo in #1347
• fix(inject): restore macos 27 space swipes by @4ni1ak in #1703
• fix(hook): identify unbundled macos applications by @4ni1ak in #1469
• chore: release v0.8.13 by @AprilNEA[bot] in #1716

New Contributors

• @FelipeIzui made their first contribution in #1267
• @d-tatianin made their first contribution in #1601
• @volkanncicek made their first contribution in #1415

Full Changelog: v0.8.12...v0.8.13

What's Changed

• test(agent): cover a BLE mouse that wakes as a new node by @kohjunhao in #1649
• fix(gui): seed the DPI editor from config while the live read is pending by @4ni1ak in #1628
• fix(hid): recognize Lightspeed receiver 046d:c541 by @hamfield-eu in #1679
• fix(gui): truncate the function-row key callout's name instead of overflowing by @4ni1ak in #1691
• fix(gui): wrap the device-enabled caption so the switch stays in the card by @Imbecile6197 in #1670
• feat(fixture): add an MX Ergo Unifying fixture by @Chernicharo in #1374
• fix(gui): set text color on mouse pairing passkey click icons by @ZOZiBoi in #1640
• fix(hidpp): tell another protocol's reports apart from malformed HID++ by @Chernicharo in #1373
• fix(macos): log the candidate displays when Space state has no match by @4ni1ak in #1694
• fix(agent): phase horizontal thumb-wheel scroll when smoothing is off by @nredd in #1689
• feat(i18n): add Czech locale by @Imbecile6197 in #1669
• fix(core): write config through symlinks instead of replacing them by @FunJim in #1642
• fix(hook): keep the short budget for tap teardown after a probe break by @TheMedpreneur in #1600
• fix(i18n): name the real update-check host in the consent dialog by @4ni1ak in #1629
• fix(agent): restore ring toggle and publish expired sessions by @isleofgreg in #1665
• fix(gui): scale configuration labels with interface text by @4ni1ak in #1627
• fix(agent): fall back to focus when the pointer target is unidentified by @kohjunhao in #1648
• fix(gui): anchor scrollbar overlays in action ring editor and app picker by @lynicis in #1360
• fix(i18n): track the locale catalogs as build inputs by @zmingxie in #1327
• fix(gui): wrap the About page's link row instead of clipping it by @crnst8 in #885
• fix(cli): replace the stale receiver note with a Linux udev hint by @Chernicharo in #1348
• fix(gui): show wheel controls without adjustable dpi by @minatoaquaMK2 in #1369
• fix(gui): recognize MX Ergo's DPI slot name for the mouse diagram by @armandodollia in #1391
• fix(macos): write the scroll point delta last so pixel precision survives by @isleofgreg in #1156
• chore: release v0.8.12 by @AprilNEA[bot] in #1646

New Contributors

• @hamfield-eu made their first contribution in #1679
• @Imbecile6197 made their first contribution in #1670
• @Chernicharo made their first contribution in #1374
• @ZOZiBoi made their first contribution in #1640
• @nredd made their first contribution in #1689
• @FunJim made their first contribution in #1642
• @TheMedpreneur made their first contribution in #1600
• @lynicis made their first contribution in #1360
• @zmingxie made their first contribution in #1327
• @crnst8 made their first contribution in #885
• @minatoaquaMK2 made their first contribution in #1369
• @armandodollia made their first contribution in #1391

Full Changelog: v0.8.11...v0.8.12

Home Assistant 2026.10! 🎉

Last week, Nabu Casa dropped: Big Tech ruined the cloud, so we’re renaming ours. Home Assistant Cloud is on its way to becoming Home Assistant Link. Same service, new name. I love that title, by the way. If you haven’t read the story behind it yet, go have a look, and tell us what you think. The change is planned for the December release, so there is still time. 🏎️

Now, I’ll let you in on a secret: I’m an automation person. Dashboards are lovely and I admire everyone who builds a pretty one, but for me, automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] are what make a smart home actually smart. So you can imagine how happy I am with what’s in this release. One of the most powerful features you never thought you’d need has been sitting in Home Assistant for years: trigger IDs. Give your triggersA trigger is the part of an automation that makes the automation start when something specific happens, for example, when the sun sets, a door opens, or a button is pressed. [Learn more] an ID, and one automation can do the job of two, three, or five. It was also tucked away in a menu, you had to invent the IDs yourself, and then remember which was which. Plenty of you never found it, and that’s on us.

Not anymore. Trigger IDs finally get a proper UI: you check the triggers you want in the condition, and Home Assistant takes care of the IDs behind the scenes. And if you like writing your own IDs in YAMLYAML is a human-readable data serialization language. It is used to store and transmit data in a structured format. In Home Assistant, YAML is used for configuration, for example in the configuration.yaml or automations.yaml files. [Learn more], nothing changes. Those keep working exactly as before. That makes it my favorite of this release. 🧠

Don’t get me wrong, the map is absolutely a cool feature too. Last release, every map in Home Assistant broke overnight when our map provider wanted an API key. We moved to OpenStreetMap, and it turns out that swapping out the map opens a lot of doors: a vector map that stays sharp at every zoom level, redesigned markers, and an overview of where everyone has been. You are here. 📍

There’s more: a tidier profile page, a panel for your Modbus connections, connecting your AI in one click, and 15 new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more]! 🚀

Enjoy the release!

../Frenck

• Cloud becomes Link
• A whole new map
  • Crisp at every zoom level
  • Redesigned markers
  • An overview for the Map dashboard
  • Zones on the new map
• A tidier profile page
• The best automation feature you never used
• 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
  • Show a card only when it matters
  • A panel for your Modbus connections
  • Connect your AI in one click
  • Name an entity after its device
  • Timers, one tap away
• Patch releases
  • 2026.10.1 - October 10
  • 2026.10.2 - October 16
• Need help? Join the community
• Backward-incompatible changes
• All changes

A huge thank you to all the contributors who made this release possible! And a special shout-out to @googanhiem and @piitaya who helped write these release notes. Also, @grischard, @moryoav, and @RaHehl for putting effort into tweaking its contents. Thanks to them, these release notes are in great shape. ❤️

Cloud becomes Link

In case you missed it, we’re making the move to rename Home Assistant Cloud to Home Assistant Link. Same service, new name.

We’re all pretty annoyed by how Big Tech has been ruining perfectly good smart home devices by making them reliant on the cloud. Ours has never locked anyone in, harvested their data, or turned working devices into e-waste, so a new name was in order. Home Assistant Link is all about being clearer that it does things differently. The change is planned for the December release, so tell us your thoughts before then.

The best link is a fast link. 🏎️ Nabu Casa has been hard at work making remote access even faster across the globe. They recently migrated all of their servers to bare metal and added more servers to boost their coverage of the world. This month, they added a latency checker that pings multiple servers on boot and picks the best connection for you.

A whole new map

Last release, something changed underneath every map in Home Assistant, and we barely mentioned it in the release notes. The map provider we relied on started stamping an “API key required” message across its map images, breaking every map in Home Assistant at once. Instead of hunting for another free tile provider, we switched from pre-rendered map images to vector tiles generated and served by the OpenStreetMap Foundation. Both maps use OpenStreetMap data, but your device now draws the map itself. The new Map tiles integration fetches and caches the tiles through your Home Assistant instance, so your browser does not contact external tile servers directly. Recently viewed parts of the map remain available through a short internet hiccup.

Guillaume Rischard (@grischard), the former chair of the OpenStreetMap Foundation who initiated and led its vector-tile initiative, joined us during the 2026.9 release party.

Swapping out the map underneath opened a lot of doors. This release walks through the first few.

Crisp at every zoom level

The map is drawn entirely on your device, as vectors, instead of being stitched together from pictures. Streets and labels stay sharp at any zoom level, and zooming in and out is smooth. The map also has a dedicated dark style, with colors designed for dark mode. Older devices that can’t render vector maps, like the old tablet on your wall, automatically fall back to the classic map.

Redesigned markers

The markers on the map got a complete redesign. People show up with their picture, zonesZones allow you to specify certain regions on a map. They enable zone presence-detection and can be used in automations. For example, to start the vacuum after you left home or start the heating at home when you leave the office. [Learn more] get a marker with their icon in their own color, and everyone in the same zone shares a single bubble on that zone, instead of a pile of markers stacked on top of each other. Zoom out far enough, and bubbles that would overlap merge into one.

An overview for the Map dashboard

The Map dashboard now comes with an overview, next to the map on a desktop and as a sheet you pull up on your phone. It has three tabs: People, Devices, and Zones. Select someone to see their recent activity, with each stop colored by the zone they were in. Select a zone to see who’s there. On a phone, the map now also fills the whole screen, edge to edge.

The same overview shows up when you put a map card in a panel view on your own dashboard.

Zones on the new map

The zone editor in Settings > Areas, labels & zones now uses the same new map. Your zones are sorted alphabetically, with Home always at the top, and they show the same icons and colors you see on the map.

The redesign follows an Open Home Foundation design concept for the Map dashboard.

Thanks to @maartenla, @matthiasdebaat, @bramkragten, and @bgoncal; @grischard for initiating vector maps on the OpenStreetMap side and for assisting us; and Paul Norman (@pnorman) for developing Tilekiln and the tile service. Thanks also to the OpenStreetMap Foundation and the MapLibre, Shortbread, and VersaTiles communities.

Like Home Assistant, OpenStreetMap is built in the open by people like you. Spot something in your neighborhood that’s missing or out of date? You can leave a note or edit the map yourself.

A tidier profile page

Select your name at the bottom of the sidebar, and you land on your User profile. Over the years, that page quietly turned into a bit of a junk drawer. Language, theme, date formats, sidebar order, push notifications, keyboard shortcuts: all stacked in one long General tab, with Security as its only neighbor. Everything was there. You just had to scroll past most of it to find the one thing you came for.

The profile page is now an overview, using the same kind of navigation you already know from Settings. At the top is a card with your account, followed by your Theme, and a short list of sections that each hold a handful of related settings:

• Appearance: Your default dashboard and the order of your sidebar
• Localization: Your language, time zone, and how dates, times, and numbers are shown
• This browser (or This mobile app in the companion app): Notifications, display, and shortcuts for the device you’re using right now
• Security: Your password, multi-factor authentication, and access tokens

Nothing was taken away. Every setting is still there, just grouped so it’s easier to find. Thanks, @pcan08 and @maartenla!

That account card at the top learned a new trick, too. Until now, your own name and picture weren’t actually yours to change. Only an administrator could set them, tucked away in the person settings. Not an administrator, but you wanted a nicer picture of yourself in the sidebar? You had to go ask whoever runs your Home Assistant. A bit odd, for something that is literally your face.

Every user, administrator or not, now has an Edit profile button right next to Log out. Upload and crop a picture, change your name, and save. Your name is used for both your user and the person linked to it, so it’s the same everywhere you show up, from the sidebar to your dashboards and Assist. Your new picture shows up in the sidebar right away.

The best automation feature you never used

Take a look at your automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more], and chances are you’ll find a few that come in pairs. One turns the hallway light on when motion is detected, the other turns it off again when the motion stops. One sends a notification when the washing machine starts, the other when it’s done. Two automations, doing one job.

Home Assistant has had a way to combine those into one for years. Give each triggerA trigger is the part of an automation that makes the automation start when something specific happens, for example, when the sun sets, a door opens, or a button is pressed. [Learn more] an ID, and use the Triggered by conditionConditions check whether something is true at that moment, for example, whether a door is closed. You can use them in automations and scripts. If a condition is not met, the actions that come after it in the same sequence do not run. At the top level of an automation or script, this stops the automation or script. [Learn more] to do something different depending on which trigger fired. It’s one of the most powerful things you can do in the automation editor, and also one of the best-hidden. The trigger ID field sat in the menu of each trigger. You had to come up with an ID, type it in yourself, and then remember which ID belonged to which trigger when you picked them in the condition. Most people never found it, and honestly, we can’t blame them.

Not anymore. Add a Triggered by condition, and you check the triggers it should match. You see the triggers themselves, not some ID you made up, and each one is numbered by its position in your list, with the same number shown next to the trigger itself. So you always know which one is which. There are no IDs to come up with at all. Home Assistant takes care of those behind the scenes, and cleans up after itself when you remove a trigger.

If you set your trigger IDs yourself in YAMLYAML is a human-readable data serialization language. It is used to store and transmit data in a structured format. In Home Assistant, YAML is used for configuration, for example in the configuration.yaml or automations.yaml files. [Learn more], nothing changes. Those IDs keep working exactly as they did, sharing one ID between several triggers is still fine, and Home Assistant won’t add IDs to your YAML for you. The trigger ID field is gone from the automation editor, because you no longer need it there: to run the same actions for several triggers, check them all in one Triggered by condition.

The editor does keep an eye out for two things, but only in the Triggered by condition. If a condition points to a trigger that no longer exists, it flags it, so you can clear it. And if several triggers share the same ID, it shows a warning with a Fix that gives each trigger its own ID and updates your conditions to match. It’s a suggestion, not a repair, so if sharing an ID is what you want, you can leave it as it is.

This completes an Open Home Foundation roadmap opportunity to make referencing triggers in automations a lot easier. Thanks, @jpbede, @wendevlin, @marcinbauer-ohf, and @nielsrowinbik!

While you’re in the automation editor, you’ll notice your triggersA trigger is the part of an automation that makes the automation start when something specific happens, for example, when the sun sets, a door opens, or a button is pressed. [Learn more], conditionsConditions check whether something is true at that moment, for example, whether a door is closed. You can use them in automations and scripts. If a condition is not met, the actions that come after it in the same sequence do not run. At the top level of an automation or script, this stops the automation or script. [Learn more], and actionsAn action makes Home Assistant do something, for example, turn on a light, send a notification, or activate a scene. Automations and scripts run a list of actions. [Learn more] tell you a bit more at a glance. Each row now shows the details that used to be hidden until you opened it: the threshold a trigger or condition checks for, like “above 10 °C”, how long something needs to stay that way, the offset on a sunrise or sunset, and how long a wait action waits before it gives up. Thanks, @wendevlin and @MindFreeze!

Integrations

Thanks to our community for keeping pace with the new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] and improvements to existing ones! You’re all awesome 🥰

New integrations

We welcome the following new integrations in this release:

• Axle Energy, added by @Herbertmt978
  Bring the grid event schedule of your Axle Energy account into Home Assistant. It tells you whether an upcoming event asks you to import from or export to the grid, and exactly when it starts and ends, so your automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] can get your home ready in time.

• Bitvis Power Hub, added by @MandusBorjesson
  Read real-time electricity data from your smart meter using a Bitvis Power Hub, which plugs into the meter’s HAN port. The Power Hub pushes its measurements, like power, voltage, and current per phase, straight to Home Assistant over your local network. No cloud, no pollingData polling is the process of querying a device or service at regular intervals to check for updates or retrieve data. By defining a custom polling interval, you can control how frequently your system checks for new data, which can help optimize performance and reduce unnecessary network traffic. [Learn more].

• Gree Infrared, added by @Dr-Blank, launching at 🥈 silver quality
  Control a Gree air conditioner using any infrared transmitter you already have set up in Home Assistant, like an ESPHome device with an infrared LED. Add an infrared receiver, and the climateThe Climate entity allows you to control and monitor HVAC (heating, ventilating, and air conditioning) devices and thermostats. [Learn more] entity follows along when someone uses the physical Gree remote. Gree builds air conditioners for many brands, so units sold as Onida, Sinclair, and others work as well.

• INDI Allsky, added by @TN-1
  Connect your INDI Allsky camera server, an allsky camera system for astrophotography and keeping an eye on cloud cover. You get the latest capture as a camera, plus sensors for sky quality, the number of stars detected, exposure time, and whether it’s night.

• KACO Modbus, added by @g4bri3lDev
  Connect a KACO new energy solar inverter directly over your local network using Modbus TCP. It shows what the inverter is producing right now, its lifetime energy counter for the Energy dashboard, and what it is doing, without any cloud account or manufacturer portal involved.

• my-PV, added by @rrooggiieerr
  Control my-PV devices, like the AC•THOR range and AC ELWA 2, which turn your surplus solar power into hot water. Home Assistant talks to them locally and discovers them on your network automatically.

• OSRAM Infrared, added by @freeDom-, launching at 🥈 silver quality
  Control OSRAM and LEDVANCE RGB lights that come with a 24-button infrared remote, using an infrared transmitter set up in Home Assistant. With an infrared receiver, the lightA light has a brightness you can control, and optionally color temperature or RGB color control. [Learn more] entity also picks up commands from the physical remote.

• Persang Infrared, added by @Dr-Blank
  Control a Persang Bluetooth speaker using an infrared transmitter set up in Home Assistant, giving you a media player and buttons for its remote functions.

• SolarEdge Modbus, added by @frenck, launching at 🏆 platinum quality
  Connect to your SolarEdge solar inverter over your own network, using the Modbus TCP interface built into the inverter. No account, no API key, no cloud. Readings arrive every few seconds instead of every few minutes, and keep arriving when your internet connection is down. You can also change the export limit and how your battery charges.

• Sunsynk, added by @jamesridgway
  Bring your Sunsynk hybrid solar inverter and battery into Home Assistant using your Sunsynk Connect account. You get sensors for solar production, grid import and export, and your battery. Home Assistant can even discover the Sunsynk data logger on your network.

• Theben Conexa Smart Meter Gateway, added by @mdluhosch
  Read your meter data locally from a Theben Conexa 3.0 smart meter gateway, using its built-in Home Area Network (HAN) interface. No cloud needed.

• Threema, added by @LukasQ
  Send end-to-end encrypted messages from your automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] to people on Threema, the privacy-focused messenger that doesn’t need a phone number. It uses the Threema Gateway service, and each person you add as a recipient gets their own notify entity.

• Vitesy, added by @chemelli74
  Connect the Vitesy Shelfy, an air purifier that lives in your refrigerator. See the air quality and temperature inside your fridge, how often the door was opened, and when the filter needs cleaning or replacing. You can even switch the purifier mode, for example to boost it after a grocery run.

• Willow, added by @PaxPrz
  Keep an eye on the health of your indoor plants with Willow sensors. Temperature, humidity, soil moisture, and light levels come from the Willow cloud into Home Assistant, ready for your dashboards and automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more]. Your plants can’t tell you they’re thirsty, but now Home Assistant can.

• Zonneplan, added by @erwindouna
  Get the electricity and gas prices of your Zonneplan contract, a Dutch provider of dynamic energy contracts. Handy for running your appliances when energy is cheapest.

This release also has new virtual integrations. Virtual integrations are stubs that are handled by other (existing) integrations to help with findability. These ones are new:

• Austroflamm, provided by Fumis, added by @frenck
• EcoSpar, provided by Fumis, added by @frenck
• HAAS+SOHN, provided by Fumis, added by @frenck
• HETA, provided by Fumis, added by @frenck
• O General, provided by FGLair, added by @Dr-Blank
• Onida Infrared, provided by Gree Infrared, added by @Dr-Blank
• Steinway & Lyngdorf, provided by Lyngdorf, added by @fishloa

Noteworthy improvements to existing integrations

It is not just new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] that have been added; existing ones keep getting better too. Here are some of the noteworthy improvements this release:

• Matter added switchesSwitches are things that have two states you can select between, such as turning on or off a socket. [Learn more] to turn the visual and audible alarms of supported leak sensors on or off, like the IKEA KLIPPBOK, and a switch for one-touch locking, so you decide whether a single touch on the keypad of your lock is enough to lock the door. DevicesA device is a model representing a physical or logical unit that contains entities. that measure electrical power now also report the frequency and power factor. Thanks, @wardmatter, @mmmspatz, and @lboue!
• Tuya supports a lot more devicesA device is a model representing a physical or logical unit that contains entities. this release: two-channel DIN rail energy meters with readings per channel, circuit breakers, EV chargers (with their charging current, charging mode, and session energy), water valves (with water usage and temperature), and the keypad tone and alarm push settings of the Duosmart C30 alarm panel. Three-phase electricity meters now also report reactive power, apparent power, and power factor for each phase. Thanks, @keranm, @tmunzer, @o-borovets, @syl-craft, @ChayoteJarocho, @huangrenwei79, and @epenet!
• Internet Printing Protocol (IPP) added page counters, so you can keep track of how many pages, impressions, and sheets your printer has gone through, split into color and black and white on printers that report it. Thanks, @brianegge!
• ESPHome devicesA device is a model representing a physical or logical unit that contains entities. can now open the connection to Home Assistant themselves, so they work even when Home Assistant can’t reach them directly. Turn on the outgoing_connection option on your ESPHome device, and Home Assistant takes it from there, with the same encryption as always. Thanks, @bdraco!
• HomeKit Bridge can now show your valve entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] in the Home app as a faucet, shower head, or sprinkler. How long a valve runs can now also come from any number entity, not just a number helperA helper is a virtual entity you create inside Home Assistant. It is not backed by a physical device. Helpers store values, track state, or do calculations that your automations and dashboards need. [Learn more]. Thanks, @louwii17!
• Philips Hue added a switch to turn each MotionAware zone on or off, just like you can in the Hue app. Rooms and zones also gained a sceneScenes capture the states you want certain entities to be. For example, a scene can specify that light A should be turned on and light B should be bright red. [Learn more] select, showing which scene (or smart scene) is currently active, and letting you pick another one. Thanks, @marcelveldt and @sliekens!
• Reolink can now control the pan and tilt lens of cameras that combine multiple lenses in one device, when connected to a Reolink NVR or Home Hub. Thanks, @starkillerOG!
• Music Assistant announcements can now speak a message, not only play an audio file. The announcement action takes a message and a “text-to-speech”TTS (text-to-speech) allows Home Assistant to talk to you. [Learn more] entity to speak it, while keeping the pre-announcement chime and announcement volume that tts.speak doesn’t offer. The AI search tool can now also search inside artists, albums, and playlists. Thanks, @marcelveldt and @balloob!
• Roborock wet and dry vacuums now update in real time, so docking or starting a cleaning shows up in Home Assistant right away. The Roborock Q10 can now also clean specific zones, drive to a spot you pick, and report where it is. Thanks, @piitaya and @hmmbob!
• Z-Wave added three new conditionsConditions check whether something is true at that moment, for example, whether a door is closed. You can use them in automations and scripts. If a condition is not met, the actions that come after it in the same sequence do not run. At the top level of an automation or script, this stops the automation or script. [Learn more] to the automation editor, with proper fields to fill in: check a device’s node status, the value of a configuration parameter, or any other Z-Wave value. Z-Wave triggersA trigger is the part of an automation that makes the automation start when something specific happens, for example, when the sun sets, a door opens, or a button is pressed. [Learn more] got the same treatment. Thanks, @raman325!
• UniFi Network now reports the battery level and runtime of your UniFi UPS, along with its output power, current, voltage, and power factor. Thanks, @jimstrang!
• Broadlink now supports the RM5 Plus, which used to fail with a “device not supported” error. Thanks, @DAB-LABS!
• UniFi Protect now supports the key fob, with an event entityAn event entity represents a momentary occurrence without a lasting state, for example, when you press a doorbell or a button on a remote control. Instead of a state such as on or off, the event entity keeps track of when the last event was detected and its event type, such as a single press or a long press. [Learn more] that fires on every button press, and shows each relay input as its own binary sensorA binary sensor is an entity that reports one of two mutually exclusive states, on or off. The device class determines how those states are labeled in the UI. For example, open/closed for a door or detected/clear for motion. [Learn more]. The API key only mode now also handles motion and smart detections, smart sensors, sirens, relays, and several camera and floodlight settings. Thanks, @sbesh91, @igoraugustynski, and @RaHehl!
• OpenAI added support for the GPT-6 Astra and GPT-Image-2.5 models. GPT-Image-2.5 Flare is now the default for generating images with AI Task. Thanks, @Shulyaka!
• SwitchBot Bluetooth added support for the Lock Ultra Max, the Universal Remote, and the RGBICWW Light Bars, and lets you set how fast your SwitchBot curtains move. Thanks, @Onero-testdev and @joostlek!
• SwitchBot Cloud added support for the Lock Ultra Max. Thanks, @XiaoLing-git!
• LIFX now supports LIFX lights that connect over ThreadThread is a low-power mesh networking standard that is specifically designed for smart home applications. It is a protocol that defines how devices communicate. [Learn more], and the signal strength sensor works for those lights too. Thanks, @Djelibeybi!
• Proxmox VE added “update entities”An update entity is an entity that indicates if an update is available for a device or service. [Learn more] for your Proxmox nodes, showing when updates are available and how many Proxmox and other packages are waiting. Installing them from Home Assistant is not possible yet. Thanks, @CoMPaTech!
• LinkPlay speakers that follow another speaker in a multiroom group now show the title, artist, album, and album art of what’s playing. Each speaker keeps its own volume. Thanks, @MagicMicky!
• Apple iCloud brings your iCloud calendars and Reminders into Home Assistant. Each calendar shows up as a calendar entityA calendar entity represents a schedule of events coming from a local or external calendar source. It can be used to trigger automations based on the start or end of an event, react to offsets (like 15 minutes before), or retrieve event details through services. [Learn more], and each Reminders list as a to-do list, where you can add, complete, and remove items that sync right back to your Apple devices. Thanks, @FezVrasta!
• Hikvision added “event entities”An event entity represents a momentary occurrence without a lasting state, for example, when you press a doorbell or a button on a remote control. Instead of a state such as on or off, the event entity keeps track of when the last event was detected and its event type, such as a single press or a long press. [Learn more] that tell you what triggered a smart event: a human, a vehicle, or a pet. Great for getting notified about people at your gate, while ignoring passing traffic. Thanks, @ptarjan!
• Opower now uses the import and export readings from your meter itself for your grid statistics. Before, grid import was worked out from your net usage, which undercounted it for homes with solar panels, and could even show no import at all on a sunny day. Thanks, @tronikos!
• TP-Link Omada now shows your Omada controller as a deviceA device is a model representing a physical or logical unit that contains entities., with its status and an “update entity”An update entity is an entity that indicates if an update is available for a device or service. [Learn more] for its firmware. Thanks, @rubempoli!
• EnergyZero can now use quarter-hourly electricity prices, and added all-in electricity prices next to the market prices. Thanks, @klaasnicolaas!
• Bosch SHC grew a lot this release. Micromodule shutters, awnings, and blinds now show up as coversCovers are devices such as blinds, garage doors, etc that can be opened and closed and optionally set to a specific position. [Learn more], and there are new switches for child locks, the alarm bypass of door and window contacts, the silent mode of thermostats, the intrusion alarm of the Smoke Detector II, and the settings of the Motion Detector 2, Door/Window Contact II Plus, Micromodule Relay, and Camera Eyes. A new sensor counts the open doors and windows in your home, thermostats show their valve position, and motion detectors now fire an event for every motion. Thanks, @mosandlt!
• Midea added water heaters, a lock switch, a pump switch for dehumidifiers, a sensor for when the water pump of an air conditioner is running, and salt, AI mode, time remaining, and door warning entities for the appliances that support them. Thanks, @chemelli74, @rokam, @mattrossman, and @peterdey!
• Teslemetry can now control things locally: your Powerwall over your own network, and your vehicle over Bluetooth. Commands try the local route first and fall back to the cloud, so they are faster, and vehicle commands even work when the car has no connection. Thanks, @Bre77!
• Peblar chargers can now install firmware updates from Home Assistant, and you can manage the RFID cards and the autocharge vehicles allowed to charge, and authorize a charge session, all from actionsAn action makes Home Assistant do something, for example, turn on a light, send a notification, or activate a scene. Automations and scripts run a list of actions. [Learn more]. Chargers with a buzzer or status light also get selects for the buzzer volume and LED brightness. Thanks, @syphernl and @frenck!
• MELCloud Home added the outdoor temperature and a switch to put your unit in standby. Thanks, @erwindouna!
• Universal Devices ISY/IoX added “event entities”An event entity represents a momentary occurrence without a lasting state, for example, when you press a doorbell or a button on a remote control. Instead of a state such as on or off, the event entity keeps track of when the last event was detected and its event type, such as a single press or a long press. [Learn more] for Insteon buttons and keypads, so you can automate on a press, a double press, or a long press. Thanks, @shbatm!
• LG Infrared air conditioners gained swing modes, switches for the ion generator and auto clean, a select for the energy limit, and buttons for features like Jet mode and Eco mode. Thanks, @Dr-Blank!
• Samsung Infrared now supports air conditioners. Thanks, @elax46!
• Weheat added the air outlet temperature, domestic hot water target and control method, the electricity used by the indoor unit, and what your heat pump is doing while it cools. Thanks, @barryvdh!
• LED Infrared added support for generic 10-key LED candle remotes. Thanks, @tr4nt0r!
• Collection image gained actionsAn action makes Home Assistant do something, for example, turn on a light, send a notification, or activate a scene. Automations and scripts run a list of actions. [Learn more] to jump to the first, last, next, or previous image in the folder, alongside picking a random one. Thanks, @karwosts!
• Homevolt added a select to change the battery mode, and controls for the power setpoint and grid import and export limits. Thanks, @Danielhiversen!

Integration quality scale achievements

One thing we are incredibly proud of in Home Assistant is our integration quality scale. This scale helps us and our contributors to ensure integrations are of high quality, maintainable, and provide the best possible user experience.

This release, we celebrate several integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] that have improved their quality scale:

• 11 integrations reached platinum 🏆

  • Besen, thanks to @moryoav
  • Dropbox, thanks to @bdr99
  • easyEnergy, thanks to @klaasnicolaas
  • Google Assistant SDK, thanks to @tronikos
  • Lyngdorf, thanks to @fishloa
  • Monzo, thanks to @JakeMartin-ICL
  • NeoPool, thanks to @svasek
  • OpenEVSE, thanks to @c00w
  • Sofar, thanks to @darkrain-nl
  • TechnoVE, thanks to @Moustachauve
  • VIZIO SmartCast, thanks to @raman325

• 4 integrations reached gold 🥇

  • Midea, thanks to @chemelli74
  • MikroTik, thanks to @chemelli74
  • Proxmox VE, thanks to @erwindouna
  • WattWächter Plus, thanks to @smartcircuits

• 6 integrations reached silver 🥈

  • Airly, thanks to @bieniu
  • Collection image, thanks to @karwosts
  • Imou, thanks to @Imou-OpenPlatform
  • LibreNMS, thanks to @mib1185
  • MELCloud Home, thanks to @erwindouna
  • Solarman, thanks to @Yves-Xu

• 4 integrations reached bronze 🥉

  • DNS IP, thanks to @gjohansson-ST
  • Met Office, thanks to @TCWORLD
  • Subaru, thanks to @jpettitt
  • Wolf SmartSet Service, thanks to @EnjoyingM

This is a huge achievement for these integrations and their maintainers. The effort and dedication required to reach these quality levels is significant, as it involves extensive testing, documentation, error handling, and often complete rewrites of parts of the integration.

A big thank you to all the contributors involved! 👏

Now available to set up from the UI

While most integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] can be set up directly from the Home Assistant user interface, some were only available using YAML configuration. We keep moving more integrations to the UI, making them more accessible for everyone to set up and use.

The following integrations are now available via the Home Assistant UI:

• Discogs, done by @zackwag
• Rejseplanen, done by @Jawar19
• Volkszaehler, done by @StefanSchoof

Farewell to the following

Time for a little cleaning, and no, we did not wait for spring! The following “integrations”Integrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] are no longer available as of this release:

• Dublin Bus has been removed. It relied on the Real-Time Passenger Information API, which the National Transport Authority shut down in September 2020, so it has not worked since. For scheduled departures, the GTFS integration can use the timetable data published by Transport for Ireland.
• Etherscan has been removed. It relied on version 1 of the Etherscan API, which has been shut down, so its sensors only showed False instead of a balance. To keep tracking a wallet balance, you can use the RESTful sensor with the Etherscan V2 API and your own free API key.
• Melnor RainCloud has been removed. Melnor discontinued the original RainCloud WiFi Timer in April 2026, and its cloud service no longer responds.
• Orange and Rockland Utility (ORU) has been removed. The endpoint it relied on stopped returning meter data years ago. Orange and Rockland customers can use the Opower integration instead.
• Sigfox has been removed. It relied on version 1 of the Sigfox backend API, which Sigfox retired.
• SolarEdge Local has been removed. It relied on a local web API that SolarEdge disabled in inverter firmware updates starting in 2020. Use the SolarEdge integration, or the new SolarEdge Modbus integration if you want to keep things local.
• Travis-CI has been removed. It relied on the travis-ci.org API, which Travis CI shut down in June 2021.
• Zestimate has been removed. Zillow retired the API it relied on, and its replacement is aimed at commercial use, so the integration could not simply be updated.

If you still have any of these in your YAMLYAML is a human-readable data serialization language. It is used to store and transmit data in a structured format. In Home Assistant, YAML is used for configuration, for example in the configuration.yaml or automations.yaml files. [Learn more] configuration, you can remove them.

Other noteworthy changes

There is even more packed into this release. Here are some of the other changes worth a mention:

• The Home dashboard now shows active alerts too. The alerts you set up for the Security dashboard last release, like a door left open or a smoke detector going off, now also show up right on your Home dashboard, so you don’t miss them. Thanks, @timmo001!
• Tile cards gained a slider feature for input selects and select entities, so you can slide between options, in the same style as the toggle for input booleans. This was @Jump-333’s very first contribution to Home Assistant. Thanks, and welcome!
• The Energy dashboard now shows the discharge of each battery separately in the energy usage graph, just like it already did for charging. Thanks, @MindFreeze!
• Calendar cards can show a button to add an event again, so you can put something on the calendar right from your dashboard, and you pick where the button sits. Thanks, @Phil0L!
• Lawn mower entities gained a stop action and an idle state, so you can cancel a mower’s current task instead of only pausing it or sending it home. The automation editor has a matching trigger and condition, too. MQTT lawn mowers support it as well, and Husqvarna Automower and Husqvarna Automower BLE mowers already report when they are idle. Thanks, @piitaya, @Thomas55555, and @alistair23!
• Binary sensor has a new glass break device class. Glass break sensors are treated as security sensors, so they show up on the Security dashboard and in your home security summary. HomematicIP Cloud, SimpliSafe, Z-Wave, and Hive already use it. Thanks, @catellie!
• Template got two nice additions this release. Thanks, @Petro31!
  • Template entities can now be climate entities, so you can build your own thermostat from other entities. Think of a heat pump or air conditioner that an integration only exposes as a loose collection of switches, sensors, and numbers. Create one as a helperA helper is a virtual entity you create inside Home Assistant. It is not backed by a physical device. Helpers store values, track state, or do calculations that your automations and dashboards need. [Learn more] from the UI, pick templatesA template is an automation definition that can include variables for the action or data from the trigger values. This allows automations to generate dynamic actions. [Learn more] for the current temperature, target temperature, and HVAC mode, and choose the actions that run when you change them. In YAMLYAML is a human-readable data serialization language. It is used to store and transmit data in a structured format. In Home Assistant, YAML is used for configuration, for example in the configuration.yaml or automations.yaml files. [Learn more], you can take it further with fan, preset, and swing modes, and humidity. The template climate documentation has all the details.
  • Binary sensor template helpers now let you set a delay before they turn on or off, right from the UI. Until now, that was only possible in YAMLYAML is a human-readable data serialization language. It is used to store and transmit data in a structured format. In Home Assistant, YAML is used for configuration, for example in the configuration.yaml or automations.yaml files. [Learn more].
• Templates gained a timedelta_string function, which turns a duration into readable text like “1 hour 30 minutes”, the same way time_since and time_until do. Thanks, @cnotin!
• Automation traces got a fresh look that matches the automation editor, with the real icon for each triggerA trigger is the part of an automation that makes the automation start when something specific happens, for example, when the sun sets, a door opens, or a button is pressed. [Learn more], conditionConditions check whether something is true at that moment, for example, whether a door is closed. You can use them in automations and scripts. If a condition is not met, the actions that come after it in the same sequence do not run. At the top level of an automation or script, this stops the automation or script. [Learn more], and actionAn action makes Home Assistant do something, for example, turn on a light, send a notification, or activate a scene. Automations and scripts run a list of actions. [Learn more], and a clear view of branches that didn’t finish. Drag the divider to give the graph or the details more room, the step buttons now float on top of the graph, and screen readers describe each step. Thanks, @jpbede!
• The Z-Wave network map can now show the real mesh. Turn on the new neighbors toggle, and it draws the connections between your devices, not just the routes they use. It’s off by default, because large networks get busy fast. Thanks, @MindFreeze!
• Calendar events from CalDAV, Local calendar, and Google Calendar now include whether they are confirmed or tentative, so your automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] can tell the difference. Remote calendar now also leaves out canceled events. Thanks, @1358!
• Climate fan modes can now be set by voice, through a conversation agent, like “set the fan mode to auto”. Thanks, @synesthesiam!
• Units keep growing: atmospheres (atm) for pressure, and therms (thm) for energy, the unit many US utilities bill natural gas in. Weather entities can now also report pressure in kilopascals (kPa), which most weather services in Canada use. Thanks, @Bre77, @virtitnerd, and @RussellAult!
• Password managers, including the one built into Firefox, can fill in your details on the Home Assistant login page again. Thanks, @MindFreeze!
• On phones with a notch or rounded corners, tables, filter bars, settings cards, headers, and pop-up messages now reach the edges of the screen, while everything you read or tap stays clear of the cutout. Thanks, @bgoncal!
• Tables, like the ones listing your devicesA device is a model representing a physical or logical unit that contains entities. and entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more], now show placeholder rows while they load. And if something fails to load, you now see an error, instead of an empty list that looks like you have nothing set up. Thanks, @timmo001!
• YAML configuration errors now suggest what you probably meant. Mistype command_topci, and the error asks: did you mean command_topic? Error messages also show the path to the file relative to your configuration folder, so they are easier to read. Thanks, @frenck and @emontnemery!

Show a card only when it matters

Dashboards can show or hide a card, badge, or section based on conditionsConditions check whether something is true at that moment, for example, whether a door is closed. You can use them in automations and scripts. If a condition is not met, the actions that come after it in the same sequence do not run. At the top level of an automation or script, this stops the automation or script. [Learn more]: only on a phone, only for a certain user, only when the washing machine is running. Those conditions were always a smaller set than the ones you know from automations.

This release, the Visibility tab offers the same conditions as the automation editor, including Template, Sun, Zone, and Device, and the conditions integrations bring along. They sit right next to the ones that only make sense on a dashboard, like Screen and User, and you can mix them freely. Show the garden lights card only after sunset, and only on a phone. Each row now also describes what it checks, just like in the automation editor, and you can drag the rows into a different order. Your existing visibility conditions keep working as they are.

And no more guessing why a card is hiding. The top of the Visibility tab tells you whether the card is visible right now, and each condition shows whether it currently passes. Thanks, @MindFreeze and @timmo001!

A panel for your Modbus connections

Last release, we started modernizing Modbus: integrations that already know how your device talks Modbus, so you pick your device in the UI instead of writing register maps by hand. Those integrations share a single connection to each device, which is great for devices that only accept a few connections at once. It also meant there was no single place to see which integrations were talking to what.

The new Modbus panel under Settings > Connectivity fixes that. It lists every Modbus connection Home Assistant has, serial ports and network gateways alike, along with the devicesA device is a model representing a physical or logical unit that contains entities. on it and the integrations using them. Connections set up in YAMLYAML is a human-readable data serialization language. It is used to store and transmit data in a structured format. In Home Assistant, YAML is used for configuration, for example in the configuration.yaml or automations.yaml files. [Learn more] show up here too. A connection that’s closed isn’t a problem, by the way. It opens again the next time an integration needs it. The Serial panel links straight to it for ports that carry Modbus. Thanks, @balloob!

The list of integrations built this way keeps growing. This release adds two new ones: SolarEdge Modbus, launching straight at platinum, and KACO Modbus, thanks to @g4bri3lDev. STIEBEL ELTRON now shares its connection through the Modbus integration as well, and Sofar climbed all the way to platinum, thanks to @darkrain-nl.

Connect your AI in one click

Home Assistant can act as a Model Context Protocol server, which lets AI apps like Claude, ChatGPT, or Cursor talk to your home. Getting there was a bit of a hunt, though: add the integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more], pick which parts of Home Assistant to expose, and then figure out which URL to hand to your AI app.

The AI tasks page under Settings > System is now called AI, and it gained a Model Context Protocol card. Turn the server on in a single click, and the card lists the URLs to paste into your AI app, each with a button to copy it. New setups expose everything Home Assistant has to offer, including anything added later, and only allow administrator accounts to connect. You can change both whenever you like, without removing and re-adding the integration.

It also works the other way around. Apps that run their own MCP server are now discovered automatically by the Model Context Protocol integration, so connecting Home Assistant to them only takes a confirmation.

And your AI got a lot better at finding music. Ask it to play something, and instead of blindly playing the first search result, it now gets a list of results and picks the best match. It can even search inside an artist, album, or playlist to find that one specific song. Search itself improved along the way: artists, albums, and playlists from Music Assistant can now be searched inside, just like results from Jellyfin and Squeezebox, local media now finds matching folders too, and Radio Browser puts the 100 most popular stations first.

Thanks, @balloob!

If your home runs on KNX, your AI can now dig into that too. The KNX integration brings its own set of AI tools, which you can hand to your conversation agent, or to your AI app through the Model Context Protocol server. Ask about the group addresses, devices, and functions in your ETS project, go through the history of telegrams on your bus, or decode a value you don’t recognize. It can even read and write values on the bus directly. Thanks, @martinhoefling!

Name an entity after its device

Some entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] are the whole point of their deviceA device is a model representing a physical or logical unit that contains entities.. Calling the smoke sensor of a smoke detector “Smoke detector Smoke detected” doesn’t help anyone. Integrations already give their main entity the name of the device, but if you wanted to do the same for another entity, there was no clean way to do it. If you cleared its name, it jumped right back to the name the integration gave it.

The entity settings now have a Use device name switch. Turn it on, and the entity goes by the name of its device. The switch also shows you what that device name is, with a link to rename the device if you’d like. Turn it off, and you’re back to the entity’s own name, filled in with the default from the integration. If you change your mind, a restore button takes you back to the default. Thanks, @piitaya and @matthiasdebaat!

Timers, one tap away

Timer helpersA helper is a virtual entity you create inside Home Assistant. It is not backed by a physical device. Helpers store values, track state, or do calculations that your automations and dashboards need. [Learn more] are now a lot easier to control from your dashboard. Tile cards have two new features for them: Timer actions adds buttons to start, pause, and cancel a timer (and optionally finish it), and Timer presets starts a timer with a preset duration in a single tap. Presets show up as a row of buttons, or as a dropdown, handy for a longer list. You manage the presets from the timer itself: open its more info dialog and select Edit presets from the menu.

That more info dialog got a fresh look too, and when a timer finishes, you’ll see a small animation. Thanks, @maartenla!

Patch releases

We will also release patch releases for Home Assistant 2026.10 in October. These patch releases only contain bug fixes. Our goal is to release a patch release once a week, aiming for Friday.

2026.10.1 - October 10

• Split Matter TemperatureOffset range by Thermostat ClusterRevision (@lboue - #180517)
• Bump pywaze to 1.2.4 (@eifinger - #184663)
• Bump pyicloud to 2.7.0 (@FezVrasta - #184728)
• Retry failed Analytics insights refresh (@chemelli74 - #184731)
• Fix WLED color modes not following a changed LED setup (@frenck - #184778)
• Bump dwdwfsapi to 1.1.0 (@frenck - #184784)
• Add description for the device selection field in the Qingping config… (@tengfeili-qingping - #184797)
• Send a result for the ZHA reconfigure websocket subscription (@frenck - #184812)
• Bump solaredge-web to 0.5.0 (@tronikos - #184821)
• Keep a missing meter history from blocking Peblar setup (@frenck - #184824)
• Fix KeyError in the Airly integration when the API payload contain no sensor data (@bieniu - #184828)
• Restore unverified TLS for stream sources and add a verify_ssl option (@RaHehl - #184877)
• Fix FRITZ!SmartHome SSDP discovery with hostname presentation URL (@mib1185 - #184896)
• Only create Bosch SHC child lock switch when ChildProtection exists (@mosandlt - #184908)
• Skip TLS verification for UniFi Protect RTSPS streams (@RaHehl - #184930)
• Return same images as you see on the immich server, even the edited ones (@mib1185 - #184955)
• Don’t report 0 for missing FRITZ!SmartHome powermeter values (@mib1185 - #184968)
• Reload Immich integration when the server version changes (@mib1185 - #184978)
• Set state to unknown in Husqvarna Automower error sensor, when error is unknown (@Thomas55555 - #185087)
• Seed deCONZ group color modes from unreachable lights too (@marcus13371337 - #185117)
• Bump ZHA to 2.3.1 (@TheJulianJES - #185156)
• Fix storing traces for automations without an ID (@Kevin-Tamayose - #185161)
• Tag TTS audio carrying an empty ID3 tag (@tronikos - #185193)
• Fix Tradfri color bulbs losing HS color mode (@frenck - #185197)
• Fix false shell template repair for static command_line commands (@frenck - #185203)
• Constrain graphql-core below 3.3 (@frenck - #185206)
• Do not link a trace that is not stored as a child (@Xyolyp - #185207)
• Fix Hue light crash when the bridge reports no color temperature (@frenck - #185218)
• Fix generic thermostat rechecking too late after a minimum cycle or cooldown (@frenck - #185221)
• Fix Signal Messenger notify failing to load when the REST API is down at startup (@frenck - #185225)
• Don’t create Nibe number entities for date coils (@frenck - #185229)
• Round LG Infrared target temperature instead of truncating it (@frenck - #185231)
• Log in to OmniLogic again after a failed update (@frenck - #185250)
• Remember silent SolarEdge Modbus blocks across setups (@tronikos - #185255)
• Update frontend to 20260930.3 (@bramkragten - #185285)
• Bump wled to 1.1.1 (@frenck - #185344)
• Keep deprecated device config entry attributes working in templates (@frenck - #185361)
• Bump modbus-connection to 4.12.4 (@balloob - #185419)
• Fix WLED adding Wi-Fi sensors to wired devices (@frenck - #185425)
• Add new error codes to Husqvarna Automower (@Thomas55555 - #185477)
• Fix Arve availability on failed updates (@erwindouna - #185494)
• Fix EZVIZ availability on failed updates (@erwindouna - #185497)
• Fix 17TRACK availability on failed updates (@erwindouna - #185501)
• Fix Starlink availability on failed updates (@erwindouna - #185502)
• Fix Subaru availability on failed updates (@erwindouna - #185503)
• Fix SUPLA availability on failed updates (@erwindouna - #185504)
• Fix TOLO availability on failed updates (@erwindouna - #185505)
• Fix Xbox availability on failed updates (@erwindouna - #185506)
• Fix Yardian availability on failed updates (@erwindouna - #185507)
• Give SolarEdge Modbus reads a 30 s timeout (@tronikos - #185518)
• Fix typo in Husqvarna Automower (@Thomas55555 - #185532)
• Revert “Resolve integration brand images before brand images” (@joostlek - #185535)
• Allow dynamic ports for registered loopback OAuth redirects (@balloobbot - #185544)
• Fix Matter get_lock_users stopping on a null nextUserIndex (@raman325 - #182808)
• Bump pyElectra to 1.2.5 in electrasmart (@noamokman - #184187)
• Bump python-kasa to 0.11.0.1 (@rytilahti - #184235)
• Remove user-configurable polling interval from omnilogic (@tr4nt0r - #184380)
• Fix Spotify coordinator crash when playing without an item (@kleinc80 - #184723)
• Bump aioautomower to 3.1.0 (@Thomas55555 - #184970)
• Don’t toggle the OpenEVSE manual override when it is already in the requested state (@frenck - #185257)
• Retry ViCare setup on transient API errors (@lackas - #185534)
• Show app name in MCP discovery flow title (@balloob - #185541)
• Ensure IMAP actions always close TCP stream (@robin-thoni - #185547)
• Bump tplink-omada-client to 1.5.13 (@rubempoli - #185585)
• Report an uncalibrated Shelly RPC cover by its last direction (@thecode - #185624)
• Bump reolink_aio to 0.21.18 (@starkillerOG - #185631)
• Preserve fractional transition times for TRÅDFRI lights (@addibbi - #185633)
• Bump tailscale to 1.0.0 (@frenck - #185639)
• Patch the PyViCare client instead of integration setup in ViCare tests (@lackas - #184730)

2026.10.2 - October 16

• Fix IndexError on out-of-range heater levels in Tesla Fleet (@sebr - #178049)
• Deduplicate sleepers within a single SleepIQ bed (@derekcentrico - #181461)
• Handle Enphase envoy Session is Closed in background tasks (@catsmanac - #183172)
• Treat MPD protocol errors as a connection failure (@mattias-arrelid - #184481)
• Bump py-opendisplay to 7.18.1 (@g4bri3lDev - #184911)
• Bump aiotankerkoenig to 0.5.5 (@mib1185 - #185714)
• Tankerkoenig handle api errors config flow (@mib1185 - #185719)
• Handle Gemini generation parameters and complete WAV TTS responses (@oohhddaanngg - #185723)
• Fix SmartTub error sensor reporting stale historical errors (@mdz - #185726)
• Bump aiohttp to 3.14.5 (@bdraco - #185746)
• Mark Aquacell sensors unavailable when data is stale (@alexborro - #185762)
• Bump aionanoleaf2 to 1.0.5 (@feixm1 - #185777)
• Bump my-pv to 0.0.13 (@rrooggiieerr - #185797)
• Catch TimeoutError in the Nettigo Air Monitor integration (@bieniu - #185812)
• Ignore devices without TR-064 support during FRITZ!Box Tools SSDP discovery (@mib1185 - #185816)
• Bump arcam-fmj to 3.0.1 (@elupus - #185887)
• Handle Alexa RequireRelink on cloud entity registry updates (@balloob - #185894)
• Redact schedule coordinates in Teslemetry and Tesla Fleet diagnostics (@Bre77 - #185905)
• Report a dedicated error when the Tedee bridge has no locks (@zweckj - #185907)
• Prevent WiiM browse failures from marking devices unavailable (@Linkplay2020 - #185926)
• Fix group sensor crash when the group has no members (@joostlek - #185931)
• Do not cut off KNX SQLite telegram store initialization with a timeout (@farmio - #185940)
• Bump nyt_games to 1.0.1 (@joostlek - #185968)
• Gate Nanoleaf event listener on supports_events (@loebi-ch - #185977)
• Fix MQTT device triggers and tags firing twice after reload (@klejejs - #185998)
• Fix FRITZ!SmartHome SSDP host selection (@mib1185 - #186029)
• switch Broadlink to broadlink-async (fixes #184800, replaces #184806) (@DAB-LABS - #186053)
• Fix weatherflow last_reset updating on every device report (@jeeftor - #186141)
• Bump weatherflow4py to 1.5.12 (@jeeftor - #186142)
• Bump intellifire4py to 4.5.6 (@jeeftor - #186143)
• Fix scrape subentry reconfigure flow not finishing (@joostlek - #186144)
• pin pycares to 5.0.1 (@aclerici38 - #186164)
• Allow a list of states for state conditions with a duration (@emontnemery - #186165)
• Bump airthings-ble to 1.3.1 (@LaStrada - #186387)
• Guard owner and existing credentials in auth provider create command (@zweckj - #186398)
• Fetch missing Renault vehicle details (@epenet - #186402)
• Fix Discogs random record sensor when release has no format description (@cerealkiller57540 - #186405)
• Fix permissions validation for ProxmoxVE (@CoMPaTech - #186420)
• Hide MELCloud Home swing modes on units without vanes (@erwindouna - #186468)
• Fix modbus reload without YAML config (@joyjit - #186554)
• Revoke refresh tokens when removing a user (@frenck - #186558)
• Redact credentials and host in SFR Box diagnostics (@epenet - #186668)
• Fix SolarEdge module statistics sum resetting after a gap (@tronikos - #186753)
• Bump deebot-client to 18.7.0 (@edenhaus - #186779)
• Redact identifying data in NRGkick diagnostics (@andijakl - #186781)
• Persist Ecovacs account credentials to avoid device verification (@erwindouna - #186796)
• Update frontend to 20260930.4 (@bramkragten - #186813)
• Fix Fritz setup failing when UPnP info lacks NewEnable key (@mib1185 - #186896)
• Bump aiomelcloudhome to 0.3.0 (@erwindouna - #185769)
• Pin pypasser below 1.0.0 (@erwindouna - #186527)

Need help? Join the community

Home Assistant has a great community of users who are all more than willing to help each other out. So, join us!

Our very active Discord chat server is an excellent place to be, and don’t forget to join our amazing forums.

Found a bug or issue? Please report it in our issue tracker to get it fixed! Or check our help page for guidance on more places you can go.

Are you more into email? Sign up for the Open Home Foundation Newsletter to get the latest news about features, things happening in our community, and other projects that support the Open Home straight into your inbox.

Backward-incompatible changes

We do our best to avoid making changes to existing functionality that might unexpectedly impact your Home Assistant installation. Unfortunately, sometimes it is inevitable.

We always make sure to document these changes to make the transition as easy as possible for you. This release has the following backward-incompatible changes:

homeassistant:
  allowlist_external_dirs:
    - /media/telegram

If you are a custom integration developer and want to learn about changes and new features available for your integration: Be sure to follow our developer blog. The following changes are the most notable for this release:

• DeviceEntry.config_entries deprecation is now enforced
• Deprecating modbus.get_hub in favor of async_get_unit
• LLM tools return a ToolResult and declare their integration
• New device and state class selectors
• New stop action and idle activity for lawn mowers
• OAuth2 error handling moved into the helper
• Probatio is our validation engine
• Shared config flow abort reasons are translated centrally
• Use Config Entry exceptions in integration migration method

All changes

Of course, there is a lot more in this release. You can find a list of all changes made here: Full changelog for Home Assistant Core 2026.10.

• Assassin's Creed Shadows may crash to desktop after extended gameplay after updating to driver 616.56 [6685219]

• N/A

From ever-increasing subscription prices to outages and data harvesting: we don’t like what the cloud has come to represent. So we’re redefining what an online service should be: private, optional, and free from lock-in or walled gardens.

That’s why today Nabu Casa is renaming Home Assistant Cloud to more accurately describe what the service actually does, and to better reflect our values. Allow us to introduce:

Home Assistant Link

I’m Carl, Vice President of Commercial at Nabu Casa. You probably know us as the folks making all that sleek, highly optimized Home Assistant hardware. Beyond hardware, we also manage and run Home Assistant Link, and as one of the Open Home Foundation’s commercial partners, we’re here to help fund all their amazing work. We feel pretty passionately about the word cloud, and we’d love to explain how the old name never fit, and why Link finally does.

Created for the community

Home Assistant began with a group of core developers working nights and weekends alongside their regular jobs to create the platform – a good recipe for burnout, and one that has ended plenty of similar open source projects. So in 2018, we founded Nabu Casa and created Home Assistant Cloud to make sure that didn’t happen.

Home Assistant Cloud set out to make Home Assistant easier for more people to use, starting with a problem many of you had: reaching your Home Assistant when you’re not at home, without having to spend a weekend on it. It was also built to make Home Assistant’s development sustainable.

The intent was never to just ask for donations, but to build an optional service that benefited the community and funded the work at the same time. The majority of profits from subscriptions now fund the Open Home Foundation. That money supports everyone working on Home Assistant – from salaried staff to volunteers – keeping the project sustainable. That shift took Home Assistant from a passion project to one that could invest back into its community, and one that could stick around for the long haul.

A breath of fresh air

We even took it out of the Nabu Casa logo… did we take this too far? 🤔

We had a service that we and the community loved, but the name just didn’t feel right. For example, there were times when Paulus, founder of Home Assistant and President of the Open Home Foundation, was on stage saying “don’t buy products that require the cloud to work,” then in the next breath having to explain how Home Assistant Cloud is different, despite the name. That created unnecessary friction.

It also caused confusion, since some new users thought (and continue to think) Home Assistant Cloud is a way to run Home Assistant in the cloud. This has never been the case, because we believe Home Assistant should always be run locally, in your home.

Big Tech has given the cloud a bad name, and while Link does run online, it is very different from other cloud-powered smart home services:

Your subscriptions help sustain Home Assistant, but we’ve been clear from the beginning that you do not need Link to use the platform. We hate what Big Tech has done to smart devices, turning them into paperweights when they drop support. Thermostats that can’t be scheduled or cameras that can’t detect motion, giving the smart home a bad reputation and making a mountain of e-waste. By not using Link, you’ll miss out on some extras, but that’s all they are: extras. And if you do use Link but have to unsubscribe, your smart home will keep working.

Big Tech treats your data as a commodity and a tool for mass surveillance: sold to advertisers, used to train AI, and dealt to third parties for the best price. We think this is morally bankrupt. That’s why when you use Home Assistant Link, your data is encrypted, and only you have the key. Neither Nabu Casa nor the Open Home Foundation want your data, and we work hard to never have an opportunity to see it.

This is what tech serving people looks like: data that’s yours, and a smart home that answers to you – not corporate shareholders.

Choose your own path

Many of you build DIY projects to customize your setup, and Home Assistant isn’t going anywhere on that front. But for those who’d like a simpler approach, Link makes using Home Assistant easier, opening up the local and private smart home to more people. For example, connecting to Alexa and Google Home can be complex to set up yourself, but Link allows you to… ahem… link them to Home Assistant without the hassle. Not having the time or know-how shouldn’t be a barrier to using the platform, and Link ensures it isn’t.

On top of things that can only be done online, there are other features that just work better with Link’s connected services. For instance, online speech-to-text tends to be faster, supports more languages, and is more reliable than self-hosted alternatives. Likewise, Link offers a way to store a backup online, so your data is always recoverable while remaining private. Plus, if you run into trouble with a feature, we have real humans you can contact to help you out. You heard that right. A real person.

See everything at a glance on our new account page.

We’re also constantly improving the service and are now working to add new features. You may have noticed the new, easier-to-use account page, the speech-to-text Labs test, or the new settings page in Home Assistant with a setup wizard. What you probably won’t notice is the massive backend update to improve the responsiveness of your remote access (we’ve migrated to a new bare-metal setup that always tries to get you on the closest server, and it’s fast 🏎️). Most importantly, these updates let us add new security features, account management tools, and more.

What’s in a name?

In the end, our actions speak louder than product names, and we’ll continue to run a subscription that’s about privacy, transparency, and not locking users in, all the while supporting the development of Home Assistant.

Whenever features get renamed, we always come to you, the community, first. Even though this is a service from Nabu Casa, Home Assistant is a community project, and we value your opinion and thoughts. Love the new name? Something we didn’t consider? We’re all ears. We intend to make the name change official in the December 2026.12 release, so please provide all your feedback well before then! 👇

What's Changed

• fix(macos): press Back and Forward as the frontmost app's menu item by @AprilNEA in #1622
• chore(nix): update flake.lock by @AprilNEA[bot] in #1217
• fix(agent): recognize an overlay tenant by any image we ever shipped by @AprilNEA in #871
• feat(linux): add verified release installer by @AprilNEA in #1109
• ci(nix): only run Nix CI on flake and packaging changes by @davidbudnick in #1250
• fix(macos): confirm desktop switches with private space APIs by @AprilNEA in #1586
• fix(macos): drive the device-I/O gate from powerd instead of workspace notifications by @AprilNEA in #1323
• fix(core): match Actions Ring layouts with the per-app selector by @AprilNEA in #643
• chore: release v0.8.11 by @AprilNEA[bot] in #1637
• fix: clear the lints rustc 1.99 raises on untouched code by @AprilNEA in #1638
• chore: release v0.8.11 by @AprilNEA in #1643
• chore: release v0.8.11 by @AprilNEA in #1644

Full Changelog: v0.8.10...v0.8.11

What's Changed

• feat(keyboard): key controls by HID++ control ID, fix Keys tab and Fn-lock by @AprilNEA in #1604
• fix(macos): keep the hook from hearing the keys OpenLogi posts by @AprilNEA in #1618
• fix(gui): unpair a forgotten receiver device so it stays deleted by @AprilNEA in #1617
• fix(macos): press shortcut keys where the active layout types them by @guslipkin in #948
• feat(core): add a Super modifier and make Win/Meta name it by @sungyongcho in #1387
• fix(agent): re-arm a crash respawn instead of going dormant by @AprilNEA in #1619
• fix(hook): give the macOS tap's capability probes their own watchdog budget by @hyspacex in #1282
• fix(hook): give the callback watchdog the same watched-time rule by @AprilNEA in #1624
• chore: release v0.8.10 by @AprilNEA[bot] in #1616

New Contributors

• @guslipkin made their first contribution in #948
• @hyspacex made their first contribution in #1282

Full Changelog: v0.8.9...v0.8.10

What's Changed

• fix(gui): swap the thumb-wheel volume preset labels onto the pairing they describe by @4ni1ak in #1436
• fix(hook): stop the GNOME frontmost observer leaking a socket per renewal by @sungyongcho in #1418
• fix(gui): rebuild the agent's launchd registration when its job is gone by @raphaeljostan in #1303
• fix(hook): hit-test the window under the pointer through AppKit by @pseudoseed in #1568
• chore: release v0.8.9 by @AprilNEA[bot] in #1599

New Contributors

• @sungyongcho made their first contribution in #1418
• @raphaeljostan made their first contribution in #1303

Full Changelog: v0.8.8...v0.8.9

What's Changed

• feat(hid): recognise Nano receiver 046d:c534 (MK270, MK295) by @4ni1ak in #1456
• fix(agent): divert a single-bound gesture button by @pseudoseed in #1569
• fix(gui): restore per-app profile removal and add reset controls by @AprilNEA in #1580
• fix(gui): prefer firmware codename over catalog name for M650 variants by @4ni1ak in #1366
• refactor(gui): simplify variant name correction ownership by @AprilNEA in #1585
• chore: release v0.8.8 by @AprilNEA[bot] in #1573

New Contributors

• @pseudoseed made their first contribution in #1569

Full Changelog: v0.8.7...v0.8.8

What's Changed

• feat(agent): follow pointer for mouse button profiles by default by @AprilNEA in #1566
• chore: release v0.8.7 by @AprilNEA[bot] in #1567

Full Changelog: v0.8.6...v0.8.7

• Judgement/Lost Judgement/ Virtua Fighter 5 R.E.V.O. may fail to launch after updating to driver 616.56 [6681537]

• No picture on Samsung Odyssey G95NC monitor when connected via HDMI after updating to R615 drivers [6771206]
• Certain monitors may not wake from sleep when connected via DisplayPort after updating to R615 drivers [6757568]

What's Changed

• refactor(gui): split app_icon around an AppIconExt trait by @AprilNEA in #1422
• fix(gui): hold a config reload until the agent connects by @AprilNEA in #1416
• refactor(ipc): own the client handshake once and guard it with ast-grep by @AprilNEA in #1424
• refactor(core): name the process roles, host profiles, and environment knobs once by @AprilNEA in #1426
• refactor(ipc,cli): bound the handshake once and give the CLI one agent door by @AprilNEA in #1427
• refactor(core): build every worker runtime in one place by @AprilNEA in #1428
• refactor(core): spell the app bundle's layout once by @AprilNEA in #1429
• docs(infra): add openlogi workflow skills by @AprilNEA in #1409
• docs(infra): refine agent guidance and diagnostic workflows by @AprilNEA in #1485
• refactor(cli): give the command modules that carry code a file of their own by @AprilNEA in #1494
• refactor(hidpp): split the pending-request queue and the mock channel out of channel.rs by @AprilNEA in #1495
• refactor(hook): split the macOS backend by responsibility by @AprilNEA in #1496
• refactor(hook): split the Linux backend into the evdev hook and the foreground watcher by @AprilNEA in #1497
• chore: drop an unused dependency, a dead parameter, and stale docs by @AprilNEA in #1487
• refactor(gui): let state mutators own their events and views share one relevance filter by @AprilNEA in #1505
• refactor(gui): give write-on-release sliders one component by @AprilNEA in #1506
• refactor(ipc): own the observe loop's connection state in one Observer by @AprilNEA in #1507
• perf(gui): resolve each device's assets once per asset generation by @AprilNEA in #1508
• refactor(gui): say what the state types are by @AprilNEA in #1509
• refactor(core): give the key vocabulary one owner by @AprilNEA in #1488
• refactor(core): give seven copied decisions one owner each by @AprilNEA in #1489
• refactor(xtask): spell xtask's waits and its bundle builder in the workspace's vocabulary by @AprilNEA in #1490
• ci(windows): run the tests on Windows by @AprilNEA in #1491
• refactor(device): drop the capture paths nothing calls and type the session errors by @AprilNEA in #1500
• refactor(core): split the config module by concern by @AprilNEA in #1511
• refactor(device): split the inventory and probe modules by responsibility by @AprilNEA in #1512
• refactor(device): call durations that bound a wait timeouts by @AprilNEA in #1513
• refactor(device): run gesture and keyboard capture through one session skeleton by @AprilNEA in #1501
• refactor(device): share one pending-restore token between capture and host switch by @AprilNEA in #1502
• refactor(agent): run the capture watchers on one harness and name the device-access handles by @AprilNEA in #1503
• refactor: say what eight identifiers are by @AprilNEA in #1517
• refactor(camera): suffix the macOS backends like the other platforms' by @AprilNEA in #1518
• refactor(gui): move the F-key geometry into function_row/key_points.rs by @AprilNEA in #1525
• refactor(agent): move the device list and re-apply plan into orchestrator/devices.rs by @AprilNEA in #1526
• refactor(gui): split the AppState tests by what they exercise by @AprilNEA in #1527
• refactor(inject): run scripts and workflows once, over four platform hooks by @AprilNEA in #1529
• refactor(core): split the config tests by what they exercise by @AprilNEA in #1530
• refactor(device): split the inventory and gesture capture tests by what they exercise by @AprilNEA in #1531
• refactor(agent): split the orchestrator tests by what they exercise by @AprilNEA in #1532
• refactor(hidpp): split the channel tests by what they exercise by @AprilNEA in #1533
• refactor(device): move the host-switch session's tests to host_switch/tests.rs by @AprilNEA in #1535
• refactor(agent): move the button runtime's worker loop into button/worker.rs by @AprilNEA in #1536
• refactor(inject): break the macOS injector into scroll, browser and SPI modules by @AprilNEA in #1537
• refactor(gui): move the mouse view's binding labels and tests out of view.rs by @AprilNEA in #1538
• refactor(gui): move the camera panel's row builders into controls/rows.rs by @AprilNEA in #1539
• feat(gui): detect and display installation sources by @AprilNEA in #1515
• docs(gui): mend the desktop crate's intra-doc links by @AprilNEA in #1541
• chore: release v0.8.6 by @AprilNEA[bot] in #1481

Full Changelog: v0.8.5...v0.8.6

What's Changed

• fix(gui): resolve depot metadata named only by the manifest by @4ni1ak in #836
• docs(gui): adopt upstream gpui kit skills by @AprilNEA in #1400
• fix(linux): keep the generated systemd unit out of the user's tier by @AalmanSadath in #796
• fix(hidpp): stop HID++ replies landing on the wrong request by @isleofgreg in #1286
• feat(gui): enable supported button gestures by @juan-apa in #1167
• fix(gui): restore stacked card layout under gpui-kit 0.6 by @AprilNEA in #1408
• chore: release v0.8.5 by @AprilNEA[bot] in #1399

Full Changelog: v0.8.4...v0.8.5

What's Changed

• feat(i18n): migrate catalogs to semantic TOML keys by @AprilNEA in #1169
• perf(i18n): avoid copying borrowed translations by @AprilNEA in #1184
• fix(i18n): polish supported locale copy by @AprilNEA in #1180
• fix(i18n): localize DPI steps and correct count labels by @AprilNEA in #1292
• fix(i18n): polish Brazilian Portuguese profile and settings copy by @uricholiveira in #1276
• fix(i18n): refine French asset and control descriptions by @didlawowo in #1278
• fix(hid): keep pairing phase after device selection by @AprilNEA in #1181
• refactor(gui): model camera preview lifecycle states by @AprilNEA in #1182
• refactor(agent): consolidate capture manager slots by @AprilNEA in #1183
• docs(linux): fix the Debian install command and the bug form's platform note by @AalmanSadath in #791
• docs: add Russian README translation by @MonteNegroX in #1039
• Fix typo in installation guide by @mikevankuik in #1189
• fix(i18n): correct mistranslations in the Spanish catalog by @eibidia in #1315
• feat(i18n): Updated French README.md file by @DimitriDR in #1271
• fix: add Debian runtime dependencies by @MauricioSilv in #1249
• fix(hook): normalize Windows cursor position to DIP scale by @fly530 in #1246
• fix(agent): restore diverted HID++ controls on a clean shutdown by @4ni1ak in #1106
• refactor(hook): type windows cursor dpi normalization by @AprilNEA in #1318
• fix(linux): declare F13-F20 in uinput key capabilities by @costantinoai in #1224
• fix(core): stop seeding Back/Forward with a divertable default by @litityum in #1225
• fix(agent): fence queued pairing discovery after selection by @AprilNEA in #1320
• fix(agent): avoid capture recovery deadline busy loops by @AprilNEA in #1321
• test(gui): cover camera preview lifecycle by @AprilNEA in #1322
• fix(gui): place Windows actions ring correctly across mixed-DPI monitors by @AprilNEA in #1319
• fix(gui): stop linking SMAppServiceErrorDomain so macOS 13 and 14 can launch by @AprilNEA in #1324
• feat(hid): add hardware-aware mock device record and replay by @AprilNEA in #1165
• test(agent): cover native and browser side-button profiles by @AprilNEA in #1325
• fix(macos): bind Safari navigation to press-time process by @foleykyle01 in #1082
• fix(camera): surface startup failures and retry preview by @yuzi-co in #1069
• chore(gui): upgrade to gpui kit 0.6.1 and published pre adapters by @AprilNEA in #1338
• feat(hid): add rgb-effects lighting and receiver routing by @LuisUrrutia in #351
• fix(gui): keep update consent buttons visible by @AprilNEA in #1398
• fix(linux): preserve gesture capture across receiver probes by @yvvlee in #1043
• chore: release v0.8.4 by @AprilNEA[bot] in #1179

New Contributors

• @uricholiveira made their first contribution in #1276
• @didlawowo made their first contribution in #1278
• @AalmanSadath made their first contribution in #791
• @MonteNegroX made their first contribution in #1039
• @mikevankuik made their first contribution in #1189
• @eibidia made their first contribution in #1315
• @DimitriDR made their first contribution in #1271
• @MauricioSilv made their first contribution in #1249
• @fly530 made their first contribution in #1246
• @costantinoai made their first contribution in #1224
• @litityum made their first contribution in #1225
• @foleykyle01 made their first contribution in #1082
• @LuisUrrutia made their first contribution in #351
• @yvvlee made their first contribution in #1043

Full Changelog: v0.8.3...v0.8.4

• N/A

• Intermittent flicker may be observed in browsers when navigating to certain websites [6673430]
• Fixed an issue where virtual displays could not be created after updating to driver 616.56 [6674464]
• Remote Desktop Protocol (RDP) sessions may display a black screen after updating to driver 616.56 [6687328]

• N/A

• N/A