Home Assistant 2025.9! 🎉

But before we dive into this release: Did you see we launched a new product? 👀

We’ve introduced the Home Assistant Connect ZWA-2, the ultimate way to connect Z-Wave devices to Home Assistant. You can read all about it in our announcement blog 📰 or re-watch the product launch live stream on YouTube 📺.

It was a busy month, as we also had two new Works with Home Assistant program partners joining this month as well: AirGradient and Frient! 🎉

While the above was happening this month, as if the project wasn’t already busy enough, we kept on pushing to prepare for this release; and it is an absolute massive one! 🤯

This month introduces a new experimental Home dashboard, which aims to become the new default dashboard for Home Assistant in a future release. A first iteration, of which we love to see your feedback and input on. As you know, we develop and iterate in the open. Give it a shot and let us know what you think!

Talking about dashboards, my personal favorite card is definitely the tile card; it is just so versatile. And this release brings in a staggering amount of new features for it! Most notably, the ability to add a trend graph to the tile card! 📈

I’m the most excited about the visual changes to the automation editor this release brings: a sidebar. It is a huge and very visible change, that just makes so much sense. This release denotes the start of a whole series of improvements to the automation editor in this, and upcoming releases. As automations make a smart home feel magical, I personally can’t wait to see how this evolves. 🤖

Enjoy the release!

../Frenck

• Automation editor sidebar
• Introducing the Home dashboard
• New tile card features
  • Trend chart
  • Media player controls
  • Bar gauge
  • Fan direction and oscillation controls
  • Buttons
  • Valve open/close and position controls
  • Setting the date
• Integrations
  • New integrations
  • Noteworthy improvements to existing integrations
  • Integration quality scale achievements
  • Now available to set up from the UI
  • Farewell to the following
• Other noteworthy changes
  • Analog clock
  • Storage insights
• Patch releases
  • 2025.9.1 - September 5
  • 2025.9.2 - September 12
  • 2025.9.3 - September 13
  • 2025.9.4 - September 19
• Need help? Join the community!
• Backward-incompatible changes
• All changes

Automation editor sidebar

On this year’s Home Assistant roadmap, we have set the goal of making automations easier to create. We have big plans, all based on tons of research, and with this release… we are shipping the first part of all this work, with the intent to gradually add more improvements over multiple releases!

This release tweaks the automation editor user interface experience by introducing a sidebar! If you select an item in your automation, instead of that item expanding, it will open a new sidebar to the right with the settings for that selected item.

This allows you to keep an overview of your automation on the left side of your screen, while you can tweak its behavior on the right. Of course, we have thought of smaller screens as well. On mobile, instead of the sidebar, a sheet will pop up at the bottom of the screen. This pop-up is also resizable, making it easier than ever to edit an action while reviewing your triggers.

Besides the sidebar, we have made tons of other little improvements as well. Tiny layout and styling changes that you will definitely notice as they really help with the overall readability. For example, small lines and borders around grouped elements have been added, making it easier to distinguish between different parts of your automation. Oh! And drag-and-drop support is now available on mobile! 🎉

Introducing the Home dashboard

Over the past year, we have focused on dashboards and their capabilities a lot. We’ve looked at a lot of your dashboards you’ve shared on socials, and talked to many of you about how you organize all your smart home devices and services. The goal? Making dashboards faster and easier to create, while still making them very customizable.

With this release, we’re introducing a brand-new Home dashboard. The purpose is simple: to give you easy access to the right information at the right time.

The dashboard adapts to your Home Assistant experience level: powerful enough for advanced users, yet approachable for newcomers. We’re working to have it earn its name, and hope it will eventually become your new Home page. As always, it’s optional; you can always pick your own dashboard. This is the first iteration, and we’ll continue developing it in the open.

When you first open the Home dashboard, it gives you a quick way to navigate to useful summaries for your light, climate, security, and media devices. You can also browse by areas, getting an overview of all the devices and services associated with that part of your home.

We’re also introducing Favorites. You can pin any entity to the top, whether it’s a light, climate, or a person. We’d love to see what you choose (more on this in the future).

The Home dashboard is not just about quick control. It also brings insights and information about your home. This first release includes weather and energy cards. It’s a simple start, and we have a lot of ideas to explore with you. For example, helping you create your first automation, or show discovered devices.

For now, the Home dashboard is considered experimental. Configuration options are limited, and it’s guaranteed to evolve. It won’t appear automatically, and if you want to try it you’ll need to add it manually in the dashboard settings, by adding a new “Home” dashboard.

New tile card features

The tile card is the most versatile card we have in our arsenal of cards for our dashboards.

One superpower of the tile card is its “features”, which are small additions where you can add quick interactions to these cards. For example, a slider to control the brightness of a light or buttons for the speed presets of a fan. Features have been extended quite a bit in this release by a dedicated group of community members.

Trend chart

This release, an absolute banger is the addition of the trend chart features for tile cards created by @MindFreeze.

This feature adds a handy quick graph to the tile card, showing the history of a specific entity over time. For this initial version, the time window shown is 24 hours.

Media player controls

@timmo001, added tile card features for media player controls and volume! This makes the tile card now a viable alternative to the media player card. Awesome!

Bar gauge

A new tile card feature, made by @MindFreeze: The bar gauge!

For this initial version, it works with sensors that use a percentage (%) for their unit of measurement. This makes the card great, for example, for a battery overview dashboard. Nice work!

Fan direction and oscillation controls

Thanks to @pcan08 we now have a tile card feature to control fan direction and oscillation!

Buttons

Thanks to @dhoeben we now have a tile card feature for buttons! He added these buttons for automation, script, and button entities. The text can be changed to display standard button text or custom text.

Valve open/close and position controls

Thanks to @timmo001 we now have a tile card feature to control the open/close and the position of valves.

Setting the date

@timmo001 continued and also added a new tile card feature to support date and datetime entities (including the input datetime helpers). It allows you to add a feature that allows for setting a date.

Integrations

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

New integrations

We welcome the following new integrations in this release:

• Aladdin Connect, added by @swcloudgenie
  Control and monitor your Genie Aladdin Connect garage doors directly from Home Assistant.
• SEKO PoolDose, added by @lmaertin
  Integrate your SEKO water treatment system of your pool or spa to monitor temperature and chemical levels.
• Sleep as Android, added by @tr4nt0r
  Connects the Sleep as Android app to Home Assistant, allowing you to trigger automations based on alarm clock or sleep cycle events.
• ToGrill Bluetooth BBQ thermometers, added by @elupus
  Connect your ToGrill-compatible Bluetooth grill thermometer and monitor your BBQ efforts to cook steaks to absolute perfection.

Noteworthy improvements to existing integrations

It is not just new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] that have been added; existing integrations are also being constantly improved. Here are some of the noteworthy changes to existing integrations:

• Husqvarna Automower got some nice additions from @Thomas55555! You can now reset cutting blade usage time and track error events with a new event entity. Perfect for keeping track of your lawn mowing robot!
• The Reolink integration now includes speak and doorbell volume controls, plus a chime silent time number entity! Nice @starkillerOG!
• You can now send notifications with the PlayStation Network integration! Send direct messages to your friends! Thanks, @tr4nt0r!
• Network admins will love @Tomeroeni bringing individual (enable/disable) switch port control to UniFi switches!
• The OpenWeatherMap integration now includes a wind gust sensor, thanks to @gjohansson-ST!
• @kizovinh added support for battery status and online status sensors to the EZVIZ integration, making it easier to monitor your EZVIZ cameras. Nice!
• If you own a Russound RIO device, you can now browse your device’s saved presets directly from the media browser! Thanks, @noahhusby!
• @mbo18 added an absolute humidity sensor to the Awair integration. Nice!
• The Teslemetry integration added charging and preconditioning actions for your Tesla vehicle. Thanks, @Bre77!
• @catsmanac added IQ Meter Collar and C6 Combiner support to the Enphase Envoy integration. Good work!

Integration quality scale achievements

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

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

• 2 integrations reached platinum 🏆

  • Network UPS Tools (NUT), thanks to @tdfountain
  • Uptime Kuma, thanks to @tr4nt0r

• 1 integration reached bronze 🥉

  • Mastodon, thanks to @andrew-codechimp

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

A big thank you to all the contributors involved! 👏

Now available to set up from the UI

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

The following integration is now available via the Home Assistant UI:

• Bayesian, done by @HarvsG

Farewell to the following

The following integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] is no longer available as of this release:

• Uonet+ Vulcan has been removed. Vulcan has changed their API and their policies forbid using the API from unofficial software.

Other noteworthy changes

There are many more improvements in this release; here are some of the other noteworthy changes:

• Based on feature requests from the community, all modern template entity syntax now supports setting a default entity ID directly in YAML. Thanks @Petro31 for implementing that!
• @Petro31 also added support for two new entity types to the template integration. You can now create your own templated event entities and update entities. Awesome!
• Home Assistant now supports m³/min as a volume flow rate unit. Nice addition @fetzerch!
• Our voice guy @synesthesiam has been busy with some great QoL improvements this release as well.
  • The intent handling for the default agent (non-LLM) now supports fuzzy matching. The technique ensures voice pipelines recognize many more sentences. This improvement is available for English only, while we are looking for ways to extend this to other languages.
  • We now have built-in intents to control the volume of (active) media players! Like the song? Just ask Home Assistant to turn it up a notch!
  • After all that dancing, you might have gotten a little warm. Hence in this release, we now also have intents to control fan speeds. Nice!

Analog clock

In Home Assistant 2025.4, we introduced the clock card, which provides a digital clock display for your dashboards.

For this release, @timmo001 made this card more feature-rich by adding support for displaying the clock in a customizable analog clock style. Nice!

Storage insights

Disk almost full? You might wonder where your storage space has gone…

This release adds disk metrics to the storage configuration panel, letting you see usage at a glance, helping you identify what is taking up space.

You can find these metrics by navigating to Settings > System > Storage, or by selecting the My Home Assistant button down below.

Patch releases

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

2025.9.1 - September 5

• Add support for migrated Hue bridge (@marcelveldt - #151411)
• Add missing device trigger duration localizations (@karwosts - #151578)
• Correct capitalization of “FRITZ!Box” in FRITZ!Box Tools integration (@tr4nt0r - #151637)
• Fix Sonos Dialog Select type conversion (@PeteRager - #151649)
• Fix WebSocket proxy for add-ons not forwarding ping/pong frame data (@felipecrs - #151654)
• Fix, entities stay unavailable after timeout error, Imeon inverter integration (@Imeon-Energy - #151671)
• Bump aiohue to 4.7.5 (@marcelveldt - #151684)
• Update frontend to 20250903.3 (@bramkragten - #151694)
• Require OhmeAdvancedSettingsCoordinator to run regardless of entities (@dan-r - #151701)
• Bump ohmepy version to 1.5.2 (@dan-r - #151707)
• Update Mill library 0.13.1 (@Danielhiversen - #151712)
• Handle match failures in intent HTTP API (@synesthesiam - #151726)
• Bump pyschlage to 2025.9.0 (@dknowles2 - #151731)
• Bump bimmer_connected to 0.17.3 (@rikroe - #151756)
• Fix recognition of entity names in default agent with interpunction (@arturpragacz - #151759)
• Fix enable/disable entity in modbus (@janiversen - #151626)

2025.9.2 - September 12

• Fix XMPP not working with non-TLS servers (@Human - #150957)
• Update SharkIQ authentication method (@funkybunch - #151046)
• Add event entity on websocket ready in Husqvarna Automower (@Thomas55555 - #151428)
• Fix Aladdin Connect state not updating (@hbludworth - #151652)
• Fix support for Ecowitt soil moisture sensors (@blotus - #151685)
• Fix update of the entity ID does not clean up an old restored state (@jbouwh - #151696)
• Revert “Jewish Calendar add coordinator “ (@tsvi - #151780)
• Remove device class for Matter NitrogenDioxideSensor (@lboue - #151782)
• Improve config entry migration for edge cases in Alexa Devices (@chemelli74 - #151788)
• Bump habluetooth to 5.3.1 (@bdraco - #151803)
• Fix KNX BinarySensor config_store data (@farmio - #151808)
• Fix KNX Light - individual color initialisation from UI config (@farmio - #151815)
• Mark Tractive switches as unavailable when tacker is in the enegy saving zone (@bieniu - #151817)
• Allow delay > 1 in modbus. (@janiversen - #151832)
• max_temp / min_temp in modbus light could only be int, otherwise an assert was provoked. (@janiversen - #151833)
• removed assert fron entity in modbus. (@janiversen - #151834)
• Bump pydrawise to 2025.9.0 (@dknowles2 - #151842)
• Bump aioharmony to 0.5.3 (@bdraco - #151853)
• Update pysmarty2 to 0.10.3 (@martinssipenko - #151855)
• fix rain sensor for Velux GPU windows (@wollew - #151857)
• Bump aioecowitt to 2025.9.1 (@edenhaus - #151859)
• Use native_visibility property instead of visibility for OpenWeatherMap weather entity (@bieniu - #151867)
• Bump aiontfy to v0.5.5 (@tr4nt0r - #151869)
• Bump aiolifx-themes to 1.0.2 to support newer LIFX devices (@Djelibeybi - #151898)
• Bump aiovodafone to 1.2.1 (@chemelli74 - #151901)
• Avoid cleanup/recreate of device_trackers not linked to a device for Vodafone Station (@chemelli74 - #151904)
• Fix _is_valid_suggested_unit in sensor platform (@epenet - #151912)
• Bump habluetooth to 5.5.1 (@bdraco - #151921)
• Bump bleak-esphome to 3.3.0 (@bdraco - #151922)
• Bump habluetooth to 5.6.0 (@bdraco - #151942)
• Fix invalid logger in Tuya (@epenet - #151957)
• Fix for squeezebox track content_type (@peteS-UK - #151963)
• Fix playlist media_class_filter in search_media for squeezebox (@peteS-UK - #151973)
• Bump habluetooth to 5.6.2 (@bdraco - #151985)
• Bump yt-dlp to 2025.09.05 (@joostlek - #152006)
• Bump accuweather to version 4.2.1 (@bieniu - #152029)
• Fix HomeKit Controller stale values at startup (@bdraco - #152086)
• Fix duplicated IP port usage in Govee Light Local (@abmantis - #152087)
• Fix DoorBird being updated with wrong IP addresses during discovery (@bdraco - #152088)
• Fix supported _color_modes attribute not set for on/off MQTT JSON light (@jbouwh - #152126)
• Fix reauth for Alexa Devices (@chemelli74 - #152128)
• Bump hass-nabucasa from 1.1.0 to 1.1.1 (@ludeeus - #152147)
• Update frontend to 20250903.5 (@bramkragten - #152170)
• Use position percentage for closed status in Velux (@wollew - #151679)

2025.9.3 - September 13

• Bump habluetooth to 5.6.4 (@bdraco - #152227)

2025.9.4 - September 19

• Bump habiticalib to v0.4.4 (@tr4nt0r - #151332)
• Bump habiticalib to v0.4.5 (@tr4nt0r - #151720)
• Fix bug with the hardcoded configuration_url (asuswrt) (@Vaskivskyi - #151858)
• Fix HomeKit Controller overwhelming resource-limited devices by batching characteristic polling (@bdraco - #152209)
• Upgrade waterfurnace to 1.2.0 (@sdague - #152241)
• Bump aiohomekit to 3.2.16 (@bdraco - #152255)
• Bump bluetooth-auto-recovery to 1.5.3 (@bdraco - #152256)
• Add proper error handling for /actions endpoint for miele (@astrandb - #152290)
• Bump aiohomekit to 3.2.17 (@bdraco - #152297)
• Update authorization server to prefer absolute urls (@allenporter - #152313)
• Bump imeon_inverter_api to 0.4.0 (@Imeon-Energy - #152351)
• Bump pylamarzocco to 2.1.0 (@zweckj - #152364)
• Add La Marzocco specific client headers (@zweckj - #152419)
• Fix KNX UI schema missing DPT (@farmio - #152430)
• Bump pyemoncms to 0.1.3 (@alexandrecuer - #152436)
• Fix Sonos set_volume float precision issue (@PeteRager - #152493)
• Bump opower to 0.15.5 (@tronikos - #152531)
• Bump holidays to 0.80 (@gjohansson-ST - #152306)
• Bump holidays to 0.81 (@gjohansson-ST - #152569)
• Bump asusrouter to 1.21.0 (@Vaskivskyi - #151607)

Need help? Join the community!

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

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

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

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

Backward-incompatible changes

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

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

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:

• Standardize encoding of μ in units of measurement
• The DeviceEntry.suggested_area attribute is deprecated and will be removed

All changes

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

• View downloads
• View release notes

• View downloads
• View release notes

We’re making new frients this week, and they’re bringing an extensive line of Zigbee devices to our Works With Home Assistant program. Each device is tested by our team, ensuring they provide the best experience possible for Home Assistant. Frient is widely available across Europe, and are well-known for their sleek, unobtrusive designs that its customers love for their high Home Approval Factor.

Our newest frient

Based in Denmark, the frient brand was developed by Onics, (formerly Develco Products), and they have years of experience with Zigbee devices. Frient is bringing its proven technology to the Works With Home Assistant program, as well as their Danish design that easily blends into almost any home.

Recent Works With partners have brought Z-Wave, Matter, and even Bluetooth devices to Home Assistant, but it’s been a couple of years 😅 since Zigbee-specific devices have joined the program. Zigbee is one of the most popular open protocols that is used with Home Assistant, with hundreds of thousands of users making use of it today. It’s a proven technology that connects directly to Home Assistant, no cloud or Wi-Fi connection required. Zigbee is a mesh protocol, where some devices act as repeaters, strengthening the network as more are added. It was built from the ground up to power the smart home, and has been optimized to give devices really long (sometimes multi-year) battery life.

All you need to get started with Zigbee in Home Assistant is a Zigbee adapter or ‘stick’, such as the Home Assistant Connect ZBT-1 (wow, we released this in 2022, I wonder when we’re finally going to build a successor? 😉). By plugging the adapter into a USB port on your Home Assistant system, it should then discover the device and add the ZHA integration. After that is set up, you can start adding devices to your Zigbee network.  We’ve even added in a cool new visualization so that you can see how your Zigbee devices interact with each other.

ZHA is built with the support of the Open Home Foundation, and it even has a full-time developer (@puddly) dedicated to improving it and helping certify new Works With partner devices. Your support makes this possible, whether through a Home Assistant Cloud subscription or by purchasing official hardware.

Devices

When your energy company won’t provide your raw usage data, there’s always another way 😉

In case you didn’t know, Works With Home Assistant differs from other certification programs as products are rigorously tested in-house to ensure they work seamlessly out of the box with Home Assistant. Any company joining also commits to providing long-term support and firmware updates while being a positive force in the Home Assistant community. Works With Home Assistant is operated by the Open Home Foundation, and the support of Home Assistant Cloud subscribers funds this work.

Our team has worked extensively with frient to ensure that the following items work seamlessly with Home Assistant.

• frient Motion Sensor Pro

• frient IO Module

• frient Smart Plug Mini

• frient Entry Sensor 2 Pro

• frient Smart Siren UK

• frient Smart Siren EU

• frient Intelligent Keypad

• frient Water Leak Detector

• frient Smart Button

• frient Intelligent Smoke Alarm

• frient Air Quality Sensor

• frient Smart Humidity Sensor

• frient Electricity Meter Interface 2 LED

This is a big portion of frient’s product line, and provides energy monitoring, device control, safety, and security sensors. The frient IO Module is the first certified Zigbee module that can be used to turn low-voltage dumb devices like electric blinds or garage doors into devices that can be controlled by Home Assistant.

There are some great devices here for building a more sustainable smart home. The Electricity Meter Interface 2 LED allows you to get the data off your energy meter and record it into Home Assistant. Another win for sustainability is their use of AA and AAA batteries wherever practical, meaning you can use rechargeables instead of constantly buying and recycling coin cells.

I also selfishly love to see some great UK-specific devices being brought into the program with the frient Smart Siren having both UK and EU versions.

Best frients forever

It’s great to see Zigbee get some high-quality certified Works With Home Assistant devices after a multi-year wait. Frient has put a good deal of work into this launch and are big fans of our work and the community. There are more exciting Zigbee developments to come, so stay tuned!

FAQs

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

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

Q: Ok, so what’s the point of the Works With program?

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

Q: How were these devices tested?

A: All devices in this list were tested using a standard HA Green Hub with the ZBT-1 and with the ZHA integration. We haven’t tested these devices with Zigbee2MQTT, so we would recommend checking their device compatibility documentation. If you have another hub, Zigbee adapter, or 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.

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

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

Part-DB 2.0.2

This upgrade introduces a new web based configuration system. Existing configuration using environment variables will continue to work. If you want to configure these parameters via the WebUI in the future, an additional migration step is required. See the upgrade guide for more information.

Bug fixes

• Properly pass environment variables to Part-DB in jbtronics/partdb1 docker image to prevent startup issues (issue #1006)

Improvements

• Updated translations
• Do not pollute docker error logs with deprecation notices

Full Changelog: v2.0.0...v2.0.1

Changelog

Features

• ab5fa0e: feat: add hindi language (hi-IN) (@seriousm4x)
• f6a208f: feat: use new svelte 5 syntax (@seriousm4x)

Others

• 9ad5314: update deps (@seriousm4x)

Npm dependencies

• 7d5fa68: npm-dep: bump @sveltejs/kit from 2.36.2 to 2.36.3 in /frontend (@dependabot[bot])
• 2d1c64c: npm-dep: bump @sveltejs/kit from 2.36.3 to 2.37.0 in /frontend (@dependabot[bot])
• 6eadc5b: npm-dep: bump daisyui from 5.0.50 to 5.0.51 in /frontend (@dependabot[bot])
• 05a6a54: npm-dep: bump daisyui from 5.0.51 to 5.0.54 in /frontend (@dependabot[bot])
• 10469c8: npm-dep: bump svelte from 5.38.3 to 5.38.6 in /frontend (@dependabot[bot])
• b5ecd4b: npm-dep: bump typescript-eslint from 8.40.0 to 8.41.0 in /frontend (@dependabot[bot])

Part-DB 2.0.1

This upgrade introduces a new web based configuration system. Existing configuration using environment variables will continue to work. If you want to configure these parameters via the WebUI in the future, an additional migration step is required. See the upgrade guide for more information.

Bug fixes (compared to 2.0.0)

• Fixed broken english translations
• Fixed problem that wrong column was sorted after columns were reordered in a table

Full Changelog: v2.0.0...v2.0.1

Part-DB 2.0.0

This upgrade introduces a new web based configuration system. Existing configuration using environment variables will continue to work. If you want to configure these parameters via the WebUI in the future, an additional migration step is required. See the upgrade guide for more information.

Breaking changes

• Part-DB now requires at least PHP 8.2 or higher. If you are still using PHP 8.1 you need to upgrade PHP first
• Nodejs 20 or higher is now required
• The config/banner.md file does not exist anymore. If you wanna customize the banner, either do it via the WebUI or the BANNER env.
• The parameters partdb.sidebar.items, partdb.sidebar.root_node_enable and partdb.sidebar.root_expanded in config/parameters.yaml,
  were removed. You can configure them now directly in the admin interface.

New features

• Introduced capability to configure system settings and info providers via the WebUI. No need to work with environment variables anymore
• Improved emoji dialog for rich text editor

Miscellaneous

• Updated dependencies

Full Changelog: v1.17.4...v2.0.0

Part-DB 1.17.3

Bug fixes

• Pass the proxy related settings to the docker application (issue #1001)

Full Changelog: v1.17.3...v1.17.4

32.0 New Features

• Added a basic plugin manager [FiniteSingularity/PatTheMav/Warchamp7]
• Added opt-in automatic crash log upload for Windows and macOS [PatTheMav/Warchamp7]
• Added Voice Activity Detection (VAD) to NVIDIA RTX Audio Effects, which improves noise suppression for speech, as well as several optimizations to NVIDIA Effects [pkviet]
• Added chair removal option for NVIDIA RTX Background Removal, allowing removal of chairs [pkviet]
• Added Hybrid MOV support [derrod]
  • Brings ProRes support on macOS and HEVC/H.264 and PCM audio support on all platforms

32.0 Changes

• OBS Studio will no longer load plugins built for a newer release of OBS to prevent future compatibility issues [norihiro]
• Added custom OBS widgets in preparation for larger UI updates [derrod/gxalpha/Warchamp7]
• Added preparations for Metal renderer (stay tuned!) [PatTheMav]
• Improved audio deduplication logic to cover more cases of nested scenes, groups, and multiple canvases [pkviet]
• Prevent audio duplication when sources are set to "Monitor and Output" while the monitoring device is also being captured [pkviet]
• Updated the default settings for AMD encoders [rhutsAMD]
• Improved accuracy of chapter markers in Hybrid MP4/MOV [derrod]
• Re-hid the cursor in edit fields on macOS [gxalpha]
• Improved format selection for PipeWire video capture [tytan652]

32.0 Bug Fixes

• Potentially fixed a rare crash on macOS when moving or resizing the OBS window [PatTheMav]
• Fixed a crash with SRT when using an invalid URL [pkviet]
• Fixed a crash when setting non-default pkt_size with SRT [pkviet]
• Fixed a crash in Media Source when playback starts with certain video files [howellrl]
• Fixed rare occurrence of multiview becoming blank [norihiro]
• Fixed SRT reconnection failures [pkviet]
• Fixed overflow texture rendering sRGB-awareness [PatTheMav]
• Fixed incorrect color range property setting for AMD AV1 encoder [rhutsAMD]
• Fixed Hybrid MP4 file splitting not working correctly in some cases [derrod]
• Fixed not being able to capture higher than 60fps with macOS Screen Capture [jcm93]
• Fixed focus not displaying properly in hotkey settings on macOS [gxalpha]
• Fixed the scrollbar appearing invisible in Light and Rachni themes [shiina424]
• Fixed HEVC frame priority not being set correctly in some cases, potentially causing playback errors when dropping frames [dsaedtler]
• Fixed an issue that could result in increases to output latency after temporary encoder stalls [dsaedtler]
• Removed a workaround for older Qt versions that prevented docks from loading correctly while OBS is maximized [RytoEX]

Checksums

OBS-Studio-32.0.0-beta1-Sources.tar.gz: 72d2e06709e1d74a7156dae6d1d597f2e6e7da2ae4ba37d097d73cbc127dc878
OBS-Studio-32.0.0-beta1-Ubuntu-24.04-x86_64-dbsym.ddeb: 673acb9d8408c846d3722545d1667ffa5dad97cccfd6a3e8a2b6c165e77fb06c
OBS-Studio-32.0.0-beta1-Ubuntu-24.04-x86_64.deb: 429e07e28bc8589c38242338e85f251471fd324d51ea7a12268186c40711546f
OBS-Studio-32.0.0-beta1-Windows-arm64-PDBs.zip: d39c3ce52916d306e8b56dc300537d073a054894b1243f632cf75ea5a2a88f1f
OBS-Studio-32.0.0-beta1-Windows-arm64.zip: 61db85892fbb0c95c034a25637557a62af7092742f666720ef4792244c353162
OBS-Studio-32.0.0-beta1-Windows-x64-Installer.exe: d66ec70ce78e2f2524e518ae28abd784b4869c7a3c38f6bc3595a56ba52c3d17
OBS-Studio-32.0.0-beta1-Windows-x64-PDBs.zip: ba7b9812b85313b50f8c67dde4002abd1848cfcdea8498468a2ba20b60bf0543
OBS-Studio-32.0.0-beta1-Windows-x64.zip: 9723fd3a39100de673d3ef770bf71324240912d0f45f9acd8b0db99d96e609a7
OBS-Studio-32.0.0-beta1-macOS-Apple-dSYMs.tar.xz: 940e7aed21dc60ae5d449eb4e15771e49f8d6e668647ca7830f97a94db4dc184
OBS-Studio-32.0.0-beta1-macOS-Apple.dmg: 77ade98d6ca7276a56c0fa393f34468453e5f560c4b42ded50708327cdb8de68
OBS-Studio-32.0.0-beta1-macOS-Intel-dSYMs.tar.xz: 458e173cce7118d58e40317e8bd89fd9fece6308c621223cf640cbc8f98a4b76
OBS-Studio-32.0.0-beta1-macOS-Intel.dmg: 22de072a348f35b20fbd19c432dfd753eeba008f17090f2dd26f6eb0a59b5116

• read-only demo server at https://a.ocv.me/pub/demo/
• docker image ╱ similar software ╱ client testbed

there is a discord server with an @everyone in case of future important updates, such as vulnerabilities (most recently 2025-07-30)

recent important news

• v1.18.9 (2025-08-01) fixed CVE-2025-54796 (Denial-of-Service)
• v1.15.0 (2024-09-08) changed upload deduplication to be default-disabled
• v1.14.3 (2024-08-30) fixed a bug that was introduced in v1.13.8 (2024-08-13); this bug could lead to data loss -- see the v1.14.3 release-notes for details

🧪 new features

• new option chdir to change the PWD (process working-directory) before volumes are mapped 14555d5

🩹 bugfixes

• fix using empty folders as statefile storage (v1.19.6 made this a bit too strict) 0d96786
• holding I/K to scroll through folders quickly now works better 914686e

🔧 other changes

• #717 docker: fix the image repo metadata (thx @EmilyxFox!) 6f08711
• docker: change $HOME to /state 01cf20a d1f7522
  • and use the new chdir option to preserve old config-file semantics 14555d5
  • helps avoid statefiles accidentally landing in /w as a consequence of misconfiguration

🌠 fun facts

• this release was made at RevSpace NL

⚠️ not the latest version!

• Marvel's Avengers - The Definitive Edition: Game crashes to desktop on startup [5350712]

• Certain monitors may display a random flicker when hot plugged over HDMI [5280259]

Links

• Update instructions

Full List of Changes

This release contains the following fixes and changes:

• Updated new WYSIWYG editor with various fixes focused on collapsible block behaviour & interaction. (#5775)
• Updated translations with latest Crowdin changes. (#5759)
• Updated versions of PHP dependencies.
• Updated code to address some remaining PHP 8.4 deprecations.
• Fixed diagrams in ZIP imports not being editable post-import. (#5761)
• Fixed books detaching from shelves on shelf update where users don't have permission to view child books. (#5728)

Bugfixes and minor changes:

• Fixed a crash if loading a custom X.509 private key or certificate fails using implicit FTP over TLS

• Stability improvements when using multi-command input binds.
• Fixed issue where Jonathan Young music kit would loop incorrectly.

• read-only demo server at https://a.ocv.me/pub/demo/
• docker image ╱ similar software ╱ client testbed

there is a discord server with an @everyone in case of future important updates, such as vulnerabilities (most recently 2025-07-30)

recent important news

• v1.18.9 (2025-08-01) fixed CVE-2025-54796 (Denial-of-Service)
• v1.15.0 (2024-09-08) changed upload deduplication to be default-disabled
• v1.14.3 (2024-08-30) fixed a bug that was introduced in v1.13.8 (2024-08-13); this bug could lead to data loss -- see the v1.14.3 release-notes for details

🧪 new features

• #673 add Portuguese translation (thx anonymous!) 4b8c221
  • ...and enable the Polish translation (whoops) 8f235be
• #689 add option to control authentication priority/precedence 543b7ea
• url-parameter ?dl forces file download instead of displaying in-browser 48d6224
• #533 more ways to make the QR-code always-visible in the console 2848941
• #695 option to log invalid xml from clients 28b93d7
• #552 configurable markdown newline behavior 0491123
  • and tweak the styling of monospace in links 6850344

🩹 bugfixes

• #628 FTP-server now accepts connections from IPv6 link-local addresses 978801d
• incorrect assumption that all IPv6 link-local addresses start with fe80 d39c74c
• ftp: fix file rename d40f061
• u2c: couldn't upload files located at the very top of the unix file hierarchy 599e82f
• #699 markdown-editor: fix panic if the table-formatter is executed on something that isn't a table 4c042b3

🔧 other changes

• #696 a volume can be one single file, not just folders aa1c921
• #442 strongly prefer XDG_CONFIG_HOME as config location 3547255
• #691 album-art collected from audio-files can now become folder thumbnails 0b50fde
• allow spaces in more of the comma-separated options d30240b
• docs:
  • mention config requirements for syncing folders with u2c 6cd0a39 59f142c

⚠️ not the latest version!

⚠️ Potential Breaking Changes

Fixed Content Versioning to correctly merge relational data and support all query parameter functionality (#25437)
The following changes should be kept in mind when updating:

1. Relational versioned data now requires explicit field expansion to be included in the response.
2. Invalid data (e.g. Fails validation rules) will error on query
3. Filter conditions now apply to the versioned data instead of the main record
4. For more information, please read the breaking change docs for a full list of changes.

Additionally there will be further breaking changes to USER_CREATED, USER_UPDATED, DATE_CREATED, DATE_UPDATED default values in a followup PR to improve this behavior further.

Check in with #25744 to see more info about the breaking changes.

✨ New Features & Improvements

• @directus/api

  • Fixed Content Versioning to correctly merge relational data and support all query parameter functionality (#25437 by @Nitwel)

• @directus/app

  • Fixed links in WYSIWYG missing underline and pointer cursor styling (#25739 by @Abdallah-Awwad)
  • Added a new field to conditions for clearing hidden fields on save (#25646 by @robluton)

🐛 Bug Fixes & Optimizations

• @directus/app
  • Fixed timestamp fields being incorrectly marked as changed due to timezone mismatch (#25718 by @khanahmad4527)
  • Fixed code button state not updating when exiting code mode in WYSIWYG (#25741 by @Abdallah-Awwad)
  • Added currentItem id check to prevent in-flight api call from returning stale data (#25660 by @robluton)
  • Added RTL support for popper context menu (#25697 by @AlexGaillard)
  • Fixed an issue with focus trap in TinyMCE dialogs within the WYSIWYG editor (#25746 by @formfcw)
  • Upgraded esbuild and Vite (#25737 by @ComfortablyCoding)
• @directus/api
  • Upgraded esbuild and Vite (#25737 by @ComfortablyCoding)
  • Updated nodemailer to us AWS SESv2 (#25730 by @br41nslug)
  • Fixed permissionsCacheable erroring on null operator value (#25753 by @AlexGaillard)
• @directus/types
  • Fixed Content Versioning to correctly merge relational data and support all query parameter functionality (#25437 by @Nitwel)
• @directus/sdk
  • Fixed auth being cleared before login/refresh request succeeds (#25367 by @ComfortablyCoding)

📦 Published Versions

• @directus/app@13.14.0
• @directus/api@30.0.0
• create-directus-extension@11.0.18
• @directus/extensions@3.0.10
• @directus/extensions-registry@3.0.10
• @directus/extensions-sdk@16.0.1
• @directus/schema-builder@0.0.5
• @directus/types@13.2.2
• @directus/sdk@20.0.3

• Restored some grenade lineup visuals.
• Misc clipping fixes.

• Fixed issues with the classic knife's inspect animations.
• Fixed the deploy for the Stiletto knife.
• Fixed the deploy for the Butterfly knife.
• Updated Talon knife inspect while 'fidgeting' to be more responsive.
• Adjusted Flip knife animation when inspecting immediately after deploying.
• Adjusted Bayonet knife animation when inspecting immediately after deploying.

• Fixed a performance regression when creating bullet impact effects.
• View angle velocity now affects spectator target viewmodels the same way it affects local player viewmodels.
• Fixed a case where looping weapon inspects weren't networking to spectators.
• Fixed a bug where matchmaking was avoiding servers playing the nighttime version of Ancient.
• Removed legacy sprite-based shell casing fallback particle effects.
• Fixed case where overlapping smoke clouds would prematurely extinguish molotov fire.

Changelog

Bug fixes

• 0fcd048: fix: device cards not updating (@seriousm4x)

Others

• 7ab8170: remove log (@seriousm4x)

Changelog

Features

• 954c964: feat: Add i18n vi-VN (#1324) (@flashvnn)

Bug fixes

• 8afe2f1: fix: change device.link to string (@seriousm4x)
• 2aef980: fix: search not working, close #1325 (@seriousm4x)

Others

• c9e9248: add vi-VN (@seriousm4x)

Go dependencies

• d028e2d: go-dep: bump github.com/pocketbase/pocketbase in /backend (@dependabot[bot])

• View downloads
• View release notes

• View downloads
• View release notes

Changelog

Features

• 7ef8ba6: feat: Add Bulgarian language (#1319) (@grivanov)

Npm dependencies

• 9205590: npm-dep: bump @sveltejs/kit from 2.34.0 to 2.36.1 in /frontend (@dependabot[bot])
• bb8a854: npm-dep: update (@seriousm4x)

A new major release, FFmpeg 8.0 "Huffman", is now available for download. Thanks to several delays, and modernization of our entire infrastructure, this release ended up being one of our largest releases to date. In short, its new features are:

• Native decoders: APV, ProRes RAW, RealVideo 6.0, Sanyo LD-ADPCM, G.728
• VVC decoder improvements: IBC, ACT, Palette Mode
• Vulkan compute-based codecs: FFv1 (encode and decode), ProRes RAW (decode only)
• Hardware accelerated decoding: Vulkan VP9, VAAPI VVC, OpenHarmony H264/5
• Hardware accelerated encoding: Vulkan AV1, OpenHarmony H264/5
• Formats: MCC, G.728, Whip, APV
• Filters: colordetect, pad_cuda, scale_d3d11, Whisper, and others

A new class of decoders and encoders based on pure Vulkan compute implementation have been added. Vulkan is a cross-platform, open standard set of APIs that allows programs to use GPU hardware in various ways, from drawing on screen, to doing calculations, to decoding video via custom hardware accelerators. Rather than using a custom hardware accelerator present, these codecs are based on compute shaders, and work on any implementation of Vulkan 1.3.
Decoders use the same hwaccel API and commands, so users do not need to do anything special to enable them, as enabling Vulkan decoding is sufficient to use them.
Encoders, like our hardware accelerated encoders, require specifying a new encoder (ffv1_vulkan). Currently, the only codecs supported are: FFv1 (encoding and decoding) and ProRes RAW (decode only). ProRes (encode+decode) and VC-2 (encode+decode) implementations are complete and currently in review, to be merged soon and available with the next minor release.
Only codecs specifically designed for parallelized decoding can be implemented in such a way, with more mainstream codecs not being planned for support.
Depending on the hardware, these new codecs can provide very significant speedups, and open up possibilities to work with them for situations like non-linear video editors and lossless screen recording/streaming, so we are excited to learn what our downstream users can make with them.

The project has recently started to modernize its infrastructure. Our mailing list servers have been fully upgraded, and we have recently started to accept contributions via a new forge, available on code.ffmpeg.org, running a Forgejo instance.

As usual, we recommend that users, distributors, and system integrators to upgrade unless they use current git master.