Lees weergave

Bitfocus Companion v4.1.6

📦 Downloads available at

💵 Donate to the project at

Companion v4.1.6 - Release Notes

🐞 BUG FIXES

  • Setting local variables for another control failing #3813
  • Unable to select module beta version for connection #3815
  • Suppress some logged errors about local variable names
  • Avoid spamming log with surface lock state messages #3792

Full Changelog: v4.1.5...v4.1.6

  •  

BookStack v25.11.6

Security Release

BookStack v25.11.6 has been released.

This is a security release to address a vulnerability in our dependencies related to XML
handling, which could allow users to replay SAML authentication requests with specially crafted & manipulated requests.

It's strongly advised to update if you're using SAML authentication for BookStack.

Full List of Changes

  • Updated application PHP dependencies.

  •  

Minecraft 1.21.11 (stable) Released

1.21.11, the release of Mounts of Mayhem, is a game drop for Java Edition released on December 9, 2025, which adds the nautilus, zombie nautilus, nautilus armor, spears, netherite horse armor, camel husks, parched, and zombie horsemen. Full changelog: https://minecraft.wiki/Java_Edition_1.21.11
  •  

More devices, more choice: celebrating a massive year for certification

More devices, more choice: celebrating a massive year for certification

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.

Moving to a non-profit foundation

In August 2024, the Open Home Foundation took over Works with Home Assistant. This helped reinforce that this program is not a commercial venture: it exists solely to connect our users with brands that support the foundation’s core values of privacy, choice, and sustainability.

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! 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! 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. 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 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?

  1. 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? 😉
  2. 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.
  3. 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 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! 🎉🥳🎊

  •  

Firefox 146.0

New

  • Windows 10 users can now automatically protect their passwords, bookmarks, and more by turning on backup in Firefox. Your browsing data is saved daily on your device and can be encrypted with a password. When you set up a fresh install of Firefox on any operating system for a new device or your current one, you can restore from this backup and pick up right where you left off. This feature is currently available on Windows devices and will be coming to other operating systems soon.

    Fx Backup Image

    This feature is part of a progressive roll out.

    What is a progressive roll out?

    Certain new Firefox features are released gradually. This means some users will see the feature before everyone does. This approach helps to get early feedback to catch bugs and improve behavior quickly, meaning more Firefox users overall have a better experience.

  • MacOS users now have a dedicated GPU process by default. This includes WebGPU, WebGL, and Firefox's own WebRender. With this feature enabled, fatal errors in graphics code will no longer crash the browser, and will instead transparently restart the GPU process.

  • Firefox Labs is now available to all desktop users, regardless of whether they choose to participate in studies or submit telemetry. This means more experimental features are now available to more people.

  • Users can now skip the results page and see direct results as they type in the search bar for faster, simpler browsing.

    Skip the Result Page Example

    This feature is part of a progressive roll out.

    What is a progressive roll out?

    Certain new Firefox features are released gradually. This means some users will see the feature before everyone does. This approach helps to get early feedback to catch bugs and improve behavior quickly, meaning more Firefox users overall have a better experience.

  • There is a New Tab Weather opt-in workflow available for users in the EU and some other countries, where they can choose whether to enable location detection or manually search for a location.

    Newtab Weather workflow

    This feature is part of a progressive roll out.

    What is a progressive roll out?

    Certain new Firefox features are released gradually. This means some users will see the feature before everyone does. This approach helps to get early feedback to catch bugs and improve behavior quickly, meaning more Firefox users overall have a better experience.

  • Firefox now natively supports fractional scaled displays on Linux (Wayland), making rendering more effective.

  • For users of the English-language versions of Firefox in France, Germany, and Italy, the address bar now shows English-language suggestions for holidays and other important dates.

Fixed

  • When the timepicker is enabled for <input type="time"> and <input type="datetime-local">, it now provides full keyboard and assistive technology support. This update also improves the behavior of the time spin buttons for users who prefer reduced motion. The Firefox Accessibility team hopes that making the built-in timepicker accessible will encourage wider adoption of browser-provided time and date inputs across the web, reducing the need for custom controls, and improving accessibility for all users.

  • Various security fixes.

Changed

  • The Colors dialog in Settings now uses clearer color picker controls that keep each color sample next to its label. It makes it easier to understand and adjust text, background, and link colors when using a forced colors palette to customize the default text, link, and page background colors, especially with or without screen magnifiers.

    Colors dialog in Settings

  • Firefox removed support for Direct2D on Windows. If you still require Direct2D support, please use ESR 140.0 or higher.

Enterprise

Developer

  • Firefox now supports ML-KEM for WebRTC, by sending a post-quantum (PQ) key share during the DTLS 1.3 handshake. ML-KEM is the next-generation public-key cryptosystem that is believed to be secure against attackers with large quantum computers.

  • Firefox now supports compressed elliptic curve points in WebCrypto. These reduce the size of public keys by nearly half, saving bandwidth and storage, while still allowing the full point to be reconstructed mathematically.

  • The Skia graphics library has been updated to improve rendering performance and compatibility.

  • Unused CSS custom properties are now hidden by default in the Rule view of the Inspector. This not only reduces clutter, but in some cases also speeds up the rendering of the inspector panel.

Web Platform

  • The @scope rule is now supported, allowing authors to restrict styling to a subtree of the DOM. This avoids having to write overly-specific selectors.

  • Firefox now supports the contrast-color() CSS function that takes a color value and returns a contrasting color. Note that the specification currently restricts the contrasting color to black or white. This limitation is expected to be removed in the future. (Learn more)

  • Introduced the text-decoration-inset property, which allows authors to adjust the start and end points of line decorations.

  • Firefox now supports the legacy -webkit-fill-available keyword as a value for the CSS width and height properties. This improves rendering of content on websites that use this value. This keyword is an alias for the recently standardized stretch keyword, which is not yet enabled in Firefox.

Unresolved

  • On Windows, clicking tabs may not work at the very top of the screen when Firefox is maximized on a second monitor. We’re working to fix this in a future release. (Fixed in 147.0)

Community Contributions

  •  

Counter-Strike 2 Update

[p]\[ RENDERING ][/p]
  • [p]Improved shadow fidelity on view models.[/p][/*]
  • [p]Added local client icon cache for inventory items.[/p][/*]
  • [p]Fixed a case that caused a small number of users to receive an erroneous VAC ban. The bans will be removed.[/p][/*]
  •  
❌