Release Highlights: Although GeForce Game Ready Drivers and NVIDIA Studio Drivers can be installed on supported notebook GPUs, the original equipment manufacturer (OEM) provides certified drivers for your specific notebook on their website. NVIDIA recommends that you check with your notebook OEM for recommended software updates for your notebook.
Game Ready for ARC Raiders: Headwind Update
This new Game Ready Driver provides the best gaming experience for the latest new games supporting DLSS 4 technology including ARC Raiders: Headwind Update and Arknights: Endfield. In addition, there is Game Ready support for Highguard which features DLSS Super Resolution.
Fixed Gaming Bugs
Total War: Three Kingdoms: Artifacts may be observed during gameplay when Screen Space Reflections is enabled [5745647]
Fixed General Bugs
Color banding observed with SDR content when Windows Automatic Color Management enabled [5754551]
Asus G14 may freeze on startup when Asus Ultimate Mode is enabled [5754849]
This is not the final version, this is a test version. Please report problems and bugs in our issue tracker.
Highlights in OpenWrt 25.12
OpenWrt 25.12.0-rc3 incorporates over 4300 commits since branching the previous OpenWrt 24.10 release and has been under development for over one year.
Only the main changes are listed below. See changelog-25.12.0-rc3 for the full changelog.
General changes
The hardware requirements did not change significantly, most devices supported by OpenWrt 24.10 should also work with OpenWrt 25.12.
Switch package manager from opkg to apk
OpenWrt has transitioned from the traditional opkg package manager to apk (Alpine Package Keeper).
This change brings several advantages:
apk is still maintained, the OpenWrt opkg fork was not maintained any more.
apk supports most features of opkg. Only very few package names changed. The command line arguments of apk are different from the command line arguments of opkg.
For users migrating existing systems, an official opkg to apk cheatsheet is available to ease the transition and map common workflows.
Automatically rebuild firmware images with all currently installed packages
Preserve system configuration during upgrades
This dramatically simplifies upgrades: with just a few clicks in LuCI and a short wait, a custom firmware image is built and installed without manual intervention.
Shell history is preserved
Shell command history is now preserved across sessions by storing it in a RAM-backed filesystem.
Benefits:
Command history is no longer lost between logins
No unnecessary writes to flash storage by default
For users who prefer persistent history storage, this behavior can be changed by editing: /etc/profile.d/busybox-history-file.sh
โ ๏ธ Note: Storing history on flash will increase write cycles and may impact flash endurance over time.
Integration of video feed
The OpenWrt video feed with Qt5 and UI applications is integrated by default.
Wi-Fi scripts in ucode
The wifi scripts were rewritten in ucode.
Target changes
Extend realtek target with support for more switch SoCs like 10G Ethernet switches.
Extend qualcommax target with support for ipq50xx and ipq60xx SoCs.
Added siflower target for Siflower SF21A6826/SF21H8898 SoCs
Added sunxi/arm926ejs subtarget for Allwinner F1C100/200s SoCs
Many new devices added
OpenWrt 25.12 supports over 2180 devices. Support for over 160 new devices was added in addition to the device support by OpenWrt 24.10.
Core components update
Core components have the following versions in 25.12.0-rc3:
Updated toolchain:
musl libc 1.2.5
glibc 2.41
gcc 14.3.0
binutils 2.44
Updated Linux kernel
6.12.66 for all targets
main packages:
cfg80211/mac80211 from kernel 6.18.0
hostapd master snapshot from August 2025
dnsmasq 2.91
dropbear 2025.89
busybox 1.37.0
In addition to the listed applications, many others were also updated.
Upgrading to 25.12
Upgrading from 24.10 to 25.12 should be transparent on most devices, as most configuration data has either remained the same or will be translated correctly on first boot by the package init scripts.
Sysupgrade from 23.05 to 25.12 is not officially supported.
Cron log level was fixed in busybox. system.@system[0].cronloglevel should be set to 7 for normal logging. 7 is the default now. If this option is not set, the default is used and no manual action is needed.
Bananapi BPI-R4: Interfaces eth1 was renamed to sfp-lan or lan4 and the interface eth2 was renamed to sfp-wan to match the labels. You have to upgrade without saving the configuration.
Scratch installs/upgrades
If you wish to start from scratch (always the safest, but also the most work), simply download the pre-built image from the downloads site or from the Firmware Selector to your device. Make sure to create and save a backup, then install the image using sysupgrade -n /tmp/firmware.bin or the LuCI Backup/Flash Firmware, being sure to set "Keep settings and retain the current configuration" to its off position. Restore or reconstruct your configuration using the contents of the backup as a template.
Attended Sysupgrade options
Attended Sysupgrade (ASU) allows you to build a custom image that retains all of your installed packages and their configuration transparently. You need to use one of the three ASU clients that interface with the ASU server to produce this custom image:
Firmware Selector - an online builder that requires you to manually supply it with the packages you wish to have installed. This package list is sent to the ASU server, and a new custom device image is created containing those packages. You may then download and install the image in LuCI Backup/Flash Firmware, but for this you would enable "Keep settings..."
Luci Attended Sysupgrade - the web interface to the ASU server. This tool allows you to choose a new OpenWrt version, then collects the names of the packages on your device and sends them up to the ASU server. LuCI ASU then downloads the created image directly to your device and allows you to install it, without having to do any of the bookkeeping tasks involved with using the Firmware Selector.
owut - a command line package that does the same job as LuCI ASU, but provides more diagnostics and better visibility into what's happening at the various steps before and during the build process.
Both the LuCI ASU app and owut are optional packages in 24.10, so if you have not installed them, they won't be there by default. Use either the LuCI Package Manager to install them, or you can do it from the command line with opkg:
Note that you can install one or the other, or both together, they are completely independent packages.
Upgrades with Firmware Selector
The Firmware Selector does an excellent job of searching through the thousands of available device configurations and getting you to the right place. But, some devices have several variants and possibly different image formats, so if you're unsure about which one you need or which device you're dealing with or anything else, go to the |Firmware Selector support thread and ask away.
Upgrades with LuCI Attended Sysupgrade
The LuCI web interface should be fairly self explanatory. Since you have fairly limited options there that should be pretty obvious, but if anything is unclear or you're unsure about something, go to the LuCI Attended Sysupgrade support thread and ask.
Upgrades with owut
If you choose to use owut, the fact that it's a command line program means you'll need a little more explanation regarding best practices. In any situation, it's always safe to do a check to see what's going on.
$ owut check --verbose --version-to 25.12
... a lot of output ...
This check should show you all the details of what this upgrade entails with regards to the packages available, and will point out any issues with package versions and so on.
Assuming the results of the check look good, you can simply do an upgrade next.
$ owut upgrade --verbose --version-to 25.12
... even more output ...
If you are unsure of anything you see in the check, during the upgrade, or simply have questions, jump on over to the owut support thread on the forum and ask.
Known issues
Users of Zyxel EX5601-T0 devices need to check their WAN interfaces as port was renamed from eth1 to wan.
Microchip LAN969x devices are missing the network driver, so no network ports work.
Itโs time to celebrate what weโve built together, and get excited about whatโs coming next โ at State of the Open Home, our annual look at how weโre championing privacy, choice, and sustainability in the smart home. And this year, weโre doing something new: inviting you to be part of the action in our audience! ๐
Thatโs right, you donโt have to watch from home โ you can join us live in Utrecht, the Netherlands, on Wednesday, April 8.
This yearโs theme: Building in the open
Building in the open has always been at the heart of what the Open Home Foundation does, across Home Assistant and other projects. This year, weโre taking it to the next level โ shining a spotlight on the transparency and collaboration that sets this community apart.
Weโre talking open roadmaps, honest conversations about the way we work and the challenges we face, and how we solve them together. Plus, weโll be showcasing what our community achieved in 2025, giving you a look at whatโs ahead โ and asking you to help shape it.
What to expect
Weโre putting the final touches on the program (watch this space!) โ but hereโs a taste of whatโs in store:
Celebrate all weโve achieved together in 2025
See whatโs ahead for Home Assistant and the wider ecosystem
Connect with fellow Open Home advocates and contributors in person
Have your say in the discussions guiding the future of the Open Home
And thatโs just the start. Expect special guests, a few surprises, and the kind of positive energy you only get when this community gathers in one room โก.
Tickets available soon!
Limited spots will be available for our live audience in Utrecht, the Netherlands. Tickets will be available from early February โ and theyโll go fast, so stay tuned for details! Weโll also be livestreaming globally for those who canโt make it in person.
This is not the final version, this is a test version. Please report problems and bugs in our issue tracker.
Highlights in OpenWrt 25.12
OpenWrt 25.12.0-rc2 incorporates over 4300 commits since branching the previous OpenWrt 24.10 release and has been under development for over one year.
Only the main changes are listed below. See changelog-25.12.0-rc2 for the full changelog.
General changes
The hardware requirements did not change significantly, most devices supported by OpenWrt 24.10 should also work with OpenWrt 25.12.
Switch package manager from opkg to apk
OpenWrt has transitioned from the traditional opkg package manager to apk (Alpine Package Keeper).
This change brings several advantages:
apk is still maintained, the OpenWrt opkg fork was not maintained any more.
apk supports most features of opkg. Only very few package names changed. The command line arguments of apk are different from the command line arguments of opkg.
For users migrating existing systems, an official opkg to apk cheatsheet is available to ease the transition and map common workflows.
Automatically rebuild firmware images with all currently installed packages
Preserve system configuration during upgrades
This dramatically simplifies upgrades: with just a few clicks in LuCI and a short wait, a custom firmware image is built and installed without manual intervention.
Shell history is preserved
Shell command history is now preserved across sessions by storing it in a RAM-backed filesystem.
Benefits:
Command history is no longer lost between logins
No unnecessary writes to flash storage by default
For users who prefer persistent history storage, this behavior can be changed by editing: /etc/profile.d/busybox-history-file.sh
โ ๏ธ Note: Storing history on flash will increase write cycles and may impact flash endurance over time.
Integration of video feed
The OpenWrt video feed with Qt5 and UI applications is integrated by default.
Wi-Fi scripts in ucode
The wifi scripts were rewritten in ucode.
Target changes
Extend realtek target with support for more switch SoCs like 10G Ethernet switches.
Extend qualcommax target with support for ipq50xx and ipq60xx SoCs.
Added siflower target for Siflower SF21A6826/SF21H8898 SoCs
Added sunxi/arm926ejs subtarget for Allwinner F1C100/200s SoCs
Many new devices added
OpenWrt 25.12 supports over 2180 devices. Support for over 160 new devices was added in addition to the device support by OpenWrt 24.10.
Core components update
Core components have the following versions in 25.12.0-rc1:
Updated toolchain:
musl libc 1.2.5
glibc 2.41
gcc 14.3.0
binutils 2.44
Updated Linux kernel
6.12.63 for all targets
main packages:
cfg80211/mac80211 from kernel 6.18.0
hostapd master snapshot from August 2025
dnsmasq 2.91
dropbear 2025.89
busybox 1.37.0
In addition to the listed applications, many others were also updated.
Upgrading to 25.12
Upgrading from 24.10 to 25.12 should be transparent on most devices, as most configuration data has either remained the same or will be translated correctly on first boot by the package init scripts.
Sysupgrade from 23.05 to 25.12 is not officially supported.
Cron log level was fixed in busybox. system.@system[0].cronloglevel should be set to 7 for normal logging. 7 is the default now. If this option is not set, the default is used and no manual action is needed.
Bananapi BPI-R4: Interfaces eth1 was renamed to sfp-lan or lan4 and the interface eth2 was renamed to sfp-wan to match the labels. You have to upgrade without saving the configuration.
Scratch installs/upgrades
If you wish to start from scratch (always the safest, but also the most work), simply download the pre-built image from the downloads site or from the Firmware Selector to your device. Make sure to create and save a backup, then install the image using sysupgrade -n /tmp/firmware.bin or the LuCI Backup/Flash Firmware, being sure to set "Keep settings and retain the current configuration" to its off position. Restore or reconstruct your configuration using the contents of the backup as a template.
Attended Sysupgrade options
Attended Sysupgrade (ASU) allows you to build a custom image that retains all of your installed packages and their configuration transparently. You need to use one of the three ASU clients that interface with the ASU server to produce this custom image:
Firmware Selector - an online builder that requires you to manually supply it with the packages you wish to have installed. This package list is sent to the ASU server, and a new custom device image is created containing those packages. You may then download and install the image in LuCI Backup/Flash Firmware, but for this you would enable "Keep settings..."
Luci Attended Sysupgrade - the web interface to the ASU server. This tool allows you to choose a new OpenWrt version, then collects the names of the packages on your device and sends them up to the ASU server. LuCI ASU then downloads the created image directly to your device and allows you to install it, without having to do any of the bookkeeping tasks involved with using the Firmware Selector.
owut - a command line package that does the same job as LuCI ASU, but provides more diagnostics and better visibility into what's happening at the various steps before and during the build process.
Both the LuCI ASU app and owut are optional packages in 24.10, so if you have not installed them, they won't be there by default. Use either the LuCI Package Manager to install them, or you can do it from the command line with opkg:
Note that you can install one or the other, or both together, they are completely independent packages.
Upgrades with Firmware Selector
The Firmware Selector does an excellent job of searching through the thousands of available device configurations and getting you to the right place. But, some devices have several variants and possibly different image formats, so if you're unsure about which one you need or which device you're dealing with or anything else, go to the |Firmware Selector support thread and ask away.
Upgrades with LuCI Attended Sysupgrade
The LuCI web interface should be fairly self explanatory. Since you have fairly limited options there that should be pretty obvious, but if anything is unclear or you're unsure about something, go to the LuCI Attended Sysupgrade support thread and ask.
Upgrades with owut
If you choose to use owut, the fact that it's a command line program means you'll need a little more explanation regarding best practices. In any situation, it's always safe to do a check to see what's going on.
$ owut check --verbose --version-to 25.12
... a lot of output ...
This check should show you all the details of what this upgrade entails with regards to the packages available, and will point out any issues with package versions and so on.
Assuming the results of the check look good, you can simply do an upgrade next.
$ owut upgrade --verbose --version-to 25.12
... even more output ...
If you are unsure of anything you see in the check, during the upgrade, or simply have questions, jump on over to the owut support thread on the forum and ask.
Known issues
Users of Zyxel EX5601-T0 devices need to check their WAN interfaces as port was renamed from eth1 to wan.
This is not the final version, this is a test version. Please report problems and bugs in our issue tracker.
Highlights in OpenWrt 25.12
OpenWrt 25.12.0-rc1 incorporates over 4300 commits since branching the previous OpenWrt 24.10 release and has been under development for over one year.
Only the main changes are listed below. See changelog-25.12.0-rc1 for the full changelog.
General changes
Switch package manager from opkg to apk
Integration of attended Sysupgrade into default LuCI installation
The shell history is stored in RAM till the next reboot
Integration of video feed
Wi-Fi scripts converted to ucode
Target changes
Extend realtek target with support for more switch SoCs like 10G Ethernet switches.
Extend qualcommax target with support for ipq50xx and ipq60xx SoCs.
Added siflower target for Siflower SF21A6826/SF21H8898 SoCs
Added sunxi/arm926ejs subtarget for Allwinner F1C100/200s SoCs
Many new devices added
OpenWrt 25.12 supports over 2180 devices. Support for over 160 new devices was added in addition to the device support by OpenWrt 24.10.
Core components update
Core components have the following versions in 23.05.0-rc1:
Updated toolchain:
musl libc 1.2.5
glibc 2.41
gcc 14.3.0
binutils 2.44
Updated Linux kernel
6.12.62 for all targets
main packages:
cfg80211/mac80211 from kernel 6.18.0
hostapd master snapshot from August 2025
dnsmasq 2.91
dropbear 2025.89
busybox 1.37.0
In addition to the listed applications, many others were also updated.
Upgrading to 25.12
Sysupgrade can be used to upgrade a device from 24.10 to 25.12, and configuration will be preserved in most cases.
:!: Sysupgrade from 23.05 to 25.12 is not officially supported.
ipq806x: migrate wifi configuration when downgrading from
kernel 6.12
mediatek: Cudy AP3000 v1: fix IPv4 address missing on interface
in failsafe mode
mediatek: Cudy WR3000H: fix Ethernet port order
mediatek: Zbtlink ZBT Z8102AX V2: fix ubi size
mpc85xx: p1010: Sophos RED 15w : Fix NAND partitions
mpc85xx: p1010: Watchguard Firebox T10: fix boot
mvebu: GL.iNet GL-MV1000: fix sdhci1 controller
ramips: Improve eMMC and SD Card support
Various fixes and improvements
ath11k: fix transmit queue flushing
dropbear: backport security fixes
dropbear: enable configurable port forwarding options
imagebuilder: fix image generation for some devices
kernel: add support for ESMT F50L1G41LC flash chip (found on recent Cudy boards)
kernel: add support for Fudan Micro FM25S01BI3 flash chip
mwl8k: improve stability of AP mode
odhcpd: fix memory leaks
ppp: add reqprefix, norelease and ac_mac options
Core components update
Linux kernel: update from 6.6.110 to 6.6.119
mac80211: update from 6.12.52 to 6.12.61
mt76: update from 2025-09-15 to 2025-11-06
wireless-regdb: update from 2025.07.10 to 2025.10.07
Upgrading to 24.10
Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.
For for upgrades inside the OpenWrt 24.10 stable series for example from a OpenWrt 24.10 release candidate Attended Sysupgrade is supported in addition which allows preserving the installed packages too.
Sysupgrade from 22.03 to 24.10 is not officially supported.
There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA. You have to upgrade without saving the configuration.
''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''
User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki. This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible.
Known issues
LEDs for Airoha AN8855 are not yet supported. Devices like the Xiaomi AX3000T with an Airoha switch will have their switch LEDs powered off. This issue will be addressed in an upcoming OpenWrt SNAPSHOT and the OpenWrt 24.10 minor release.
5GHz WiFi is non-functional on certain devices with ath10k chipsets. Affected models include the Phicomm K2T, TP-Link Archer C60 v3 and possibly others. For details, see issue #14541.
ramips: Hongdian H7920: Fix pin configuration and MAC addresses
Various fixes and improvements
mac80211: ath10k: improve "failed to flush transmit queue" errors
rockchip: rk3399: Fix PCIe
kernel: ksmbd: Fix SMB access from Linux clients
bcm53xx: Fix bootup of devices
Core components update
Linux kernel: update from 6.6.104 to 6.6.110
mac80211: update from 6.12.44 to 6.12.52
odhcpd: update from 2024-05-08 to 2025-10-02
ubus: update from 2025-07-02 to 2025-10-17
mbedtls: update from 3.6.4 to 3.6.5
openssl: update from 3.0.17 to 3.0.18
Upgrading to 24.10
Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.
For for upgrades inside the OpenWrt 24.10 stable series for example from a OpenWrt 24.10 release candidate Attended Sysupgrade is supported in addition which allows preserving the installed packages too.
Sysupgrade from 22.03 to 24.10 is not officially supported.
There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA. You have to upgrade without saving the configuration.
''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''
User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki. This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible.
Known issues
LEDs for Airoha AN8855 are not yet supported. Devices like the Xiaomi AX3000T with an Airoha switch will have their switch LEDs powered off. This issue will be addressed in an upcoming OpenWrt SNAPSHOT and the OpenWrt 24.10 minor release.
5GHz WiFi is non-functional on certain devices with ath10k chipsets. Affected models include the Phicomm K2T, TP-Link Archer C60 v2, TP-Link Archer C60 v3 and possibly others. For details, see issue #14541.
The OpenWrt community is proud to announce the newest stable release of
the OpenWrt 23.05 stable series. It improves device support and brings a
few bug fixes including security fixes.
Download firmware images using the OpenWrt Firmware Selector:
iptables: backport "nft: track each register individually" from 1.9
wifi-scripts: Fix parsing of Capabilities
Core components update
Update Linux from 5.15.167 to 5.15.189
Update mac80211 from 6.1.110-1 to 6.1.145-1
Update wireless-regdb from 2024.07.04 to 2025.07.10
Update openssl from 3.0.15 to 3.0.16
Update mbedtls from 2.28.9 to 2.28.10
Update wolfssl from 5.7.2 to 5.7.6
Update ca-certificates from 20230311 to 20241223
Update jsonfilter from 2024-01-23 to 2025-04-18
Update libxml from 2.12.5 to 2.14.5
Upgrading to 23.05.6
Sysupgrade can be used to upgrade a device from 22.03 to 23.05, and
configuration will be preserved in most cases.
Sysupgrade from 21.02 to 23.05 is not officially supported.
ipq40xx EA6350v3, EA8300, MR8300 and WHW01 require tweak to the
U-Boot environment on update from 22.03 to 23.05. Refer to the Device
wiki or the instruction on sysupgrade on how to do this change.
Config needs to be reset on sysupgrade.
Known issues
lantiq/xrx200 target shows error messages in DSA switch
configuration of the integrated GSWIP switch. (see: #13200)
OpenWrt 23.05.6 was signed with the wrong signing keys. The keys from
OpenWrt snapshot were used for OpenWrt 23.05.6, OpenWrt 23.05.5,
OpenWrt 23.05.4, OpenWrt 23.05.3, OpenWrt 23.05.2, OpenWrt 23.05.0 and
the release candidates. A later OpenWrt 23.05 service release will use
a different key.
realtek: Avoid interrupt storm on mass packet receive
realtek: Fix stall after restart of otto timer
rockchip: Fix for MSI/MSI-X bug: no MSI/MSI-X, Back to INTx.
rockchip: NanoPC-T6 with A3A444 chips: Fix eMMC corruption
rockchip: rk35xx: Increase the number of serial ports
tegra: Bring back workaround for spurious interrupts
x86: Fix boot problems by activating CONFIG_PCI_MMCONFIG
Various fixes and improvements
busybox: Fix login applet on selinux
hostapd: Reduce debug logging
kernel: Add support for FudanMicro FM25S01A SPI-NAND
kernel: Fix netdev trigger for PHY LEDs
mac80211: Improve WiFi-7 TX performance
mt76: Improve system recovery routine for MT7915
wifi-scripts: Correctly set basic-rates with wpa_supplicant
Core components update
Linux kernel: update from 6.6.93 to 6.6.104
mac80211: update from 6.12.6 to 6.12.44
mt76: update from 2025-02-14 to 2025-09-15
kmod-r8125: update from 9.016.00 to 9.016.01
kmod-r8126: update from 10.015.00 to 10.016.00
kmod-r8127: update from 11.014.00 to 11.015.00
libubox: update from 2024-12-19 to 2025-07-23
udebug: update from 2023-12-06 to 2025-08-24
ucode: update from 2025-05-11 to 2025-07-18
uhttpd: update from 2023-06-25 to 2025-07-06
uqmi: update from 2024-08-25 to 2025-07-30
rpcd: update from 2024-09-17 to 2025-09-01
ubus: update from 2025-05-16 to 2025-07-02
libxml2: update from 2.13.6 to 2.14.5
mbedtls: update from 3.6.3 to 3.6.4
openssl: update from 3.0.16 to 3.0.17
ca-certificates: update from 20241223 to 20250419
wireless-regdb: update from 2025.02.20 to 2025.07.10
Upgrading to 24.10
Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.
For for upgrades inside the OpenWrt 24.10 stable series for example from a OpenWrt 24.10 release candidate Attended Sysupgrade is supported in addition which allows preserving the installed packages too.
Sysupgrade from 22.03 to 24.10 is not officially supported.
There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA. You have to upgrade without saving the configuration.
''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''
User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki. This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible.
Known issues
LEDs for Airoha AN8855 are not yet supported. Devices like the Xiaomi AX3000T with an Airoha switch will have their switch LEDs powered off. This issue will be addressed in an upcoming OpenWrt SNAPSHOT and the OpenWrt 24.10 minor release.
5GHz WiFi is non-functional on certain devices with ath10k chipsets. Affected models include the TP-Link Archer C60 v1, and possibly others. For details, see issue #14541.
kmod-r8125: load module at boot time, disable ASPM
kmod-r8125-rss: enable ENABLE_MULTIPLE_TX_QUEUE
kmod-r8126: load module at boot time
kmod-r8126-rss: enable ENABLE_MULTIPLE_TX_QUEUE
kmod-r8127: load module at boot time
kmod-r8127-rss: enable ENABLE_MULTIPLE_TX_QUEUE
kmod-r8168: load module at boot time
kmod-r8168-rss: add variant
lldpd: enable hardware inventory information (TLV) management
mac80211: add patch to suppress PREP when mesh forwarding is disabled
mac80211: ath11k: fix broadcast failures during GTK rekeying
qmi: increase SIM power-cycle timeouts
Core components update
Linux kernel: update from 6.6.86 to 6.6.93
ucode: update from 2025-02-10 to 2025-05-11
netifd: update from 2024-12-17 to 2025-05-23
bcm27xx-gpu-fw: update to v1.20250430
kmod-phy-realtek: backport upstream v6.15 patches
kmod-phy-realtek: backport upstream v6.16 patches
kmod-r8125: update to v9.016.00
kmod-r8169: backport upstream v6.15 patches
kmod-r8169: backport upstream v6.16 patches
Upgrading to 24.10
Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.
For for upgrades inside the OpenWrt 24.10 stable series for example from a OpenWrt 24.10 release candidate Attended Sysupgrade is supported in addition which allows preserving the installed packages too.
Sysupgrade from 22.03 to 24.10 is not officially supported.
There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA. You have to upgrade without saving the configuration.
''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''
User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki. This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible.
Known issues
LEDs for Airoha AN8855 are not yet supported. Devices like the Xiaomi AX3000T with an Airoha switch will have their switch LEDs powered off. This issue will be addressed in an upcoming OpenWrt SNAPSHOT and the OpenWrt 24.10 minor release.
5GHz WiFi is non-functional on certain devices with ath10k chipsets. Affected models include the TP-Link Archer C60 v1, and possibly others. For details, see issue #14541.
Main changes between OpenWrt 24.10.0 and OpenWrt 24.10.1
Only the main changes are listed below. See changelog-24.10.1 for the full changelog.
Device support
Added new devices:
bmips: Actiontec T1200H
mediatek: CMCC A10
mediatek: Huasifei WH3000
mediatek: Keenetic KN-3811
mediatek: Keenetic KN-3911
mediatek: netis NX31
qualcommax: Linksys MX4300 (LN1301)
ramips: Cudy M1200 v1
ramips: Cudy M1300 v2
ramips: Genexis / Inteno Pulse EX400
ramips: Hongdian H8922 v30
ath79: mikrotik Routerboard 911G: Fix clock speed
ath79: NEC Aterm: Fix initramfs execution
bcm27xx: Raspberry Pi: Fixes for r8169 Ethernet driver
bcm27xx: Raspberry Pi: Update GPU firmware and drivers
imx: Gateworks boards: Misc fixes
mediatek: ASUS: RT-AX59U/TUF-AX4200/TUF-AX6000: Fix boot problems with recent bootloader
mediatek: Xiaomi AX3000t: Fix NMBM handling for devices with Winbond W25N01KVZEIR flash
mediatek: Zyxel EX5601-T0: Fix eth1 wan configuration
ramips: Dovado Tiny AC: Fix wifi MAC addresses
ramips: hiwifi hc5962: Fix reading MAC address
ramips: LAVA LR-25G001: Fix wifi MAC address
ramips: MT7621: Improve MT7621S core detection
ramips: TP-Link Deco M4R v4: Fix port name conflict
realtek: Add new auxiliary MDIO driver and switch devices to it
realtek: HPE 1920: Fix FAN configuration
realtek: Zyxel GS1900-8: Split into v1 and v2
Various fixes and improvements
ath10k-ct: Silence some harmless noisy logs
build: build LLVM toolchain for BPF when packet selects it
dnsmasq: Fix handlers for options filter_rr and cache_rr
kernel: Fix IPv6 TCP GSO segmentation with NAT
kernel: Globally enable CONFIG_PCPU_DEV_REFCNT
kernel: usbnet: Restore usb%d naming for cdc-ethernet devices with local MAC
mac80211: rt2x00: Fix loading EEPROM from card
odhcpd: Fix missed packets in relay mode
umdns: Automatically configure firewall for umdns when needed
Core components update
Update Linux from 6.6.73 to 6.6.86
Update mt76 from 2025-01-14 to 2025-02-14
Update mwlwifi from 2024-04-19 to 2025-02-06
Update wireless-regdb from 2024.10.07 to 2025.02.20
Update ucode from 2024-07-22 to 2025-02-10
Update unetd from 2024-12-17 to 2025-03-09
Update umdns from 2024-09-17 to 2025-02-10
Update omcproxy from 2021-11-04 to 2025-02-27
Update libnl-tiny from 2023-12-05 to 2025-03-19
Update ethtool from 6.10 to 6.11
Update openssl from 3.0.15 to 3.0.16
Update mbedtls from 3.6.2 to 3.6.3
Update ca-certificates from 20240203 to 20241223
Update bcm27xx-gpu-fw from 2024.11.26 to 2025.03.05
Update bcm27xx-utils from 2024.12.19 to 2025.03.14
Update r8125 from 9.014.01 to 9.015.00
Update r8126 from 10.014.01 to 10.015.00
Update r8168 from 8.054.00 to 8.055.00
Update bcm63xx-cfe from 2024-06-25 to 2025-04-02
Update intel-microcode from 20240531 to 20250211
Update firmware-utils from 2024-10-20 to 2025-02-16
Upgrading to 24.10
Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.
For for upgrades inside the OpenWrt 24.10 stable series for example from a OpenWrt 24.10 release candidate Attended Sysupgrade is supported in addition which allows preserving the installed packages too.
Sysupgrade from 22.03 to 24.10 is not officially supported.
There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA. You have to upgrade without saving the configuration.
''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''
User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki. This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible.
Known issues
LEDs for Airoha AN8855 are not yet supported. Devices like the Xiaomi AX3000T with an Airoha switch will have their switch LEDs powered off. This issue will be addressed in an upcoming OpenWrt SNAPSHOT and the OpenWrt 24.10 minor release.
5GHz WiFi is non-functional on certain devices with ath10k chipsets. Affected models include the TP-Link Archer C60 v1, TP-Link Archer C6 v2, and possibly others. For details, see issue #14541.
Ethernet link instability on some MT7530 switches. Users experiencing unstable Ethernet connections should disable Energy-Efficient Ethernet (EEE) as a workaround. See issue #17351 for more information.
The OpenWrt community is proud to announce the first stable release of the OpenWrt 24.10 stable series.
OpenWrt 24.10.0 incorporates over 5400 commits since branching the previous OpenWrt 23.05 release and has been under development for over one year.
Download firmware images using the OpenWrt Firmware Selector:
Upgrades of many components to new versions like the Linux kernel from version 5.15 to 6.6
TLS 1.3 support in default images
mbedtls was updated to version 3.6 which includes support for TLS 1.3
Activate POSIX Access Control Lists and file system security attributes for all file systems on devices with big flash sizes. This is needed by docker nowadays.
This is activated for all targets which do not have the small_flash feature flag. small_flash is set for the ath79/tiny, bcm47xx/legacy, lantiq/ase, lantiq/xrx200_legacy, lantiq/xway_legacy, ramips/mt76x8, ramips/rt288x, ramips/rt305x and ramips/rt3883 targets.
Activate kernel support for Multipath TCP on devices with big flash sizes.
Improved support for WiFi6 (802.11ax) and initial support for WiFi7 (802.11be)
Not many Wifi7 devices are supported by OpenWrt yet
Improved Link Layer Discovery Protocol (LLDP) support
OpenWrt 24.10 uses OPKG only, APK packages are not supported. Only main branch was changed to APK.
Many new devices added
OpenWrt 24.10 supports over 1970 devices. Support for over 100 new devices was added in addition to the device support by OpenWrt 23.05.
Added loongarch64 target for SoCs with Loongson LoongArch CPUs.
Added starfive target for StarFive JH71x0 (7100/7110) SoCs.
Added stm32 target for STMicroelectronics STM32 SoCs.
Renamed ipq807x target to qualcommax.
Removed ath25 target. It supported Atheros ieee80211g devices with maximum 16MB RAM
Removed bcm63xx target. It supported some Broadcom DSL MIPS SoCs and was replaced by the bmips target. The Broadcom DSL itself was never supported.
Removed octeontx target. It supported the Octeon-TX CN80XX/CN81XX based boards
Removed oxnas target. It supported the PLXTECH/Oxford NAS782x/OX8xx
The qoriq target for the NXP QorIQ (PowerPC) SoCs is built
The ipq806x target for Qualcomm Atheros IPQ806X SoCs was converted to DSA
Added support for Airoha AN8855 DSA Switch (Xiaomi AX3000T ship both Mediatek and Airoha Switch in the same revision)
Added bcm2712 subtarget for Raspberry Pi 5.
Core components update
Core components have the following versions in 24.10.0:
Updated toolchain:
musl libc 1.2.5
glibc 2.38
gcc 13.3.0
binutils 2.42
Updated Linux kernel
6.6.73 for all targets
Network:
hostapd master snapshot from September 2024, dnsmasq 2.90, dropbear 2024.86
cfg80211/mac80211 from kernel 6.12.6
Upgrading to 24.10
Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.
For for upgrades inside the OpenWrt 24.10 stable series for example from a OpenWrt 24.10 release candidate Attended Sysupgrade is supported in addition which allows preserving the installed packages too.
Sysupgrade from 22.03 to 24.10 is not officially supported.
There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA. You have to upgrade without saving the configuration.
''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''
User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki. This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible.
Known issues
LEDs for Airoha AN8855 are not yet supported. Devices like the Xiaomi AX3000T with an Airoha switch will have their switch LEDs powered off. This issue will be addressed in an upcoming OpenWrt SNAPSHOT and the OpenWrt 24.10 minor release.
5GHz WiFi is non-functional on certain devices with ath10k chipsets. Affected models include the TP-Link Archer C60 v1, TP-Link Archer C6 v2, and possibly others. For details, see issue #14541.
Ethernet link instability on some MT7530 switches. Users experiencing unstable Ethernet connections should disable Energy-Efficient Ethernet (EEE) as a workaround. See issue #17351 for more information.
Kernel warning in ath10k-ct driver at startup. The warning WARNING: CPU: 3 PID: 1695 at backports-6.9.9/net/mac80211/main.c:270 ieee80211_do_open+0x4e8/0x5e0 [mac80211] appears during boot but is harmless and can be ignored. See issue #15959 for details.
The OpenWrt community is proud to announce the seventh release candidate of the upcoming OpenWrt 24.10 stable series.
OpenWrt 24.10.0-rc7 incorporates over 5300 commits since branching the previous OpenWrt 23.05 release and has been under development for over one year.
This is just a release candidate and not the final release yet.
Download firmware images using the OpenWrt Firmware Selector:
This is not the final version, this is a test version. Please report problems and bugs in our issue tracker. https://github.com/openwrt/openwrt/issues
If there is already an existing ticket feel free to comment that the problem also occurs with OpenWrt 24.10.0-rc7.
Changes between OpenWrt 24.10.0-rc6 and 24.10.0-rc7
Target changes:
airoha: multiple fixes
apm821xx: NETGEAR WNDR4700: fix compat version
ath79: make kmod-usb-chipidea select kmod-phy-ath79-usb
octeon: ubnt-usg: add board name to supported devices
qualcommax: Spectrum SAX1V1K: add missing WAN LED support
ramips: USW-Flex: restore full switch performance
realtek: HPE 1920-8G PoE: fix old compatible
stm32: enable CONFIG_SMSC_PHY
Generic changes:
dnsmasq: add fix related to DNSSEC verification from upstream
generic: fix probe issues with RealTek RTL8221B PHYs
unetd: fix interface teardown
wolfssl: update to version 5.7.6
For a detailed list of changes since OpenWrt 24.10.0-rc7 see the 24.10.0-rc7 changelog.
Highlights in OpenWrt 24.10:
General changes
TLS 1.3 support in default images
mbedtls was updated to version 3.6 which includes support for TLS 1.3
Activate POSIX Access Control Lists and file system security attributes for all file systems on devices with big flash sizes. This is needed by docker nowadays.
This is activated for all targets which do not have the small_flash feature flag. small_flash is set for the ath79/tiny, bcm47xx/legacy, lantiq/ase, lantiq/xrx200_legacy, lantiq/xway_legacy, ramips/mt76x8, ramips/rt288x, ramips/rt305x and ramips/rt3883 targets.
Activate kernel support for Multipath TCP on devices with big flash sizes.
Improved support for WiFi6 (802.11ax) and initial support for WiFi7 (802.11be)
Not many Wifi7 devices are supported by OpenWrt yet
Improved Link Layer Discovery Protocol (LLDP) support
OpenWrt 24.10 uses OPKG only, APK packages are not supported. Only main branch was changed to APK.
Many new devices added
OpenWrt 24.10 supports over 1950 devices. Support for over 100 new devices was added in addition to the device support by OpenWrt 23.05.
Added loongarch64 target for SoCs with Loongson LoongArch CPUs.
Added starfive target for StarFive JH71x0 (7100/7110) SoCs.
Added stm32 target for STMicroelectronics STM32 SoCs.
Renamed ipq807x target to qualcommax.
Removed ath25 target. It supported Atheros ieee80211g devices with maximum 16MB RAM
Removed bcm63xx target. It supported some Broadcom DSL MIPS SoCs and was replaced by the bmips target. The Broadcom DSL itself was never supported.
Removed octeontx target. It supported the Octeon-TX CN80XX/CN81XX based boards
Removed oxnas target. It supported the PLXTECH/Oxford NAS782x/OX8xx
The qoriq target for the NXP QorIQ (PowerPC) SoCs is built
The ipq806x target for Qualcomm Atheros IPQ806X SoCs was converted to DSA
Added support for Airoha AN8855 DSA Switch (Xiaomi AX3000T ship both Mediatek and Airoha Switch in the same revision)
Core components update
Core components have the following versions in 24.10.0-rc7:
Updated toolchain:
musl libc 1.2.5
glibc 2.38
gcc 13.3.0
binutils 2.42
Updated Linux kernel
6.6.73 for all targets
Network:
hostapd master snapshot from September 2024, dnsmasq 2.90, dropbear 2024.86
cfg80211/mac80211 from kernel 6.12.6
Upgrading to 24.10
Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.
Sysupgrade from 22.03 to 24.10 is not officially supported.
There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA. You have to upgrade without saving the configuration.
''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''
User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki. This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible.
Known issues
LEDs handling for Airoha AN8855 is currently not supported. Xiaomi AX3000T with Airoha Switch mounted will have Switch LEDs powered OFF. (problem will be addressed in later OpenWrt SNAPSHOT and later Openwrt 24.10 minor release)
5GHz Wifi on TP-Link Archer C60 v1, TP-Link Archer C6 v2 and probably more devices with ath10k Wifi chip does not work, see #14541
Ethernet link unstable on some mt7530 switches. Deactivate EEE (Energy-Efficient Ethernet) as a workaround, see: #17351
Last month โ and indeed last year! โ we published a blog recapping the highlights from the Works with Home Assistant program in 2025. As with any certification program, our partnerships evolve: some start anew, some grow bigger and stronger, and some naturally run their course. In the interest of visibility for our community, we want to share an update about one such change. When a partner leaves the program, we believe itโs important to document this openly so you get the full picture.
Why weโre making a change
Despite reaching out to HELTUN multiple times during 2025 to discuss renewing their Works with Home Assistant contract with the Open Home Foundation, we havenโt been able to connect. As their previous contract has now lapsed, weโre formally removing HELTUN from the Works with Home Assistant program.
We have no specific issues with the HELTUN devices, and hope they will continue to be compatible with Home Assistant โ as Z-Wave devices operate on an open standard, they should continue to function. However, without a contract, HELTUN has no formal obligation to provide ongoing support, such as firmware updates via Z-Wave JS.
This is an example of why the contract is more than just paperwork. Itโs intrinsic to the badging as it outlines, in a legal and binding document, our partnersโ commitment to the community, keeping devices working long-term, and the values we all care about. Without it, we canโt maintain certification.
What happens now
HELTUNโs integration page will now be removed from the partner filter, and an update has been published on our original HELTUN launch blog stating that the information is no longer applicable. They are now also prohibited from using the Works with badge on relevant marketing materials.
As we have no problems with the devices themselves, we will be happy to welcome HELTUN back into the program should they wish to re-engage in the future.
Looking ahead
In more positive news, donโt forget weโve introduced an up-to-date list of all certified devices from our current Works with partners to help guide your purchasing decisions โ and watch this space for details of more brands joining us in 2026!
Release Highlights: Although GeForce Game Ready Drivers and NVIDIA Studio Drivers can be installed on supported notebook GPUs, the original equipment manufacturer (OEM) provides certified drivers for your specific notebook on their website. NVIDIA recommends that you check with your notebook OEM for recommended software updates for your notebook.
Game Ready for DLSS 4.5
This new Game Ready Driver provides the best gaming experience for the latest new games and updates and resolves key issues which were found in the previous release.
Fixed Gaming Bugs
Arena Breakout: Infinite: Game stability issues [5748974]
Fixed General Bugs
Brightness adjustment issues on various displays [5739739]
Colors are not applied correctly when using Digital Vibrance [5718365]
Slight banding may be observed on gradients in SDR color mode [5720512]
Unable to deselect "Show Notification Tray Icon" from NVIDIA Control Panel [5622213]
Using RTX HDR in Vulkan games causes black screen on LG OLED TVs [5763163]
I hope you had a wonderful holiday, spending time with your loved ones. Weโre kicking off 2026 with a smaller release, as our contributors and maintainers have been enjoying some well-deserved time off as well. But donโt worry, thereโs still plenty of good stuff in this release!
Home Assistant 2026.1 brings a refreshed Home dashboard experience on mobile, with summary cards right at your fingertips without extra taps. Weโve also made it easier than ever to navigate to the protocol connecting your devices, such as Zigbee, Z-Wave, Thread and more.
For automation enthusiasts, weโre continuing our work on our even more โhuman-friendlyโ triggers, which can be enabled via Home Assistant Labs, so you can build automations using easy-to-understand language instead of technical state changes, like initiating automations if a button is pressed or someone arrives home.
On the integrations front, we welcome eight new integrations to the family, including pet tracking with Fressnapf, energy monitoring with eGauge, and smart heating control with Watts Vision +. Plus, improvements to existing integrations from our amazing community contributors.
I wish you a happy and healthy 2026! Enjoy the release!
A huge thank you to all the contributors who made this release possible! And a special shout-out to @bramkragten, @piitaya, and @abmantis who helped write the release notes for this release. โค๏ธ
Home dashboard improvements
The Home dashboard continues to evolve! In the previous release, we introduced a brand-new sidebar layout, weather tiles, and energy distribution summaries. This release takes it even further with a streamlined mobile experience and better device management.
Streamlined mobile navigation
On mobile devices, the Home dashboard now displays summary cards (like lights, climate, security, media players, weather, and energy) directly at the top of the view, followed by your favorites and areas. This replaces the previous tab-based navigation, giving you instant access to everything that matters without any extra taps.
The desktop experience remains unchanged, with summaries displayed in the sidebar under the For you heading.
New devices page
Ever wondered where your devices went after you removed them from an area? A new Devices page now appears on the Home dashboard, showing all devices that arenโt currently assigned to a specific area. This makes it easy to find and control those โorphanedโ devices without hunting through the settings.
The new Devices page shows devices not assigned to any area.
Purpose-specific triggers and conditions progress
In the previous release, we introduced purpose-specific triggers and conditions. Instead of thinking in technical state changes, you can now simply pick things like โWhen a light turns onโ or โIf the climate is heatingโ when building your automations.
This feature is still being refined in Home Assistant Labs, but this release adds a lot more trigger types, making this new approach even more useful. Here is an overview of all the new triggers added in this release:
Button triggers fire when a button entity has been pressed.
Climate triggers now cover all common scenarios. You can trigger on HVAC mode changes, target temperature changes, or when the target temperature crosses a threshold. There are also triggers for current temperature and humidity changes, and even target humidity changes.
Device tracker triggers let you automate based on when a device entered or left home, with support for the first device arriving, last device leaving, or any change. Donโt worry, person-specific triggers are coming soon, the device tracker ones were simply available sooner.
Humidifier triggers will fire when a humidifier turns on or off, starts humidifying, or starts drying. You can also trigger on humidity changes or when humidity crosses a threshold.
Light triggers let you automate based on brightness changes or when brightness crosses a specific threshold.
Lock triggers can now fire when a lock is locked, unlocked, opened, or jammed.
Scene triggers fire when a scene is activated.
Siren triggers fire when sirens are turned on or off.
Update trigger fires when an update becomes available.
As the new purpose-specific triggers and conditions all support targeting something bigger than a simple entity (an area, a floor, or even a label), we also redesigned how the target gets displayed on the automation flow.
The goal of this change is to allow you to quickly glance at your automation, and understand its purpose.
Head over to Settings > System > Labs to enable purpose-specific triggers and conditions and give them a try!
Easier navigation to protocol dashboards
For an organization that loves the open standards that seamlessly connect our devices, we sure didnโt promote them enough! Most people didnโt even know that Home Assistant has dedicated dashboards for protocols like Zigbee, Z-Wave, and more.
This release reorganizes the Settings page to give these open protocols a more prominent spot. The protocols section now appears right after the core settings, making it much easier to find all the different ways youโre connecting your devices and quickly access some very useful protocol-specific configurations.
The menu items only appear when you have the corresponding integration set up, so youโll only see whatโs relevant to your setup.
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:
AirPatrol, added by @antondalgren
Control your air conditioning units through AirPatrol Wi-Fi devices directly from Home Assistant.
eGauge, added by @neggert
Integrate eGauge energy monitors for residential and commercial applications, commonly used with solar energy installations.
Fluss+, added by @Marcello17
Connect your Fluss+ Button to Home Assistant for quick and easy control of your smart home.
Fish Audio, added by @noambav
Use Fish Audioโs text-to-speech service to generate natural-sounding speech in Home Assistant.
Fressnapf Tracker, added by @eifinger
Track the location of your pets and monitor their activity using Fressnapf GPS Trackers.
HomeLink, added by @ryanjones-gentex
Integrate your HomeLink devices to trigger smart home routines from the comfort of your vehicle.
Watts Vision +, added by @theobld-ww
Control your Watts Vision + smart heating system, allowing remote control of individual home heating zones.
WebRTC, added by @balloob
An internal integration providing WebRTC functionality for camera streaming in Home Assistant.
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 are also being constantly improved. Here are some of the noteworthy changes to existing integrations:
The Matter integration gained three new diagnostic binary sensors for thermostat remote sensing status from @lboue, helping you keep an eye on your climate system.
@joostlek added lots of new sensors to the SmartThings integration, including air quality sensors for PM1, PM2.5, and PM10, hood filter usage tracking, fridge temperature sensors for One Door refrigerators, and fan speed control for range hoods.
Roborock owners with Q7 devices can now integrate them thanks to @Lash-L, who added basic read-only support with sensors for battery, status, and cleaning data.
@mib1185 improved the FRITZ!SmartHome integration by adding switch entities that let you enable or disable FRITZ! Smart Home routines (triggers) directly from Home Assistant.
The Ping integration now tracks packet loss, thanks to @mib1185. The new sensor shows packet loss as a percentage and is disabled by default.
@Shulyaka added support for GPT-5.2 and GPT-5.2-pro models to the OpenAI integration, including a new โxhighโ reasoning effort level.
The HomeWizard integration gained two new battery charge modes from @DCSBL: zero charge only and zero discharge only, giving you more control over your energy storage.
@Abestanis expanded the KNX UI configuration to support time, date, and datetime entities, while @farmio added sensor, scene, text, and fan entities, making it easier than ever to set up your KNX installation.
The Squeezebox integration now offers alarm monitoring, thanks to @wollew: you get binary sensors to track if an alarm is upcoming, active, or snoozed, plus a timestamp sensor showing when the next alarm is scheduled.
@andrew-codechimp added support for new meal plan types in Mealie 3.7, including dessert, drink, and snack plans, giving you more flexibility in your meal planning.
The Hikvision integration gained NVR support from @ptarjan, including extended event detection and automatic discovery of video channels.
@FredericMa added a set_time action to the Risco integration, allowing you to sync your local alarm panelโs clock and fix those pesky clock drift issues.
The Nederlandse Spoorwegen integration got a major overhaul from @heindrichpaul, splitting the monolithic sensor into over 15 individual sensors, one for each train route, making it much easier to track specific journeys.
@zweckj added a beautiful entity picture of your coffee machine to the La Marzocco integrationโs main switch entity.
The Actron Air integration gained a new switch platform from @kclif9, exposing Away Mode, Continuous Fan, Quiet Mode, and Turbo Mode controls.
@Djelibeybi gave the Pooldose integration a massive upgrade: you now get water meter sensors for monitoring levels, number entities for configuring dosing targets, and select entities for controlling your poolโs operating mode.
The AirPatrol integration now lets you monitor temperature and humidity, thanks to new sensor entities added by @antondalgren.
@mettolen added sensor and number platforms to the Airobot integration, letting you monitor air quality data and control hysteresis band settings.
A huge thank you to all the contributors who improved these integrations, and to everyone else who contributed improvements that arenโt listed here. Your work makes Home Assistant better for everyone! โค๏ธ
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:
This is a huge achievement for these integrations and their maintainers. The effort and dedication required to reach these quality levels is significant, as it involves extensive testing, documentation, error handling, and often complete rewrites of parts of the integration.
A big thank you to all the contributors involved! ๐
Now available to set up from the UI
While most integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] can be set up directly from the Home Assistant user interface, some were only available using YAML configuration. We keep moving more integrations to the UI, making them more accessible for everyone to set up and use.
The following integrations are now available via the Home Assistant UI:
There are many more improvements in this release; here are some of the other noteworthy changes:
If you monitor your homeโs oil tank or other slow flow rates, you might appreciate the new gallons per day unit of volume flow rate added by @StaleLoafOfBread. This unit is particularly useful for tracking daily consumption rates of heating oil or similar resources.
Got a Matter speaker? @lboue added volume control support to the Matter integration, exposing a volume slider entity for Matter speakers using the LevelControl cluster.
The statistics graph card now includes a link to the history panel in its header, just like the history graph card already had. Selecting the link takes you directly to the history with the same entities and time range pre-selected, thanks to @joepio.
When using the state badge element in your picture elements card, you can now set a custom name option, giving you more flexibility in your dashboard designs, thanks to @ildar170975.
In 2025.11 we improved the logging efficiency by disabling the duplicated log file. This release adds a new configuration option to re-enable it if needed. If you are using the official Terminal & SSH add-on, make sure it is updated to 9.22.0 or higher to be able to use that option. The Advanced SSH & Web Terminal add-on has not been updated yet, but will be soon.
For integration developers: @bramkragten added a new choose selector, allowing users to select between different input types in the UI. Youโll start seeing this pop up in various places where flexible input is needed.
Energy dashboard date picker
In the previous release, the Energy dashboard received a big update with real-time power monitoring and downstream water tracking. However, some of you noticed that navigating between periods required scrolling back up, making it harder to compare data while looking at graphs further down the page.
This release fixes that! The date picker is now sticky at the bottom of the screen, so you can easily switch between days, weeks, or months without losing sight of the graph youโre viewing. This also makes it much easier to access on mobile devices.
ESPHome action responses
ESPHome 2025.12 introduced a powerful new feature called API action responses, enabling true bidirectional communication between your ESPHome devices and Home Assistant. With this release, Home Assistant now fully supports receiving these responses!
Previously, when calling an action on an ESPHome device, communication was one-way: you could send a command, but the device couldnโt send structured data back. Now, your ESPHome devices can return JSON data in response to actions, unlocking new possibilities like querying device configuration, reading sensor values on demand, or retrieving diagnostic information.
This is particularly useful for actions that answer questions rather than perform tasks. For example, you could create an action that returns your deviceโs current Wi-Fi signal strength, firmware version, or any custom sensor readings, all as structured data you can use in your automations.
We will also release patch releases for Home Assistant 2026.1 in January.
These patch releases only contain bug fixes. Our goal is to release a patch
release once a week, aiming for Friday.
2026.1.1 - January 12
Fix Hikvision NVR binary sensors not being detected (@ptarjan - #160254)
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:
Coolmaster
The climate entities provided by the Coolmaster integration now use medium for the medium fan mode; before this change, it was med. If your automations are using med when setting or querying the fan speed, youโll have to change it to medium.
The โSupports hairpinningโ binary sensor has been removed from the Tailscale integration. According to the official Tailscale API documentation, this information is no longer tracked and will always return null.
Select entity state values have been changed from their original mixed-case format to snake_case format with proper translations. This improves consistency and enables proper localization support.
Chime type: Mechanical โ mechanical, Digital โ digital
Recording mode: Always โ always, Detections โ detections, Never โ never
Infrared mode: Auto โ auto, On โ on, AutoNoLEDsOn โ auto_no_leds_on
Status light mode: On โ on, Off โ off, OnWhenDark โ on_when_dark
HDR mode: Auto โ auto, On โ on, Off โ off
If you have automations, scripts, or templates that check or set the state of UniFi Protect select entities, you need to update them to use the new snake_case values. The UI will continue to display properly translated, human-readable text.
Allowing extra/unused parameters has been removed from the action for Telegram bot. Only users who have used undefined parameters for Telegram bot actions are affected. If you are affected, remove such parameters from your automations and scripts. Supported parameters can be found in the Telegram bot notification actions documentation.
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.
Release Highlights: Although GeForce Game Ready Drivers and NVIDIA Studio Drivers can be installed on supported notebook GPUs, the original equipment manufacturer (OEM) provides certified drivers for your specific notebook on their website. NVIDIA recommends that you check with your notebook OEM for recommended software updates for your notebook.
Game Ready
This new Game Ready Driver provides the best gaming experience for the latest new games and updates and resolves key issues which were found in the previous release.
Fixed Gaming Bugs
Enshrouded: Game stability issues on GeForce RTX 50 Series GPUs [5664067]
Assassin's Creed Valhalla: HDR toggle not functional when Smooth Motion is enabled [5469746]
Dying Light: The Beast: Game stability issues after updating to 591.44 driver [5720536]
Fixed General Bugs
Display color seems faded after switching to non-native resolution [5548662]
Using RTX HDR on select televisions causes games to blackscreen [5720286]
Itโs been a busy few months composing behind the scenes, building up to a massive crescendo. Today, the beat finally drops on Music Assistantโs biggest update yet. With version 2.7, Music Assistant is getting all jazzed up with a visual overhaul, a chart-topping lineup of new features and providers, along with a brand-new streaming protocol weโre spinning up ourselves.
Of course, you can always update and experience all the great new stuff without reading the rest of this, but you might miss a deep cut. In fact, we canโt even cover everything in this blog (there really is that much), so go sing your praises for anything we missed in the comments!
Music Assistant has gained its first full-time employee at the Open Home Foundation. No, not me! My day job is leading the Ecosystems department at the foundation (which comprises all the software projects the Foundation has that are not Home Assistant itself). Marvin will be joining the foundation in the new year to work full-time on Music Assistant, leading the projectโs day-to-day operations. Marvin has been contributing to the project for three years now, working on all sorts of parts of the project, and specifically with the Apple Music and YouTube providers.
Not to worry, Iโm pretty obsessed with my audio setup and will still be tinkering on my little pet project ๐.
โEverything in Its Right Placeโ
A visual overhaul
A well deserved visual refresh
Music Assistant joining the foundation has given us a lot more than a nice open home; itโs given the project clearer direction and some expert help. One area some people felt Music Assistant fell short was its UI and UX, and in version 2.7, weโre starting the process of giving it a major overhaul, making it look as good as your music sounds!
This is just the beginning of a big process, so expect every update to bring more polish. The first thing youโll probably notice is the collapsible navbar on the left of the screen, which looks pretty familiar to another Assistant ๐. Now itโs much more intuitive, especially for new users. The settings page has also been made much easier to navigate with breadcrumbs.
The biggest star of the show is the new Built-in Player, which lets you listen to music on the browser youโre using to hunt for your next track. Great for double-checking if the next song is family-friendly before sending it to every speaker in the home.
โBulletproofโ
Users and logins
User profiles for the whole family!
A lot of new features weโve implemented wouldnโt be possible without some form of login and authentication. It was a much-requested feature, as security even within your home shouldnโt be ignored. We know logging in every once in a while can be a minor inconvenience, but weโve tried to make it as unobtrusive as possible, even implementing a way to use your Home Assistant login as a โSingle Sign-Onโ.
You can now have different user profiles with their own music providers. No more having four Tidal accounts all sitting next to each other, cluttering up the Playlists tab. You can even assign who has access to each speaker; say goodbye to the kids playing Demon Hunters on your office speaker during your performance review ๐ . In Settings, just head to the User Management section, where you can add and edit your new users.
โAround the worldโ
Remote music streaming
No matter where, no matter when
One feature made possible with our new login interface is remote music streaming โ yes, thatโs correct, Music Assistant anywhere you can connect to the internet. Weโve created a new web app that allows for remote connections while youโre out and about.
It uses Home Assistant Cloudโs built-in multimedia streaming capabilities (WebRTC) to help route the audio from your Music Assistant server to wherever you are. A Home Assistant Cloud subscription is not required to use this feature; a big shoutout to Nabu Casa for providing their infrastructure for free to our users. Home Assistant Cloud subscribers get access to even more powerful routing, which improves streaming in more places. This subscription also supports the full-time development of Music Assistant ๐.
This connection is peer-to-peer and end-to-end encrypted, meaning no one will know if youโre listening to ABBA ๐. I wouldnโt say itโs ready to replace your current music streaming service, but itโs a great way to get your FLACs playing at a friendโs house. You could even open two instances of the web app and stream it to two devices, and theyโll be synchronizedโฆ but how is that even possible?
โSpin me right roundโ
Introducing Sendspin
For some time, the Music Assistant team has been looking for the best way to stream audio, album art, and other music visualizations to the devices we have around our homes. There are a couple of projects out there doing cool stuff with streaming audio, but not any that fit our needs. So, when it doesnโt exist, itโs time to start building.
Introducing Sendspin, a new multimedia streaming and synchronizing protocol. Itโs fully open source and free to use. Sendspin can stream high-fidelity audio, album art, and visualizer data, automatically adapting to each deviceโs capabilities. Imagine an e-paper display showcasing the album cover, while multiple speakers play in sync, and smart lights pulse to the rhythm.
The best way to use it right now is either via your browser or a Home Assistant Voice Preview Edition running beta firmware. Weโve built the experimental ability to use Sendspin on Google Cast-capable speakers (weโre also looking to do the same with AirPlay-capable speakers), which will allow Sendspin to work with a lot of different hardware.
A big thanks to Maxim and Kevin at the Open Home Foundation, who have been instrumental in making Sendspin a reality. Even though it can do some impressive stuff today, itโs very much a tech preview, and this announcement is our call to all developers and DIY audio hobbyists โ we need your help building and testing this. This is the spec, start building with it!
All the best things in life are meant to be shared, and your music should be as free and open as the software we love. So spin that record ๐ฟ, drop the needle, and send that music across your entire home.
โAeroplaneโ
AirPlay additions
We recently added support for external audio sources, the first being Spotify Connect. This allows you to stream audio from the Spotify app to your Music Assistant server, which could send it across all your speakers, even if they donโt support Spotify Connect. Weโve now added the ability to send AirPlay audio to Music Assistant, which you can then send anywhere in your home.
We also now support AirPlay 2 speakers as a player provider, which means perfectly synced audio across all your AirPlay 2-capable speakers, like HomePods. We recommend reading the limitations in the documentation, as not all AirPlay 2 devices are made equal ๐คฆโโ๏ธ.
โSingโ
Lyrics support
It's time for karaoke!
Never again be left guessing what Kurt is saying in Smells Like Teen Spirit. As of Music Assistant 2.6, you can now see the lyrics of the song youโre playing. If the lyrics provider supports it, there is the ability to have these words time-synced, making it more like karaoke. Lyrics can be found when you open the queue menu and it will be in the โlyricsโ tab (this tab will only appear if the track name, artist and album are matched to the lyrics providers). We started with support of LRCLIB, but have since added Tidal lyric syncing, Genius lyrics, and local LRC files.
โSmooth operatorโ
Smart fading
Making your playlists seamless
Music Assistant is now your personal in-house DJ, perfectly blending one song into the next, and unlike a DJ it always takes your requests ๐. This latest update adds Smart fading, which takes into account the BPM of each song, to make crossfading between songs sound more natural. To turn it on, go to your player of choice, scroll down to the Audio section, and choose โEnable Smart Fadesโ.
โAll the small thingsโ
And much more
None of these updates are small things, but Iโm running out of space, so here is the rest of the hot 100:
There are now DSP presets that allow you to quickly save and apply custom configurations.
Track and share your listening history, with the addition of scrobbling, with support for LastFM, ListenBrainz, and Subsonic.
Several new player providers have been added, including Yamaha MusicCast, and Roku devices running Media Assistant.
Added VBAN as a new input provider.
New radio and podcast providers include Radio Paradise, Podcast Index, BBC Sounds, gPodder, iTunes Podcasts, Dl.fm, and ARD Audiothek.
Canโt follow Phish on tour? Luckily, the new Phish.in provider has you covered. Thereโs also Nugs.net if youโre looking for more live music.
Another cool hodgepodge of audio is the Internet Archive, which can now be added as a provider.
One of Japanโs biggest streaming platforms Niconico has been added as an audio provider ใ๏ธ.
โRebel yellโ
Join the audio revolution
Music Assistant is also cast compatible!
Your music, your players โ itโs time to take back control of your music and the devices you want to play it on. If youโre new to Music Assistant, check how to get started here. While weโre excited about these new features, weโre not hitting pause anytime soon. Weโd love to hear your feedback in the comments or on Discord.
If youโre ever in need of a device that works great with Home Assistant, well, I have just the program for you. Works with Home Assistant is our certification program that ensures devices work seamlessly and locally, all with brands that back them up.
Did you know that this year the Works with Home Assistant program has certified 12 partners across 12 months? Thatโs more than were certified in the two years since the program launched in 2022! The full list of devices is insanely long now (luckily, we made it searchable). To make all this happen over just one year, a lot of important things have been happening behind the scenes.
When we moved it over to the foundation, we also took that chance to beef-up our processes, with robust legal contracts that ensure every partner who joins the program formally commits to things like offering users long-term support and easy updates.
Itโs all about the devices
When we started the program we certified brands, but now we certify devices. This means you know exactly which sensors, switches, or other gadgets have been rigorously tested by us to ensure the best experience with Home Assistant. Each certified device has to work locally, without the need for cloud subscriptions or control.
We can now certify in phases, rather than overwhelming our testers with a truckload of devices in order to launch one partner. Also, if a manufacturer has one device that is cloud-controlled, it doesnโt blacklist any remaining items they have that could operate perfectly well locally. It sometimes means that sometimes your favorite devices arenโt part of the first wave of certification but, trust us, the partners check the comments ๐.
Making it easy to find certified devices
Hereโs a conundrum: the more products that are certified, the harder it is for you to see and find them. The good news is I think weโve cracked it!
Last week, we published the first version of our new searchable certified device list. Previously, youโd have to hunt around for info by checking the integration page or digging through launch blogs to see if a device was certified. Now, certified devices are kept up to date in one central, easy-to-use location, with extra information on the region theyโre available in, the protocol weโve certified them under, and notes about any secondary functionality weโre still working on.
So many (useful) columns!
The badge had a makeover
Every certified device earns the right to display our badge on its packaging, proudly announcing it Works with Home Assistant. If youโre not part of the program, youโre not allowed to use the Home Assistant logo. We used to have different versions of the badges depending on whether the device used Matter, Zigbee, or Z-Wave, and so on, but โ letโs be honest โ they were overcomplicated and impossible to actually read on a box!
Since the badge is such an important signal when youโre browsing products, we decided to simplify it and focus purely on that mark of quality. Now we have just two versions: a color badge and a monochrome design that are easier to read on any packaging.
We love to see the new badge being used IRL!
Companies of all sizes
For 2025, our goal was simple: we wanted both the big names and passionate community projects to be able to join. Yes, weโre thrilled to have major smart home players such as Shelly and Reolink committing to the program, but itโs equally important for us to connect with smaller, community-built projects โ the start-ups or developers who keep open source at the heart of everything they do, like AirGradient and Apollo Automation.
This commitment to inclusivity is a big reason why we keep the annual fee for joining the program deliberately low, at only 500 CHF (per partner, not device) per year. We want to ensure being part of Works with Home Assistant is achievable for everyone who shares our vision.
Some of our team visiting the Apollo booth at IFA Berlin in September.
Improving testing
Testing hasnโt always been perfect โ we knew we needed to make improvements, and the community has been amazing in helping us find things we need to look at. Like everything we do, we learn as we go, we iterate, and we improve. Previously, everyone was testing in their own way, but now weโve standardized the way we test and give feedback to partners. This means testing is more consistent, exacting, and able to handle higher volumes โ one of the reasons why weโve been able to increase the number of devices weโve certified so radically!
A lot of devices that come across our desks donโt pass certification, and itโs often due to organizations not fully understanding the requirements of joining. While this can vary greatly depending on the device and protocol, it was clear we needed to be more transparent. So as well as publishing our Works with Home Assistant Working Group Resolution, weโre also publishing further testing information: this sample testing report for a simple smart plug shows you the process we follow.
Keeping Home Assistant on the bleeding edge
Because we get to see and test new devices in advance, and receive feedback from our certified partners as part of the process, we have a sneak peek into what vendors have in mind for 2026 and beyond. This allows us to look at our product roadmap and see where we need to realign with innovations in the market. By testing todayโs devices, weโre guiding tomorrowโs Home Assistant features!
Spot one of the certified cameras in our State of the Open Home segment
What can be controlled in Home Assistant
A core aim of the program is to ensure all certified devices have their โkey functionalityโ available within Home Assistant. So how do we decide what aspects are controllable in Home Assistant and what doesnโt make the cut?
Key: First, we look at the functionality as a whole. Letโs use a door lock for example. The door should lock and unlock from within Home Assistant. Thatโs key functionality, get it? ๐
Secondary: If the lock also chimes when it locks or unlocks, we think of that as โsecondaryโ functionality. We recommend that the manufacturer has it as an โexposed featureโ in Home Assistant, so you can turn it off during quiet hours for example, but it wouldnโt block certification.
We have to look at whatโs actually supported by the open standard that weโre testing against too. If a feature is not currently supported by the specification, thereโs no way for the manufacturer to actually implement it. This is one of the major challenges in certifying against โyoungerโ specifications such as Matter.
We use our best judgment on this, but we also want your feedback, because everyone has a slightly different point of view, even within our team and testers โ so look out for our user research requests, or please share your thoughts in our comments below!
Connecting with our community
For all this talk of testing, Works with Home Assistant is primarily about people and partnerships! As a foundation, weโre focused on making sure the program stays deeply connected with the community it serves, both online and in person.
Weโve been stepping up our presence at meetups and events around the world, so we can share the latest developments and gather your valuable feedback. From gigantic trade shows like CES in Las Vegas to small, local get-togethers, you can expect to see us there! We also want to do this online, so you can ask partners questions on streams, or in comments โ keep an eye out for more of this in future.
San Diego Meetup
On to 2026
So that was 2025 in a (big) nutshell. As for 2026, we want to kick it off with some wonderful Zigbee partners weโve been working really hard on โ particularly after the awesome launch of Connect ZBT-2. Even though Zigbee is one of the longest-established protocols, itโs actually one of the hardest for us to test and certify because so many devices operate outside the official specification. This means our team and partners do a lot of prep to get them to a testable state โ but in doing so weโre driving big improvements in functionality for everyone!
We also want to improve coverage globally, so, regardless of region, everyone who uses Home Assistant has a good range of certified options to choose from. This means weโre actively seeking partners who will cover regions outside of Europe and North America for everyday essentials like smart plugs and lighting.
As ever, everything coming up will be covered right here โ so stay tuned for updatesโฆ and hereโs to certifying many more devices in 2026! ๐๐ฅณ๐
Release Highlights: Although GeForce Game Ready Drivers and NVIDIA Studio Drivers can be installed on supported notebook GPUs, the original equipment manufacturer (OEM) provides certified drivers for your specific notebook on their website. NVIDIA recommends that you check with your notebook OEM for recommended software updates for your notebook.
Game Ready for Battlefield 6: Winter Offensive
This new Game Ready Driver provides the best gaming experience for the latest new games supporting DLSS 4 technology including Battlefield 6: Winter Offensive and Call of Duty: Black Ops 7. In addition, support for 32-bit GPU-accelerated PhysX effects has been added for select classic titles on GeForce RTX 50 Series GPUs.
Fixed Gaming Bugs
Battlefield 6: Gaming stability issues [5582125]
Counter-Strike 2: Text may appear slightly distorted when in-game resolution is lower than the native resolution of the display [5278913]
Like a Dragon: Infinite Wealth: Light flickering after driver update on some system configurations [5432356]
Like a Dragon Gaiden: The Man Who Erased His Name: Corruption after driver update on some system configurations [5432356]
Black Myth: Wukong: Lower performance in driver branches newer than R570 [5562283]
Monster Hunter World: Iceborne: Some particle effects may be missing on GeForce RTX 50 Series GPUs [5546598]
Call of Duty: Black Ops 3: Gameplay becomes dim over time [5488108]
Madden 26: Stability issues [5535693]
Users running R580 branch drivers (58x.xx) or newer may observe lower performance in some games after updating to Windows 11 October 2025 KB5066835 [5561605]
The Witcher 3: Wild Hunt: Random corruption on main character's sword corruption [5363151]
Fixed General Bugs
Adobe Premiere Pro: Freeze During Export Using Hardware Encoding [5431822]
Sophos Home Antivirus: System stability issues [5581371]
Green line observed while viewing videos in Chromium browser on GeForce RTX 50 Series GPUs [5535388]
As the year winds down and the holidays approach, weโre closing out 2025 with a release thatโs all about giving you more control and a little bit of magic. โจ
This month, weโre unveiling Home Assistant Labs, a brand-new space where you can preview features before they go mainstream. And what better way to kick it off than with Winter mode? โ๏ธ Enable it and watch snowflakes drift across your dashboard. Itโs completely unnecessary, utterly delightful, and exactly the kind of thing we love to build. โ๏ธ
But thatโs just the beginning. Weโve been working on making automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] more intuitive over the past releases, and this release finally delivers purpose-specific triggers and conditions. Instead of thinking in (numeric) states, you can now simply say โWhen a light turns onโ or โIf the climate is heatingโ. Itโs automation building the way our mind works, as it should be. ๐ง
Oh, and if youโre looking to level up your Zigbee or Thread network, check out the Home Assistant Connect ZBT-2 we released last month. Itโs four times faster and has a gorgeous new antenna design that youโll actually want to display on your desk. ๐ก
From all of us working on Home Assistant:
Thank you for an amazing 2025! โค๏ธ
Happy holidays, and enjoy the release!
../Frenck
A little holiday cheer ๐๐ถ
Jingle Labs by Frenck and Darren
Dashing through the code,
With a brand-new Labs to show,
Snowflakes start to fall,
Watch the dashboard glow!
Triggers now make sense,
Conditions feel just right,
What fun it is to automate,
Your smart home every night!
Chorus
Jingle Labs, jingle Labs,
Features on the way!
Oh what fun it is to run,
Home Assistant every day, hey!
Jingle Labs, jingle Labs,
Winter mode is here!
Turn your lights on with a thought,
And spread some holiday cheer!
Power graphs are live,
Water meters too,
Dashboards you can set,
For every userโs view!
Xbox got some love,
Shellyโs platinum now,
Contributors came through this year,
Take a final bow!
Chorus
Jingle Labs, jingle Labs,
Triggers for the win!
Climate, lights, and fans galore,
Let the automations spin!
Jingle Labs, jingle Labs,
Thank you all so much!
Happy holidays from us,
Now go and automate stuff!
When we develop new features for Home Assistant, we often find ourselves in a tricky spot. A feature might be fully built and tested, but weโre not entirely sure if itโs the right fit for everyone just yet. Maybe we want to gather some real-world feedback first, or perhaps we want to see how the community uses it before committing to keeping it around forever.
Thatโs where Home Assistant Labs comes in! ๐งช
Labs is a brand-new place in Home Assistant that gives you a sneak peek at features weโre working on. These are not unfinished experiments or unstable beta features. They are fully functional and tested, but they might change or even disappear based on feedback. We are committed to building in the open, and we want to give more people the choice to hop into the lab with us. By joining us, your feedback will directly help refine these features for the entire community.
The very first preview feature available in Labs is Winter mode โ๏ธ, inspired by a community post on Reddit originally created by u/Possible-Week-5815. Enable it, and watch your Home Assistant interface transform into a winter wonderland with falling snow. A fun way to get into the holiday spirit!
When you enable a preview feature, you can also choose to create a backup first, just to be safe. And if you change your mind? Simply disable it again. No restart required!
Preview features are off by default, and enabling them wonโt affect your existing setup. Itโs completely optional, so if you prefer to stick with the battle-proven experience, thatโs totally fine. But if youโre curious and want to explore whatโs coming next, Labs is the place to be.
But what was the first Labs preview feature we put in there? Well, itโs a big oneโฆ
Purpose-specific triggers and conditions
Almost two years ago, we released a new automationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] editor that unwrapped all our actionsActions are used in several places in Home Assistant. As part of a script or automation, actions define what is going to happen once a trigger is activated. In scripts, an action is called sequence. [Learn more] and made them easier to understand. Instead of a single, obscure โCall serviceโ action, you now see clear options like โLight: Turn onโ or โMedia Player: Set Volumeโ.
Ever since, weโve been wondering: could we do the same for triggersA trigger is a set of values or conditions of a platform that are defined to cause an automation to run. [Learn more] and conditionsConditions are an optional part of an automation that will prevent an action from firing if they are not met. [Learn more]? Instead of relying on technical, state-based options, what if we could offer intuitive alternatives that just make sense? Options like โWhen a light turns onโ or โIf a light is onโ.
That idea set a two-year plan in motion, and today itโs finally becoming a reality.
Along the way, we discovered something interesting: many of you take a โtarget-firstโ approach when building automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more]. You think about what you want to automate (a deviceA device is a model representing a physical or logical unit that contains entities., 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], or an areaAn area in Home Assistant is a logical grouping of devices and entities that are meant to match areas (or rooms) in the physical world: your home. For example, the living room area groups devices and entities in your living room. [Learn more]) before thinking about how to automate it (which action to perform or which trigger to use). This release embraces that mindset with a completely new way to build automations.
Purpose-specific triggers and conditions are now provided directly by domainsEach integration in Home Assistant has a unique identifier: The domain. It is often shown as the first part (before the dot) of entity IDs. like Light, Climate, Fan, and others, covering the most common automation use cases.
These new triggers and conditions fully support targeting. This means you can trigger an automation when any light in your living room turns on, without having to list them one by one or create a group beforehand. Targeting an area keeps things simple: itโs always aligned with how your home is organized, and you donโt have to update anything when you add or remove devices.
LabelsLabels in Home Assistant allow grouping elements irrespective of their physical location or type. Labels can be assigned to areas, devices, entities, automations, scenes, scripts, and helpers. Labels can be used in automations and scripts as a target for actions. Labels can also be used to filter data. [Learn more] are supported too! You can now check if any of your Christmas lights are on. Perfect timing for the holidays! ๐
Weโve also introduced a new way to pick triggers, conditions, and actions that fits this target-first approach. You can navigate your home by floorA 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], then area, then device, and see exactly which options are available for each target. Itโs a much more intuitive way to build automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more].
This feature is still being refined, so weโve made it available as a preview feature in Labs. Head over to Settings > System > Labs to enable it and help us shape the future of automation building!
More dashboard improvements!
We have a lot of dashboard improvements to share in this release! From better default dashboard management to an improved Home dashboard, we have been busy making your Home Assistant experience even better.
Set a system-wide default dashboard
Picking a default dashboard is now a system-level setting that takes effect instantly for all users on your Home Assistant installation. The dashboard you choose will appear at the top of the sidebar, replacing the current default.
But donโt worry, personal preferences still matter! We added a new setting in your User profile where you can override the system default and set your own preferred dashboard.
If you set your phone to one dashboard and your wall tablet to another, theyโll now both revert to the default dashboard. If you want your wall tablet to use a different dashboard than your other devices, we recommend giving it a separate user profile that you can customize however you want.
Reorder areas and floors
When using the built-in dashboard experiences (Home, Lights, Security, and others), one of the main pain points was the strict ordering of areasAn area in Home Assistant is a logical grouping of devices and entities that are meant to match areas (or rooms) in the physical world: your home. For example, the living room area groups devices and entities in your living room. [Learn more] (alphabetically) and 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] (numerically by level). This often didnโt make sense in a real home, where your guest bathroom shouldnโt appear before your living room, and the attic is rarely more relevant than the main floor.
Now you can go to Settings > Areas, labels & zones and use the new Reorder floors and areas menu to manually drag and drop any area or floor to reorder them. Your changes will instantly apply to all built-in dashboards that show areas and floors.
Experimental dashboards have graduated
With the launch of Labs, we retired the experimental flag from the dashboard creation list. The Home dashboard can now be found in the dashboard list (still not visible by default), and the Areas dashboard has evolved into Home, so weโve removed it for now. If youโre using the Areas dashboard, it will continue to work; you just wonโt be able to create another.
Note
We want to keep hearing your voice! Share your experience with us in the Home dashboard survey and help us improve every step of the way. And of course join us on Discord to work together on the future of dashboards.
Home dashboard improvements
We added a new sidebar to the Home dashboard that gathers quick access links we think are useful for you. Thereโs also a nicer area and floor layout that uses space more efficiently. On a more technical level, the Home dashboard is now a proper built-in dashboard and shows up in the dashboard list.
Important
There is a chance your current favorites might disappear in this release and need to be re-added. This is due to the migration of this dashboard from a strategy to a built-in dashboard.
Undo and redo in the dashboard editor
The dashboard editor now includes the undo and redo feature that we added in 2025.10 to the automationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] and scriptScripts are components that allow you to specify a sequence of actions to be executed by Home Assistant when turned on. [Learn more] editor. This allows you to experiment safely while editing your dashboards. You can undo up to 75 changes or restore them with a single click, making editing dashboards faster and less stressful.
Thanks to @jpbede for implementing this handy feature!
Power and water in the Energy dashboard
The Energy dashboard has been helping you track your energy and gas usage for years now, and this release brings two great additions: real-time power monitoring and downstream water tracking.
Real-time power monitoring
Until now, the Energy dashboard was all about energy: the cumulative kWh youโve consumed or produced over time. But sometimes you want to know whatโs happening right now. How much power is that appliance actually drawing? Is your solar system producing at this very moment?
With this release, you can now configure power sensors alongside your energy sensors. Track your real-time grid consumption, see how much youโre exporting back to the grid, and watch those watts flow in real-time. The power configuration options now appear alongside energy settings for each source or device, and new power graphs let you see your power consumption throughout the day.
Downstream water meters
The Energy dashboard has been tracking your water consumption for a while now, but it was missing something: the ability to see where all that water is actually going. Just like you can track individual devices for energy consumption, you can now add downstream water meters to break down your water usage.
Got a smart irrigation controller? A water softener with a flow meter? A separate meter for your pool? Now you can track them all and see exactly how your water consumption is distributed across different uses.
Thereโs also a brand-new water sankey card that visualizes your water flow, just like the energy sankey diagram you already know. Itโs a great way to see where your water is going at a glance.
The new water sankey card shows where your water is going at a glance.
New energy layout
To make room for this new functionality, the Energy dashboard has been reorganized. Donโt worry: if you only have energy configured, youโll still see the same dashboard. But if you add water, gas, or power, the dashboard will be split into several tabs.
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:
Airobot, added by @mettolen
Control and monitor your Airobot smart thermostats for intelligent floor heating control via the local REST API.
Anglian Water, added by @pantherale0
Integrate your Anglian Water smart water meter to track water usage and consumption costs.
Backblaze B2, added by @ElCruncharino
Use a Backblaze B2 cloud storage bucket as a backup location for your Home Assistant backups.
EnergyID, added by @Molier
Sync anything from your home directly to EnergyID for advanced analytics, performance tracking and benchmarking.
Essent, added by @jaapp
Monitor dynamic electricity and gas prices for Essent customers in the Netherlands with variable pricing contracts.
Google Air Quality, added by @Thomas55555
Get real-time air quality data for your location using Googleโs Air Quality API.
Google Weather, added by @tronikos
Use Google Weather as a source for weather data, providing current conditions, hourly forecasts for the next 24 hours, and daily forecasts for the next 10 days.
Hanna, added by @bestycame
Fetch pool water quality data from your Hanna Pool Controller device, including pH, chlorine levels, ORP values, and water temperature.
Home Assistant Labs, added by @frenck
A dedicated panel where you can preview and test new features before they become standard in Home Assistant.
Philips Hue BLE, added by @flip-dots
Control your Philips Hue Bluetooth lights directly with Home Assistant, without the need for a Hue Bridge.
Saunum, added by @mettolen
Integrate your Saunum Leil sauna control unit to precisely control temperature and monitor your saunaโs operation.
Victron BLE, added by @rajlaud
Integrate Victron Energy devices that support the Bluetooth Low Energy protocol for real-time monitoring.
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 are also being constantly improved. Here are some of the noteworthy changes to existing integrations:
@piitaya updated the ESPHome integration to let Home Assistant generate entity IDs using its standard rules, aligning it with how other integrations work.
Thanks to @bdraco, you can configure Wi-Fi on Shelly generation 2+ devices directly from Home Assistant via Bluetooth.
Shelly now supports control modes for upcoming Shelly Cury devices. Nice work, @bieniu!
The Tuya integration received a lot of love! Cat litter boxes now expose switches, buttons, lights, and sensors for controlling your petโs automated litter box. On top of that, doorbell events are now supported too. Thanks, @heindrichpaul!
@starkillerOG expanded the Reolink integration with an exposure mode select and audio noise reduction controls for supported cameras.
Air conditioner and microwave support has landed in the Home Connect integration, expanding the range of supported BSH appliances. Thanks, @Diegorro98!
@zerzhang added support for the SwitchBot smart thermostat radiator to the SwitchBot integration. Nice!
The Xbox integration got some love from @tr4nt0r! You can now link multiple Xbox accounts, track how many friends you (and your friends) have, see if theyโre in a party, and control more remote functions. The media browser also gained a new category showcasing official game art and screenshots.
Got an Ecovacs robot? The Ecovacs integration now has a border spin switch (to reach those tricky edges while mopping) and an auto-empty select entity. Thanks, @aronnebrivio!
The VeSync integration gained a child lock switch, giving you control over this safety feature for your devices. Thanks, @cdnninja!
The SQL integration now supports using templates in your queries, giving you more flexibility when querying your databases. Great addition, @gjohansson-ST!
@tomwilkie expanded the Prometheus integration to export metrics for the water_heater domain.
The Anthropic integration now supports AI task entities. Thanks, @Shulyaka!
Portainer can now show you resource usage of your containers. Nice work, @erwindouna!
@thomasddn added a button to enable reduced guard mode for compatible vehicles to the Volvo integration.
The Plugwise integration now supports the new Anna P1 device and gained a select entity for zone profiles on Adam devices. Thanks, @bouwew!
Bang & Olufsen users can now use their Beoremote One with Home Assistant. The remoteโs buttons are exposed as event entities. Awesome, @mj23000!
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:
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:
The following integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] are no longer available as of this release:
Dominos Pizza: The Dominos Pizza integration has been removed. The integration no longer functions and its underlying source has been unmaintained since 2019.
Flick Electric: The Flick Electric integration has been removed. All customers of the Flick Electric company have already been moved to Meridian Energy. The service this integration used is already non-functional.
The following integrations have been removed as they are incompatible with the currently supported installation methods:
Bluetooth Tracker
CUPS
Decora
dlib Face Detect
dlib Face Identify
Eddystone Temperature
GStreamer
Keyboard
LIRC
Pandora
Raspberry Pi Camera
SMS
Snips
TensorFlow
Other noteworthy changes
There are many more improvements in this release; here are some of the other noteworthy changes:
New template math functions! @akx added clamp, wrap, and remap to manipulate numbers in your templates. Awesome!
The activity card now supports filtering by state, making it easier to see specific events. Nice one, @karwosts!
@MindFreeze added min and max options to the bar gauge feature for tile cards, giving you more control over the gauge range.
You can now delete helpers directly from the helpers panel, without having to open them first. Thanks, @frenck!
The blueprints panel now shows how many automations and scripts use each blueprint. Great for keeping track, @EarMaster!
@timmo001 added a handy trick: double-click the automation editor sidebar to reset its width.
Labels now show up on the device information card, making it easier to see how your devices are organized. Thanks again, @timmo001!
Get insight into your AI conversations
Ever played around with AI in Home Assistant and wondered what data is actually being sent?
@balloob upgraded the voice assistant debug interface, and you can now inspect the system prompt that tells the AI how to behave, along with any tool calls it made to generate your answer.
This makes it much easier to figure out why the AI decided to skip over that one 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], or why it called a specific tool. You can find the debug interface in the voice assistant configuration panel.
Add entities to Android widgets and favorites
If youโre using the Home Assistant Companion app for Android, thereโs a handy new feature waiting for you! Starting with app version 2025.11, you can now add 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] to widgets and Android Auto favorites directly from the entityโs more info dialog.
With just a few taps, you can:
Add widgets for quick control of entities right from your home screen
Set entities as Android Auto favorites, making them quickly accessible in your car
No more deep-diving into app settings! The Add to option appears in the more info dialog with options tailored to the entity youโre viewing. For example, adding a media player widget is only available for media players.
This is a first step in integrating native mobile features directly into the Home Assistant interface. Future releases will expand this with support for creating shortcuts, tiles, and watch favorites.
We will also release patch releases for Home Assistant 2025.12 in December. ๐
These patch releases only contain bug fixes. Our goal is to release a patch
release once a week, aiming for Friday.
Bump aiomealie to 1.1.1 and statically define mealplan entry types (@andrew-codechimp - #158907)
Update systembridgeconnector to 5.2.4, fix media source (@timmo001 - #158917)
Assume cover or valve is always โrunningโ in google assistant when the state is assumed or the position is reported to allow it to be be stopped (@jbouwh - #158919)
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:
Core and Supervised installation methods, and 32-bit systems
After a 6-month deprecation period, support for the Home Assistant Core and Home Assistant Supervised installation methods, as well as all 32-bit system architectures (i386, armhf, and armv7), has now been fully removed.
These installation methods and architectures will no longer receive updates, including security updates. If you are still using one of these installation methods or architectures, please migrate to a supported installation method and architecture as soon as possible to continue receiving updates and support.
Hive has removed support for their security products. We have removed the alarm control panel from the integration, as the Hive APIs no longer support these products.
The legacy license plate event sensor has been removed from the UniFi Protect integration, as it no longer functions with Protect 6 and newer. The UniFi Protect integration has not been compatible with Protect versions older than 6 for quite some time.
This sensor has been replaced with a new Vehicle Detection Event entity that provides significantly more functionality, including license plate recognition, vehicle type detection, color detection, and confidence scores. The new event entity fires with a 3-second delay to ensure optimal thumbnail and LPR data quality.
The Xbox media browser has been completely overhauled to support multiple accounts and introduce a range of other improvements. As part of this update, the format of the media-source identifiers has been changed as well.
The following and followers sensors introduced in the last release previously included friends in their counts. After a recent API update, friends are no longer included.
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:
Taipei, Taiwan โ 26 november 2025 โ Synology heeft vandaag Deep Search geรฏntroduceerd, een AI-gestuurde zoekmachine voor bestanden die is ontworpen om
Log in
