Neat Preview Channel Firmware

Last updated on August 28, 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.5.1
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.5.2

On Saturday, August 29, we will roll out Neat OS 26.5.2 to our Preview Channel.

This build focuses on a handful of small fixes and improvements since the previous Preview build. For instance, this build includes a fix for Neat Board 32 USB-C connectivity with certain laptop models.

Alongside this Neat OS update, we’re also releasing an update to Microsoft Teams Panels.

2. Device and app versions

Preview release (August 29, 2026)
The Neat firmware builds:	(New): Android 10 – Neat OS 26.5.2: Neat Bar firmware: NFB1.20260810.1016 Neat Board firmware: NFC1.20260810.1016 (New): Android 13 – Neat OS 26.5.2: Neat Pad firmware: NFA2.20260810.1316 Neat Bar Pro firmware: NFD2.20260810.1318 Neat Bar Generation 2 firmware: NFE2.20260810.1318 Neat Frame firmware: NFF2.20260810.1318 Neat Board 50 firmware: NFH2.20260810.1318 Neat Board Pro firmware: NFK2.20260810.1318 Neat Pulse Agent: Pulse Agent 2.5.59 (New): Android 15 – Neat OS 26.5.2: Neat Pad Pro firmware: NFJ2.20260810.1518 Neat Center firmware: NFL2.20260810.1518 Neat Board 32 firmware: NFM2.20260810.1518 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.1.5 (5387) Zoom Room Appliance software version: 7.1.5 (10317)
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 (856): 1.0.0.202607160723.product – Teams Rooms Devices (MTR-A 2.10.2) : 1449/1.0.96.2026144512 – Intune AOSP agent: 26.06.0 – Authenticator: 6.2606.4246 Microsoft Teams Panels: – Admin Agent (856): 1.0.0.202607160723.product – (NEW): Panels (Panels 3.7.0): 1449/1.0.97.2026286706 – Intune AOSP agent: 26.06.0 – Authenticator: 6.2606.4246

Keeping your Neat devices supported: The table above shows the compatible Neat firmware builds with Microsoft Teams and Zoom 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.

Previous releases

Preview release (August 18, 2026)
The Neat firmware builds:	Android 10 – Neat OS 26.5.1: Neat Bar firmware: NFB1.20260810.1010 Neat Board firmware: NFC1.20260810.1010 Android 13 – Neat OS 26.5.1: Neat Pad firmware: NFA2.20260810.1310 Neat Bar Pro firmware: NFD2.20260810.1312 Neat Bar Generation 2 firmware: NFE2.20260810.1312 Neat Frame firmware: NFF2.20260810.1312 Neat Board 50 firmware: NFH2.20260810.1312 Neat Board Pro firmware: NFK2.20260810.1312 Android 15 – Neat OS 26.5.1: Neat Pad Pro firmware: NFJ2.20260810.1512 Neat Center firmware: NFL2.20260810.1512 Neat Board 32 firmware: NFM2.20260810.1512 Neat Pulse Agent: Pulse Agent 2.5.59 Built in Chromium version: M141	Android 10 – Neat OS 26.5.0: Neat Bar firmware: NFB1.20260810.1008 Neat Board firmware: NFC1.20260810.1008 Android 13 – Neat OS 26.5.0: Neat Pad firmware: NFA2.20260810.1308 Neat Bar Pro firmware: NFD2.20260810.1310 Neat Bar Generation 2 firmware: NFE2.20260810.1310 Neat Frame firmware: NFF2.20260810.1310 Neat Board 50 firmware: NFH2.20260810.1310 Neat Board Pro firmware: NFK2.20260810.1310 Android 15 – Neat OS 26.5.0: Neat Pad Pro firmware: NFJ2.20260810.1510 Neat Center firmware: NFL2.20260810.1510 Neat Board 32 firmware: NFM2.20260810.1510 Neat Pulse Agent: Pulse Agent 2.5.58 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.1.5 (5387) Zoom Room Appliance software version: 7.1.5 (10317)	Zoom Room Controller software version: 7.1.5 (5387) Zoom Room Appliance software version: 7.1.5 (10317)
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 (856): 1.0.0.202607160723.product – Teams Rooms Devices (MTR-A 2.10.2): 1449/1.0.96.2026144512 – Intune AOSP agent: 26.06.0 – Authenticator: 6.2606.4246 Microsoft Teams Panels: – Admin Agent (856): 1.0.0.202607160723.product – Panels (Panels 3.6.1): 1449/1.0.97.2026181101 – Intune AOSP agent: 26.06.0 – Authenticator: 6.2606.4246	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 (856): 1.0.0.202607160723.product – Teams Rooms Devices (MTR-A 2.10.2) : 1449/1.0.96.2026144512 – Intune AOSP agent: 26.03.1 – Authenticator: 6.2606.4246 Microsoft Teams Panels: – Admin Agent (856): 1.0.0.202607160723.product – Panels (Panels 3.6.1): 1449/1.0.97.2026181101 – Intune AOSP agent: 26.03.1 – Authenticator: 6.2606.4246

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

New features in this release:

Small fixes and improvements

Previously introduced in 26.5.1

Neat Frame moves to Android 13

Previously introduced in 26.5.0:

Intelligent Framing — a more engaging far-end view

Stronger pairing between Neat devices

Use the room’s USB accessories with your laptop on Neat Board 32

Automatic proxy setup on enterprise networks (WPAD)

More accurate network-location data on Microsoft Teams

Previously introduced in 26.5.1

4.1 Neat Frame moves to Android 13

Neat Frame is being upgraded from Android 10 to Android 13, bringing it onto a current Android base for continued security updates and platform improvements.

Because this is a bigger platform move than a routine release, your Neat Frame goes through two steps before it lands on Neat OS 26.5.1 (Android 13):

Step 1 – Your Neat Frame updates to a small transition release, Neat OS 25.4.4 (still Android 10). This prepares the device for the Android 13 upgrade.

Step 2 – Overnight, your Neat Frame continues automatically to Neat OS 26.5.1 (Android 13).

What you’ll see, depending on how your device updates:

Overnight automatic updates – Both steps happen during the scheduled update window. In the morning, your Neat Frame is on Neat OS 26.5.1 (Android 13). Nothing to do.

Manual updates from Neat Pulse – If you push the update during the day, your Neat Frame updates immediately to Neat OS 25.4.4 (Android 10), then continues automatically to Neat OS 26.5.1 (Android 13) during the next overnight window.

Settings, installed apps, and pairing all carry over — no reconfiguration required.

Important for Microsoft Teams users:

Microsoft ended Microsoft Teams certification and support for Neat Frame, effective 3 September 2025. Neat Frames running Microsoft Teams will continue to work after the Android 13 upgrade, but Microsoft Teams is no longer a supported configuration on Neat Frame.

For Microsoft Teams troubleshooting on Neat Frame, please use the User Data Reset option rather than Factory Reset — a Factory Reset removes the ability to run Microsoft Teams (Microsoft Teams will no longer appear as an option during the out-of-box setup).

If you’re using Neat Frame with Microsoft Teams for a specific workflow — for example, as a virtual assistant or in another configuration — please reach out to your Neat contact. We have alternative options we can help you evaluate.

Zoom and Neat App Hub on Neat Frame are unaffected.

Previously introduced in 26.5.0:

4.2. Intelligent Framing — a more engaging far-end view

Neat OS 26.5.0 introduces Intelligent Framing: two new camera modes that emphasize the people actively engaged in the conversation instead of showing everyone as equally sized tiles. Both modes ship as Beta in Neat OS 26.5.0. Equal framing remains the default and can still be selected at any time.

Highlights – The most engaged participants are shown at larger sizes so remote participants can immediately see who is speaking. Less-engaged people do not appear as prominently.

Highlights + room – The same idea, but a persistent wide shot of the room sits alongside the highlighted participants, so remote participants keep a sense of the whole room.

What does this mean for you?

A better far-end experience in bigger rooms – In more crowded rooms, Equal framing can fragment the far-end view into a wall of small tiles. Highlights and Highlights + room keep the focus on who is actually engaged in the conversation.

Adjustable highlight count – Choose how many participants get their own highlight tile, based on your preference. Configurable on the device or centrally in Neat Pulse.

No change unless you switch modes – Existing deployments continue to use Equal framing by default. Nothing changes until you or an administrator selects one of the new modes.

Why this change?

Equal framing works well in huddle and small rooms, but in medium and large rooms the far-end view can collapse into a grid of small equally sized faces, and remote participants lose track of who is actually driving the conversation. Intelligent Framing was announced at InfoComm 2026 as Neat’s answer to that limitation. Shipping as Beta lets Neat gather real-world feedback across a wider set of rooms and iterate quickly before promoting to a general-availability configuration.

How does it work?

Enable Intelligent Framing on the device under Audio & video, or centrally in Neat Pulse under Device Settings and Profiles. Pick either Highlights or Highlights + room, then set the number of highlighted participants to match your room. The Neat device uses its microphones and voice localization to identify who is engaged in the conversation and adjusts the framing accordingly. Both modes are labelled Beta wherever they appear.

Supported devices

Available on Neat Bar Pro, Neat Bar 2 (Neat Bar Gen 2), Neat Board Pro, and Neat Board 50 running Neat OS 26.5.0 or later. When any of these devices is paired with Neat Center, Neat Center also provides the best possible framing experience. Not available on other Neat devices in this release.

4.3. Stronger pairing between Neat devices

Neat OS 26.5.0 adds a short PIN confirmation step to the pairing process between Neat Pad and the room device (Neat Bar or Neat Board). During pairing, a short PIN appears on the room screen; you confirm it on the Neat Pad to complete the pairing. Under the hood, the exchange uses a modern cryptographic protocol (PAKE) that provides a significant security improvement to the pairing protocol.

Everything else about setting up a room stays the same.

What does this mean for you?

A quick, obvious step to confirm the right device – The PIN on the room screen matches what you enter on the Neat Pad, so there’s no doubt you’re pairing to the intended device — useful in shared spaces or busy deployments where multiple devices might be within range.

A significant security improvement – The pairing exchange has been upgraded from a password-based mechanism to a modern cryptographic protocol.

Why this change?

The previous pairing method relied on a shared password mechanism. Neat OS 26.5.0 replaces it with a modern cryptographic protocol (PAKE), providing a significant security improvement while keeping the setup process essentially unchanged. Over time, more of this identity verification will happen automatically in the background, so the PIN step will only be needed when required.

How does it work?

Start pairing the way you always have — from Neat Pad, using whichever pairing method your deployment uses. During the pairing exchange, a short PIN appears on the room screen; enter that PIN on the Neat Pad to confirm the pairing. The two devices complete the underlying cryptographic exchange automatically, and the pairing is finished.

Supported devices

Available on all Neat devices running Neat OS 26.5.0 or later.

4.4. Use the room’s USB accessories with your laptop on Neat Board 32

On Neat Board 32, USB devices plugged into the Neat Board — a headset, keyboard, mouse, external camera, or other peripheral — now switch automatically to your laptop when you connect it over USB-C, and switch back when you disconnect. The same USB-C cable also mirrors your laptop screen to the Neat Board display and charges the laptop, so one connection handles everything: peripherals, display, and power.

What does this mean for you?

One cable, everything switches – Plug your laptop in with a single USB-C cable and the room’s headset, keyboard, mouse, and camera all switch to your laptop. Unplug, and everything switches back to the room system.

Great for shared and hot-desk rooms – Rooms with a nice headset or webcam wired to Neat Board 32 stay useful when someone brings their own laptop, without unplugging cables or adding a separate USB switch box.

IT teams can control the behavior per room – Choose automatic switching on connect (default), manual switching (the user decides when to hand over), or turn the feature off entirely.

Why this change?

BYOD on Neat devices already covered the room’s camera and microphones, but every other USB peripheral wired to the Neat Board — headset, keyboard, mouse, external camera — stayed locked to the room system. If someone walked up with a laptop and wanted to use the room’s headset for their own call, they had to unplug it from the Neat Board first. Neat OS 26.5.0 makes this transparent: peripherals move with the person who connects, and no one has to touch the cables.

How does it work?

Connect your laptop to Neat Board 32 with a USB-C cable. Every USB peripheral wired to the Neat Board is handed over to your laptop; your laptop screen mirrors to the Neat Board display, and the cable charges your laptop at the same time. Disconnect the USB-C cable and return the peripherals to the room device. Administrators can change the switching behavior in System Settings → System → USB Connectivity, choosing between Automatic on connect, Manual, or Disabled.

Supported devices

Available on Neat Board 32 running Neat OS 26.5.0 or later.

4.5. Automatic proxy setup on enterprise networks (WPAD)

Neat devices now discover and use your corporate proxy automatically on networks configured with WPAD (Web Proxy Auto-Discovery). During network setup, each Neat device requests a proxy configuration file from your DHCP server, retrieves it, and routes its outbound traffic through your proxy according to the rules in that file.

This covers everything the device sends out: Neat Pulse enrollment and telemetry, meeting-platform services (Google Meet, Microsoft Teams, Zoom), firmware updates, and diagnostics.

What does this mean for you?

Plug-in-and-boot deployment – Once WPAD is enabled on Neat devices, IT teams no longer need to configure the proxy on each device by hand. IT teams get Neat devices onto the primary network the same way they onboard any other device.

No more workarounds – Special VLANs, firewall bypasses, or one-off exceptions for Neat devices are no longer needed to route around missing WPAD support.

Regulated environments unlocked – Deployments in networks where WPAD is a mandatory policy — for example in financial services, healthcare, government, and large enterprises — are now supported directly.

Why this change?

WPAD is the standard way corporate IT teams tell every device on the network which proxy to use for outbound traffic, automatically, without touching each device. Neat devices previously ignored the WPAD signal (DHCP Option 252), so customers had to either configure the proxy on every Neat device by hand, or design network carve-outs to route Neat traffic around the proxy. Neat OS 26.5.0 closes that gap and brings Neat in line with the enterprise-network expectations of any other device in the room.

How does it work?

Enable WPAD support in the device’s network settings. Once enabled, when a Neat device joins the network, it requests DHCP Option 252 from your DHCP server. If a WPAD URL is provided, the device fetches the PAC (Proxy Auto-Config) file at that URL and applies its rules to all outbound traffic. If your DHCP server does not advertise Option 252, the device operates as before with no proxy applied

Supported devices

Available on all Neat devices running Neat OS 26.5.0 or later.

4.6. More accurate network-location data on Microsoft Teams

Neat devices now store the LLDP information they receive from your network switch — switch name, port ID, VLAN, and related details — in a single, always-current place that the Microsoft Teams Rooms app reads on demand. Previously, Teams kept its own cached copy, which could go stale or drop fields over time. Neat OS 26.5.0 makes this a shared source of truth, so Teams sees the current network location of the device instead of a possibly stale cache.

This change applies to Neat devices running Microsoft Teams — Google Meet and Zoom Rooms are unaffected.

What does this mean for you?

Dynamic emergency calling (E911) is more reliable – When someone makes an emergency call from a Neat device, Microsoft Teams reports the current network location of the device to the emergency service, not a stale one. Especially important for devices that have been moved between rooms or floors.

Network-location-based policies stay accurate – Any Microsoft Teams policy that keys off LLDP data — VLAN-based quality of service, per-office rules, admin dashboards showing which switch a device is on — now works from consistent, up-to-date information.

Nothing to configure – The change is automatic once devices are on Neat OS 26.5.0

Why this change?

Every managed network switch broadcasts LLDP (Link Layer Discovery Protocol) information on each port, telling the connected device which switch and which port it is on. Microsoft Teams uses this to power dynamic emergency calling and location-aware policies. Previously, the Teams Rooms app on Neat devices kept its own internal cache of LLDP data, and that cache could drift out of sync with the actual switch information — a problem when the whole point of dynamic E911 is that the location must be current. Neat OS 26.5.0 moves LLDP storage into a system-owned location that Teams reads directly, so there is only one copy and it is always up to date.

How does it work?

Nothing to do. Neat OS listens for LLDP broadcasts from the network switch and stores the current information in a secure settings string on the device. Microsoft Teams reads that information on demand when it needs to report the device’s network location. If the switch stops advertising LLDP — for example, because a device is moved to an unmanaged network or an LLDP-disabled port — the stored data clears automatically, so the device does not report stale switch information.

Supported devices

Available on all Neat devices running Microsoft Teams on Neat OS 26.5.0.

5. Improvements and bug fixes

5.1 Improvements

Issue reference	Description
AUD-598 Added in 26.5.0	Improved Speaker Framing and Intelligent Framing in rooms with external loudspeakers Neat devices use small differences in how sound arrives at each microphone to determine where the current speaker is located, and steer the camera accordingly. In rooms where audio from remote participants plays through loudspeakers that sit apart from the Neat device — for example, ceiling speakers, HDMI audio-out setups, or a separate USB audio interface — that sound could look identical to a real human talker from the microphone array, and the camera would occasionally lock onto a nearby person as if they were speaking. Neat OS 26.5.0 now filters this sound out before deciding where to frame, using voice-activity detection and awareness of whether remote participants are talking, so the camera stays on the actual in-room speaker.
AUD-655 Added in 26.5.0	Faster outbound audio for more natural conversations. Neat OS 26.5.0 shortens the outbound audio path by approximately 20 milliseconds on most Neat devices. That means the sound of someone speaking in the room reaches remote participants faster, which makes back-and-forth conversation feel more natural and reduces the moments where two people accidentally talk over each other because of the delay between them. The improvement applies across most of Neat’s current product line, on any supported platform.
AUD-611 Added in 26.5.0	Louder, clearer audio playback on Neat Pad Pro. The audio playback level on Neat Pad Pro has been increased by 16 dB, making voice prompts, notifications, and audio in Panel or Touch Console modes substantially easier to hear. This helps in busier or noisier environments — open-plan offices, corridors, and rooms with a lot of ambient sound — where the previous playback level could be difficult to catch. Available on Neat Pad Pro.
AUD-614 Added in 26.5.0	Better background noise reduction. Constant background sounds — HVAC hum, projector fans, air conditioning, and other steady room noise — are now suppressed more effectively before the audio reaches remote participants. Voices come through more clearly and remote participants no longer hear a persistent wash of ambient noise sitting under the call for its full duration. This closes a common source of complaints about background noise on Neat devices, and continues the audio tuning work started in earlier releases.
INBUGS-4551 Added in 26.5.0	Clearer voice pickup on Neat Board 32. Microphone pickup on Neat Board 32 has been improved, so voices in the room come through more clearly to remote participants. The improvement applies across all use cases. Available on Neat Board 32.

5.2 Bug fixes

Issue reference	Description
CUS-2173 Fixed in 26.5.2	Fixed an issue where Neat Board 32 could stop accepting USB-C connections from Windows ARM-based laptops after several hot-plug cycles, requiring a reboot to temporarily restore recognition.
CUS-2250 Fixed in 26.5.1	Fixed inconsistent camera selection in Active Speaker mode on Neat Bar Pro paired with one or more Neat Centers
CUS-2223 Fixed in 26.5.0	Fixed an issue where a video encoder error could cause Neat Pad to restart repeatedly. The crash was independent of meeting state, though it was often noticed by customers when a meeting was in progress
CUS-2201 Fixed in 26.5.0	Fixed an issue where the switch camera button in Google Meet could not switch to Neat Bar 2’s built-in camera when the room was paired with Neat Center.
CUS-2128 Fixed in 26.5.0	Fixed an issue where individual person brightness could over-weight Neat Bar Pro’s camera exposure in wide-view shots. Exposure now gives person brightness less weight when the view is zoomed out, prioritizing the overall room exposure when a person is not prominent in the frame.
CUS-2055 Fixed in 26.5.0	Fixed an issue where Neat Bar 2 would not accept content shared through certain Crestron HDMI extender pairs, even though a direct HDMI connection to the same source worked correctly.
CUS-2163 Fixedin 26.5.0	Fixed an issue where Neat devices (all models except Neat Pad) could transmit PTPv2 Delay Response messages onto the network, causing intermittent clock synchronization problems for other audio DSP and video equipment sharing the environment. These messages are meant to be sent only by a PTP Grandmaster Clock, and Neat endpoints should not be replying with them. Neat OS 26.5.0 prevents Neat devices from emitting these PTPv2 responses so that customer clock-sync infrastructure remains undisturbed.
CUS-2041 Fixed in 26.5.0	Fixed an issue where the Neat Pad microphone could turn itself off overnight and remain disabled the following morning until manually re-enabled from Neat Pulse.
CUS-1812 Fixed in 26.5.0	Fixed an issue on Neat Bar 2, Neat Board 50, and Neat Board Pro where connecting a USB cable during an ongoing HDMI BYOD share could drop the HDMI content stream and trigger a “Connect HDMI” prompt.
CUS-2229 Fixed in 26.5.0	Fixed an issue where Neat Pad Pro could not pair with a Neat Bar-family device still running Neat OS 24.6, a release now more than a year old. Neat OS 26.5.0 restores pairing compatibility so 24.6-era front-of-room devices pair directly with Neat Pad Pro on newer Neat OS versions without a staging device.
CUS-2192 Fixed in 26.5.0	Resolved a regression on Neat Bar Pro where audio from remote participants stopped playing out when an external Yamaha UR22C USB audio interface was in use, while microphone capture through the UR22C continued to work. The regression came from a change in the USB audio output routing path that affected a limited number of advanced USB audio class 2.0 interfaces; standard USB audio devices were unaffected. Neat OS 26.5.0 restores the previous output routing behavior for USB audio class 2.0 interfaces, so interfaces like the UR22C are once again fully bidirectional.
CUS-2169 Fixed in 26.5.0	Resolved an issue where a small subset of devices could get stuck in the “Downloading” status during a Neat OS upgrade rather than completing the install. The root cause was a startup race between the Zoom Device Management (ZDM) MQTT client and the pending-upgrade state machine when devices booted into an interrupted upgrade state. Neat OS 26.5.0 hardens the MQTT client startup sequence so it recovers cleanly from that state.
CUS-2174 Fixed in 26.5.0	Resolved an issue where far-end participants intermittently heard an echo of their own voices during meetings from a Neat Bar + Neat Pad + Neat Center configuration; the echo lasted around 30 seconds and reoccurred every 10–15 minutes. The fault was traced to the acoustic echo cancellation (AEC) alignment path across the satellite link between Neat Bar and Neat Center. Neat OS 26.5.0 includes AEC alignment and clock-offset tuning that stabilizes echo cancellation across the Neat Bar + Neat Pad + Neat Center link, so periodic echo bursts no longer occur, and rooms keep clean far-end audio.
CUS-2162 Fixed in 26.5.0	Fixed two Neat Pad issues introduced by Neat OS 26.3.0: upgrades could stall at the “Reboot required” step and need a manual reboot to complete, and devices using a hidden (stealth) SSID could lose their Wi-Fi configuration after the upgrade.
CUS-2114 Fixed in 26.5.0	Fixed an issue where Neat devices could not connect to 802.1X Wi-Fi networks after a firmware upgrade, particularly on RADIUS servers whose certificates carry only a Common Name (CN) and no Subject Alternative Name (SAN).
CUS-1765 Fixed in 26.5.0	Fixed an issue where Neat Bar Pro could be slow to reframe to a new active speaker during Speaker Focus, particularly for participants seated further from the device or off-axis. Speaker Focus now follows the active speaker more reliably as the conversation moves around the room.
CUS-2135 Fixed in 26.5.0	Fixed an issue where the Neat Bar 2’s video could appear overexposed to far-end participants during Google Meet calls, particularly in rooms with bright or white backgrounds
CUS-2187 Fixed in 26.5.0	Resolved an issue on Neat Bar Pro where the camera could become unavailable during a meeting and could not be re-enabled.
CUS-2204 Fixed in 26.5.0	Fixed an issue where Neat Bar Pro could intermittently fail to detect a Shure IntelliMix P300 audio conferencing processor connected over USB, reporting the device as disconnected even though the cable was physically in place.
CUS-2137 Fixed in 26.5.0	Fixed an issue where Speaker Framing and Intelligent Framing could pick up a non-speaking person in the room as the active speaker while only remote participants were talking, particularly in rooms using external loudspeakers connected via USB or HDMI.
CUS-2139 Fixed in 26.3.0	Fixed an issue where USB audio could not function correctly when joining a Microsoft Teams meeting from a Zoom Room on Neat Bar Pro and Neat Board Pro. In some cases on Neat Bar Pro, USB audio devices could experience disconnects, loss of audio output, or degraded speaker performance with severe noise during Zoom-to-Teams interop calls. The underlying audio routing issue has been corrected, so USB audio now works reliably in Zoom-to-Teams interop calls.
CUS-2052 Fixed in 26.3.0	Fixed an issue where a temporarily unreachable DHCP Option 42 NTP server caused the device to stay on the fallback server (time.neat.no) permanently, even after the advertised server recovered and across reboots. While the DHCP server is unreachable the device now uses time.neat.no only temporarily, and returns to the DHCP server automatically once it is reachable again.
CUS-2119 Fixed 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 Fixed 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 Fixed 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.
VID-443 Fixed in 26.3.0	Improved the algorithm for selecting the best camera for a person when a device is paired with one or more Neat Centers. Previously, in some multi-Center room setups, automatic camera selection did not always choose the most appropriate camera for framing a given speaker. Camera selection logic has been refined across several smaller improvements, so the best-positioned camera for each person is now chosen more reliably in these setups.
AUD-552 Fixed 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 Fixed 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 Fixed 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.
INBUGS-4171 Fixed in 26.3.0	Updated Auto BYOD activation behavior on Neat 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 Fixed 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 Fixed 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 Fixed 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 Fixed 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 Fixed 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 Fixed 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.

6. Known issues

Issue reference	Description
INBUGS-4416 Introduced in 26.3.0	We’ve identified an issue in which the screen may briefly flash black when opening the swipe-left menu on the Neat Board 32 in BYOD-only mode. The flash is short but visible, and it may momentarily interrupt the in-room visual experience.
INBUGS-4331 Introduced in 26.3.0	We’ve identified an issue where disabling Color Correction (Settings → Device settings → Accessibility → Color Correction) does not take effect immediately. Enabling Color Correction and switching between options work as expected, but disabling the feature is not applied until the next screen frame is rendered. In typical use, the change is reflected within about 30 seconds — the delay can be longer in rooms with multiple connected displays, or if the device is left idle with no user interaction. This behavior is due to how Android handles screen rendering and is not expected to be resolved.
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-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.
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-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-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 on Neat Center. 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. The ranges are technically correct, but the naming inconsistency may cause confusion. We plan to align the terminology to Depth 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.
ZTC-118	When using Neat Board Pro 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-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-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.