v1.19.1-pre
Bump to 1.19.1 for @SomeoneToIgnore
Bump to 1.19.1 for @SomeoneToIgnore
Bump to 1.18.1 for @SomeoneToIgnore
Fixed Firefox becoming unresponsive on some pages that use CSS blur and backdrop filters together. (Bug 2068836)
Fixed the sidebar not reappearing after restarting Firefox when the "Hide tabs and sidebar" option was turned on. (Bug 2065431)
Fixed some profile icons not being displayed in the account and application menus. (Bug 2064729, Bug 2067734)
Fixed the current device being listed among connected devices in the account menu. (Bug 2059763)
Reference link to 155.0 release notes.
Standard dynamic range (SDR) video in some formats can appear washed out on macOS. The issue is under investigation and a fix will ship in a future release. (Bug 2068961)
This is the 15th update to ElegantFin.
Settings > Display > Theme > Light. (See #15)--appBarHeight. You will need to use the code block documented in the updated customisation section. (See #8.)You may use the provided CSS file for self-hosting purposes. Alternatively, you may use the following code snippet to get the latest version via a free CDN.
@import url("https://cdn.jsdelivr.net/gh/lscambo13/ElegantFin@main/Theme/ElegantFin-jellyfin-theme-build-latest-minified.css");
For more detailed information, be sure to read the README.md file.
![]()
VIENNA, Austria – September 04, 2026 – Proxmox Server Solutions today announced that Proxmox Virtual Environment has been officially certified under the Omnissa® Horizon Ready Hypervisor program. The certification confirms compatibility between Proxmox VE and Omnissa Horizon in Manual Provisioning Mode, allowing organizations running Proxmox VE to deploy Omnissa Horizon, Omnissa’s digital work platform for virtual desktops, applications, and end-user devices, for centralized desktop and application delivery on their existing infrastructure.
With official Horizon support, organizations can now run their Omnissa virtual desktops directly on Proxmox VE, reducing infrastructure costs without compromising on performance. By combining Proxmox VE's open-source hypervisor with Omnissa Horizon's enterprise management capabilities, organizations gain a flexible, cost-effective desktop virtualization solution built on infrastructure they already run.
Proxmox VE is also listed in the Horizon Ready Hypervisor program as a certified third-party hypervisor supporting NVIDIA® vGPU. This enables IT teams to allocate physical GPU resources across multiple virtual machines, delivering high-performance graphics workloads within Horizon virtual desktop deployments.
Verified configurations and deployment requirements are available in the Omnissa Horizon Ready Hypervisor Compatibility Guide at https://interopmatrix.omnissa.com/Compatibility/hypervisors
###
About Proxmox Virtual Environment
Powering over 2.3 million hosts globally, Proxmox Virtual Environment is a complete open-source platform for enterprise virtualization and hyper-converged infrastructure. It natively unifies KVM virtualization, LXC containers, software-defined storage, and networking on a single platform. Alongside its dedicated Backup Server and Datacenter Manager, the Proxmox ecosystem eliminates multi-site complexity as well as dependency on proprietary stacks. Backed by a global community of over 225,000 members, the platform serves as a scalable, cost-effective foundation for modern data centers.
About Proxmox Server Solutions GmbH
Proxmox Server Solutions provides powerful, intuitive open-source server software that guarantees vendor independence and minimizes total cost of ownership. Enterprises of all sizes rely on the company’s reliable vendor support, certified training services, and a global network of 3,000 integration partners to ensure business continuity. More than 60,000 enterprises worldwide hold active Proxmox support plans to secure their mission-critical IT. Established in 2005, Proxmox Server Solutions GmbH is headquartered in Vienna, Austria, with its subsidiary Proxmox North America Inc. based in Kingston, Ontario.
Media contact: Daniela Häsler, Proxmox Server Solutions GmbH, press@proxmox.com
nginx-1.31.5 mainline version has been released, featuring control API, predicate locations, and the ngx_http_json_module module.
The Stable channel has been updated to 153.0.8010.27/.28 for Windows. Mac is coming shortly , as part of our early stable release to a small percentage of users. A full list of changes in this build is available in the log.
You can find more details about early Stable releases here.
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
Full Changelog: v5.0.4...v5.0.5
The Stable channel has been updated to 152.0.7977.82/.83 for Windows and Mac and 152.0.7977.82 for Linux, which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log
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 12 security fixes. Please see the Chrome Security Page for more information.
[$1,000][542403045] High CVE-2026-85046: Type confusion in V8. Reported by Salvatore Gulizia (nickname: Serotav) on 2026-08-04
Full Changelog: v4.3.15...v4.3.16
This is the initial release for the ECS-24S, ECS-24S-PoE, ECS-48S and ECS-48S-PoE.
nginx-1.31.5 mainline version has been released, featuring control API, predicate locations, and the ngx_http_json_module.
We're happy to announce that the Open Beta for the 1.61 update for Euro Truck Simulator 2 is now available for players to try out and test. If you choose to participate, we'd greatly appreciate any feedback, bug reports, or issues you encounter being shared in the appropriate section of our official forums.
Vehicles
So enjoy all the new additions, but please remember: It's only an open beta, not a stable public version - so you may encounter bugs, instability, or crashes. It's completely okay if you want to wait for the final release. But if you're interested in helping us to get there faster, we'd appreciate all of your feedback on our forum and your bug reports in the dedicated section.
Please check our modding wiki to get details pertaining to mods for the game.
If you wish to participate in this Open Beta, you can find this version in the Experimental Beta branch on Steam. The way to access it is as follows: Steam client → LIBRARY → right-click on Euro Truck Simulator 2 → Properties → Betas tab → Beta Participation drop-down menu → public_beta. No password is required. Sometimes you will have to restart your Steam client to see the correct branch name there.
COOLIFY_URL and COOLIFY_FQDN, including multi-domain configurations with ports. (#11527, fixes #10824)Full Changelog: v4.3.14...v4.3.15
Windows Installer
Windows No Installer (zip)
macOS - Universal
Linux - deb, AppImage or rpm
ChangeLog:
The wait is almost over, truckers! The time has come to mark your calendars and get ready to explore the rugged landscapes, wide-open roads, and unique sights of the Mount Rushmore State. We’re excited to officially reveal that the...
To celebrate this milestone, we’re also happy to share the official South Dakota DLC trailer on our YouTube channel. This new video offers a glimpse at the scenery and experiences awaiting you!
So, sit back, turn up the volume, and take a look at the trailer below!
As we approach release, our teams are putting the finishing touches on the DLC and making sure everything is ready for its big debut.
South Dakota offers plenty of variety for truckers to discover. You’ll travel through the vast Great Plains, pass through the stunning Badlands, and explore the rugged rock formations of the Black Hills while encountering iconic landmarks along the way, including the famous Mount Rushmore National Memorial, the waterfalls of Sioux Falls, the Dignity of Earth and Sky statue overlooking the Missouri River, the Corn Palace, Hot Springs, and many more.
From busy cities and industrial areas to smaller settlements and scenic stretches of highway, every route brings something different to your journey, with plenty of new ground to cover.
If you haven’t already, be sure to add the South Dakota DLC to your Steam wishlist. It’s a great way to support the project and ensures you’ll be notified when the DLC becomes available.
We’re incredibly excited to finally share the release date and trailer with you, and we can’t wait to see you hitting the roads of South Dakota for yourselves. Thank you for your continued support and enthusiasm throughout the development of this DLC.
Remember to follow us on X/Twitter, Facebook, Instagram, Bluesky, TikTok, and YouTube for all the latest news, or sign up for our newsletter to stay informed. Until the release day, keep those wheels turning, and we’ll see you on the road!
This week's release includes refreshed Markdown preview styling, inline debugger values for C and C++, and File Finder history that persists across workspace sessions.
Learn about the Zed Guild.
edit_predictions.<provider>.prediction_debounce setting for inline completions. (#61568; thanks ddeityy)git: toggle diff base action to toggle the diff base between HEAD and the default branch. (#62966)lsp.bash-language-server.settings. (#57487; thanks CathalMullan)in_preview keybinding context for editors in preview mode. (#61777; thanks krawitzzZ).editorconfig files. (#63323)on_last_window_closed was set to "quit_app" and restore_on_startup was set to "last_session". (#60477; thanks Caleul)cmd-p. (#61716; thanks HuaGu-Dragon)if __name__ in ("__main__", ...)-style main guards. (#58911; thanks tlium)tasks.json not being applied when debugging Python tasks. (#63154; thanks andreyfedoseev)format_on_save was enabled. (#62921; thanks mateioprea)object field in stream chunks, such as GLM 5.2. (#62517; thanks ummon-v)alt-f5 keystroke. (#62891; thanks nbdd0121)lsp_results_location setting being ignored by the editor: go to declaration and editor: go to type definition actions. (#61060; thanks xdBronch)f10 now steps over and f11 steps into while execution is paused, while fullscreen remains available outside paused sessions. (#58729; thanks Andrej730)
This week's release includes call hierarchy support, multi-select in the Git Panel, automatic language detection for untitled buffers, and project search on type by default.
Learn about the Zed Guild.
Open File on Remote and Copy Remote File URL options to file tabs and the Project Panel. (#62177; thanks JacobNWolf)m i m and m a m. (#59201; thanks GoldStrikeArch)call hierarchy: show incoming calls and call hierarchy: show outgoing calls, with default keybindings cmd-k cmd-h on macOS and ctrl-k ctrl-h on Linux and Windows. (#53239; thanks swiftcoder)cmd-shift-v and cmd-k v on macOS and ctrl-shift-v and ctrl-k v on Linux and Windows to open the tabular data preview for CSV, TSV, SSV, and PSV files. (#63369; thanks HalavicH).bash_login files. (#63466; thanks mnipritom)outline_panel.multi_buffer_hide_symbols setting and outline panel: toggle symbols action to show only files and directories in the Outline Panel for multi-buffer views. (#63404; thanks FrantisekGazo)reveal_if_open setting to reveal buffers already open in another pane instead of opening them in the active pane. (#63306; thanks WoodyWoodsta)close_panel_on_toggle setting to the Settings UI and improved its documentation. (#63548; thanks mateioprea)folder_indicator setting for showing disclosure chevrons and folder icons together in the Project Panel, Outline Panel, and Git Panel. (#62393; thanks dongdong867).editorconfig files. (#63323).dockerignore files displaying a generic icon instead of the Docker icon in the bundled icon theme. (#63398; thanks tech-dipesh): in Python. (#63125; thanks dmitriegorov16)url. (#62818; thanks porada)${ shell variable reference on Windows. (#63446; thanks 39ali){ "search": { "search_on_type": false } } to restore the previous behavior. (#62506)
Home Assistant 2026.9! 🎉
I’ll be honest: Modbus has never been the flashiest part of Home Assistant. It quietly powers solar inverters, heat pumps, and energy meters, but only if you’re comfortable hand-writing your own register map in YAML, a real wall that’s kept a huge category of devices out of reach. This release finally makes room on the bus: integrations that already know how a device talks over Modbus, sharing a single connection instead of fighting over it, so you simply pick your device in the UI like anything else in Home Assistant. It won’t show up in a screenshot, but modernizing Modbus is hands-down my favorite change this release. 🔧
I’m also really looking forward to jumping on the new Cloud voice processing myself and putting it through its paces. We’re a household with a non-English main language, and if you’ve ever run a private voice assistant in one, you know exactly how fast accents and background noise trip things up. This new speech-to-text engine specifically targets those pain points, so I’m very curious to see how it holds up against my own accent. 😉
And there’s plenty more: active alerts and favorites for the Security dashboard, a shared Sources panel for History and Activity, Activity that finally explains why something changed, a brand new network map for Matter, charts you can now navigate by keyboard and sound, and 13 new integrations! 🚀
One more thing before you dive in: we’re at IFA Berlin this weekend! It’s one of the largest consumer electronics expos out there, running September 4 to 8, 2026, and the Open Home Foundation has its own booth in the Smart Home hall: Hall 1.2, stand 1.2-153. If you’re around, come find us and say hi. 👋
Enjoy the release!
../Frenck
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, @Diegorro98, @jan-tdy, @RaHehl, and @farmio for putting effort into tweaking its contents. Thanks to them, these release notes are in great shape. ❤️
Home Assistant Cloud is an essential part of funding the Open Home Foundation. We’re so thankful for all the support from our subscribers, and from the start we’ve always been clear: this isn’t just a donation to Home Assistant, we want it to provide real benefits to subscribers. Together with Nabu Casa, we’ve been constantly working to make Cloud better, and here are some useful recent additions.
A new addition that should help security-conscious Home Assistant Cloud subscribers is the ability to better see who is attempting to log into your instance. In the past, they all looked like local requests, and you may have seen the 127.0.0.1 invalid login attempt message, which wasn’t that helpful. Now the proper IP address gets passed through, so whether that’s you mixing up your passwords when logging in, or some bot trying their luck, you’ll now know better where it’s coming from.
A side benefit of this change is that it’s now possible to use IP banning to make it harder for these malicious actors, which was added to the UI in the previous release. In conjunction with setting up multi-factor authentication (2FA) in Home Assistant, you can add a little extra peace of mind to your home, but that’s not the only Cloud benefit being improved this month.
When we launched Home Assistant Voice Preview Edition, a good amount of the community jumped into running their own private voice assistants in their homes. Building something to rival big tech is still a work-in-progress, but every year we get closer. Today, we’re again asking for our Cloud subscribers to help us test another awesome step forward.
Our friends at Nabu Casa are testing a new speech-to-text engine for Home Assistant Cloud, and it significantly improves the three common places voice processing gets tripped up: accents, background noise, and non-English languages. Many of us around the Foundation have been using it and finding it works great with our sometimes unique accents even in noisy environments.
There are several big changes under the hood, including switching to a new provider Soniox, so it needs to be tested. You’ll still get the same privacy guarantee of no logging, storing, or training on your audio. It’ll be available to test via Labs, with the normal caveat that it may not be a permanent addition, so provide your feedback on the Labs page if it’s the right step forward.
If you’re a Home Assistant Cloud subscriber, you can toggle this on right now by heading to Settings > System > Labs. If you’re not a subscriber, there is a 31-day trial. Speaking of which, there are some big improvements on signing up coming as well.
Signing up for Home Assistant Cloud now begins on a clearer start page: one obvious button to Start your free trial, and a link to Sign in if you already have an account. It also finally shows what you would actually be getting. The old page left you to guess what was behind that button, which, fair enough, didn’t help anyone. Now the features are listed right there, before you even start the trial.
Now confirming your email will automatically log you in to Home Assistant Cloud, so you can immediately set up remote access, voice, and backupsHome Assistant has built-in functionality to create files containing a copy of your configuration. This can be used to restore your Home Assistant as well as migrate to a new system. The backup feature is available for all installation types. [Learn more]. No more logging in after signing up! And as always, the one-month trial requires no payment details.
Home Assistant Cloud is built and run by Nabu Casa, a commercial partner of the Open Home Foundation. Every subscription funds the foundation directly, and with it, the full-time development of Home Assistant, this release included. 😊
In return, you get secure remote access with no port forwarding or VPN, encrypted off-site backupsHome Assistant has built-in functionality to create files containing a copy of your configuration. This can be used to restore your Home Assistant as well as migrate to a new system. The backup feature is available for all installation types. [Learn more] ready to restore your whole system the moment you need them, faster and more accurate speech-to-text and text-to-speech for your own voice assistant, native Amazon Alexa and Google Assistant support, and more. It’s all built with the same respect for your privacy as Home Assistant itself: no ads, no data harvesting, just a service that keeps Home Assistant independent.
If you have been thinking about a subscription, there has never been an easier moment to try it.
The built-in Security dashboard is getting more love, and this release adds two things people kept asking for, both managed from the same editor.
The new Active alerts section only shows up when something actually needs your attention, like a door left open or a smoke detector going off. You choose which 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] can trigger it, and how serious each one is, as an Alert or a Warning, so a window left open doesn’t get the same red treatment as an actual smoke alarm. Nothing going on? The section stays out of the way entirely.
Right alongside it, a new Favorites section lets you pin the entities you check most, so your most important doors, locks, or sensorsSensors return information about a thing, for instance the level of water in a tank. [Learn more] sit at the top of the dashboard instead of wherever they happen to fall.
This started as a community-designed concept from @ricardoantoniocm, right down to the severity colors and the pulsing animation for anything that needs attention. It’s part of an Open Home Foundation roadmap opportunity to bring severity to the Security dashboard, and there’s more to come: surfacing these same alerts on the Home dashboard is still on the list for a future release.
Browsing and finding what you’re looking for in History and Activity can be daunting, so… we made it better! Both pages now share a single Sources panel on the left side that merges target picking (floorsA floor in Home Assistant is a logical grouping of areas that are meant to match the physical floors in your home. Devices & entities are not assigned to floors but to areas. Floors can be used in automations and scripts as a target for actions. For example, to turn off all the lights on the downstairs floor when you go to bed. [Learn more], areasAn area in Home Assistant is a logical grouping of devices and entities that represents a room or space in your home, such as the living room, kitchen, or garage. [Learn more], 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]) with filtering by domainEach integration in Home Assistant has a unique identifier: The domain. It is often shown as the first part (before the dot) of entity IDs., device class, and integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more], so you can narrow a whole area down to, say, just its motion sensors. The panel docks to the side and opens automatically on wider screens, and tucks away as a pull-up sheet on narrower ones. Whatever you filter on is remembered the next time you come back.
The two pages still behave the way they always have, on purpose: History waits for you to pick something before it draws a chart, since showing everything at once wouldn’t be very useful (or fast in that regard 😅). Activity keeps showing everything by default, and you can narrow it down with filters alone, no target required.
A couple of smaller improvements come along for the ride: the date range picker is now a single pill with previous and next arrows, and long entity names on the History timeline draw above their bar and truncate to fit, instead of being cut off. Always nice to see the attention to detail.
This follows an Open Home Foundation design discussion on giving History and Activity a shared layout.
Open Activity and you can see exactly what changed: a light turned on, a door unlocked, a blind closed. What you couldn’t see was why. Figuring that out meant guessing which automationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] was responsible, opening it, digging into its trace, and working backward to the 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] that actually triggered it. It got harder still after a recent redesign of the log rows, which traded the sentence that used to explain where an entry came from for showing an entity’s area and device instead, so even that small hint disappeared.
Selecting any row in Activity now opens a details dialog that lays out the full story, read top to bottom: what started it (a person, a state change, a schedule, an integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more], or a restart), the automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] or scriptsScripts are components that allow you to specify a sequence of actions to be executed by Home Assistant when turned on. [Learn more] it passed through, and finally the entity’s own change. Every step in that chain is clickable, opening the entity behind it or, for automations, its trace directly. Timestamps go down to the millisecond, so even events that landed in the same second keep their correct order.
Zigbee (through ZHA), Z-Wave, and Bluetooth have shown you a map of how their devices connect to each other for a while now. 🗺️ MatterMatter is an open-source standard that defines how to control smart home devices on a Wi-Fi or Thread network. [Learn more] never got the same treatment in Home Assistant, even though the data existed all along, just not here: the Matter Server has its own working network map, tucked away in a separate web interface most people never open.
The Matter panel now has a Show map button that brings that same picture right into Home Assistant, using the same graph experience you already know from the other protocols. It shows the full picture: which devices talk 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 which over Wi-Fi, which ones are routers or “border routers”A Thread border router forwards data packets between your local network and the Thread network. This enables smart home devices within a Thread network to communicate with IPv6-capable devices in your local network. A Thread border router is connected to your network either via Wi-Fi or Ethernet and uses its radio frequency (RF) radio to communicate with the Thread mesh network. In case of Matter, the data that is forwarded is encrypted. Examples of Thread border routers are the Nest Hub (2nd gen), the HomePod mini, and the Home Assistant Connect ZBT-2 together with the OpenThread Border Router app. [Learn more] versus battery-powered end devices, and the path from Home Assistant to each one. Border routers and access points are named from things you’d actually recognize, like their network host name or Wi-Fi network name, instead of a serial number. Link color tells you the transport, Thread or Wi-Fi, and the thickness and direction reflect the signal strength on each side of the connection.
If your Matter server is a bit older and doesn’t support this yet, the page tells you so instead of just failing, so you know to update rather than assume something’s broken.
This closes out an Open Home Foundation roadmap opportunity to bring Matter’s network map in line with the other protocols.
The tile card keeps gaining more ways to control an 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] without opening its more-info dialog, and this release adds three, all from the same contributor.
Lights get a new Light effect feature, so you can pick and preview an effect, like Rainbow, directly from the tile.
Vacuums get a new Vacuum fan speed feature, so you can switch between fan speeds, like min, medium, high, or max, right alongside the existing start, stop, and dock commands.
And the existing Target humidity feature, previously limited to humidifiers, now also works with ClimateThe Climate entity allows you to control and monitor HVAC (heating, ventilating, and air conditioning) devices and thermostats. [Learn more] entities that support humidity control, using the step size your device reports instead of a fixed one.
All three come with matching tile card suggestions, so Home Assistant offers to add them automatically when they make sense for an entity.
Thanks to @pcan08 for all three!
One more tile card fix: with the Feature position set to Inline, only the first feature used to show up, and the rest were silently dropped. Now the first one sits next to the entity name as before, and the others appear below it in two columns.
Thanks to @JulianHock for that one!
Modbus devices, like solar inverters, energy meters, and heat pumps, have long been supported in Home Assistant through the 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]-based Modbus integration, where you hand-write a register map for your device yourself. That still works and isn’t going anywhere, but it puts the burden of understanding a device’s protocol on every user. This release lays the groundwork for a different way: integrations that already know how a device talks over Modbus, so you pick your device in the UI, the same as any other integration.
The first integrations built this way are already here: Fronius gained optional Modbus TCP (SunSpec) support, adding per-string solar data — current, voltage, power, and lifetime energy for each MPP tracker — that its existing local HTTP API doesn’t expose. It shares its connection with anything else talking to the same inverter, which matters in practice: some Fronius models only accept a handful of simultaneous Modbus sessions. Sofar Inverter Modbus and Flexit are built the same way.
For the full story, including the new standalone modbus-connection library and how to build your own integration on top of it, read Modernizing Modbus in Home Assistant on the developer blog. Underneath, it talks to devices through tmodbus, a modern, fully typed Modbus library.
Thanks to Paulus (@balloob) for pushing this forward, @wlcrs for tmodbus, the library it’s built on, @farmio for Fronius, @darkrain-nl for Sofar Inverter Modbus, and @troelde for Flexit!
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:
Besen, added by @moryoav
Connect Besen EV chargers to Home Assistant over Bluetooth Low Energy, using Home Assistant’s built-in Bluetooth support or an ESPHome Bluetooth proxy. It works with the Besen BS20 charging station and other Besen chargers that use the same protocol.
Collection image, added by @karwosts
Turn a folder from a media source into a dynamic image entity. Home Assistant picks a random picture from the folder, so you can show a changing image on a dashboard or use it as a view background.
Flow-it, added by @albertogeniola
Monitor and control your Flow-it ventilation system from Home Assistant. Adjust the fan speed, switch between preset modes such as Auto and Boost, and bring it into your automations alongside your other smart home devices. The integration connects to the device on your local network and supports automatic discovery.
Hot Spring, added by @Moustachauve, launching at 🏆 platinum quality
Monitor and control a Hot Spring spa equipped with the HotSpring Connected Spa Kit 2 module, directly over your local network.
ISEO Argo BLE, added by @FezVrasta
Control an ISEO Argo Bluetooth smart lock, common on armored doors in Italy and Switzerland, syncing its access log into the Home Assistant logbook and managing its users through actions. Home Assistant appears to the lock as its own gateway, polling it locally over Bluetooth.
LibreNMS, added by @mib1185
Bring your LibreNMS network monitoring instance into Home Assistant. This initial release adds a binary sensor for the online status of each monitored device, with alerts and more sensor data planned for later.
NexBlue, added by @nexblue-maintainer
Connect a NexBlue EV charger account to Home Assistant. It discovers the chargers on your account and provides read-only sensors for charging state, power, session and lifetime energy, and other electrical and diagnostic values. Charging controls are planned for a future release.
Ridder HortiMaX Pro, added by @wildekek
Bring measurements from a Ridder HortiMaX Pro greenhouse controller into Home Assistant, including temperatures, humidity, vent and screen positions, irrigation volumes, and energy use. The integration is read-only, so your growing decisions stay fully in the controller’s hands. It’s the same kind of controller running the greenhouses at Amsterdam’s Hortus Botanicus, one of the oldest botanical gardens in the world, which we visited earlier Read the full story in our newsletter.
Samsung TV via ExLink, added by @balloob, launching at 🥈 silver quality
Control Samsung TVs through their RS-232 serial port, which Samsung markets as ExLink, using a serial cable, a USB-to-serial adapter, or an ESPHome-based serial proxy. Talking directly to the TV’s serial port makes control fast and reliable, and it also works with TVs that lack smart features or a network connection.
Silla Prism, added by @ebaschiera
Monitor a Silla Prism EV wallbox over its local MQTT API, with sensors for charging status, power, current, voltage, and session and lifetime energy. Setup only needs the MQTT topic your Silla app already shows you. Charging controls are planned for a future release.
Sofar Inverter Modbus, added by @darkrain-nl
Connect a Sofar Solar inverter to Home Assistant over Modbus TCP, either directly or through a Modbus TCP bridge. Setup automatically detects your inverter model, and it works with both PV-only and hybrid inverters with battery storage.
Specialized Turbo, added by @JamieMagee
Connect a Specialized Turbo e-bike over Bluetooth Low Energy, covering the TCU1 and TCX1 through TCX4 models, with detailed ride and battery telemetry. Encrypted bikes can sign in through your Specialized account or use a manually entered key, and Home Assistant manages the Bluetooth connection itself without storing your password.
Tonewinner, added by @emma-sg, launching at 🥈 silver quality
Control Tonewinner AV processors, receivers, and amps over an RS-232 serial connection, using a USB-to-serial adapter or an ESPHome-based serial proxy.
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:
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:
get_prices action to fetch electricity prices for a given period, handy for building your own price charts or automations that react to tomorrow’s rates. Thanks, @petschni!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:
3 integrations reached platinum 🏆
1 integration reached gold 🥇
1 integration reached silver 🥈
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:
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:
There is even more packed into this release. Here are some of the other changes worth a mention:
attributes option is now fully templatable, cutting down on repeated Jinja2 templates.conditions option. When set, the conditions block all updates to the entity it’s attached to.Rebuilding automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] around the sun has been a slow-burn project, and this release wraps it up. 2026.7 replaced the old, offset-heavy sun triggerA trigger is a set of values or conditions of a platform that are defined to cause an automation to run. [Learn more] with dedicated ones for sunrise, sunset, solar noon, solar midnight, dawn, dusk, and elevation changes, plus matching conditionsConditions are an optional part of an automation that will prevent an action from firing if they are not met. [Learn more] like is up, is night, and twilight. 2026.8 then added a time-based offset option to those triggers, the same way the calendar trigger already works, so you can fire an automation a set amount of time before or after a sun event.
This release adds the last of it to the Sun integration: four new conditions and eight matching triggers for golden hour, blue hour, midnight sun, and polar night. Golden hour and blue hour are the warm and cool light either side of sunrise and sunset, handy for automations that match your lighting to the mood outside, or close the blinds before direct sun hits a room. Each one can be limited to morning, evening, or either.
Farther from the equator, midnight sun and polar night cover the more extreme stretches of the year: the sun staying above the horizon for a full day around midsummer, or below it for a full day around midwinter. Both now have their own condition and start and end triggers too, so automations that only make sense at high latitudes finally have something to hook into. Documentation for the full set is still catching up.
Thanks, @emontnemery!
Making Home Assistant work for everyone isn’t a one-off project for us, it shows up release after release. Better color contrast and clearer buttons landed in 2025.8, clearer status indicators for people who can’t rely on color alone arrived in 2026.7, and this release, it’s charts’ turn.
Charts render straight to a single image, which means every data point on them has been invisible to screen readers and unreachable by keyboard. If you rely on either, a chart in Home Assistant might as well not have been there at all.
That changes this release. Tab into a chart and it becomes a real focus stop: the arrow keys walk you through it point by point, and a live region announces the time and value of each one to your screen reader. Press H at any point to bring up a list of every shortcut, styled to match your own theme.
Here’s the best part: as you move through a chart, Home Assistant also plays a short tone for each point, rising and falling with the data. You don’t just hear the individual numbers, you hear the shape of the whole trend, like a little melody. 🎵 It plays for anyone navigating a chart by keyboard, not only people using a screen reader, since there is no reliable way to know who needs it, so it’s on for everyone.
This works on your line and bar charts, including the device breakdown on the Energy dashboard. A few more specialized ones, like timelines, sankey diagrams, and network graphs, aren’t covered yet.
Thanks to @MindFreeze for bringing this to charts!
Serial joins the other protocol panels under Settings > Connectivity, the same recognition infrared and radio frequency got over the last two releases. Once anything is using a serial port, whether that’s a USB dongle like a Zigbee or 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] radio, or an appApps are additional standalone third-party software packages that can be installed on Home Assistant OS. [Learn more] talking to one, the new Serial page lists it.
It splits what it finds into three groups: ports actually in use by an integration or app, ports that are connected but not used by anything, and ports something expects but that aren’t currently plugged in. A status banner at the top gives you the numbers at a glance, so if a stick has come loose or an app lost its connection, you see it the moment you open the page instead of hunting through logs.
This rounds out the trio planned in an Open Home Foundation roadmap opportunity: serial, infrared, and radio frequency all have their own place in Settings now. Documentation for all three is still on its way.
Thanks to @puddly, who built this end to end, panel and all!
MQTT got a settings page of its own this release too, sitting right alongside Serial and Bluetooth in Connectivity instead of hiding its tools behind the integration’s options. A status banner at the top shows whether the broker is online and how many devices it’s found, with quick links to the devices and entities on your network. Discovery options and the broker connection settings each get their own row instead of sharing one options flow, and a new Publish a packet tool lets you send a test message, topic, QoS, and retain flag included, straight from the page, with a code editor for the payload. The topic subscribe view also now formats incoming messages as code, with a copy button. Thanks, @jbouwh!
The Storage page in Settings has always shown which network shares you have connected, like a NAS for backupsHome Assistant has built-in functionality to create files containing a copy of your configuration. This can be used to restore your Home Assistant as well as migrate to a new system. The backup feature is available for all installation types. [Learn more] or media, but not how full each one actually was, so there was no early warning before one quietly ran out of room.
Each active mount now gets a small usage bar and a “{used} of {total} used” line. Rows appear immediately, and each bar fills in as soon as its own request comes back, so one slow or unreachable share never holds up the rest of the list. The bar also changes color as it fills, amber past 85% used and red past 95%, so you get a heads-up before you actually run out of space. A mount that’s currently unreachable just shows no usage bar; it already gets its own warning treatment.
Thanks to @MindFreeze and @silamon for keeping an eye on this!
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:
The deprecated fireplace mode switch entity has been removed. If you have automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] or scriptsScripts are components that allow you to specify a sequence of actions to be executed by Home Assistant when turned on. [Learn more] that use switch.<device>_fireplace_mode, use the climate.set_preset_mode action on the Flexit climate entity with preset_mode: fireplace instead.
(@magnusoverli - #179272) (Flexit Nordic (BACnet) documentation)
KNX exposes no longer send an entity’s first value to the KNX bus. Previously, this depended on timing: if the entity already had a value when the expose was set up, nothing was sent, but if the value arrived later, it was sent to the bus right away.
Now, both cases behave the same way. The first value is adopted locally without sending a telegram, but stays available for read requests and periodic sending. Later value changes are still sent as before.
To send the first value right away, turn on Send on initialization for the expose in the KNX panel, or set send_on_init: true in your YAML configuration.
(@Kolbi - #178793) (KNX documentation)
LLM tool names are now prefixed with the domain of the integration that offers them. For example, GetLiveContext becomes homeassistant__GetLiveContext and HassTurnOn becomes intent__HassTurnOn. If you have a custom prompt that names a tool directly, update it to use the new prefixed name.
Updating a persistent notification that already exists now triggers an update_type of updated instead of added. If you have an automationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] that triggers on an update_type of added to catch every new or changed notification, add updated to the list of types it triggers on.
(@davidlang42 - #171067) (Persistent Notification documentation)
The smart detection switches (for example Detections: Person, Detections: Vehicle, and the audio alarm toggles) are no longer hidden while recording is disabled. They now stay available and follow the same public API as the other camera configuration switches. Their entity IDs and what happens when you toggle them are unchanged.
(@RaHehl - #174963) (UniFi Protect documentation)
UniFi Protect 7.2.105 or newer is now required. On an older version, the integration stops setting up and tells you to update. Update UniFi Protect, then reloadApplies the changes made to Home Assistant configuration files. Changes are normally automatically updated. However, changes made outside of the front end will not be reflected in Home Assistant and require a reload. the integration.
Installing an updateAn update entity is an entity that indicates if an update is available for a device or service. [Learn more], skipping an update, and clearing a skipped update now require an administrator account. These are configuration-level actions, so they are now restricted to admins, like other sensitive actions in Home Assistant.
AutomationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] are not affected, because they run without a user context. A scriptScripts are components that allow you to specify a sequence of actions to be executed by Home Assistant when turned on. [Learn more] runs in the context of the user who started it, so a script that installs or skips an update now fails when a non-admin user starts it. Trigger it from an automation instead, or start it as an admin.
The deprecated battery_level property has been removed from the base vacuum entity. All core vacuum integrations were already migrated in Home Assistant 2026.8. If a custom integration still sets this property, it no longer reports a battery level; add a separate battery sensor instead.
The Z-Wave actions to manage lock users and credentials (set_user, delete_user, delete_all_users, set_credential, delete_credential, and delete_all_credentials) now require an administrator account.
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:
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.9.
Global round-the-clock vendor-direct support for Proxmox Virtual Environment, Proxmox Backup Server, and Proxmox Datacenter Manager goes live October 19, 2026. A new Kingston, Ontario subsidiary provides localized sales, administrative, and business-hours technical support across all North American time zones.
VIENNA, Austria, and KINGSTON, Ontario, Canada – September 02, 2026 – Proxmox Server Solutions GmbH today announced the expansion of its enterprise support to 24/7 coverage, effective October 19, 2026, alongside the launch of Proxmox North America Inc., a new subsidiary headquartered in Kingston, Ontario, Canada.
The 24/7 expansion follows sustained growth in Proxmox's installed base, now exceeding 2.3 million active Proxmox Virtual Environment servers worldwide and increasing demand across cloud, healthcare, government, finance, and enterprise sectors for continuous, direct-from-vendor support coverage. With Proxmox's global engineering and support organization having scaled substantially over recent years, 2026 is the right moment to extend the support offering to around-the-clock availability without compromising the engineering depth that customers expect from Proxmox.
The Canadian hub complements this global capability with a dedicated local presence for North America. A team of Proxmox infrastructure experts handles sales, contract administration, procurement support, and business-hours technical assistance across all North American time zones.
Bill Hughes, appointed CEO of Proxmox North America Inc., has spent over a decade in the open-source infrastructure and enterprise IT space, working closely with both vendors and end customers to deploy large-scale virtualization solutions.
"This is a natural next step," said Tim Marx, COO of Proxmox Server Solutions GmbH. "Our support team has grown significantly over the last few years, and the demand from customers across sectors including cloud, healthcare, government, education, finance has been consistent: they want direct, vendor-backed, around-the-clock support that doesn't depend on someone's local business hours. Making 24/7 a standard part of our enterprise offering is the logical move. It removes one of the last reasons organizations hesitate to put open-source infrastructure at the core of their production stack."
"The Kingston team is an integrated part of the global Proxmox support organization," said Bill Hughes, CEO of Proxmox North America Inc. It provides North American customers with a local entity for procurement and contracts, a team on your clock for day-to-day engagements across Eastern through Pacific, and a direct line into the same engineering bench that supports Proxmox globally."
24/7 Enterprise Support
Starting October 19, 2026, Proxmox's enterprise support offering expands to continuous, around-the-clock coverage for all customers worldwide:
Availability by tier:
Proxmox North America Inc.
The team operates within Proxmox's global support and engineering organization headquartered in Vienna, Austria, which continues to drive product development and the global roadmap.
Global continuity and frictionless transition for existing clients and partners
###
About Proxmox Server Solutions GmbH
Proxmox Server Solutions GmbH provides powerful, intuitive open-source server software that guarantees vendor independence and minimizes total cost of ownership. Enterprises of all sizes rely on the company’s reliable vendor support, certified training services, and a global network of 3,000+ integration partners to ensure business continuity. More than 60,000 enterprises worldwide hold active Proxmox support plans to secure their mission-critical IT. Established in 2005, Proxmox Server Solutions GmbH is headquartered in Vienna, Austria, with its subsidiary Proxmox North America Inc. based in Kingston, Ontario.
About Proxmox North America Inc.
Proxmox North America Inc. is the North American subsidiary of Proxmox Server Solutions GmbH, headquartered in Kingston, Ontario, Canada. It provides localized sales, enterprise technical support across North American business hours, certified training, contract administration, and consulting for Proxmox solutions across the United States and Canada. The team operates as part of Proxmox's global technical enterprise support organization.
Contact: Proxmox Server Solutions GmbH, press@proxmox.com
nginx-1.31.5 mainline version has been released, featuring control API, predicate locations, and the ngx_http_json_module.
njs-1.0.1 version has been released, with fixes for access control bypass vulnerability in js_access (CVE-2026-18329), worker process crash vulnerability in ngx.fetch() (CVE-2026-78222), and heap buffer overflow vulnerability in xml.exclusiveC14n() (CVE-2026-78689).
The Stable channel has been updated to 152.0.7977.75/.76 for Windows and Mac and 152.0.7977.75 for Linux, which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log
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 26 security fixes. Please see the Chrome Security Page for more information.
[N/A][522307103] Critical CVE-2026-84353: Use after free in Shared Tab Groups. Reported by Google on 2026-06-10
[N/A][546260492] Critical CVE-2026-84352: Use after free in WebGL. Reported by Google on 2026-08-14
[N/A][498839176] High CVE-2026-84354: Incorrect authorization in FileSystem. Reported by Google on 2026-04-02
[N/A][514078656] High CVE-2026-84359: Information leak in Skia. Reported by Google on 2026-05-17
[N/A][523208474] High CVE-2026-84357: Improper input validation in Omnibox. Reported by Google on 2026-06-12
[N/A][533534913] High CVE-2026-84324: Use after free in Proxy. Reported by Google on 2026-07-10
[N/A][537105664] High CVE-2026-84349: Use after free in Browser. Reported by Google on 2026-07-21
[TBD][547936520] High CVE-2026-84326: Uninitialized resource in V8. Reported by Jihyeon Jeong (Compsec Lab, Seoul National University / Research Intern) on 2026-08-17
[N/A][549311485] High CVE-2026-84333: Use after free in Dawn. Reported by Google on 2026-08-19
[TBD][551593376] High CVE-2026-84351: Buffer overflow in GPU. Reported by Cassio Lima on 2026-08-24
[N/A][553117928] High CVE-2026-84325: Improper input validation in DataTransfer. Reported by Google on 2026-08-26
[N/A][498710886] Medium CVE-2026-84328: Missing authorization in FileSystem. Reported by Google on 2026-04-01
[N/A][501679156] Medium CVE-2026-84347: Use after free in WebRTC. Reported by Google on 2026-04-11
[N/A][502411391] Medium CVE-2026-84323: Missing authorization in FileSystem. Reported by Google on 2026-04-14
[N/A][511774376] Medium CVE-2026-84355: Incorrect authorization in Navigation. Reported by Google on 2026-05-10
[N/A][514006886] Medium CVE-2026-84358: Improper privilege management in Downloads. Reported by Google on 2026-05-17
[N/A][514489238] Medium CVE-2026-84332: Incorrect authorization in SiteSettings. Reported by Google on 2026-05-19
[N/A][517091927] Medium CVE-2026-84330: UI misrepresentation in FullScreen. Reported by Google on 2026-05-27
[N/A][517798926] Medium CVE-2026-84334: Incorrect authorization in Chromoting. Reported by Google on 2026-05-29
[N/A][518100026] Medium CVE-2026-84348: Information leak in MediaCapture. Reported by Google on 2026-05-30
[N/A][522302504] Medium CVE-2026-84335: Incorrect authorization in TabStrip. Reported by Google on 2026-06-10
[N/A][498725213] Low CVE-2026-84327: Incorrect authorization in Autofill. Reported by Google on 2026-04-01
[N/A][498850269] Low CVE-2026-84329: Confused deputy in CredentialProvider. Reported by Google on 2026-04-02
[TBD][503787232] Low CVE-2026-84356: UI misrepresentation in FullScreen. Reported by Francesco Topol (k4tedu) on 2026-04-18
[N/A][513713427] Low CVE-2026-84350: Use after free in TabStrip. Reported by Google on 2026-05-16
[N/A][521753402] Low CVE-2026-84331: Incorrect authorization in Actor. Reported by Google on 2026-06-09
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.
Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.
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
Note
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: v2.16.0...v2.16.1
Thanks to @mwpastore for adding this!
UpSnap can now automatically track changing IP addresses. For devices with IP tracking enabled, UpSnap periodically scans the local subnet with nmap, matches discovered hosts by MAC address, and updates the stored IP when a device is found at a new address.
We do not recommend anything lower than 1 minute. Depending on the amount of devices you have added to UpSnap, the scan duration will increase. Every 30 minutes is plenty for most users.