neat.no

Neat Devices: Version 26.1.0 Release Notes

Last updated on April 30, 2026

If you’d like to get email updates about new releases, please subscribe here.

Contents

1. Introduction

This document describes the new features, improvements, bug fixes, and known issues in the 25.4.2 software releases for Neat Bar, Neat Bar Gen 2, Neat Bar Pro, Neat Pad, Neat Board, Neat Board Pro, Neat Board 50, Neat Frame, and Neat Center.

  • On Saturday, May 2, we will roll out updates for Zoom Rooms (ZR 7.0.2), Zoom Room Controller (ZRC 7.0.2), and Microsoft Teams (MTRA) to our Stable Channel.

Changes to Stable software rollout

NeatOS updates on the Stable channel are now rolled out in a more controlled way for organizations using Neat Pulse. Previously, Stable firmware updates were delivered over-the-air (OTA) to all customers at the same time once a release became generally available (GA).

Now, Stable updates are scheduled per Neat Pulse organization (tenant).

If you use Neat Pulse

To see when the update will be available for your devices:

  1. Log in to Neat Pulse
  2. Select Updates in the side menu
  3. Check the schedule under NeatOS Roadmap

This shows when your organization is planned to receive the Stable release.

If you do not use Neat Pulse

Nothing changes. Your devices will continue to receive both Preview and Stable updates automatically via our standard over-the-air update process.

Note: The NeatOS Preview channel remains shared across both OTA and Neat Pulse organizations.

As long as your Neat equipment was up and on the network on the following dates, and your Neat equipment was configured on the stable channel with automatic updates enabled, the update would have been downloaded and your devices would upgrade overnight.

If you had opted out of automatic upgrades by disabling ‘Automatic updates’ on your Neat device, please note that it will remain on the existing software release and will not upgrade. However, if you would like to upgrade to the 25.4.2 release, please enable ‘Automatic updates’ and the Neat device(s) will download the latest firmware release and upgrade the Stable channel as above. 

Automatic updates can be enabled or disabled by going into your Neat’s System settings (from a Neat Pad, Neat Board, or Neat Frame) -> System -> Software Update. To ensure that your devices update properly, please make sure they are powered on and connected to the internet when updates are released, as well as overnight.

Note: Previous release notes can be found here.

2. What’s new in Neat OS 26.1.0

Stable release (April 18, 2026)Stable release (May 2, 2026)
The Neat firmware builds:Android 10 – Neat OS 26.1.0:
Neat Bar firmware:
NFB1.20260312.1018
Neat Board firmware:
NFC1.20260312.1018

Android 13 – Neat OS 26.1.0:
Neat Pad firmware:
NFA2.20260312.1318
Neat Bar Pro firmware:
NFD2.20260312.1318
Neat Bar Generation 2 firmware:
NFE2.20260312.1318
Neat Board 50 firmware:
NFH2.20260312.1318
Neat Board Pro firmware:
NFK2.20260312.1318

Neat Pulse Agent: Pulse Agent 2.2.57

Android 13 – Neat OS 25.4.3 (transition build):
Neat Center firmware: NFL1.20251114.0741

Android 15 – Neat OS 26.1.0:
Neat Center firmware: NFL2.20260312.1520

Neat Pulse Agent: Pulse Agent 2.3.44

Built in Chromium version:
M141		Android 10 – Neat OS 26.1.0:
Neat Bar firmware:
NFB1.20260312.1018
Neat Board firmware:
NFC1.20260312.1018

Android 13 – Neat OS 26.1.0:
Neat Pad firmware:
NFA2.20260312.1318
Neat Bar Pro firmware:
NFD2.20260312.1318
Neat Bar Generation 2 firmware:
NFE2.20260312.1318
Neat Board 50 firmware:
NFH2.20260312.1318
Neat Board Pro firmware:
NFK2.20260312.1318

Neat Pulse Agent: Pulse Agent 2.2.57

Android 13 – Neat OS 25.4.3 (transition build):
Neat Center firmware: NFL1.20251114.0741

Android 15 – Neat OS 26.1.0:
Neat Center firmware: NFL2.20260312.1520

Neat Pulse Agent: Pulse Agent 2.3.44

Built in Chromium version:
M141
The built-in Zoom Room versions. More information about the latest versions of Zoom can be found here: New Updates for Zoom Rooms Android Controller
New updates for Zoom Room Appliances		Zoom Room Controller software version:
7.0.1 (4876)

Zoom Room Appliance software version:
7.0.1 (9561)		New: Zoom Room Controller software version:
7.0.2 (4923)

New: Zoom Room Appliance software version:
7.0.2 (9666)
The built-in Microsoft Teams versions: More information about the latest versions of Microsoft Teams can be found here: Release notes for Microsoft Teams Rooms on Android
What’s new in Microsoft Teams devices – Teams Displays and Panels		Microsoft Teams Rooms Devices (Neat Bar, Neat Bar Gen 2, Neat Bar Pro, Neat Board, Neat Board 50, Neat Board Pro, and a Neat Pad as a controller):
– Admin Agent (803): 1.0.0.202511230136.product
Teams Rooms Devices (MTRA 2.8.1):
1449/1.0.96.2026048906
– Intune AOSP agent: 25.02.1
– Authenticator: 6.2601.0189
Microsoft Teams Displays:
– Admin Agent (803): 1.0.0.202511230136.product
– Company Portal (for Displays): 5.0.6423.0
– Display (Display 4.2.1): 1449/1.0.95.20260127111
Microsoft Teams Panels:
– Admin Agent (803): 1.0.0.202511230136.product
Panels: 1449/1.0.97.2025369004
– Intune AOSP agent: 25.02.1
– Authenticator: 6.2601.0189		Microsoft Teams Rooms Devices (Neat Bar, Neat Bar Gen 2, Neat Bar Pro, Neat Board, Neat Board 50, Neat Board Pro, and a Neat Pad as a controller):
– Admin Agent (803): 1.0.0.202511230136.product
New: Teams Rooms Devices (MTRA 2.9.0): 1449/1.0.96.2026087210
– Intune AOSP agent: 25.02.1
– Authenticator: 6.2601.0189
Microsoft Teams Displays:
– Admin Agent (803): 1.0.0.202511230136.product
– Company Portal (for Displays): 5.0.6423.0
– Display (Display 4.2.1): 1449/1.0.95.20260127111
Microsoft Teams Panels:
– Admin Agent (803): 1.0.0.202511230136.product
Panels: 1449/1.0.97.2025369004
– Intune AOSP agent: 25.02.1
– Authenticator: 6.2601.0189

Keeping your Neat devices supported: The table above shows the compatible Neat firmware builds with Zoom and Microsoft Teams versions. To ensure you can receive technical support, please keep your devices on a supported software combination. If you experience an issue while using an older or unsupported version, Neat’s support team will ask you to update to a supported release before troubleshooting. For more details, check out our Neat Technical Support Policy.

New features in this release:

  • Soft Mixing for improved multi-device audio
  • Neat Center upgraded to Android 15
  • Smart Power Management for Neat Rooms
  • Expanded language support
  • Google Meet can now be installed without Neat Pulse enrolment
  • Improved admin security and password protection
  • Remote access support for Neat Center
  • Static IP and 802.1X support for Neat Center (Beta)
  • Improvements and stability updates for Google Meet
  • Support for HTTPS proxy configurations with Microsoft Teams

3.1. Soft Mixing for improved multi-device audio

Neat introduces Soft Mixing, a new audio technology designed to deliver more natural and seamless sound in rooms using multiple Neat devices with Neat Center.

What does this mean for you?

  • More natural conversations – Audio is continuously blended from multiple microphones across devices, creating smoother transitions between speakers without abrupt changes.
  • Everyone is heard clearly – When multiple people speak at the same time from different parts of the room, all voices are captured and heard—no one is dropped.
  • Always uses the best microphone – The system dynamically prioritizes microphones based on who is speaking and their proximity, ensuring optimal audio pickup at all times.
  • Improved meeting flow – Eliminates noticeable audio switching, resulting in a more consistent and immersive experience for remote participants.

Why this change?

Traditional microphone switching activates only one device at a time, which can lead to missed voices, delayed transitions, and less natural conversations. Soft Mixing solves this by intelligently combining audio from multiple sources, improving clarity, inclusivity, and overall meeting quality.

How does it work?

Soft Mixing continuously analyzes speech levels across microphones on the front-of-room device and any connected Neat Centers. It blends audio in real time, giving more weight to the most relevant microphones while maintaining a balanced and natural sound.

Supported setups

Soft Mixing is available on setups pairing the following devices with one or more Neat Centers:

  • Neat Bar
  • Neat Bar (Gen 2)
  • Neat Bar Pro
  • Neat Board
  • Neat Board 50
  • Neat Board Pro

3.2. Neat Center upgraded to Android 15

Neat Center has been upgraded to Android 15, bringing enhanced security, improved stability, and a more modern platform for future innovation.

What does this mean for you?

  • Enhanced security – Updated to the latest Android security patch levels, helping protect devices and data with improved security safeguards.
  • Improved system stability – Platform improvements deliver a more reliable and consistent experience in day-to-day use.
  • Aligned with certification requirements – Ensures continued compatibility with evolving Microsoft Teams Rooms certification standards.

Why this change?

Keeping devices aligned with the latest Android platform ensures ongoing security, compliance, and long-term support, while enabling future feature development.

How does it work?

The upgrade is automatically delivered to existing Neat Center deployments via OTA. No manual action is required, and all existing functionality remains unchanged.

3.3. Smart power management for Neat rooms

Neat devices now support smarter, room-wide power management to reduce energy usage while keeping your meeting spaces ready when you need them.

With this update, your Neat Pad and room devices work together as one system. When a room is not in use, devices can automatically enter standby to save power. When you return, a single tap on the Neat Pad instantly wakes the entire setup—including the controller, front-of-room device (Neat Bar or Neat Board), and connected displays.

What does this mean for you?

  • Automatic power savings – Devices will now enter standby after periods of inactivity, helping reduce energy use and prevent unnecessary screen wear.
  • Instant room wake-up – A single tap on the Neat Pad wakes the whole room setup, so you can start meetings right away without delay.
  • Scheduled room readiness – Administrators can define working hours so devices automatically wake before the day starts and return to standby outside those hours.
  • Consistent room behavior – Power settings apply across all devices in the room, creating a seamless and predictable experience.
  • Simple management at scale – Sleep schedules and standby settings can be configured directly on devices today, with centralized management through Neat Pulse coming soon.

What to expect?

  • The screen may turn off when the room is not in use
  • A single tap on the Neat Pad will wake the entire room setup
  • During nights (if scheduled), devices may return to standby shortly after use
  • Rooms can automatically power on ahead of working hours

Important

If your Neat devices are using Preview channel software and previously had the Keep Screen On setting enabled, this behavior has changed. After this update, devices will use the new standby functionality, and the screen may turn off after a few minutes of inactivity.

If you prefer the screen to stay on, you will need to disable the new Screen Standby setting on the device.

Why this change?

These improvements help reduce energy consumption and extend the lifespan of your displays, while ensuring your meeting rooms are always ready to use—without requiring manual setup or extra steps.

3.4. Expanded language support

NeatOS now supports additional languages and improved translations across the device interface, delivering a more consistent and user-friendly experience for global teams.

What does this mean for you?

  • More languages available – NeatOS now supports French, Norwegian, and Turkish as device languages, making it easier for users to interact with devices in their preferred language.
  • Consistent language experience – The selected language is now applied consistently throughout the entire device interface for a seamless user experience.
  • Flexible language management – Administrators can easily set and manage device language through the admin settings or via Neat Pulse.

How does it work?

Select the desired device language through the admin settings or in Neat Pulse. The chosen language will be applied across all on-screen elements, including menus, prompts, and notifications.

3.5. Google Meet can now be installed without Neat Pulse enrolment

Google Meet is now available as a primary mode on supported Neat devices, giving Google Workspace customers a dedicated and optimized meeting experience for Google Meet.

With Google Meet mode enabled, devices are fully tailored for Google Meet—from setup through to daily use—making it easy to deploy and manage meeting rooms within the Google ecosystem.

Supported devices
Google Meet as a primary mode is supported on:

  • Neat Bar (Gen 2)
  • Neat Bar Pro
  • Neat Pad

What does this mean for you?

  • Seamless Google Meet experience – Devices run natively in Google Meet mode, with a consistent interface designed specifically for Meet users.
  • Simplified setup and provisioning – The out-of-box experience guides administrators through Google Meet configuration, making it easy to get rooms up and running.
  • One-touch join – Users can join scheduled meetings directly from the home screen with a single tap, using calendar integration.

Why this change?

As more organizations standardize on Google Workspace, there is a growing need for dedicated meeting room solutions that integrate seamlessly with Google Meet. This update enables Neat devices to deliver a native, high-quality Meet experience across supported room setups.

How does it work?

During setup, select Google Meet as the primary mode and sign in with your Google Workspace account. Once configured, the device will operate fully in Google Meet mode, with all controls, scheduling, and meeting experiences optimized for Google Meet.

Please note: If you choose to enroll a Google Meet device into Neat Pulse after the initial setup, the device will automatically restart. This is expected behavior and ensures the device is correctly configured in its new setup. A message will be shown before enrollment is completed. The restart happens only once, and the device will return to normal operation after it powers back on.

3.6. Improved admin security and password protection

We’ve strengthened device security with enhanced admin password requirements and protection against unauthorized access.

What does this mean for you?

  • Mandatory password update on first use – Devices running NeatOS 26.x or later now require administrators to set a new, unique password when signing in with the factory default. If the admin password has already been updated (for example via Neat Pulse or a configuration profile), no action is required. After entering the default password, you will be taken directly to the Change Password screen and won’t be able to access device settings until a new password is set. If you cancel or leave this step, you will be signed out, and the prompt will appear again the next time you sign in.
  • Improved protection against unauthorized access – New safeguards help prevent repeated failed sign-in attempts, reducing the risk of brute-force attacks.
  • Stronger security standards – These updates align with industry security requirements, including EN18031 and UK PSTI, ensuring better protection for your devices and data.
  • Centralized password management – Administrators can set and update device passwords directly through Neat Pulse for easier management at scale.
  • Consistent security across devices – Password policies are enforced across device settings, whether configured locally or through Neat Pulse.

Why this change?

As security requirements evolve, it’s important to ensure that device access is properly protected. These updates help prevent unauthorized access while aligning with modern security standards and best practices.

How does it work?

When signing in with the default admin password, you will be prompted to create a new password before continuing. After multiple failed sign-in attempts, temporary lockouts will be applied to protect the device.

3.7. Remote access support for Neat Center

Neat Center can now be accessed and managed directly through the web remote access interface, providing a more unified and consistent management experience.

What does this mean for you?

  • Full device visibility – Neat Center now appears alongside other paired devices in the remote access interface.
  • Simplified remote management – Administrators can access and manage Neat Center remotely without needing separate workflows.
  • Consistent experience across devices – All devices in a room setup can now be monitored and managed from a single interface.

Why this change?

This update improves visibility and control for administrators by ensuring all devices in a Neat room setup are accessible through the same remote management tools.

How does it work?

Neat Center will now be listed alongside other paired devices and can be accessed directly.

3.8. Static IP and 802.1X support for Neat Center (beta)

We’ve introduced support for Static IP configuration and 802.1X authentication (including SCEP) on Neat Center, enabling improved deployment flexibility in enterprise and security-restricted network environments.

What does this mean for you?

  • Greater network control – Administrators can now assign Static IP addresses to Neat Center devices, allowing for predictable network configuration and easier integration into managed infrastructures.
  • Enterprise-grade authentication – Support for 802.1X (including certificate-based authentication via SCEP) enables Neat Center to securely connect to networks that require RADIUS authentication and strict access policies.
  • Expanded deployment scenarios – These capabilities make it possible to deploy Neat Center in environments where DHCP is restricted or where advanced network security is enforced.

Why this change?

Many enterprise environments require strict network configuration and authentication policies. This update allows Neat Center to better integrate into these environments, aligning with existing IT standards and security requirements.

How does it work?

Static IP can be configured via the device’s web interface, allowing manual assignment of IP address, subnet, gateway, and DNS settings. 802.1X configuration enables the device to authenticate with a RADIUS server using supported EAP methods, including certificate-based authentication through SCEP.

This functionality is currently available as a beta. It is intended for testing and validation in non-production environments, and behavior or workflows may change in future releases. Customers should work with their Solution Engineer when enabling and validating these features.

3.9. Improvements and stability updates for Google Meet

We’ve introduced a range of improvements and stability fixes for Google Meet on supported Neat devices, enhancing overall performance and usability.

This update includes refinements to touch interaction on Neat Pad when used as a controller in Google Meet mode, along with fixes for issues that could cause the app to crash during certain interactions. We’ve also improved display scaling on Neat Bar to ensure the Google Meet interface renders correctly on connected screens.

What does this mean for you?

  • More reliable touch interaction – Improved responsiveness and stability when using Neat Pad as a controller in Google Meet mode.
  • Improved app stability – Fixes for issues that could cause unexpected app crashes during use.
  • Correct display scaling – Google Meet UI now displays with proper proportions on connected screens.

Why this change?

These updates improve the overall reliability and usability of Google Meet on Neat devices, ensuring a smoother and more consistent meeting experience.

How does it work?

The improvements are applied automatically as part of the software update, with no additional setup required.

3.10. Support for HTTPS proxy configurations with Microsoft Teams

Neat devices now support HTTPS proxy configurations for Microsoft Teams, enabling deployment in security-conscious environments such as financial institutions.

With this update, Root CA certificates uploaded through the remote access system settings now apply to all device network traffic, including Microsoft Teams. This enables comprehensive TLS/SSL inspection in enterprise environments without disrupting Teams connectivity.

What does this mean for you?

  • Support for secure network environments – Deploy Neat devices in networks that require HTTPS proxy and TLS/SSL inspection.
  • Expanded certificate coverage – Root CA certificates uploaded to the device now apply to all network traffic, including Microsoft Teams, enabling trusted connections through proxy appliances.
  • Reliable Microsoft Teams connectivity – Maintain seamless Microsoft Teams sign-in and communication, even in restricted network environments.

Why this change?

Many organizations operate in environments with strict network security requirements, including the use of HTTPS proxies and certificate inspection. This update ensures Neat devices can be deployed reliably in these environments without compromising security or functionality.

How does it work?

Administrators can configure an HTTPS proxy and upload the required Root CA certificate through the remote access system settings. With this update, those certificates are applied to all device network traffic, including Microsoft Teams, allowing traffic to pass securely through proxy environments with TLS/SSL inspection enabled.

4. Improvements and bug fixes

Issue referenceDescription

CUS-1928 (New)
Included from 26.1.0
Fixed an issue where certain USB audio devices (such as Q-SYS Core X10) could fail to be recognized on Neat Bar Pro.
In some cases, the device would briefly appear and then disconnect when connected via USB-C, preventing it from being used as an audio source. USB device detection and stability have been improved to ensure more reliable audio connectivity.
CUS-2022 (New)
Included from 26.1.0		Fixed an issue where the auxiliary PoE port on Neat Bar Pro could fail to provide power to connected devices.
In some cases, devices connected via the auxiliary PoE port would not power on as expected. Power delivery has been improved to ensure reliable operation when using the auxiliary PoE port.
CUS-1920 (New)
Included from 26.1.0		Fixed an issue where the date displayed on Neat devices could be out of sync in BYOD mode.
In some cases, the on-screen date would not update correctly—particularly in certain time zones—while the time remained accurate. The date display has been corrected to stay properly synchronized with the system time
CUS-1881 (New)
Included from 26.1.0		Fixed an issue where Neat Center could repeatedly lose network connection and restart on certain networks.
In some cases, devices would go offline shortly after startup and enter a reboot cycle, preventing them from staying connected. Network stability has been improved to ensure reliable operation across a wider range of network environments.
CUS-1871 (New)
Included from 26.1.0		Fixed an issue where Neat Bar Pro could lose audio output after upgrading to NeatOS 25.4.2.
In some cases, the device speakers would stop producing sound following the update, requiring a restart to recover. Audio stability has been improved to ensure consistent sound output after upgrades.
CUS-1869 (New)
Included from 26.1.0		Fixed an issue where Neat Bar Pro could experience occasional crashes related to HDMI CEC.
In rare cases, a fault in the HDMI CEC service could cause the device to become unresponsive and require a restart. Stability has been improved to prevent these crashes and ensure more reliable operation when HDMI CEC is enabled.
CUS-1764 (New)
Included from 26.1.0		Fixed an issue where Neat Center could incorrectly detect large static images as active participants.
In some cases, large facial images (such as wall graphics or posters) were not properly ignored by the framing system, causing unintended camera behavior. Static image detection has been improved to more reliably distinguish between real participants and background visuals.
CUS-1762 (New)
Included from 26.1.0		Fixed an issue where Neat Bar (Gen 2) could fail to detect HDMI input when using certain extenders.
In some cases, devices connected through HDMI extenders (such as Crestron) could appear as “No device connected,” even though the signal was working when connected directly. Compatibility has been improved to ensure more reliable HDMI input detection when using supported extenders.
CUS-1746 (New)
Included from 26.1.0		Fixed an issue where some Neat devices could unexpectedly perform a factory reset.
In rare cases, devices such as Neat Pad and Neat Bar Pro could reset during setup or following firmware updates. We’ve addressed several underlying causes and continue to improve system stability to prevent unexpected resets.
CUS-1731 (New)
Included from 26.1.0		Fixed an issue where the microphone could appear unavailable in Microsoft Teams-to-Zoom interop meetings.
In some cases, audio input was not detected when joining Zoom interop calls from a Microsoft Teams room on Neat Bar Pro. This has been resolved to ensure the microphone is correctly recognized and available during meetings.
CUS-1944 (New)
Included from 26.1.0		Fixed an issue where some devices could unexpectedly reset to factory settings after a firmware upgrade.
In rare cases, devices required manual reconfiguration after updating. This has been resolved to ensure a stable and reliable upgrade process.
CUS-1954 (New)
Included from 26.1.0		Fixed an issue where Neat Pad could report inaccurate room temperature readings.
In some cases, reported temperatures were higher than actual ambient conditions. Temperature readings have been corrected to more accurately reflect real room conditions.
CUS-1222 (New)
Included from 26.1.0		Fixed an issue where HDMI content sharing in Microsoft Teams could display incorrect colors.
In some cases, shared content could appear with color offsets or reduced detail quality. Color rendering has been corrected to ensure accurate and consistent visuals during content sharing.
CUS-1358 (New)
Included from 26.1.0		Fixed an issue where Neat Bar Pro could produce distorted audio in BYOD mode during extended playback.
In some cases, audio could degrade after several hours of continuous media playback from connected devices. This has been resolved, ensuring consistent audio quality over longer sessions.
CUS-1572 (New)
Included from 26.1.0		Fixed an issue where the maximum digital zoom setting was not applied correctly.
In some cases, changes made in the device admin web portal were ignored, preventing zoom levels above the default from taking effect. The setting is now correctly saved and applied across supported devices.
CUS-1595 (New)
Included from 26.1.0		Fixed an issue where Neat Center could fail to pair in certain room setups.
In some cases, pairing would fail with an error despite the device working in other rooms. This has been resolved, ensuring more reliable pairing across environments.
CUS-1684 (New)
Included from 26.1.0		Fixed an issue where Neat Center could incorrectly detect wall images or objects as people.
In some cases, this could affect framing accuracy and cause real participants—especially at the far end of the room—to be excluded. Detection has been improved to better distinguish between people and background objects.
CUS-1724 (New)
Included from 26.1.0		Fixed an issue where auto-framing on Neat Bar Pro could behave erratically during meetings.
In some cases, the system could lose track of participants and switch abruptly to other areas of the room. Auto-framing stability has been improved to provide smoother and more consistent participant tracking.
CUS-1728 (New)
Included from 26.1.0		Fixed an issue where Neat Bar (Gen 2) could experience intermittent display flickering on HDMI output 1.
In some cases, the display on HDMI 1 could flicker over time, while HDMI 2 remained unaffected, and a reboot only provided temporary relief. This has been resolved, ensuring stable and consistent display output.
CUS-1831 (New)
Included from 26.1.0		Fixed an issue where wired content sharing in Zoom could stop working after upgrading to Android 13.
In some cases, sharing via HDMI or USB-C in Zoom meetings was not functioning on Neat Bar and Neat Board devices, while other sharing methods remained unaffected. Wired sharing in Zoom is now working as expected.
CUS-1848 (New)
Included from 26.1.0		Fixed an issue where 802.1X device certificates could become unavailable after SCEP renewal.
In some cases, certificates renewed using the forceRenewKeyPair option were no longer visible after a reboot. This has been resolved, and certificates are now correctly retained and displayed following renewal.
CUS-1855 (New)
Included from 26.1.0		Fixed an issue where HDMI content sharing in BYOD mode could fail when using certain third-party extenders and switchers.
In some cases, non-standard resolutions from devices such as Kramer extenders caused content sharing to fail. The system now better handles slight resolution variations, restoring reliable HDMI content sharing.
CUS-1919 (New)
Included from 26.1.0		Fixed an issue where Neat Center could incorrectly detect participants shown on a display as people in the room, even with Screen Detection enabled.
This could result in unstable or incorrect framing behavior. Detection has been improved to more reliably distinguish between on-screen and in-room participants.
CUS-1861 (New)
Included from 26.1.0		Fixed an issue where Voice Isolation settings from Neat Pulse profiles could be overwritten during out-of-box setup.
In some cases, devices running Zoom or Google mode would reset Voice Isolation to Off despite being configured as On in the Neat Pulse profile. The setup flow now correctly respects and applies Neat Pulse profile settings.

5. Known issues

Issue referenceDescription
INBUGS-4112
Introduced in 26.1.0		We’ve identified an issue where devices running NeatOS 26.1, Neat Pulse does not display several Display settings, including the Sleep/Standby toggle, Screen Scheduler, and HDMI CEC (on supported models such as Neat Board 65). Instead of a proper on/off toggle, the Sleep/Standby option only appears as a dropdown for setting the timer. As a result, IT administrators are unable to view or manage these settings remotely through their Neat Pulse tenant. A fix is being worked on to ensure all Display settings are correctly reflected in Neat Pulse.
INBUGS-4185
Introduced in 26.1.0		We’ve identified an issue where devices configured in Auto BYOD mode may take longer than expected to exit a BYOD session after the USB cable is disconnected from either the device or the host laptop. This can result in a noticeable delay before Zoom or Microsoft Teams restarts. In some cases, if audio is being shared at the time of disconnection, a brief audio spike may be heard just before the BYOD session ends. This issue affects devices running Zoom and Microsoft Teams in Auto BYOD mode, and a fix is being worked on to improve the transition experience.
INBUGS-4126
Introduced in 26.1.0		We’ve identified an issue where third-party USB audio devices may not function correctly when joining a Microsoft Teams meeting from a Zoom Room on Neat Bar Pro. Affected devices may experience loss of audio input and output or degraded speaker performance with severe noise. This issue is limited to Zoom-to-Teams calls; other call directions are not affected. A fix is currently being investigated.
INBUGS-4141
Introduced in 26.1.0		We’ve identified an issue in version 26.1 where Screen Standby behavior may not follow the configured timer. On Microsoft Teams devices with a TAC profile applied, Automatic Wake Up (AWU) settings may be overridden by an internal screen saver timeout (e.g. 5 minutes), causing the device to go black later than expected. As this screen saver setting is not user-configurable, this may lead to inconsistent standby behavior.
CUS-TBD
Introduced in 26.1.0		We’ve identified a change in behavior for devices running Preview channel software where the previously set Keep Screen On setting is no longer respected. This setting has disappeared in 26.1.0 due to the new Sleep / Wake on the Pads. However this means devices will now migrate their settings to the new Screen Standby functionality and may turn off the display after a period of inactivity. To keep the screen on, Screen Standby must be disabled.
CUS-1760
Introduced in 25.4.2		We’ve identified an issue where Neat Center may appear as Offline in Neat Pulse after a new installation, even though the device is successfully paired, added to the room, and fully functional in meetings.
INBUGS-3787
Introduced in 25.4.2		We’ve identified an issue where Neat Bar (Gen 2) and Neat Pad could fail to pair after an Android 10 to Android 13 upgrade performed during out-of-box setup, causing the bar not to appear in the available pairing list despite successful migration and a healthy Neat network connection. An additional factory reset solves this issue.
INBUGS-3399
Introduced in 25.4.0		For EFT-customers: Accessing Neat settings during a Google Meet call may end the call.
An issue may occur when opening the Neat settings menu from the swipe menu during an active Google Meet call. Changing certain settings — such as Dark Mode or Language — while in a call may cause the meeting to end unexpectedly. We recommend avoiding changes to Neat settings during an ongoing Google Meet call until this issue is resolved.
INBUGS-3021
Introduced in 25.3.0		We’ve identified an issue where in some cases, boundary green boxes can appear on the FOR and Neat Center when changing the Camera Selection options.
INBUGS-3042
Introduced in 25.3.0		We’ve identified an issue where the Picture-in-Picture (PIP) view on Neat Board devices may show both Neat Board and Neat Center video streams instead of only the selected Neat Center camera. This can happen when the Neat Board camera toggle is disabled and the Neat Center camera is selected, then later the Neat Board camera toggle is re-enabled.
INBUGS-3100
Introduced in 25.3.0		We’ve identified an issue where the minimum depth/diameter setting for Framing Boundary on Neat Center is not available when camera selection is set to automatic.This option is only visible when using custom camera selection, which can cause confusion if a user sets a minimum depth while in custom mode and then switches back to automatic. In this case, the previous minimum depth setting will still be active but hidden, with no way to adjust it unless the user switches back to custom camera selection.
INBUGS-3101
Introduced in 25.3.0		We’ve identified an issue with the minimum and maximum values for the Framing Boundary width and depth sliders. This does not affect most users but may limit how precisely the framing area can be adjusted in very small spaces.
INBUGS-3119
Introduced in 25.3.0		We’ve identified an issue where verification mode and field of view constraints may appear during a call after modifying Framing Boundary settings. In some cases, the verification mode view and field of view overlays can remain visible once a call starts. This occurs when the camera is reselected after changing Framing Boundary settings and before starting a call. The issue mainly affects setups with a Neat Board and Neat Center; using a Neat Pad as the controller instead can prevent it. Restarting the call or readjusting the Framing Boundary settings may temporarily resolve this behavior.
INBUGS-3006
Introduced in 25.3.0		We’ve identified an inconsistency in how the Camera Selection preview appears when using a Neat Board and Neat Pad together. When a camera is selected using a Neat Pad paired with a Neat Board, the full-screen Preview view appears on the Neat Board, similar to how it works on a Neat Bar/Neat Pad setup — this is the expected behavior. However, if the camera selection is done directly on the Neat Board, a Picture-in-Picture (PIP) window is shown instead. This difference in behavior may cause confusion about what to expect when switching between the Neat Board and Neat Pad for camera selection.
INBUGS-3038
Introduced in 25.3.0		We’ve identified an issue where a camera’s LED will stay on during ongoing calls when that camera is disabled in Camera Selection. This can happen on Neat Board Pro and Neat Center devices. For example, if the Neat Center camera or Board Pro camera is disabled before joining a Microsoft Teams meeting, its LED may still light up even though the video feed is not active. This behavior is due to how the camera streams and how it’s exposed to the app, and does not affect meeting functionality — but it may be confusing for users who expect the LED to turn off when the camera is disabled.
INBUGS-3099
Introduced in 25.3.0		We’ve identified an inconsistency in the Framing Boundary slider labels for the Neat Center camera. When Camera Selection is set to Automatic, the slider uses Diameter with a range of 0–10 m. When Camera Selection is set to Custom, it uses Depth with a range of 0–5 m. While the ranges are technically correct, this inconsistency in naming may confuse users. We plan to align the terminology to use Depth consistently in a future update.
CUS-1579
Introduced in 25.3.0		Since Neat OS 25.2.0 release, Neat Pads running Microsoft Teams could respond very slowly to user actions, such as joining a call or changing a setting, and in some cases show a black screen. The root cause of this issue is under investigation. More information about this technical issue can be found here.
INBUGS-3034Framing Boundary changes from 25.2.0 to 25.3.0
NeatOS 25.3.0 firmware version includes some user interface changes in the Framing Boundary section, to accommodate the inclusion of the new Beta feature (Camera selection), when paired with a Neat Center. Although the Framing Boundary selectors for Neat Boards and Neat Bars are still including Width and Depth as the Boundary parameters, NeatOS 25.3.0 includes a secondary slider selector allowing the user to modulate the inferior and upper Depth parameters on the Front room device. A difference compared to NeatOS 25.2.0 and older firmware versions is that in NeatOS 25.3.0, the lowest value for the Depth parameter is 1m instead of 0m. This is a known issue included in this firmware version as the changes are to accommodate the new Camera selection implementation. The inferior Depth parameter will be set back to 0m in future firmware updates
What if the device is paired to a Neat Center? If the Neat Bar/Neat Board device is paired to a Neat Center and Camera selection is set to ‘Automatic’– In this situation, Framing Boundary for Neat Center will remain showing Diameter as the only parameter, and the value can be adjusted between 0-10 meters as usual.If the Neat Bar/Neat Board device is paired to a Neat Center and Camera selection is set to ‘Custom’– In this case, Framing Boundary for Naet Center will show 2 new parameters to adjust: Field of View and Depth. The Field of View can be set from 5-162 degrees, and Depth will show again the 2 slider selectors to adjust the inferior and upper values. As mentioned before, the inferior value for Depth is set to 1m instead of 0m, and will be set back to 0m in future updates.
ZTC-118When using Neat Board 65 in Companion Zoom Room mode, connecting a peripheral device (e.g. a laptop) to the Neat Board’s local input port causes Zoom to log out of the Companion ZR mode. This occurs because when the local input port is used, the touch-ability of the Neat Board is disabled by design (as in this mode, the Neat Board is being used outside of Zoom as an independent display). However, since Zoom expects the display to be a touch-enabled device at all times, it notices this change and logs out from the Companion ZR mode. This is a known limitation (however expected) as the local input port is not considered part of the Zoom’s work-flow and therefore not supported.
INBUGS-2732In the current 25.1 Release on Preview, a bug affects Board 50 and Board Pro devices. Prior to 25.1 (in 24.6 and earlier), users could connect a USB-C (C2C) cable from a laptop to a Board (50 or Pro) supporting Display Port and mirror their screen regardless of the cable orientation. However, in 25.1, if the C2C cable is connected with the wrong orientation, media content cannot be shared, although the device can still be used in BYOD mode without screen mirroring.
INBUGS-31‘Unable to verify certificate’ message is displayed when uploading CA certificate which has a text part before the actual certificate part. To work around this issue, copy only the certificate portion (BEGIN CERTIFICATE / END CERTIFICATE) to a file and save it as .pem/.cert etc. 
ZOOM-93In this release, it is not possible to disable Zoom’s ‘Advanced Noise Suppression’ feature. As a result, any users using the ‘Music mode’ feature will notice that their audio is being suppressed by Zoom’s noise suppression algorithm, making the experience poor. This issue is being investigated by the Zoom engineering team.
CUS-326In this release, color correction configuration options are available in the accessibility settings on the Neat Board and Neat Bar Pro, but enabling the feature will not have any effect on the screen.
CUS-635In this release, if a Neat Bar is rebooted while BYOD mode is enabled and in use, the Neat camera and Microphone will no longer function as expected until the USB-C cable is unplugged and replugged from the device.
CUS-760In this release, it is possible for a Neat device to show an “untrusted server certificate” warning due to a network timing issue. Rebooting the device should resolve the error in these scenarios.
INBUGS-1664In this release, switching between external audio hardware and the internal speaker while using Audio over USB on a Neat Bar Pro does not always work during a Zoom meeting.
INBUGS-2482When a Neat Pad is paired with a Neat Board or Neat Board 50, and manual BYOD mode is started on the Board itself (instead of the Neat Pad), then the Board/Board 50 enters the BYOD mode, but the Pad does not. The workaround is to either start BYOD mode on the Pad or if it has already started on the Board, to enter it from the Pad by selecting the manual BYOD mode.
INBUGS-2484We have identified a compatibility issue affecting users who are utilizing USB Audio with third-party audio devices (such as Shure) in conjunction with the BYOD mode. When both the USB Audio setting and the BYOD Enabled setting are activated in Pulse management platform, USB audio functionality is disrupted. As a result, users with USB Audio connected to third-party devices may experience audio disruptions when both USB Audio and BYOD are enabled. To avoid this issue, please ensure that you do not enable both BYOD and USB Audio in Pulse simultaneously. Disabling the BYOD settings in Pulse will prevent the conflict and maintain USB audio functionality.
INBUGS-2502Neat Bar Gen 2 can show a shifted layout during OOB phase when connected to some high resolution monitors.
CUS-1181If an update is requested via Pulse (by changing profile to a newer channel such as Preview from Stable) OR all devices are restarted at the same time when an upgrade is available it can synchronise the OTA polling across the devices for a site.Assuming the devices for the site are all on the same network, the Neat devices will then simultaneously request to download from the Neat OTA servers their upgrade files (around 1GB worth of data per device). When there are many devices doing this on certain networks it can potentially cause network throttling or alert security monitors that block the downloads part way through.If a device has started the upgrade procedure and it is unable to complete within the set upgrade window (1am – 5am local time) it can cause the device to be stuck on a purple upgrade screen and a restart (via Pulse or by removing the power to the device) is needed to restore functionality.
INBUGS-2985
Introduced in 25.2.0		If CEC is enabled on Neat Bar (Neat Bar 2 or Neat Bar Pro) and the CEC-enabled monitor connected to Neat Bar is turned OFF, Neat Bar will go to sleep as a result of the monitor being turned off. However, turning the monitor back on will not wake Neat Bar. If auto-wakeup is disabled, the only way to wake Neat Bar is by touching a connected Neat Pad. If auto wake-up is enabled on Neat Bar, the device will wake up as normal by motion detection.

6. How to check your software and firmware version

Here’s how to find out if your Neat device is running the latest build:

  • For Zoom Rooms: Select Settings (bottom left) on your Neat Pad, Neat Board, or Neat Frame, then select About. You’ll see the Zoom software version on the right.
  • For Microsoft Teams: Select More on the main screen, then go to Settings → About to view the Microsoft Teams software version.
  • For Neat Firmware: On your device, go to System Settings → System → About to find the firmware version and serial number.

You can also check the Zoom Room administrator portal or the Teams Admin Center (TAC) online to see the serial number and firmware version of your Neat devices.

Note for Neat Pad and devices enrolled in Neat Pulse: You can normally check for updates on the device’s Software Update page. But if any of your Neat devices are enrolled in Neat Pulse, that option will be greyed out. In that case, just head over to Neat Pulse to view and manage updates.

7. Need help? We’re here for you!

For quick answers and troubleshooting, check out our Neat Support website, where you’ll find helpful articles, FAQs, and step-by-step guides. We regularly update our content to make finding solutions easier.

If you need further assistance, our support team is ready to help! Simply email us at support@neat.no, and one of our technical support engineers will get back to you.

Privacy Policy: You can review our privacy policy here: Neat Privacy Policy.

Support Policy: Neat provides support for devices running the current or previous software release. For full details, see Neat’s Technical Support Policy.