Neat Preview Channel Firmware
Last updated on April 29, 2026
If you would like to receive email notifications for new releases, please subscribe here.
This document details what features, improvements, and bug fixes are new in the Neat Preview channel when compared to the Stable update channel.
- Introduction
- Device and App Versions – Summary Table
- Important information about the Preview Channel
- What’s new
- NeatOS 26.1.0 — All release builds (Improvements & bug fixes)
- How to check your software and firmware version
- Need help? We’re here for you!
For release notes covering NeatOS updates available only through the Microsoft Teams Admin Center (TAC), see our dedicated Microsoft TAC release notes page.
1. Introduction
NeatOS 26.1.0
On Wednesday, April 29, we will roll out an update for Neat Devices to our Preview channel. This release includes a range of improvements and updates designed to enhance performance, usability, and the overall experience across your Neat devices.
2. App and Device versions summary
NeatOS 26.1.0 — Current build summary
If you are running the latest Preview release (latest update: v5 April 29, 2026), your devices will be on the following versions:
| Type | Build |
| Android 10 – NeatOS 26.1.0 | Neat Bar: NFB1.20260312.1024 Neat Board: NFC1.20260312.1024 |
| Android 13 – NeatOS 26.1.0 | Neat Pad: NFA2.20260312.1320 Neat Bar Pro: NFD2.20260312.1324 Neat Bar Gen 2: NFE2.20260312.1320 Neat Board 50: NFH2.20260312.1320 Neat Board Pro: NFK2.20260312.1320 Neat Center: NFL1.20251114.0741 (Transition Build) |
| Android 15 – NeatOS 26.1.0 | Neat Center: NFL2.20260312.1522 |
| Zoom | Zoom Room Controller: 7.0.2 (4923) Zoom Room Appliance: 7.0.2 (9666) |
| Microsoft Teams (MTRA) | MTRA: 1449/1.0.96.2026087210 (April 2026) Authenticator: 6.2601.0189 Admin Agent: 1.0.0.202511230136.product Intune: 25.02.1 MTR Panel: 1449/1.0.97.2025385601 |
| Pulse Agent | 2.4.28 |
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.
3. Important information about the Preview Channel
At Neat, we use two channels for our software updates to give you the best experience.
- Stable Channel – This is where our finalized, production-ready updates are released, ensuring everything runs smoothly in your environment.
- Preview Channel – Before updates go live, we release them here for a few weeks. This lets you explore new features early and provide feedback.
The best part is that you already have access to both channels! So, whether you prefer rock-solid stability or an early look at what’s coming, you’re covered.
Please note that Preview updates are for evaluation and are not yet fully supported. We do not recommend installing Preview software on Neat devices used in a production environment. Ideally, you should use a Neat device that is in a lab or a lower-risk user environment to try out the Preview software. And please report any feedback or issues you find while testing to us using the steps outlined in section 7. Getting help from Neat. We would love to hear from you!
- Using Neat Pulse? Change the update channel in the device settings within Neat Pulse controls or via a room profile.
- For Zoom Neat devices: Go to System Settings → System → Software Update → Update Channel on Neat Pad, Neat Board, and Neat Frame.
- For Microsoft Teams Neat devices: Navigate to Settings → Device Settings → System → Software Update → Update Channel on Neat Pad and Neat Board.
If there is already a newer version available when you move your Neat device to the Preview channel, your Neat device will automatically download the new version and upgrade between 1:00 a.m. to 5:00 a.m. local time on the next day.
4. What’s new in NeatOS 26.1.0
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
4.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
4.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.
4.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.
4.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.
4.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.
4.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.
4.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.
4.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.
4.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.
4.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.
5. NeatOS 26.1.0 — All release builds
Select a release build below to view its firmware versions, improvements, bug fixes, and known issues.
NeatOS 26.1.0 — All release builds
New Firmware and App Versions Updated
| Type | Build Number |
| Android 10 – Neat OS 26.1.0 | Neat Bar: NFB1.20260312.1024 Neat Board: NFC1.20260312.1024 |
| Android 13 – Neat OS 26.1.0 | Neat Pad: NFA2.20260312.1320 Neat Bar Pro: NFD2.20260312.1324 Neat Bar Gen 2: NFE2.20260312.1320 Neat Board 50: NFH2.20260312.1320 Neat Board Pro: NFK2.20260312.1320 |
| Android 15 – Neat OS 26.1.0 | Neat Center: NFL2.20260312.1522 |
Improvements & bug fixes
| Issue | Description |
| CUS-1904 | Fixed an issue where entering an excessively long NTP (time server) address could cause the device to become unresponsive. In some cases, the device would repeatedly reboot and require a factory reset to recover. NTP address handling has now been improved to prevent this behavior, ensuring stable operation even with longer server entries. |
| CUS-2056 | Fixed an issue where the Zoom startup screen could briefly appear when sharing content via HDMI on Neat Bar Pro. This could happen during presentations with embedded videos, sometimes accompanied by a short audio drop at the start of playback. HDMI input handling has been improved to ensure smooth, uninterrupted video and audio during content sharing. |
| INBUGS-4036 | Fixed an issue where disconnecting the USB cable during BYOD while audio was playing could result in a audio spike. 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 audio issue has been addressed in this release. However, the delay when exiting BYOD mode remains, and we are continuing to work on improvements to make the transition faster and more responsive.(See our Known Issues below for more info: INBUGS-4185) |
Known issues
| Issue | Description |
| INBUGS-4185 | 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. This can result in a noticeable delay before Zoom or Microsoft Teams restarts, making the transition feel slower than in previous versions. |
| INBUGS-4112 | 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 | 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. A fix is being worked on to improve the transition experience. |
| INBUGS-4126 | 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 | 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. |
Updated App Versions
| App | Version |
| Zoom | ZRC: ZRC 7.0.2 (4923) ZR Appliance: 7.0.2 (9666) |
| Microsoft Teams (MTRA) | MTRA: 1449/1.0.96.2026087210 (April 2026) |
Release notes
For full details on what’s included in these app updates, see the official release notes from Zoom and Microsoft:
New Firmware and App Versions Updated
| Type | Build Number |
| Android 10 – Neat OS 26.1.0 | Neat Bar: NFB1.20260312.1022 Neat Board: NFC1.20260312.1022 |
| Android 13 – Neat OS 26.1.0 | Neat Pad: NFA2.20260312.1318 Neat Bar Pro: NFD2.20260312.1318 Neat Bar Gen 2: NFE2.20260312.1318 Neat Board 50: NFH2.20260312.1318 Neat Board Pro: NFK2.20260312.1318 |
| Android 15 – Neat OS 26.1.0 | Neat Center: NFL2.20260312.1520 |
| Microsoft Teams | Panels 3.5.2 (1449/1.0.97.2025385601) |
Improvements & bug fixes
| Issue | Description |
| CUS-1953/ INBUGS-4050 | Reinstated a fix for an issue on Neat Board 50 and Neat Board Pro running Android 13 where the captive portal overlay did not take effect correctly, causing the device to fall back to Google’s connectivity check endpoints to validate network connectivity.This was most commonly observed on networks using Zscaler or a web proxy where those endpoints are blocked, resulting in repeated network validation warnings despite the device having working internet connectivity. |
| CUS-2028 | Fixed an issue where devices displayed times one hour off when configured to the Mexico City time zone. The fix updates the underlying time zone database to the latest version, correcting offsets and DST rules for several affected regions including Mexico City, Chihuahua, Cairo, Tehran, Amman, and Fiji. |
Known issues
| Issue | Description |
| INBUGS-4112 | 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 | 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. A fix is being worked on to improve the transition experience. |
| INBUGS-4126 | 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 | 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. |
New Firmware and App Versions Updated
| Type | Build Number |
| Android 10 – Neat OS 26.1.0 | Neat Bar: NFB1.20260312.1018 Neat Board: NFC1.20260312.1018 |
| Android 13 – Neat OS 26.1.0 | Neat Pad: NFA2.20260312.1316 Neat Bar Pro: NFD2.20260312.1316 Neat Bar Gen 2: NFE2.20260312.1316 Neat Board 50: NFH2.20260312.1316 Neat Board Pro: NFK2.20260312.1316 |
| Android 15 – Neat OS 26.1.0 | Neat Center: NFL2.20260312.1518 |
| Zoom | ZRC: 7.0.1 (4876) ZR Appliance: 7.0.1 (9561) |
| Microsoft Teams | MTRA 2.8.1: 1449/1.0.96.2026048906 Authenticator: 6.2601.0189 |
Improvements & bug fixes
| Issue | Description |
| CUS-1746 | 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-1869 | 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-1920 | 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-1928/INBUGS-4053 | Improved 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-1871 | 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. |
Known issues
| Issue | Description |
| INBUGS-4112 | 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 | 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. A fix is being worked on to improve the transition experience. |
| INBUGS-4126 | 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 | 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. |
New Firmware and App Versions Updated
| Type | Build Number |
| Android 10 – Neat OS 26.1.0 | Neat Bar: NFB1.20260312.1014 Neat Board: NFC1.20260312.1014 |
| Android 13 – Neat OS 26.1.0 | Neat Pad: NFA2.20260312.1312 Neat Bar Pro: NFD2.20260312.1312 Neat Bar Gen 2: NFE2.20260312.1312 Neat Board 50: NFH2.20260312.1312 Neat Board Pro: NFK2.20260312.1312 |
| Android 15 – Neat OS 26.1.0 | Neat Center: NFL2.20260312.1514 |
| Pulse Agent | Pulse Agent 2.4.28 |
| Zoom | ZRC: 6.7.5 (4692) ZR Appliance: 6.7.6 (9416) |
Improvements & bug fixes
| Issue | Description |
| CUS-2022 | 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. |
Known issues
| Issue | Description |
| CUS-1920 | We’ve identified an issue where the date displayed on Neat devices can be out of sync in BYOD mode. In some cases, the on-screen date does not update correctly—particularly in certain time zones—while the time remains accurate. |
| CUS-1928 | In some cases, USB audio devices (such as Q-SYS Core X10) can fail to be recognized on Neat Bar Pro. The device will briefly appear and then disconnect when connected via USB-C, preventing it from being used as an audio source. |
| INBUGS-4112 | 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 | 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. A fix is being worked on to improve the transition experience. |
| INBUGS-4126 | 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 | 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. |
New Firmware and App Versions
| Type | Build Number |
| Android 10 – Neat OS 26.1.0 | Neat Bar: NFB1.20260312.1012 Neat Board: NFC1.20260312.1012 |
| Android 13 – Neat OS 26.1.0 | Neat Pad: NFA2.20260312.1310 Neat Bar Pro: NFD2.20260312.1310 Neat Bar Gen 2: NFE2.20260312.1310 Neat Board 50: NFH2.20260312.1310 Neat Board Pro: NFK2.20260312.1310 |
| Android 13 – Neat OS 25.4.3 (transition) | Neat Center: NFL1.20251114.0741 |
| Android 15 – Neat OS 26.1.0 | Neat Center: NFL2.20260312.1512 |
| Microsoft Teams | MTRA 2.8.0: 1449/1.0.96.2025421910 Authenticator: 6.2512.8111 Intune AOSP: 25.02.1 |
| Zoom | ZRC: 6.6.10 (4464) ZR Appliance: 6.6.10 (8678) |
Improvements & bug fixes
| Issue | Description |
| CUS-1222 | 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 — for example, red backgrounds showed a yellow fringe and fine details appeared degraded. Color rendering has been corrected to ensure accurate and consistent visuals during content sharing. |
| CUS-1358 | Fixed an issue where Neat Bar Pro could produce distorted audio in BYOD mode during extended playback. In some cases, audio could degrade after approximately 3 hours of continuous media playback from connected devices. This has been resolved, ensuring consistent audio quality over longer sessions. |
| CUS-1572 | 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 | 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 | 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 | 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 | 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-1731 | 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-1762 | 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-1764 | 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-1831 | 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 | 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 | 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-1861 | 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. |
| CUS-1881 | 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-1919 | 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-1944 | 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 | 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. |
Known issues
| Issue | Description |
| CUS-1920 | We’ve identified an issue where the date displayed on Neat devices can be out of sync in BYOD mode.In some cases, the on-screen date does not update correctly—particularly in certain time zones—while the time remains accurate. |
| CUS-1928 | In some cases, USB audio devices (such as Q-SYS Core X10) can fail to be recognized on Neat Bar Pro. The device will briefly appear and then disconnect when connected via USB-C, preventing it from being used as an audio source. |
| INBUGS-4112 | 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 | 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. A fix is being worked on to improve the transition experience. |
| INBUGS-4126 | 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 | 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. |
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.