Normale weergave

BEGA joins Works with Home Assistant

5 Mei 2026 om 02:00
BEGA joins Works with Home Assistant

How do you more or less double the number of Works with Home Assistant-certified devices available to our community? Have BEGA join the program! This German firm has spent more than 75 years designing a wide range of architectural lighting that sets the industry standard: and now they’re bringing that expertise to your smart home.

Bright BEGA-nnings

If you haven’t heard of BEGA before, you may have admired their work without realizing it. That’s because they produce the kind of beautifully engineered fixtures you see gracing the facades of fancy hotels, elegant public buildings, and stylish modern homes worldwide. They’re probably better known for this kind of work than for smart home tech, which is precisely what makes their joining the Works with Home Assistant program so exciting.

Because BEGA aren’t just dipping a toe in: they’re bringing what’s almost certainly the largest single addition of certified devices we’ve ever had in one go: enough to very nearly double the number of certified products in the program! And it’s not just the volume that impresses. BEGA Smart – their Zigbee-powered smart lighting system – is flexible, expandable, and designed to work entirely offline, with no internet connection required.

BEGA: putting the smart into smart home lighting. BEGA: putting the smart into smart home lighting.

"With BEGA Smart, we aim to combine high-quality architectural lighting with intelligent control. Integrating with Home Assistant allows us to bring our lighting solutions into an open and flexible smart home ecosystem that many of our customers already value. By doing so, we enhance comfort, safety, and energy efficiency while enabling new ways to experience light. We're excited to support the community and be part of this ecosystem."

- Heinrich Gantenbrink, Managing Partner at BEGA

Beyond beautiful design

BEGA’s premium positioning isn’t only about aesthetics. Their commitment to repairability also aligns well with the Open Home Foundation’s sustainability principles. Rather than treating a luminaire as a disposable unit, BEGA designs the majority of their components to be replaceable. Crack a glass panel? You can order that specific spare via their website’s search function and replace it, rather than throwing out the whole fixture.

This also makes BEGA an interesting choice if you’re thinking about illuminating your outdoor spaces. We have relatively few outdoor lighting options in the program, and BEGA fills that gap in style – just in time if you’re looking to get your garden or terrace ready for summer 😎.

Let there (Zig)bee light

We mentioned BEGA Smart runs on Zigbee, but if that’s new to you, here’s what it means. Zigbee is basically a short-range wireless communication standard: like Wi-Fi, but designed specifically for smart home devices. Unlike Wi-Fi however, it’s an open standard, so isn’t run by one specific company, and connects directly to Home Assistant without needing a router or internet connection. It’s also a mesh protocol, which means the more devices you add to your network, the stronger and more reliable it gets – handy for lighting that’s spread across your home and garden.

And on that subject, if you want to dim the patio lights from your sofa, or check they’re off while you’re away, Home Assistant Cloud can help – providing secure remote access wherever you are (your subscription helps fund the Works with Home Assistant program too!).

The path to enlightenment, with BEGA devices. The path to enlightenment, with BEGA devices.

Devices

As with every Works with Home Assistant partner, our in-house team has thoroughly tested BEGA’s devices to make sure they meet our core requirements: local control, privacy, and long-term sustainability.

Because the list of certified BEGA devices is so long, we’ve included a condensed list below (there’s not enough room for them all here without subjecting you to a loooonnnnnng scroll! 😄). Bear in mind, when you browse BEGA’s website, look for devices marked as BEGA Smart. This tells you the item is Zigbee enabled and Works with Home Assistant certified. Worth knowing, since each luminaire also comes in other variants, such as DALI or non-smart versions, which are not certified under the program.

BEGA Smart covers a swathe of indoor and outdoor luminaires, with wall or ceiling mounted options, as well as freestanding garden path lighting to illuminate those balmy summer evenings.

  • BEGA Smart Outdoor Ceiling luminaire (two variants)
  • BEGA Smart Indoor Ceiling luminaire (nine variants)
  • BEGA Smart Wall Outdoor Luminaire (10 variants)
  • BEGA Smart Outdoor Garden and pathway luminaire (79 variants)
  • BEGA Smart Indoor Ceiling and wall luminaire (two variants)
  • BEGA Smart Indoor table lamp (three variants)
  • BEGA Smart Outdoor Ceiling and wall luminaire (35 variants)
  • BEGA Smart Outdoor PRIMA wall luminaire (eight variants)
  • BEGA Smart Outdoor PRIMA ceiling and wall luminaire (eight variants)
  • BEGA Smart Outdoor PRIMA ceiling mounted downlight (eight variants)

For the full list of certified BEGA devices, see our filtered device list.

Dazzled by choice

With BEGA on board, Home Assistant users have more choice than ever when it comes to quality lighting, inside and out. Ready to explore the full range? Head over to our certified device list to be illuminated about everything that’s been approved from BEGA and beyond. The future of your smart home is looking bright 💡.

FAQs

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

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

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

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

How were these devices tested?

All devices in this list were tested using a standard Home Assistant Green Hub with the Home Assistant Connect ZBT-2 and with our Zigbee integration (ZHA). If you have another hub/antenna setup/integration that’s not a problem, but we test against these as they are the most effective way for our team to certify within our ecosystem.

Will you be adding more BEGA devices to the program?

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

  •  

v25.12.3

7 Mei 2026 om 22:46

Hi,

The OpenWrt community is proud to announce the third service release of the OpenWrt 25.12 stable series.

Download firmware images using the OpenWrt Firmware Selector:

Download firmware images directly from our download servers:

Main changes between OpenWrt 25.12.2 and OpenWrt 25.12.3

Only the main changes are listed below. See the full changelog for details.

Security fixes

  • Linux kernel: fixes CVE-2026-31431 ("Copy Fail"). In earlier releases this only affected users on the starfive target and users who had installed kmod-crypto-user.
  • mbedtls: update to 3.6.6 (multiple CVE fixes)
  • OpenSSL: update to 3.5.6 (multiple CVE fixes)
  • wolfSSL: update to 5.9.1 (multiple CVE fixes)

Device support

New devices supported in 25.12.3:

  • mediatek: filogic: ASUS RT-AX52 PRO
  • mediatek: filogic: D-Link AQUILA PRO AI E30
  • mediatek: filogic: Huasifei WH3000 Pro (NAND variant)
  • mediatek: filogic: Keenetic KAP-630 / Netcraze NAP-630
  • mediatek: filogic: Zbtlink ZBT-Z8106AX-T
  • mediatek: filogic: Zyxel WX5600-T0
  • ramips: mt7621: EDUP EP-RT2983
  • ramips: mt76x8: Cudy LT300 v3
  • x86: DFI ADN553
  • x86: DFI ASL553

Device fixes:

  • ath79: Netgear WNDAP360: multiple fixes restoring proper operation (sysupgrade, kernel loader, ethernet, LED, serial baud rate and U-Boot environment)
  • ath79: Extreme Networks WS-AP3805i: fix U-Boot environment configuration
  • ath79: Mikrotik: fix included device packages
  • ipq50xx: Linksys MX5500: add label MAC device assignment
  • lantiq: Netgear DGN3500: fix U-Boot environment size — device was broken on 25.12 (#22692)
  • mediatek: filogic: Bananapi BPI-R4: add device tree overlay for the BE14 WiFi 7 module — fixes very low WiFi TX power on this module (#17489)
  • mediatek: filogic: Keenetic KN-1812: various Ethernet PHY device tree fixes (PHY reset, interrupt support, MDIO drive strength, partition naming, xsphy node)
  • mediatek: filogic: Netgear EAX17: fix rootfs hash in FIT node for per-device rootfs builds
  • mediatek: filogic: CMCC RAX3000M: add Airoha AN8855 switch support (#21230)
  • mediatek: filogic: Zbtlink ZBT-Z8103AX-D: enable NMBM on the SPI-NAND flash
  • mvebu: ClearFog Base/Pro: fix switch kernel module
  • qualcommax: ipq50xx: Xiaomi AX6000: enable PCIe1 for QCA9887
  • qualcommax: ipq807x: Linksys MX5300: add label MAC assignment
  • ramips: Yuncore CPE200: fix EEPROM size
  • ramips: mt7621: fix reset hang
  • ramips: Wavlink WL-WN575A3: fix EEPROM size for 5 GHz WiFi
  • ramips: Xiaomi Mi Router 4C: fix WAN LED GPIO (#18578)

WiFi fixes and improvements

  • wifi-scripts: fix incorrect erp_domain and fils_cache_id values generated by the ucode-based config script (#21768)
  • wifi-scripts: add missing bridge_isolate and network_vlan fields to the ucode schema (#22620)
  • wifi-scripts: add missing iface and other fields to the ucode station/vlan schema (#22165)
  • wifi-scripts: add EHT (WiFi 7) rates to set_fixed_freq

Networking and system fixes

  • mbedtls: backport upstream patches to fix TLS 1.2 client issues — fixes a regression that broke DDNS updates and other TLS 1.2 client connections; the regression was introduced in mbedtls package updates shipped after the 25.12.2 release (#22874)
  • base-files: sysupgrade: fix -u option (skip default configuration) which was broken with apk
  • base-files: sysupgrade: fix -f (custom backup) when the path contains spaces
  • base-files: sysupgrade: update backup exclusion list
  • base-files: use DISKSEQ instead of MAJOR/MINOR for stable disk identification (MAJOR/MINOR are not sequential)
  • lantiq: fix mtdparsers refcount and memory leak
  • uqmi / umbim: introduce devpath option for selecting cellular modems by USB device path
  • kernel: add kmod-vsock and kmod-vsock-virtio for VM guests (vsock communication)

Core component updates

  • Linux kernel: update from 6.12.74 to 6.12.85
  • ca-certificates: update from 20250419 to 20260223
  • linux-firmware: update from 20251125 to 20260221
  • mbedtls: update from 3.6.5 to 3.6.6 (security fixes)
  • OpenSSL: update from 3.5.5 to 3.5.6 (security fixes)
  • wireless-regdb: update from 2026.02.04 to 2026.03.18
  • wolfSSL: update from 5.8.4 to 5.9.1 (security fixes)
  • xdp-tools: update from 1.4.3 to 1.6.3

Upgrading to 25.12.3

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.
For upgrades within the OpenWrt 25.12 stable series, Attended Sysupgrade is also supported, which allows preserving the installed packages.

  • Sysupgrade from 23.05 or earlier 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. fc0c518

  • Bananapi BPI-R4: Interface eth1 was renamed to sfp-lan or lan4, and interface eth2 was renamed to sfp-wan to match the labels. You have to upgrade without saving the configuration. cd8dcfe

  • TP-Link RE355 v1, RE450 v1 and RE450 v2: The partition layout and block size changed in this release to fix configuration loss on sysupgrade. Users upgrading from OpenWrt 25.12.0 or earlier must use sysupgrade -F to force the upgrade. The image must not exceed 5.875 MB (6016 KiB).

  • Meraki MX60: Direct sysupgrade to 25.12.3 is not possible without manual preparation — meraki_loadaddr must be changed before upgrading, as the default value is insufficient to boot OpenWrt 25.12+. See the device wiki page for instructions.

Known issues

  • Zyxel EX5601-T0: the WAN interface was renamed from eth1 to wan — check and update your network configuration after upgrading.
  • Pixel 10 phones have problems connecting to WPA3-protected WiFi 6 APs. #21486
  • 802.11r Fast Transition (FT) causes connection problems with some WiFi clients when WPA3 is used. #22200
  • SQM CAKE MQ (cake_mq): throughput may be unexpectedly low on some configurations after the scheduler fixes in this release. #22344

Full release notes and upgrade instructions are available at
https://openwrt.org/releases/25.12/notes-25.12.3

In particular, make sure to read the known issues before upgrading:
https://openwrt.org/releases/25.12/notes-25.12.3#known_issues

For a detailed list of all changes, refer to
https://openwrt.org/releases/25.12/changelog-25.12.3

To download the 25.12.3 images, navigate to:
https://downloads.openwrt.org/releases/25.12.3/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org?version=25.12.3

As always, a big thank you goes to all our active package maintainers, testers, documenters and supporters.

Have fun!

The OpenWrt Community


To stay informed of new OpenWrt releases and security advisories, there
are new channels available:

  •  
❌