Neat Preview Channel Firmware

Last updated on June 5, 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
Important information about the Preview Channel
What’s new in Neat OS 26.3.0
Improvements & bug fixes
Known issues
How to check your software and firmware version
Need help? We’re here for you!

For release notes covering Neat OS updates available only through the Microsoft Teams Admin Center (TAC), see our dedicated Microsoft TAC release notes page.

1. Introduction

Neat OS 26.3.0

On Saturday, June 6, we will 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. Device and app versions

Preview release (June 06, 2026)
The Neat firmware builds:	Android 10 – Neat OS 26.3.0: Neat Bar firmware: NFB1.20260511.1028 Neat Board firmware: NFC1.20260511.1028 Android 13 – Neat OS 26.3.0: Neat Pad firmware: NFA2.20260511.1328 Neat Bar Pro firmware: NFD2.20260511.1326 Neat Bar Generation 2 firmware: NFE2.20260511.1326 Neat Board 50 firmware: NFH2.20260511.1326 Neat Board Pro firmware: NFK2.20260511.1326 Neat Pulse Agent: Pulse Agent 2.3.44 Android 15 – Neat OS 26.3.0: Neat Center firmware: NFL2.20260511.1530 Neat Pad Pro firmware: NFJ2.20260511.1530 Neat Board 32 firmware: NFM2.20260511.1530 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.5 (5035) Zoom Room Appliance software version: 7.0.5 (9775)
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 (820): 1.0.0.202604060507.product Teams Rooms Devices (MTRA 2.9.1) : 1449/1.0.96.2026100103 – Intune AOSP agent: 25.02.1 – Authenticator: 6.2601.0189 Microsoft Teams Displays: – Admin Agent (820): 1.0.0.202604060507.product – Display (Display 4.2.1): 1449/1.0.95.2026012711 Microsoft Teams Panels: – Admin Agent (820): 1.0.0.202604060507.product Panels (Panels 3.6.0): 1449/1.0.97.2026164101 – Intune AOSP agent: 25.02.1 – Authenticator: 6.2605.3066

Previous device and app versions

	Preview release (June 2, 2026)	Preview release (May 26, 2026)
The Neat firmware builds:	Android 10 – Neat OS 26.3.0: Neat Bar firmware: NFB1.20260511.1022 Neat Board firmware: NFC1.20260511.1022 Android 13 – Neat OS 26.3.0: Neat Pad firmware: NFA2.20260511.1322 Neat Bar Pro firmware: NFD2.20260511.1320 Neat Bar Generation 2 firmware: NFE2.20260511.1320 Neat Board 50 firmware: NFH2.20260511.1320 Neat Board Pro firmware: NFK2.20260511.1320 Neat Pulse Agent: Pulse Agent 2.3.44 Android 15 – Neat OS 26.3.0: Neat Center firmware: NFL2.20260511.1524 Neat Pad Pro firmware: NFJ2.20260511.1518 Neat Board 32 firmware: NFM2.20260511.1524 Neat Pulse Agent: Pulse Agent 2.3.44 Built in Chromium version: M141	Android 10 – Neat OS 26.3.0: Neat Bar firmware: NFB1.20260511.1014 Neat Board firmware: NFC1.20260511.1014 Android 13 – Neat OS 26.3.0: Neat Pad firmware: NFA2.20260511.1316 Neat Bar Pro firmware: NFD2.20260511.1314 Neat Bar Generation 2 firmware: NFE2.20260511.1314 Neat Board 50 firmware: NFH2.20260511.1314 Neat Board Pro firmware: NFK2.20260511.1314 Neat Pulse Agent: Pulse Agent 2.3.44 Android 15 – Neat OS 26.3.0: Neat Center firmware: NFL2.20260511.1518 Neat Pad Pro firmware: NFJ2.20260511.1518 Neat Board 32 firmware: NFM2.20260511.1518 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.5 (5035) Zoom Room Appliance software version: 7.0.5 (9775)	Zoom Room Controller software version: 7.0.5 (5035) Zoom Room Appliance software version: 7.0.5 (9775)
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 (820): 1.0.0.202604060507.product Teams Rooms Devices (M-TRA ): 1449/1.0.96.2026100103 – Intune AOSP agent: 25.02.1 – Authenticator: 6.2601.0189 Microsoft Teams Displays: – Admin Agent (820): 1.0.0.202604060507.product – Display (Display 4.2.1): 1449/1.0.95.2026012711 Microsoft Teams Panels: – Admin Agent (820): 1.0.0.202604060507.product Panels (Panels 3.5.2): 1449/1.0.97.2026164101 – 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 (820): 1.0.0.202604060507.product Teams Rooms Devices (M-TRA ): 1449/1.0.96.2026100103 – Intune AOSP agent: 25.02.1 – Authenticator: 6.2601.0189 Microsoft Teams Displays: – Admin Agent (820): 1.0.0.202604060507.product – Display (Display 4.2.1): 1449/1.0.95.2026012711 Microsoft Teams Panels: – Admin Agent (820): 1.0.0.202604060507.product Panels (Panels 3.5.2): 1449/1.0.97.2026164101 – 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.

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 Neat OS 26.3.0

New features in this release:

Bring external room speakers to your Neat setup

Connect Neat devices to WPA3 and 6 GHz Wi-Fi networks

Easier 802.1X enterprise network setup

Expanded language support

Important behavior change: Auto BYOD activation has been unified with Manual BYOD

4.1. Bring external room speakers to your Neat setup

Gen 2 Neat devices can now drive external in-room loudspeakers by sending call audio over HDMI. The HDMI audio output, previously used only for assistive listening devices, is now a supported path for driving external speakers — either through your existing amplifier and passive speakers, or directly into active speakers.

Two playout modes are supported:

Internal + external (default)–Built-in and external loudspeakers play together. The internal loudspeaker anchors far-end voices to the screen, while the external speakers extend coverage across the room.
External only (new)–The internal loudspeaker is muted, and HDMI becomes the only playout path.

Supported on Gen 2 Neat devices, with Neat Bar Pro as the primary target for Large and XL room deployments. Typically, a third-party HDMI audio de-embedder is required to extract audio from the HDMI signal before feeding it to your amplifier or active speakers.

What does this mean for you?

Coverage for Large and XL rooms–Drive ceiling or wall-mounted speakers via your existing amplifier and speaker infrastructure.

Active or passive speakers–Drive passive speakers through an external amplifier, or feed active speakers with built-in amplification.

Why this change?

Neat’s integrated loudspeakers are the right answer for huddle, small, and medium rooms — but they reach their limits in Large and XL rooms, and in rooms with existing in-ceiling or in-wall speaker infrastructure. This update lets Neat plug into those environments as a supported audio source on existing Gen 2 hardware.

How does it work?

Connect a third-party HDMI audio de-embedder to one of the Neat device’s HDMI outputs. The de-embedder converts the audio to line-level, which feeds either an external amplifier (driving passive speakers) or an active speaker system directly. Volume follows the Neat device, so adjustments from the Neat Pad apply to the external path. To switch from the default mode to external-only, mute the internal loudspeaker in the device’s audio settings.

Important

Avoid non-linear processing and audio distortion in the external path. Distortion will degrade the echo cancellation performance. Typically, this means the external loudspeakers must be significantly more powerful and bigger than those built into the Neat product.

Audio delay on the external path is the responsibility of the external equipment. Any amplifier or DSP added downstream should be configured to keep latency within the limits the meeting platform expects.

An issue occurs when Speaker Framing is used together with external speakers — either with audio over USB (available today) or audio output over HDMI (new in NeatOS 26.3.0). When far-end participants are talking, Speaker Framing can frame people in the room who are not currently speaking, particularly when the external speakers are placed away from the Neat device (such as ceiling-mounted). Framing works correctly when someone in the room is speaking. As workarounds, place the external speakers close to the Neat device, or use a camera framing mode such as Auto Frame or Group Frame. We’re working on improvements.

4.2. Connect Neat devices to WPA3 and 6 GHz Wi-Fi networks

Neat devices now support WPA3, the latest Wi-Fi security standard, enabling connections to WPA3-Personal and WPA3-Enterprise access points. This also unlocks connectivity to 6 GHz (Wi-Fi 6E / Wi-Fi 7) networks, where WPA3 is mandatory.

Three scenarios are supported:

WPA3-Personal (SAE) – Connect to access points secured with WPA3-Personal.

WPA3-Enterprise (with 802.1X) – Connect to enterprise networks that combine 802.1X with the SAE handshake.

WPA2/WPA3 transition mode – Connect reliably to SSIDs that advertise both WPA2 and WPA3, without reconfiguring your network.

Supported devices

WPA3 support is delivered on the following Neat devices:

Neat Pad
Neat Board Pro
Neat Board 32
Neat Pad Pro

Other Neat devices are planned to follow in future releases.

What does this mean for you?

Connect to WPA3-only networks – Onboard Neat devices on access points hardened to WPA3 without relaxing your security policy.

No more WPA2 fallback workarounds – Mixed WPA2/WPA3 SSIDs now work as expected, so you don’t need to reconfigure APs to WPA2-only for Neat devices.

6 GHz, Wi-Fi 6E, and Wi-Fi 7 ready – Connect to the 6 GHz band on modern access points where WPA3 is mandatory.

Why this change?

Network administrators are increasingly defaulting to WPA3 or enforcing it as a security policy requirement, and 6 GHz access points require WPA3 by definition. Without WPA3, customers were hitting connection failures, reconfiguring their networks to WPA2-only just to onboard Neat devices, or unable to use 6 GHz at all. This update closes that gap and brings Neat in line with modern enterprise Wi-Fi expectations.

How does it work?

When a Neat device discovers a Wi-Fi network that uses WPA3, it negotiates the appropriate authentication method automatically. For WPA3-Personal, enter the network passphrase as you would for WPA2. For WPA3-Enterprise, configure 802.1X credentials through the device’s web interface. No additional toggle is needed to enable WPA3.

Note

The previously documented Neat Pad Pro WPA3-Personal pairing issue is improved by this update on the Neat Pad Pro side. Full room-level resolution also depends on the front-of-room device supporting WPA3 — see the Supported devices list above.

4.3. Easier 802.1X enterprise network setup

Neat devices now support 802.1X Enterprise authentication setup through the device’s web interface, offering a user-friendly alternative to the existing command-line workflow. The existing command-line workflow remains available for scripted deployments across large fleets. The new interface covers both Wi-Fi and Ethernet 802.1X, supports SCEP and standard CSR certificate flows, and accepts PEM bundle files so you can install a full certificate chain in one step.

Available on all Neat devices that connect to Wi-Fi or Ethernet. For Neat Center, 802.1X is already available—see the dedicated feature introduced in Neat OS 26.1.0.

What does this mean for you?

No command line required – Configure 802.1X end-to-end from the device’s web interface, with no need for terminal access.

Covers Wi-Fi and Ethernet – The same workflow handles 802.1X for both wired and wireless connections.

Faster, less error-prone deployments – Upload full certificate chains as a single PEM bundle, or use SCEP for automated certificate provisioning and renewal.

Why this change?

Enterprise IT teams increasingly require port-based access control on both wired and wireless networks, and certificate-based authentication is now standard in security-conscious environments. The previous CLI-only workflow created friction for teams who don’t typically work on the command line, and assembling certificate chains piece-by-piece was error-prone.

How does it work?

Configuration is done through the device’s remote access web interface, available during Out-of-Box (OOB) setup or after enabling Remote Access on the device. From there, select the network you want to configure (Wi-Fi or Ethernet), choose 802.1X as the authentication method, and enter your EAP parameters. Certificates can be uploaded individually or as a PEM bundle, and SCEP environments will have the device request and renew certificates automatically.

4.4. Expanded language support

Neat OS now supports Swedish and Japanese as device languages, building on the languages added in NeatOS 26.1.0.

What does this mean for you?

More languages available – Swedish and Japanese now join the set of supported device languages, making it easier for users in the Nordics and Japan to interact with Neat devices in their preferred language.

Flexible language management – Administrators can set and manage device language through the admin settings or via Neat Pulse.

How does it work?

Select the device language through the admin settings or in Neat Pulse. The chosen language is applied across menus, prompts, and notifications.

4.5. Important behavior change: Auto BYOD activation has been unified with Manual BYOD

NeatOS 26.3.0 changes how Auto BYOD starts and stops on Neat devices. Auto and Manual BYOD now behave more similarly, with the main difference being what happens when you connect or disconnect the USB cable

What changed

The BYOD mode button — previously only visible in Manual BYOD — is now also shown in the swipe menu when Auto BYOD is enabled.

A new Exit BYOD mode button now appears on the BYOD screen, so anyone can leave BYOD and return to the home screen directly from the display without opening the swipe menu. This applies to both Auto and Manual BYOD.

Auto BYOD now has two ways to start a session:
- Connect the USB cable—BYOD starts automatically when the cable is connected, and exits automatically when the cable is disconnected. This works the same as Auto BYOD has always worked.
- Tap BYOD mode in the swipe menu—BYOD starts even without a USB cable. To exit BYOD mode, tap BYOD mode in the swipe menu again, or tap Exit BYOD mode on the BYOD screen.

First-time exception: when you first enable the Auto BYOD toggle with a USB cable already connected, the BYOD session does not start automatically. To start it, either reconnect the USB cable or tap “BYOD mode” in the swipe menu.

Why we changed it

Previously, Manual BYOD showed a BYOD toggle on the swipe menu, and Auto BYOD did not. Unifying the two modes lets you toggle BYOD off for a quick call without unplugging the USB cable — useful when a Neat device is used as a secondary monitor. The on-screen Exit BYOD mode button also makes it easy to leave BYOD in shared spaces, where the next person may not know to use the swipe menu.

What to expect

If you’re used to the previous Auto BYOD behavior, you’ll see the new BYOD mode button on the swipe menu and may notice the device responds differently to USB connection in some scenarios. If someone has started BYOD and left the device in that state, the next person can return to the home screen by tapping Exit BYOD mode on screen (or by toggling BYOD off in the swipe menu).

5. Improvements and bug fixes

Issue reference	Description
CUS-2119 (New) Introduced in 26.3.0	Fixed an issue where Neat Bar Pro could become undiscoverable for Microsoft Teams Casting over Bluetooth. In some cases, Bluetooth would fail to turn on during device startup, leaving Neat Bar Pro invisible to laptops and phones attempting to cast via Microsoft Teams. The startup behavior has been corrected, and Bluetooth now initializes reliably so Microsoft Teams Casting works as expected.
CUS-2047 (New) Introduced in 26.3.0	Improved diagnostics for SSL certificate fingerprint mismatches during device pairing. In some cases, Neat devices could fail to pair when the SSL certificate fingerprint advertised via mDNS did not match the certificate presented during the TLS handshake — for example, after a device regenerated its self-signed certificate following a reboot. Additional SSL fingerprint logging has been added to aid diagnosis; customers encountering persistent pairing failures should contact Neat Support with logs from the affected devices.
AUD-478 (New) Introduced in 26.3.0	Reduced audio latency from Neat Center and Neat Pad Pro microphones by approximately 38 ms. Audio captured by the microphones on Neat Center and Neat Pad Pro now reaches far-end participants with noticeably less delay. A fixed internal buffer that previously added unnecessary latency to the audio path between these devices and the front-of-room device is now dynamically sized based on actual audio timing.
AUD-552 (New) Introduced in 26.3.0	Improved mixer responsiveness when switching between speakers at different volume levels. Previously, when one microphone captured a loud nearby speaker and another speaker then started talking into a different microphone at a noticeably lower volume, the mixer could stay on the louder channel longer than expected, making the quieter speaker harder to hear at the far end. The mixer now follows transitions between speakers more closely, so all voices in the room are picked up with less delay.
AUD-570 (New) Introduced in 26.3.0	Slightly higher microphone send level for more consistent in-call loudness. Audio captured by Neat microphones is now sent to far-end participants at a level approximately 1 dB higher than before, helping the in-call volume sit more naturally alongside laptops and other meeting room systems on the same call. The change is applied automatically and requires no setup.
AUD-583 (New) Introduced in 26.3.0	Improved Voice Isolation for clearer speech in reverberant rooms. The Voice Isolation model used by Neat devices has been updated in response to customer feedback that the previous version attenuated speech too much in rooms with significant reverb. Far-end participants should hear a cleaner, more intelligible voice audio in spaces like glass-walled boardrooms, large meeting rooms, and other reverberant environments. The change is applied automatically and requires no setup.
CA-1928 (New) Introduced in 26.3.0	Neat devices now securely share the Ethernet and WLAN MAC addresses with Microsoft Teams Rooms. IT administrators can identify Neat devices on the network using their Ethernet MAC addresses and apply MAC-based policies, network access controls, and asset tracking as expected. The MAC addresses are shared automatically as part of the device’s network reporting, meeting updated Android 13 security requirements — no setup is required.
INBUGS-4171 (New) Introduced in 26.3.0	Updated Auto BYOD activation behavior on Neat Bar devices. When Auto BYOD is enabled, BYOD now starts as follows: First-time activation with USB already connected: Start BYOD from the swipe menu, or disconnect and reconnect the USB cable. Subsequent USB connections: Continue to stop and launch the BYOD app automatically, as before. Swipe menu change: The “BYOD mode” button — previously available only in Manual BYOD — is now also shown when Auto BYOD is enabled.
CUS-1685 (New) Introduced in 26.3.0	Fixed an issue where parts of the System Settings menu remained in English after the device language was changed to French. In some cases, a small number of menu labels under Settings → System Settings → Time and Language did not pick up the selected language and continued to display in English. The full System Settings menu now translates as expected when the device is set to French. Other languages were unaffected.
CUS-2017 (New) Introduced in 26.3.0	Fixed an issue where ultrawide 21:9 displays connected to Neat Bar Pro did not negotiate their native 21:9 resolutions over HDMI. In some cases, panels capable of resolutions like 3840×1600, 3440×1440, or 2560×1080 at 60 Hz would fall back to standard 16:9 modes, leaving the image unable to fill the panel as intended. Resolution negotiation has been corrected, so 21:9 modes advertised by the connected display are now properly recognized and applied automatically.
CUS-2048 (New) Introduced in 26.3.0	Restored auto framing modes for Neat Center only camera in Microsoft Teams mode. In Neat OS 25.4.2, auto framing modes — including Speaker Focus — were disabled when “Neat Center only camera” was selected in Microsoft Teams mode, to avoid a conflict with the Teams default framing of the Neat automatic camera. The underlying conflict has been addressed, and auto framing modes are now available again in this configuration, so Speaker Focus and other Neat Centers framing modes can be selected as expected.
CUS-2065 (New) Introduced in 26.3.0	Fixed an issue on Neat Bar Pro running Zoom Rooms where audio from an HDMI-shared source could lag behind the on-screen content or be missing for the first several seconds of playback. In some cases, this was most visible when presenters shared a PowerPoint deck containing embedded audio or video, with the audio falling out of sync for both in-room and remote participants. Audio capture timing on the HDMI input path has been corrected, so embedded audio now plays in sync with the shared content from the moment the share begins.
CUS-2079 (New) Introduced in 26.3.0	Fixed an issue where Zoom Multi-Stream could display a “Failed to enable multi-stream. error code:5” warning on the local display when a Neat Bar Pro was paired with a Neat Center. In some cases, the warning appeared when more than two participants were in the room, and although the meeting itself continued to function, customers found the on-screen error distracting to the in-room experience. Camera handling between Neat Bar Pro and Neat Center under Zoom Multi-Stream has been corrected, so Multi-Stream now operates reliably in these setups, and the error notification no longer appears.
CUS-1883 (New) Introduced in 26.3.0	Reduced false occupancy reports in Zoom Room Scheduler caused by ultrasound motion detection. In some cases, ultrasound-based motion sensing on Neat devices could cause rooms to be marked as occupied in Zoom Room Scheduler when they were not, including being triggered by movement outside the room such as hallway traffic. Handling of motion signals sent to Zoom has been refined to reduce these false occupancy updates and improve reliability.
CUS-2016 (New) Introduced in 26.1.0	Fixed an issue where Neat Bar Pro could restart unexpectedly when a laptop was connected via HDMI. In some cases on Neat OS 25.4.2, the device would restart approximately 15–20 minutes after a laptop was connected via HDMI input. The underlying crash has been mitigated by a safeguard that stops HDMI audio after repeated input read failures rather than crashing the device. If HDMI audio becomes unavailable during a presentation, disconnecting and reconnecting the HDMI cable may restore it; persistent issues may indicate HDMI cable or source quality problems.
INBUGS-4141 (New) Introduced in 26.1.0	Fixed an issue where Screen Standby behavior on Microsoft Teams devices could ignore the configured timeout. In some cases, devices with a Microsoft Teams Admin Center (TAC) profile applied could remain awake longer than expected due to an internal Microsoft Teams screensaver timeout overriding Automatic Wake-Up (AWU) behavior. Screen Standby handling has been improved to provide more consistent and predictable sleep behavior.
CUS-1980 (New) Included from 26.1.0	Fixed an issue where the Neat Pad Sleep schedule settings where not transitioning correctly per the defaults set. An issue was identified with the new sleep mode for the Neat Pads as schedulers that meant the default settings where not accurately carried over to the new sleep settings available.
INBUGS-4036 (New) Included from 26.1.0	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)
CUS-2056 (New) Included from 26.1.0	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.
CUS-1904 (New) Included from 26.1.0	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-2028 (New) Included from 26.1.0	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.
CUS-1953 / INBUGS-4050 (New) Included from 26.1.0	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-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-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 Neat OS 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.

6. Known issues

Issue reference	Description
CUS-2137 Introduced in 26.3.0	We’ve identified a limitation when Speaker Framing camera mode is used together with external speakers — either with audio over USB (available today) or audio output over HDMI (new in NeatOS 26.3.0). When far-end participants are talking, Speaker Framing can frame people in the room who are not currently speaking. The issue is most noticeable when the external speakers are placed away from the Neat device (such as ceiling-mounted); framing works correctly when someone in the room speaks. As workarounds, place the external speakers close to the Neat device, or use a camera framing mode such as Auto Frame or Group Frame. A fix is being explored.
INBUGS-4390 Introduced in 26.1.0	We’ve identified an issue where Neat devices running Google Meet will not display the Framing Boundary tutorial under Settings > Audio & Video > Framing Boundary. When running the How it works tutorial, an error is shown instead of the tutorial content. As a workaround, dismiss the dialog by tapping OK, then close it using the X in the upper-right corner.
INBUGS-4347 Introduced in 26.1.0	We’ve identified an issue in which Neat Board 32/50/Pro will not enter standby/sleep mode when a laptop is connected to the Neat Board’s HDMI port.
INBUGS-4112 Introduced in 26.1.0	We’ve identified an issue where devices running Neat OS 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.
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-3034	Framing Boundary changes from 25.2.0 to 25.3.0 Neat OS 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, Neat OS 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 Neat OS 25.2.0 and older firmware versions is that in Neat OS 25.3.0, the lowest value for the Depth parameter is 1m instead of 0 m. 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 0 m 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 Neat 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 0 m, and will be set back to 0 m in future updates.
ZTC-118	When 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-2732	In 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-93	In 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-326	In 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-635	In 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-760	In 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-1664	In 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-2482	When 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-2484	We 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-2502	Neat Bar Gen 2 can show a shifted layout during OOB phase when connected to some high resolution monitors.
CUS-1181	If 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.

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

8. 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 raise a support ticket with us, 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.