Log in.eml files via folder right-click menubgcolor containersshareWith explicitly so calendar/address book shares survive a re-login (#257)
In today's blog, we bring you a glimpse at some of the custom depots featured in the upcoming Iceland map expansion, which is currently in development for Euro Truck Simulator 2. So let's take a look at what our map designers are working on!
The largest one is a landmark depot of a silicon metal factory, which is an accurate 1:1 copy of the real-world facility found in this location. This will be the home of a new virtual company called Kísilverksmiðja, producing silicon metal, which is used in a wide variety of applications in the chemical industry, production of silicones and silanes, or high-strength aluminium alloys for the automotive industry.
Truckers will be able to drive to nearly every corner of the complex and load or unload their truck in various locations within the complex based on the type of cargo they are hauling. The depot will also feature dynamic cargo loading of logs, which play a key role in this industry. The entire location is positioned near the coast, so in addition to the tunnel connecting the depot and the city, drivers will also get to enjoy some beautiful views of the sea.
Then, you will find three custom-made quarries located in the towns of Selfoss, Patreksfjörður, and Blönduós. Quarrying of aggregate materials, both rock and sediment, is an important industry in Iceland, since aggregates are needed for a wide range of building and road construction projects.
All of these quarries are branches of the well-established MS Stein company that truckers can already know. Set within Iceland's iconic landscapes, these unique depots offer striking surroundings: the first two lie at the foot of towering cliffs, with the second one also boasting sweeping views of the sea.
Truckers will also come across six custom farm depots, each reflecting the characteristic Icelandic rural way of life. These are usually smaller, family-owned homesteads, often situated at the foot of mountains and shaped by the surrounding landscape. Their architecture is adapted to Iceland's demanding climate, using practical materials such as concrete and corrugated metal.
On these farms, you will often see livestock typical of the region, particularly Icelandic sheep and cattle. Some, like those in Þórshöfn and near Reykjavík, are tucked into the landscape, while others are located right beside the road.
With these farms, our map designers tried to convey the narrow Icelandic roads, deep valleys, charcoal-colored rocks and soil, and farmsteads appearing as clusters of modest farm buildings nestled against the base of rugged mountains. Beyond them, you will see just vast stretches of land that extend far into the rocky highlands, with roaming sheep.
And that's all for today! If we got you excited about this map expansion, don't forget to support us by adding the Iceland DLC to your Steam wishlist.
Remember to give our X/Twitter, Instagram, Facebook, Bluesky, and TikTok a follow as you'll receive updates about our games straight to your feed, or subscribe to our newsletter to stay informed! Until next time, keep on trucking.
Fixed an issue where websites on internal or corporate networks that require a login prompt would show a blank page. (Bug 2034752)
Fixed an issue that prevented highlighting from working on scanned images in the built-in PDF viewer. (Bug 2034980)
Fixed an issue where the "New" badge persisted on Split View menu items. (Bug 2027793)
Fixed an issue that prevented some webcams from working correctly in video calls. (Bug 2034722)
Fixed an issue where a tab would crash when dragging and dropping nested folders onto a webpage. (Bug 2030461)
Improved how Firefox displays websites with advanced 3D effects, fixing cases where parts of the page could disappear or appear incorrectly. (Bug 2034283)
Fixed an issue that could prevent Firefox’s local backup feature from completing successfully. (Bug 2029240)
Fixed an issue where the status and navigation bars would flicker or show mismatched colors when editing a page’s address. (Bug 2021596)
Improved the appearance of search suggestions in the address bar by preventing icons from appearing stretched or distorted. (Bug 2035353)
Various security fixes.
Reference link to 150.0.1 release notes.
src/ bundling via esbuildhttp:fetch permission and httpOrigins manifest fieldonBeforeEmailSend hook with fromEmail exposed on OutgoingEmailEmailReadView for the email-banner slot and expose auth resultsPLUGIN_DEV_DIR plugins in admin config routecreatePluginAPI fetch optionssettingsSchema<object> with blob: in object-src CSP (#253)activeAccountId from authStore in account selectors
Home Assistant 2026.5! 🎉
What a few weeks it has been! Earlier this month, we hosted State of the Open Home 2026 live in Utrecht, the Netherlands. A big chunk of that day was dedicated to something we deeply care about: building in the open, and how we’re going to take that even further from here on out. 💙
Building in the open isn’t just about source code on GitHub. It’s about doing the planning, the decision-making, and the prioritizing out where everyone can see it, follow along, and join in. And “joining in” doesn’t mean you have to write a single line of code or even consider yourself technical. Sharing how you use Home Assistant, telling us what frustrates you, what you wish existed, voting on ideas, helping a fellow user on the forums or Discord, translating, writing documentation, or simply leaving a thoughtful comment on a roadmap item: it all counts, and it all shapes where this project goes next. 🤝
A great first step in that direction also went live this month: our roadmap is now public. You can go browse it, see what we’re working on, what’s next, and (most importantly) comment on it, share your thoughts, and help shape it. We talked about all of this, and a lot more, on stage. So if you weren’t able to join us live, please go watch the recording. It is genuinely worth your time, and it’s the best invitation I can give you to come build the Open Home with us. 🗺️
Now, on to this release. My personal favorite this month is maybe a bit unexpected, considering it sits all the way at the end of this post: the completely reworked templating documentation. I know, I know, “documentation” doesn’t exactly scream headline feature. But hear me out: making Home Assistant more approachable is one of our biggest missions this year, and darn good documentation is a big part of that. We’ve expanded our documentation team and are investing heavily in this, and the new templating docs are the very first taste of what’s to come. I’m really proud of where this is heading. 📚
That said, I’d be lying if I said I wasn’t also super stoked about radio frequency (RF) support landing this release. Just like last month’s infrared (IR) release, this brings a massive category of devices into Home Assistant natively: blinds, garage doors, ceiling fans, RF outlets, doorbells… you name it. Sure, there have always been clever workarounds and custom integrations to bridge some of these, but having it built right into the platform changes the game completely. There is so much cool stuff going on around this, and we’re only getting started. 📡
And there’s plenty more: a new Maintenance dashboard for your batteries, serial ports proxied over the network with ESPHome, new tile card features for media players, durations for purpose-specific automation triggers and conditions, redesigned more-info dialogs for vacuums and lawn mowers, autocomplete in the code editors, and 12 new integrations! 🚀
Enjoy the release!
../Frenck
A huge thank you to all the contributors who made this release possible! And a special shout-out to @piitaya who helped write the release notes this release. Also, @RaHehl, @balloob, @Tommatheussen, and @mib1185 for putting effort into improving its contents. Thanks to them, these release notes are in great shape. ❤️
Last release, we welcomed infrared as a first-class citizen of Home Assistant, opening the door to all those TVs, air conditioners, and other appliances still controlled by their little IR remote. This release continues that story with another old-school protocol: radio frequency (RF). 📡
Think about all the RF-controlled devices already living in your home: motorized blinds and curtains, garage door openers, ceiling fans, wireless wall switches, RF outlets, doorbells, and yes, those holiday string lights. Most of them haven’t had a great way into your smart home, because they don’t speak Wi-Fi, Bluetooth, Zigbee, Z-Wave, or Matter. They speak RF, and only RF. There have always been workarounds and custom integrations to bridge some of them, but with this release, Home Assistant speaks RF natively.
The new Radio frequency integration follows the exact same pattern as last release’s infrared platform. It’s an entity type that represents an RF transmitter, like an ESPHome-powered device with a sub-GHz transmitter attached. You don’t set it up directly. Instead, other integrations use it to send RF commands on your behalf, and you simply pick which transmitter they should use.
Two transmitter integrations support this from day one:
On the other side, device-specific integrations use the platform to actually do something useful. Two are shipping in this release:
Like infrared, this is about more than a single new feature. A large chunk of perfectly good RF-controlled hardware out there has no smart home story at all. By giving Home Assistant a standard way to talk to RF devices, every new consumer integration built on top instantly works with every transmitter integration. Add a new ESPHome RF proxy somewhere in the house, and your blinds, your fan, and your string lights all just work. ✨
This is a great fit with the values of the Open Home Foundation, and especially sustainability. 🌱 Instead of throwing out a working motorized blind because it’s “dumb”, you can integrate it. Instead of replacing your RF outlets with new Wi-Fi ones, you can keep using them. It’s another way to extend the life of devices you already own, and to reduce electronic waste. ♻️
You may have caught a glimpse of where this is heading at the State of the Open Home 2026. Nabu Casa is a commercial partner of the Open Home Foundation, running Home Assistant Cloud and producing devices like the Home Assistant Green and the Home Assistant Voice Preview Edition. They’ve been working on a new device, currently going by the codename Project Blast, that brings infrared and radio frequency capabilities together in a single, polished package. The new Radio frequency platform in this release is part of the foundation that makes products like that possible. Stay tuned. 👀
If this tickles your interest, watch Carl from Nabu Casa explain what’s coming in this segment of the State of the Open Home 2026. 📺
We’re excited to see where the community takes this. The Radio frequency platform is designed to grow: more transmitter integrations, more device integrations, and more protocols over time.
This work is part of an Open Home Foundation roadmap opportunity to make radio frequency a first-class citizen of Home Assistant. Mission accomplished. 🎉
We have a bit of a theme going on. Last release, infrared became a first-class citizen of Home Assistant. This release, radio frequency joined the party. And now, there’s another way you can put an ESPHome device somewhere in your home and let Home Assistant talk to things through it: serial ports. 🔌
If you’ve ever set up a Bluetooth proxy, the idea will feel familiar. Plenty of smart home gear talks over a serial connection, like energy meters with a P1 port, or that classic Denon receiver with the new Denon RS-232 integration shipping in this release. Until now, the device producing those serial signals had to be physically plugged into the same machine running Home Assistant, or wired up over a long, unwieldy cable. Not anymore. ✨
With the new serial proxy support in ESPHome, any serial port plugged into (or built into) an ESPHome device can now be exposed over your network and used by Home Assistant as if it were sitting right next to it. Drop an ESP somewhere convenient, plug your serial device into it, and Home Assistant takes care of the rest. 🪄
This is great news if you’ve ever struggled to put a serial-connected device exactly where you wanted it. A few practical examples:
Like our existing Bluetooth, infrared, and radio frequency proxies, this is also a sustainability win. ♻️ Instead of replacing perfectly good serial-only equipment with newer Wi-Fi versions, you can keep using what you already have. That energy meter, that older AV receiver, that industrial sensor: they all just work, over the network. 🌱
Behind the scenes, this release rewires Home Assistant’s serial-port handling top to bottom to make serial proxies a natural part of the system. Some highlights for the curious:
pyserial library that Home Assistant has used for years. It’s designed for the way Home Assistant works today and adds support for new connection types, including ESPHome serial proxies, transparently.If you’re an integration developer (or maintain a custom component) talking over serial, head over to the migrating from pyserial to serialx developer blog post to read all about how to take advantage of this. 🛠️
Let’s be upfront about one thing: getting a serial proxy up and running today is not a one-tap experience yet. To use this in your home, you’ll need to build your own ESPHome device with the serial_proxy component configured for the UART your serial device is wired to. That means writing an ESPHome YAML configuration, flashing the firmware, and connecting the hardware. It’s very doable, but it is on the technical side. 🤓
We think that’s okay, because this release is the foundational milestone that makes everything else possible. The plumbing is now in place across Home Assistant, ESPHome, and the integrations that need it. From here, we (and the broader community) can build on top of this with friendlier setup flows, ready-made hardware, and pre-built ESPHome configurations. Just like Bluetooth and infrared proxies before it, the experience will get more approachable release after release. 🚀
This work is part of an Open Home Foundation roadmap opportunity to make serial proxying a first-class citizen of Home Assistant. Another roadmap milestone, checked off the list. ✅
Over the past few releases, Home Assistant has been quietly growing a family of built-in dashboards that you don’t have to build yourself. It started with the Home dashboard back in 2025.9, and grew with dedicated Lights, Climate, and Security dashboards in 2025.11. This release adds a new one and upgrades an existing one. 🏠
Keeping your smart home running smoothly is a side of home automation that doesn’t always get the spotlight. We’ve all been there: that motion sensor in the hallway that suddenly stops triggering the lights one evening, only to discover days later that its battery had died. 🪫 Wouldn’t it be nice to spot that before it becomes a problem? The new built-in Maintenance dashboard gives questions like that a home of their own. 🧰
The dashboard focuses on what is probably the most-requested view of all: your batteries. It automatically discovers every battery entityAn 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 your home and lays them out grouped by area, with low ones highlighted so you can spot the ones that need swapping at a glance. No more digging through entity lists or building your own dashboard for it. 🔋
This is a community contribution from @Brookke, who built it from the ground up. Big thanks for adding such a useful new dashboard to Home Assistant! 👏
Tip
Are you a developer? Each one of these built-in dashboards is powered by a dashboard strategy: a piece of code that generates a complete dashboard on the fly, tailored to your home. Starting with this release, you can register your own custom dashboard strategies from a custom integration or frontend module, and share them with the community.
Imagine a strategy that builds the perfect dashboard for your plants, your 3D printers, your home lab, or your aquarium, automatically, for anyone who installs it. We can’t wait to see what you create. 🌱
The built-in Security dashboard also gets a nice upgrade this release: a new Activity sidebar that shows you a live, 24-hour log of everything happening with your security-related entities. Cameras, locks, alarm panels, motorized covers, door and window sensors, and the comings and goings of the people in your home, all in one place. 🔓
It’s a quiet upgrade you’ll feel every day: at a glance, you can see if a door was opened, if someone arrived home, or if the front camera spotted motion, without having to dig through the logbook or build a dashboard for it yourself. The sidebar appears automatically on wider screens whenever the Logbook integration is enabled (it is, by default).
Building your own dashboard is one of the most rewarding parts of Home Assistant. The best part: you can build the entire thing right in the UI, by dragging and dropping cards into place. You don’t need to be technical, you don’t need to know YAML, and you don’t need to touch a single line of code to make something that looks great and works exactly the way you want.
Of course, the dashboards you craft yourself get plenty of love this release too. A new card for one-tap shortcuts and fresh tile card features for your media players. 🎨
Dashboards are the front door to your smart home, and sometimes the most useful thing you can put on them isn’t an entity, but a quick way to get somewhere. Jump to your energy dashboard. Open the camera view. Launch Assist. Open the manual in a new tab. The new shortcut card makes building those one-tap launchers a breeze. ⚡
It looks and feels like a tile card, but instead of representing an entity, it triggers an action when you select it. You can pick from:
The card is smart about defaults: pick a navigation target and it picks up the title, icon, and color of that destination automatically. Pick Launch Assist and it suggests a microphone icon. You can override any of it, of course; set your own label, description, icon, and color, and pick between a horizontal or vertical layout.
The shortcut also comes as a badge, so you can drop the same one-tap actions into the badge row at the top of any view. Same options, same smart defaults, just in a more compact form.
The tile card is one of the most flexible building blocks in Home Assistant dashboards, and this release expands what it can do for media players. Two new card features and a more flexible playback feature give you a lot more choice in how your media player tiles look and behave. 🎶
The first new feature is select source: a dropdown right on the tile that lets you switch the input or source on your media player. HDMI 1, the Spotify input on your receiver, that one obscure radio station you actually like; it’s all one tap away. The second is select sound mode, with the same dropdown experience for picking modes like Movie, Music, or Night on receivers and AV gear that support it.
And the existing playback card feature got a long-requested upgrade: you can now pick exactly which buttons appear and in what order. Mix and match from on/off, play, pause, play/pause, stop, previous track, and next track to build a remote that fits your media player perfectly. No more turn-on button on a TV that doesn’t need one, no more missing the next-track button on your speaker. 🎚️
The journey to make automationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] building feel natural continues. Ever since Home Assistant 2025.12 introduced purpose-specific triggers and conditions, every release has chipped away at the gap between how you describe your home in your head (“when a light turns on”, “if the climate is heating”) and what you actually had to type into an automation. Last release added a whole batch of cross-domain triggers and conditions. This release adds something the entire community has been asking for: time. ⏱️
Reading back the feedback we’ve received in the months this has been in Home Assistant Labs, one request stood out above all others: durations. Almost every “when motion is detected” automation in the wild secretly wishes it could say “when motion has not been detected for the last 5 minutes”. And almost every “if a door is open” condition really wants to be “if a door has been open for at least 10 minutes”. 🚪
Now they can. On the trigger side, a new for field has landed across a wide range of state-based purpose-specific triggers, from motion and occupancy to doors, windows, lights, switches, climate, covers, and many more. Pick a trigger, set how long the situation has to hold, and you’re done. No more wrestling with template helpers or YAML for: keys hidden in code views to express something this fundamental.
On the condition side, duration is now available across the entire family of entity conditions in Labs. Whether you’re checking on motion, a door, a light, a switch, a climate, a media player, or anything else, you can now ask for the state to have held for a given amount of time before the condition is considered true. Same story: no template helpers, no YAML detour.
A few examples of what this unlocks:
It’s a small-looking addition with an outsized impact: a whole category of “almost possible” automations just became easy to put together.
Beyond the new sense of time, this release sprinkles a few more handy purpose-specific building blocks across your house.
If you keep an eye on updates waiting to be installed, two new conditionsConditions are an optional part of an automation that will prevent an action from firing if they are not met. [Learn more], is available and is not available, let an automation branch on whether something is pending, without templating the answer yourself.
Your media players got chatty: triggers fire when something starts playing, pauses, turns on, or turns off, and now also when a player is muted or unmuted, when its volume changes, or when the volume crosses a threshold you set. Conditions follow the same beat with is muted, is unmuted, and a numeric volume check. Perfect fuel for “dim the lights when the movie starts”, “pause the music when the doorbell rings”, or “only send the loud TTSTTS (text-to-speech) allows Home Assistant to talk to you. [Learn more] announcement if the speaker is below 30%”. 🎬🔇
Your remotes picked up matching is on and is off conditions, finishing what last release’s triggers started. And your to-do lists can now answer two questions an automation might have: are all items completed, or are there still incomplete items on the list? Great for end-of-day check-ins or those “did I forget to feed the cat” moments. 🐱
Your timers got a whole lifecycle of new triggersA trigger is a set of values or conditions of a platform that are defined to cause an automation to run. [Learn more]: started, paused, restarted, cancelled, and finished. So that 20-minute “tea is ready” timer can now actually tell your kitchen lights to flash, and your “kids screen time” timer can announce when it’s running, paused, or up. There’s also a new time remaining trigger that fires when a running timer reaches a remaining duration you pick: think a gentle “five minutes left” warning before the screen time timer runs out. ⏲️
And finally, a new doorbell rang trigger. Doorbell event entities now speak a shared language, so a single trigger lights up regardless of which brand sits at your front door. 🔔
As some of the very first, we’ve added purpose-specific triggers and conditions for Person entities and Device Tracker entities separately. More recently, we’ve decided we want to go for a more ergonomic cross-domain approach. Those the triggers entered_home and left_home as also the conditions is_home and is_not_home got removed from the Person and Device Tracker. They will get successor in one of the upcoming releases.
Purpose-specific triggers and conditions are still a preview feature in Home Assistant Labs, but with each release the rough edges get smoother, and we’re closing in on having it feature complete. If you haven’t given it a spin yet, head over to Settings > System > Labs, switch it on, and let us know what you think. Your feedback is genuinely shaping where this lands; building in the open at work. 💚
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 🥰
We welcome the following new integrations in this release:
Denon RS-232, added by @balloob
Control your Denon receiver locally over its RS-232 serial port. Connect your receiver using a serial cable or a USB-to-serial adapter for push-based state updates, without depending on the network or the cloud.
Duco, added by @ronaldvdmeer — launching at 🏆 platinum quality
Monitor and control your Duco demand-controlled ventilation system locally from Home Assistant. Track CO₂, humidity, and other sensor data, and adjust ventilation, all over your local network.
EARN-E P1 Meter, added by @Miggets7
Connect your EARN-E energy monitor to Home Assistant for real-time insights into your smart meter’s energy and gas data. The device pushes its readings over your local network, so no cloud or polling is involved.
Eurotronic Comet Blue, added by @rikroe
Integrate your Eurotronic Comet Blue (and similar) Bluetooth radiator thermostats with Home Assistant. Read thermostat status and adjust temperatures locally, without a hub or cloud connection. Compatible thermostats include Sygonix HT100 BT, Xavax Hama, and Lidl Silvercrest RT2000BT.
Fumis, added by @frenck — launching at 🏆 platinum quality
Bring your Fumis-based pellet stove into Home Assistant through the Fumis online service. Monitor your room temperature, set a comfortable target temperature, and turn your stove on or off. Pellet stoves, pellet boilers, and hybrid wood and pellet stoves equipped with a Fumis WiRCU Wi-Fi module are sold under many different brands, including Austroflamm, Eco Spar, HAAS+SOHN, and Heta.
Honeywell String Lights, added by @balloob
Control your Honeywell radio frequency (RF) remote-controlled string lights from Home Assistant. Uses the new Radio frequency entity platform, so you’ll need a compatible sub-GHz RF transmitter (for example, an ESPHome device) to send commands.
Kiosker, added by @Claeysson
Monitor your Kiosker web kiosks running on iPad or iPhone from Home Assistant. Kiosker turns your iOS device into a powerful, easy-to-use web kiosk, perfect for dashboards on the wall.
Novy Cooker Hood, added by @piitaya
Control the light and the extractor fan on your Novy cooker hood from Home Assistant. Novy hoods are typically ceiling-mounted, with no buttons within reach, so an RF remote (and now Home Assistant) is the only practical way to control them. Uses the new Radio frequency entity platform, so you’ll need a compatible sub-GHz RF transmitter (for example, a Broadlink RM4 Pro or an ESPHome device) to send commands.
OMIE, added by @luuuis — launching at 🥈 silver quality
Bring Iberian Peninsula day-ahead electricity spot prices from OMIE into Home Assistant. Sensors expose the current and next-hour prices for both Spain and Portugal, perfect for smarter automations around when to run your dishwasher, charge your EV, or heat your water.
Radio frequency, added by @balloob
A new entity type that represents a sub-GHz radio frequency (RF) transmitter, like an ESPHome device with a CC1101 module attached. You don’t set this integration up directly; instead, other integrations use it to send RF commands to devices such as remote outlets, garage doors, and string lights. The new Honeywell String Lights and Novy Cooker Hood integrations are the first to make use of it. Read more about it in the Radio frequency joins infrared as a first-class citizen section above.
Teleinfo, added by @esciara — launching at 🥈 silver quality
Read electricity consumption data from French Linky smart meters and older electronic meters using the Télé-Information Client (TIC) protocol. Connect a Teleinfo USB adapter to your meter’s TIC output to monitor real-time energy indexes, apparent power, instantaneous current, and tariff information, all locally.
Victron GX, added by @tomer-w — launching at 🏆 platinum quality
Connect your Victron Energy GX devices, like the Cerbo GX, Venus GX, and Color Control GX, to Home Assistant over MQTT. Get real-time monitoring and control of your Victron system, including inverters, solar chargers, battery systems, grid meters, and EV chargers.
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 are also being constantly improved. Here are some of the noteworthy changes to existing integrations:
html5.send_message entity action, and the integration is now correctly classified as a notification service. Thanks, @tr4nt0r!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:
6 integrations reached platinum 🏆
2 integrations reached gold 🥇
3 integrations reached silver 🥈
2 integrations reached bronze 🥉
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! 👏
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:
The following integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] is also no longer available as of this release:
There are many more improvements in this release; here are some of the other noteworthy changes:
clean_segment action, plugging straight into the new Clean by area view. 🧹 Thanks, @gustavakerstrom!When you tap on an entity in your dashboard, the more-info dialog that pops up is one of the most-used surfaces in Home Assistant. This release, two of them get a fresh new look: vacuums and lawn mowers. 🧹🌱
The redesigned vacuum dialog leads with a friendly new illustration of your vacuum that comes to life with state-driven animations: it spins while cleaning, glides home while returning, sits quietly when docked, and shakes when something’s wrong. Battery moved up into the header where you can spot it at a glance, and the action buttons (start, pause, return to dock) are now lined up in a single, consistent row.
The biggest functional addition is a brand new Clean by area view. Many modern robot vacuums let you ask them to clean a specific room, but until now, there was no built-in way to do that from the dialog. You can now map your Home Assistant areasAn area in Home Assistant is a logical grouping of devices and entities that are meant to match areas (or rooms) in the physical world: your home. For example, the living room area groups devices and entities in your living room. [Learn more] to the rooms your vacuum knows about, and start a cleaning job for one or more areas right from the dialog. If you haven’t set up a mapping yet, the dialog walks you through it with a friendly empty state.
Lawn mowers got the same love. The redesigned lawn mower dialog brings the same fresh illustration with state-driven animations (mowing, returning, docked, error), the same battery-in-the-header layout, and the same unified action button row. Whether your robot is busy on the carpet or busy on the lawn, the experience now feels the same.
This work delivers on two Open Home Foundation roadmap opportunities: refined more info screen for vacuum cleaners and refining the more info screen for lawn mowers. Two roadmap items, one redesign. ✅
Toggles across Home Assistant got a small but lovely makeover this release. Every toggle in the app has been updated with a fresh new design. 🎨
The refreshed toggles on an entities card.
It’s not just a fresh coat of paint either: the new toggle is fully keyboard-friendly. Tab to it, then use the arrow keys to flip it on or off without ever touching the mouse. Small change, big quality-of-life upgrade. ⌨️
First, the most important thing to say up front: you do not need to write code or touch a single template to use Home Assistant. Everything from setting up your devices, to building automations and crafting beautiful dashboards, can be done entirely through the user interface, and it gets better every release. If the interface does what you need, you’re done. 💚
That said, templating is one of the most powerful corners of Home Assistant for the people who do want to go a step further: dynamic notifications that read the actual temperature, automations that decide based on a calculation across several entities, template entities whose value is computed from other entities. And it has long been one of the most intimidating corners too. So we shipped a top-to-bottom rework of the templating documentation, with one goal: if you have ever felt that templates were “not for you”, we want to change that. 📚✨
If you decide to learn templating, we are now confident we have everything in place to take you all the way:
There’s a quality-of-life upgrade across the entire website too: templates in code blocks are now interactive. Hover over a function name to see its description, select it to jump to the reference page, hover over a parameter for a quick reminder of what it does. Examples render with the input on top and the actual output right below, so you never have to guess what a template will produce.
Skip it, skim it, or master it. Either way, we’ve got your back. And this is just the beginning: we’ve expanded our documentation team and are investing heavily in making all of our documentation more approachable. So expect more reworks, more tutorials, and more friendly-but-thorough guides in releases to come. 💪
The rework didn’t stop at the documentation. While building it, it became painfully clear that even with great docs, writing a template still meant flipping back and forth between tabs. So the code editors you find throughout Home Assistant, the ones you use to write a template or fine-tune an automation, got a serious upgrade this release too. They now offer rich, context-aware autocomplete for both YAML and Jinja2 templates. ✨
Start typing inside a {{ ... }} or {% ... %} block, and the editor now suggests Home Assistant’s template functions, filters, tests, and globals. Each suggestion comes with a short signature, a description, and tab-stops for the arguments, so you can fly through writing a template without keeping the template documentation open in another tab.
It gets even better inside the string arguments of those functions. The editor knows what kind of ID a function expects and offers matching suggestions:
states(), is_state(), and state_attr(), including the states["..."] shorthand.device_entities(), device_name(), and device_attr(), showing the device’s friendly name with the raw ID as the inserted value.area_entities(), area_devices(), and area_name().floor_areas(), floor_entities(), and floor_name().label_areas(), label_devices(), and label_entities().
No more copy-pasting entity IDs from the developer tools, and no more typos sneaking into your templates. Less friction, fewer mistakes. 🎯
And it’s not just autocomplete. Hover over anything in your template and the editor has something useful to say. Functions, filters, and tests get a small tooltip with their signature, what they do, and a direct link to the full documentation page. Entity IDs and attributes show their current value right where you’re typing, so you instantly see whether your template is reading what you think it is. 🔍
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.
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:
When we first introduced purpose-specific triggers and conditions, we added separate ones for Person entities and Device Tracker entities. Since then, we’ve decided to take a more ergonomic, cross-domain approach instead.
As a result, the entered home and left home triggers, and the is home and is not home conditions, have been removed from Person and Device Tracker. Replacements that work across both will land in an upcoming release.
If you have automations that use these triggers or conditions on a person or device tracker, switch them back to a regular state trigger or state condition (for example, state changed to home) until the cross-domain replacements arrive.
(@emontnemery - #168406)
The “finish watering” value in the Gardena Bluetooth integration has been moved from a binary sensor to a regular sensor that exposes the timestamp of when watering is expected to finish. This makes the value far more useful in dashboards and automations.
If you have automations, scripts, or dashboards that reference the previous binary sensor entity, update them to use the new sensor entity instead.
The pilight integration has been disabled because the underlying pilight library relies on setuptools.pkg_resources, which is no longer available in setuptools 82.0.0 and later.
If the library is updated to remove the setuptools.pkg_resources dependency, or replaced with a maintained alternative that does so, the integration can be activated again. Community contributions to make this happen are very welcome.
The Ring doorbell event entity now emits the standardized ring event type instead of the legacy ding. This change aligns Ring with the new doorbell event standard, so the entity can be used seamlessly with the new purpose-specific automation triggers and conditions.
If you have automations that listen for the ding event type from your Ring doorbell, update them to use ring instead.
Previously, all actions registered by the Supervisor integration (such as hassio.addon_start, hassio.backup_partial, and hassio.host_reboot) only logged an error on failure, and your script or automation would continue running regardless of whether the action succeeded.
These actions now properly raise on failure, which means your automation or script will stop unless continue_on_error is set to true. If you rely on the previous behavior, add continue_on_error: true to those action steps.
The local_only option on webhooks must now be a proper boolean (true or false). Previously, other truthy values like 1 or "yes" were silently accepted. This brings the option in line with the rest of Home Assistant.
If you have webhooks configured in YAML with non-boolean local_only values, update them to use true or false.
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:
We will also release patch releases for Home Assistant 2026.5 in May. These patch releases only contain bug fixes. Our goal is to release a patch release once a week, aiming for Friday.
is_closed state for DynamicGarageDoor in Overkiz (@iMicknl - #170052)is_closed state to None when a cover state returns “unknown” in Overkiz (@iMicknl - #170081)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.5.
We are excited that the 1.59 update for Euro Truck Simulator 2 is now officially released and available on Steam! We hope you will enjoy all the new features, which you can read about in more detail below.
As always, we would like to thank everyone who took part in the open beta phase and reported possible issues or any kind of feedback on our forum, as it helped us fine-tune everything for a smooth transition to the full update!
We are happy to reveal that the long-awaited Benelux Rework project is released with this update! Our assets and map designers have completely rebuilt the whole original map of Belgium, the Netherlands, and Luxembourg from scratch, delivering a richer, more detailed experience.
Truckers can explore a wide range of revamped major cities and their surroundings, including Amsterdam, Groningen, Rotterdam, Brussels, Liège, and Luxembourg City. Each location has been carefully redesigned to highlight its unique character with plenty of landmarks and details!
You can also look forward to hauling cargo through entirely new locations. These include Antwerp, home to one of Europe's largest container ports; the DAF Trucks facility in Eindhoven, which has been recreated with remarkable detail in close cooperation with our partners at DAF Trucks; as well as key transport corridors - the busy E40 and A2 motorway.
You'll be able to drive from the beautiful hilly landscapes of the Belgian Ardennes to the flat polders and picturesque coastal roads in the northern Netherlands - the reworked Benelux offers a diverse and varied environment that truly reflects the region's look and feel.
Whether you're cruising through dense city centers, navigating busy highways, or discovering scenic country routes, the Benelux region now offers a far more immersive and authentic journey. You can see more from what is coming in our already released blogs on this topic.
In partnership with our friends at Volvo Trucks, we are adding the renowned Volvo Trucks Experience Center, situated in Gothenburg, Sweden, to the map, where you can test your trucking skills.
The center's standout feature is its dedicated driving circuit, which incorporates sweeping bends, tighter technical corners, elevation changes, downhill stretches, and varied road layouts. This allows drivers to assess vehicle behaviour in a controlled environment, highlighting stability, braking precision, handling characteristics, and overall driving comfort in ways that go beyond everyday road conditions.
The Volvo Trucks Experience Center has been recreated almost entirely on a 1:1 scale in our map with a strong attention to detail. You can drive the full circuit and explore the surrounding areas of the facility.
To find this amazing facility, you need to venture around the roads near Gothenburg to discover an entrance that will initially not be shown on your GPS. And remember, since it is located in Sweden, you need the Scandinavia DLC to be able to visit it. You can read more about this addition here.
Thermo King, a global leader in transport temperature control, is coming to Euro Truck Simulator 2 with their trailer refrigeration units! These replace all the unbranded units we had on our base game and DLC reefer trailers so far. This adds an extra touch of realism when you are hauling temperature-sensitive cargo and spot a famous real-world brand on your trailer.
With this update, you can see the Thermo King A-360, A-400, A-500, SLXi-300, and SLXi-400 refrigeration units on the front of your single trailers, which deliver a range of trailer refrigeration performance to suit different transport needs. On top of that, we also added the UT-1400R unit, designed for double-trailer configurations and mounted beneath the trailer. Find out more about this update here.
We've been closely listening to feedback from our community, and one of the most common points raised in the new route advisor was that many players missed having quick access to information on vehicle damage and finances. While our teams are actively working on the next steps in our broader vision for a redesigned UI in this area, we didn't want to make you wait until that work is complete. Instead, we've prioritized implementing some of the most frequently requested improvements as soon as possible.
Based on that, we've implemented the Damage and Finances widgets. These widgets are designed to restore easy access to information about truck damage, plus trailer and cargo damage, if you are currently driving with a trailer and cargo, as well as your current bank balance, with an average profit over the last seven days displayed too.
These widgets can be turned on and off in the Widget Settings Menu, and if enabled, they will be displayed in the bottom right corner above your GPS.
The Tow to Road feature was designed to improve the overall quality of life for players by reducing frustrating situations during gameplay. It allows drivers to quickly recover if their truck overturns or gets stuck in a ditch or uneven terrain. It also helps prevent disruptions in multiplayer sessions, enabling players to continue with their convoy when they find themselves stuck, without the need to be towed to a service location, which could cause unnecessary delays.
So when you are in a difficult situation, you can simply find the new "Tow to Road" button under the Service menu (set to F7 by default). After paying a small fee for the towing service, you will be transported to your last safe location on the road. You can read more about this feature here.
The Skill Screen has received a visual rework while remaining in its original place within the interface. This update focuses on improving clarity and overall user experience without changing its core functionality.
You can now view both your current skill level and the next step in its progression. Tooltips also allow you to explore other ranks within each skill. Selecting a skill provides improved readability and clearer visual feedback, including a better indication of how many steps remain in that skill's progression path.
Each skill is represented as a clickable button, making it easy to access more detailed information. The redesign also improves navigation when using a controller.
We're continuing to refine the overall user experience with updates focused on readability, clarity, and smoother controller navigation.
The in-game news banner has received a visual refresh to better align with our newer UI style while improving readability. When hovering over a news item, a tooltip will now display a longer excerpt along with a clear call to action. Deactivated news items now feature a clearer status indicator, which also doubles as an activation button.
We're making navigation on the world map more intuitive for controller users. A new "undo last pin" feature has been added, along with remapped controls for adding, removing, setting avoid areas, and resetting pins.
Save handling has also been improved, with new saves now using the standard save icon instead of a black screenshot and overwriting clearly labeled as "Overwrite". Garage upgrade cutscenes can now be skipped more consistently using the (B) button, and the controller navigation has been further refined with improved D-pad accessibility across UI.
We've also made some adjustments to traffic audio as part of this update. Sounds have been softened and rebalanced to better match real-world perception, with less emphasis on distant engine noise and more on the subtle "road hiss" of tires. Honking behavior has also been slightly randomized to reduce repetition. Overall, traffic should now feel less intrusive and better integrated into the ambient soundscape.
We've also made a few improvements to the Height Blend feature. Derived normal maps can now be enabled to help conserve GPU memory, and we've also addressed several graphical issues to ensure more consistent, visually accurate results.
We've decided to temporarily disable the detour feature to focus on maintenance and further development. We've received numerous reports of Detours not functioning as intended, and the current system no longer meets our needs.
As a result, we'll be shutting down detours while we work on improving and upgrading the feature in the background to make it more stable and reliable. Please note that this change only affects detours - random road events will continue to be available in the game.
Map
Vehicles
UI/UX
Visuals
Sounds
Miscellaneous bug fixes, mostly surrounding the SeaBIOS storage driver code.
Full Changelog: 3.1.0...3.1.1
Important
If you are using Part-DB it would be helpful if you fill out this short survey on your usage of Part-DB (Google Forms): https://forms.gle/Q15twx3YYq3qCNfe8
Full Changelog: v4.3.1...v4.3.2
The Chrome team is delighted to announce the promotion of Chrome 148 to the stable channel for Windows, Mac and Linux. This will roll out over the coming days/weeks.
Security Fixes and Rewards
Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.
This update includes 127 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.
Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.
[$43000][493747582] Critical CVE-2026-7896: Integer overflow in Blink. Reported by c6eed09fc8b174b0f3eebedcceb1e792 on 2026-03-18
[N/A][504069514] Critical CVE-2026-7897: Use after free in Mobile. Reported by Google on 2026-04-18
[N/A][504587882] Critical CVE-2026-7898: Use after free in Chromoting. Reported by Google on 2026-04-20
[$55000][505481948] High CVE-2026-7899: Out of bounds read and write in V8. Reported by Project WhatForLunch (@pjwhatforlunch) on 2026-04-23
[$16000][496503799] High CVE-2026-7900: Heap buffer overflow in ANGLE. Reported by Anonymous on 2026-03-26
[$16000][497724490] High CVE-2026-7901: Use after free in ANGLE. Reported by Syn4pse (@ret2happy) on 2026-03-30
[$8000][502030575] High CVE-2026-7902: Out of bounds memory access in V8. Reported by JunYoung Park(@candymate) of KAIST Hacking Lab on 2026-04-13
[TBD][491760376] High CVE-2026-7903: Integer overflow in ANGLE. Reported by heesun on 2026-03-11
[TBD][492350406] High CVE-2026-7904: Out of bounds read in Fonts. Reported by c6eed09fc8b174b0f3eebedcceb1e792 on 2026-03-13
[N/A][495259842] High CVE-2026-7905: Insufficient validation of untrusted input in Media. Reported by Google on 2026-03-23
[N/A][496284584] High CVE-2026-7906: Use after free in SVG. Reported by Google on 2026-03-25
[N/A][496292089] High CVE-2026-7907: Use after free in DOM. Reported by Google on 2026-03-25
[N/A][497436531] High CVE-2026-7908: Use after free in Fullscreen. Reported by Google on 2026-03-29
[N/A][497437113] High CVE-2026-7909: Inappropriate implementation in ServiceWorker. Reported by Google on 2026-03-29
[N/A][497543810] High CVE-2026-7910: Use after free in Views. Reported by Google on 2026-03-29
[N/A][497548912] High CVE-2026-7911: Use after free in Aura. Reported by Google on 2026-03-29
[N/A][497639714] High CVE-2026-7912: Integer overflow in GPU. Reported by Google on 2026-03-30
[N/A][497936728] High CVE-2026-7913: Insufficient policy enforcement in DevTools. Reported by Google on 2026-03-30
[N/A][498401609] High CVE-2026-7914: Type Confusion in Accessibility. Reported by Google on 2026-04-01
[N/A][498454478] High CVE-2026-7915: Insufficient data validation in DevTools. Reported by Google on 2026-04-01
[N/A][498720754] High CVE-2026-7916: Insufficient data validation in InterestGroups. Reported by Google on 2026-04-01
[N/A][498752242] High CVE-2026-7917: Use after free in Fullscreen. Reported by Google on 2026-04-02
[N/A][498780188] High CVE-2026-7918: Use after free in GPU. Reported by Google on 2026-04-02
[N/A][498832921] High CVE-2026-7919: Use after free in Aura. Reported by Google on 2026-04-02
[N/A][498989348] High CVE-2026-7920: Use after free in Skia. Reported by Google on 2026-04-02
[N/A][499062376] High CVE-2026-7921: Use after free in Passwords. Reported by Google on 2026-04-02
[N/A][499449324] High CVE-2026-7922: Use after free in ServiceWorker. Reported by Google on 2026-04-04
[N/A][500080194] High CVE-2026-7923: Out of bounds write in Skia. Reported by Google on 2026-04-06
[N/A][500087204] High CVE-2026-7924: Uninitialized Use in Dawn. Reported by Google on 2026-04-06
[N/A][501833981] High CVE-2026-7925: Use after free in Chromoting. Reported by Google on 2026-04-12
[TBD][502249087] High CVE-2026-7926: Use after free in PresentationAPI. Reported by anonymous on 2026-04-14
[N/A][502830119] High CVE-2026-7927: Type Confusion in Runtime. Reported by Google on 2026-04-15
[N/A][504612429] High CVE-2026-7928: Use after free in WebRTC. Reported by Google on 2026-04-20
[N/A][504660052] High CVE-2026-7929: Use after free in MediaRecording. Reported by Google on 2026-04-20
[TBD][434825208] Medium CVE-2026-7930: Insufficient validation of untrusted input in Cookies. Reported by Satoki on 2025-07-29
[TBD][474338157] Medium CVE-2026-7931: Insufficient validation of untrusted input in iOS. Reported by Qadhafy Muhammad Tera on 2026-01-08
[TBD][481634116] Medium CVE-2026-7932: Insufficient policy enforcement in Downloads. Reported by Povcfe of Tencent Security Xuanwu Lab on 2026-02-04
[TBD][488585490] Medium CVE-2026-7933: Out of bounds read in WebCodecs. Reported by heapracer (@heapracer) on 2026-03-01
[N/A][489023922] Medium CVE-2026-7934: Insufficient validation of untrusted input in Popup Blocker. Reported by Google on 2026-03-02
[TBD][489624550] Medium CVE-2026-7935: Inappropriate implementation in Speech. Reported by Qadhafy Muhammad Tera on 2026-03-04
[TBD][490485402] Medium CVE-2026-7936: Object lifecycle issue in V8. Reported by Christian Holler on 2026-03-07
[TBD][491766258] Medium CVE-2026-7937: Insufficient policy enforcement in DevTools. Reported by lebr0nli of National Yang Ming Chiao Tung University, Dept. of CS, Security and Systems Lab on 2026-03-11
[TBD][492735384] Medium CVE-2026-7938: Use after free in CSS. Reported by c6eed09fc8b174b0f3eebedcceb1e792 on 2026-03-15
[TBD][492963096] Medium CVE-2026-7939: Inappropriate implementation in SanitizerAPI. Reported by s3zer0 on 2026-03-15
[TBD][493631402] Medium CVE-2026-7940: Use after free in V8. Reported by sakana on 2026-03-17
[TBD][493955234] Medium CVE-2026-7941: Insufficient validation of untrusted input in Mobile. Reported by Adithya Kotian on 2026-03-19
[N/A][495363705] Medium CVE-2026-7942: Integer overflow in ANGLE. Reported by Google on 2026-03-23
[TBD][495373657] Medium CVE-2026-7943: Insufficient validation of untrusted input in ANGLE. Reported by 86ac1f1587b71893ed2ad792cd7dde32 on 2026-03-23
[N/A][495783187] Medium CVE-2026-7944: Insufficient validation of untrusted input in Persistent Cache. Reported by Google on 2026-03-24
[N/A][495802788] Medium CVE-2026-7945: Insufficient validation of untrusted input in COOP. Reported by Google on 2026-03-24
[N/A][496016840] Medium CVE-2026-7946: Insufficient policy enforcement in WebUI. Reported by Google on 2026-03-25
[N/A][496169594] Medium CVE-2026-7947: Insufficient validation of untrusted input in Network. Reported by Google on 2026-03-25
[N/A][496193452] Medium CVE-2026-7948: Race in Chromoting. Reported by Google on 2026-03-25
[N/A][496206134] Medium CVE-2026-7949: Out of bounds read in Skia. Reported by Google on 2026-03-25
[N/A][496259890] Medium CVE-2026-7950: Out of bounds read and write in GFX. Reported by Google on 2026-03-25
[TBD][496266456] Medium CVE-2026-7951: Out of bounds write in WebRTC. Reported by soft.connect.fr on 2026-03-26
[N/A][496279876] Medium CVE-2026-7952: Insufficient policy enforcement in Extensions. Reported by Google on 2026-03-25
[N/A][496379792] Medium CVE-2026-7953: Insufficient validation of untrusted input in Omnibox. Reported by Google on 2026-03-26
[N/A][496380960] Medium CVE-2026-7954: Race in Shared Storage. Reported by Google on 2026-03-26
[N/A][496441232] Medium CVE-2026-7955: Uninitialized Use in GPU. Reported by Google on 2026-03-26
[N/A][496463315] Medium CVE-2026-7956: Use after free in Navigation. Reported by Google on 2026-03-26
[N/A][496607380] Medium CVE-2026-7957: Out of bounds write in Media. Reported by Google on 2026-03-26
[N/A][496632973] Medium CVE-2026-7958: Inappropriate implementation in ServiceWorker. Reported by Google on 2026-03-26
[N/A][496645205] Medium CVE-2026-7959: Inappropriate implementation in Navigation. Reported by Google on 2026-03-26
[N/A][497007825] Medium CVE-2026-7960: Race in Speech. Reported by Google on 2026-03-27
[N/A][497008295] Medium CVE-2026-7961: Insufficient validation of untrusted input in Permissions. Reported by Google on 2026-03-27
[N/A][497081987] Medium CVE-2026-7962: Insufficient policy enforcement in DirectSockets. Reported by Google on 2026-03-28
[N/A][497250399] Medium CVE-2026-7963: Inappropriate implementation in ServiceWorker. Reported by Google on 2026-03-28
[N/A][497254383] Medium CVE-2026-7964: Insufficient validation of untrusted input in FileSystem. Reported by Google on 2026-03-28
[N/A][497255035] Medium CVE-2026-7965: Insufficient validation of untrusted input in DevTools. Reported by Google on 2026-03-28
[N/A][497341787] Medium CVE-2026-7966: Insufficient validation of untrusted input in SiteIsolation. Reported by Google on 2026-03-29
[N/A][497365545] Medium CVE-2026-7967: Insufficient validation of untrusted input in Navigation. Reported by Google on 2026-03-29
[N/A][497432281] Medium CVE-2026-7968: Insufficient validation of untrusted input in CORS. Reported by Google on 2026-03-29
[N/A][497450574] Medium CVE-2026-7969: Integer overflow in Network. Reported by Google on 2026-03-29
[N/A][497487462] Medium CVE-2026-7970: Use after free in TopChrome. Reported by Google on 2026-03-29
[N/A][497529290] Medium CVE-2026-7971: Inappropriate implementation in ORB. Reported by Google on 2026-03-29
[N/A][497546281] Medium CVE-2026-7972: Uninitialized Use in GPU. Reported by Google on 2026-03-29
[N/A][497565944] Medium CVE-2026-7973: Integer overflow in Dawn. Reported by Google on 2026-03-29
[N/A][497649372] Medium CVE-2026-7974: Use after free in Blink. Reported by Google on 2026-03-30
[N/A][497735587] Medium CVE-2026-7975: Use after free in DevTools. Reported by Google on 2026-03-30
[N/A][497736679] Medium CVE-2026-7976: Use after free in Views. Reported by Google on 2026-03-30
[N/A][497821223] Medium CVE-2026-7977: Inappropriate implementation in Canvas. Reported by Google on 2026-03-30
[N/A][497828892] Medium CVE-2026-7978: Inappropriate implementation in Companion. Reported by Google on 2026-03-30
[N/A][497849876] Medium CVE-2026-7979: Inappropriate implementation in Media. Reported by Google on 2026-03-30
[N/A][497859275] Medium CVE-2026-7980: Use after free in WebAudio. Reported by Google on 2026-03-30
[N/A][497926602] Medium CVE-2026-7981: Out of bounds read in Codecs. Reported by Google on 2026-03-30
[N/A][497952533] Medium CVE-2026-7982: Uninitialized Use in WebCodecs. Reported by Google on 2026-03-30
[N/A][497975608] Medium CVE-2026-7983: Out of bounds read in Dawn. Reported by Google on 2026-03-31
[N/A][498277368] Medium CVE-2026-7984: Use after free in ReadingMode. Reported by Google on 2026-03-31
[N/A][498352423] Medium CVE-2026-7985: Use after free in GPU. Reported by Google on 2026-03-31
[N/A][498396238] Medium CVE-2026-7986: Insufficient policy enforcement in Autofill. Reported by Google on 2026-04-01
[N/A][498696266] Medium CVE-2026-7987: Use after free in WebRTC. Reported by Google on 2026-04-01
[N/A][498753456] Medium CVE-2026-7988: Type Confusion in WebRTC. Reported by Google on 2026-04-02
[N/A][498765082] Medium CVE-2026-7989: Insufficient data validation in DataTransfer. Reported by Google on 2026-04-02
[N/A][498892267] Medium CVE-2026-7990: Insufficient validation of untrusted input in Updater. Reported by Google on 2026-04-02
[N/A][499065126] Medium CVE-2026-7991: Use after free in UI. Reported by Google on 2026-04-02
[N/A][499067529] Medium CVE-2026-7992: Insufficient validation of untrusted input in UI. Reported by Google on 2026-04-02
[N/A][499099003] Medium CVE-2026-7993: Insufficient validation of untrusted input in Payments. Reported by Google on 2026-04-03
[N/A][499116954] Medium CVE-2026-7994: Inappropriate implementation in Chromoting. Reported by Google on 2026-04-03
[N/A][501745798] Medium CVE-2026-7995: Out of bounds read in AdFilter. Reported by Google on 2026-04-11
[TBD][484547631] Low CVE-2026-7996: Insufficient validation of untrusted input in SSL. Reported by heesun on 2026-02-15
[TBD][487960705] Low CVE-2026-7997: Insufficient validation of untrusted input in Updater. Reported by ochkofficial on 2026-02-26
[TBD][491676472] Low CVE-2026-7998: Insufficient validation of untrusted input in Dialog. Reported by Tianyi Hu on 2026-03-11
[TBD][493099941] Low CVE-2026-7999: Inappropriate implementation in V8. Reported by Taisic Yun (@taisic) of Theori on 2026-03-16
[TBD][494464734] Low CVE-2026-8000: Insufficient validation of untrusted input in ChromeDriver. Reported by Ryan Jupp - HAAO on 2026-03-20
[TBD][494764371] Low CVE-2026-8001: Use after free in Printing. Reported by c6eed09fc8b174b0f3eebedcceb1e792 on 2026-03-21
[N/A][495779613] Low CVE-2026-8002: Use after free in Audio. Reported by Google on 2026-03-24
[N/A][495985532] Low CVE-2026-8003: Insufficient validation of untrusted input in TabGroups. Reported by Google on 2026-03-25
[N/A][496189510] Low CVE-2026-8004: Insufficient policy enforcement in DevTools. Reported by Google on 2026-03-25
[N/A][496298665] Low CVE-2026-8005: Insufficient validation of untrusted input in Cast. Reported by Google on 2026-03-25
[N/A][496373088] Low CVE-2026-8006: Insufficient policy enforcement in DevTools. Reported by Google on 2026-03-26
[N/A][496399759] Low CVE-2026-8007: Insufficient validation of untrusted input in Cast. Reported by Google on 2026-03-26
[N/A][496426191] Low CVE-2026-8008: Inappropriate implementation in DevTools. Reported by Google on 2026-03-26
[N/A][496555077] Low CVE-2026-8009: Inappropriate implementation in Cast. Reported by Google on 2026-03-26
[N/A][496624084] Low CVE-2026-8010: Insufficient validation of untrusted input in SiteIsolation. Reported by Google on 2026-03-26
[N/A][496626029] Low CVE-2026-8011: Insufficient policy enforcement in Search. Reported by Google on 2026-03-26
[N/A][496628298] Low CVE-2026-8012: Inappropriate implementation in MHTML. Reported by Google on 2026-03-26
[N/A][497427430] Low CVE-2026-8013: Insufficient validation of untrusted input in FedCM. Reported by Google on 2026-03-29
[N/A][497490364] Low CVE-2026-8014: Inappropriate implementation in Preload. Reported by Google on 2026-03-29
[N/A][497548558] Low CVE-2026-8015: Inappropriate implementation in Media. Reported by Google on 2026-03-29
[N/A][497695401] Low CVE-2026-8016: Use after free in WebRTC. Reported by Google on 2026-03-30
[N/A][497722578] Low CVE-2026-8017: Side-channel information leakage in Media. Reported by Google on 2026-03-30
[N/A][498292657] Low CVE-2026-8018: Insufficient policy enforcement in DevTools. Reported by Google on 2026-03-31
[N/A][498353173] Low CVE-2026-8019: Insufficient policy enforcement in WebApp. Reported by Google on 2026-03-31
[N/A][498382925] Low CVE-2026-8020: Uninitialized Use in GPU. Reported by Google on 2026-04-01
[N/A][498417031] Low CVE-2026-8021: Script injection in UI. Reported by Google on 2026-04-01
[N/A][499194407] Low CVE-2026-8022: Inappropriate implementation in MHTML. Reported by Google on 2026-04-03
We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.
Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.
Srinivas Sista
Google Chrome
How do you more or less double the number of Works with Home Assistant-certified devices available to our community? Have BEGA join the program! This German firm has spent more than 75 years designing a wide range of architectural lighting that sets the industry standard: and now they’re bringing that expertise to your smart home.
If you haven’t heard of BEGA before, you may have admired their work without realizing it. That’s because they produce the kind of beautifully engineered fixtures you see gracing the facades of fancy hotels, elegant public buildings, and stylish modern homes worldwide. They’re probably better known for this kind of work than for smart home tech, which is precisely what makes their joining the Works with Home Assistant program so exciting.
Because BEGA aren’t just dipping a toe in: they’re bringing what’s almost certainly the largest single addition of certified devices we’ve ever had in one go: enough to very nearly double the number of certified products in the program! And it’s not just the volume that impresses. BEGA Smart – their Zigbee-powered smart lighting system – is flexible, expandable, and designed to work entirely offline, with no internet connection required.
BEGA: putting the smart into smart home lighting.
"With BEGA Smart, we aim to combine high-quality architectural lighting with intelligent control. Integrating with Home Assistant allows us to bring our lighting solutions into an open and flexible smart home ecosystem that many of our customers already value. By doing so, we enhance comfort, safety, and energy efficiency while enabling new ways to experience light. We're excited to support the community and be part of this ecosystem."
- Heinrich Gantenbrink, Managing Partner at BEGABEGA’s premium positioning isn’t only about aesthetics. Their commitment to repairability also aligns well with the Open Home Foundation’s sustainability principles. Rather than treating a luminaire as a disposable unit, BEGA designs the majority of their components to be replaceable. Crack a glass panel? You can order that specific spare via their website’s search function and replace it, rather than throwing out the whole fixture.
This also makes BEGA an interesting choice if you’re thinking about illuminating your outdoor spaces. We have relatively few outdoor lighting options in the program, and BEGA fills that gap in style – just in time if you’re looking to get your garden or terrace ready for summer 😎.
We mentioned BEGA Smart runs on Zigbee, but if that’s new to you, here’s what it means. Zigbee is basically a short-range wireless communication standard: like Wi-Fi, but designed specifically for smart home devices. Unlike Wi-Fi however, it’s an open standard, so isn’t run by one specific company, and connects directly to Home Assistant without needing a router or internet connection. It’s also a mesh protocol, which means the more devices you add to your network, the stronger and more reliable it gets – handy for lighting that’s spread across your home and garden.
And on that subject, if you want to dim the patio lights from your sofa, or check they’re off while you’re away, Home Assistant Cloud can help – providing secure remote access wherever you are (your subscription helps fund the Works with Home Assistant program too!).
The path to enlightenment, with BEGA devices.
As with every Works with Home Assistant partner, our in-house team has thoroughly tested BEGA’s devices to make sure they meet our core requirements: local control, privacy, and long-term sustainability.
Because the list of certified BEGA devices is so long, we’ve included a condensed list below (there’s not enough room for them all here without subjecting you to a loooonnnnnng scroll! 😄). Bear in mind, when you browse BEGA’s website, look for devices marked as BEGA Smart. This tells you the item is Zigbee enabled and Works with Home Assistant certified. Worth knowing, since each luminaire also comes in other variants, such as DALI or non-smart versions, which are not certified under the program.
BEGA Smart covers a swathe of indoor and outdoor luminaires, with wall or ceiling mounted options, as well as freestanding garden path lighting to illuminate those balmy summer evenings.
For the full list of certified BEGA devices, see our filtered device list.
With BEGA on board, Home Assistant users have more choice than ever when it comes to quality lighting, inside and out. Ready to explore the full range? Head over to our certified device list to be illuminated about everything that’s been approved from BEGA and beyond. The future of your smart home is looking bright 💡.
If I have a device that is not listed under “Works with Home Assistant” does this mean it’s not supported?
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.
OK, so what’s the point of the Works with program?
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.
How were these devices tested?
All devices in this list were tested using a standard Home Assistant Green Hub with the Home Assistant Connect ZBT-2 and with our Zigbee integration (ZHA). If you have another hub/antenna setup/integration that’s not a problem, but we test against these as they are the most effective way for our team to certify within our ecosystem.
Will you be adding more BEGA devices to the program?
Why not! We’re thrilled to foster a close relationship with the team at BEGA to work together on any upcoming releases or add in further products that are not yet listed here.
If you are upgrading from v0.16.x, replace the binary (or run docker pull). If you are upgrading from v0.15.x and below, please read the upgrading documentation for more information on how to upgrade from previous versions.
AccountSettings object return invalidProperties.mail-parser panic with certain messages containing corrupted attachments.RCPT on checks.AddressBook/query fetches wrong resources.%EMAILADDRESS% when no email address is provided.
