Despite coming across countless negative reviews about the Nuphy Halo96 V2, I decided to seek advice from Reddit and other forums before making the purchase. To my dismay, this turned out to be one of the worst decisions I’ve ever made when it comes to computer equipment!

At first glance, the keyboard is stunning, and its build quality seems flawless. However, as thousands of users have pointed out across various forums, the firmware is an absolute nightmare—it feels like it was coded by a first-semester IT student. No matter which version you update to (keyboard, RF, or dongle firmware), bugs persist. With each update, the issues only grow worse, eventually making the keyboard completely unusable.

Here are the major problems I faced:

• There’s no way to determine which firmware version is pre-installed on the keyboard.

• Right out of the box, I noticed a significant delay in connectivity (likely running version 1).

• After updating to the latest firmware for the keyboard, RF, and dongle, the keyboard became practically useless. With Num Lock enabled, the delay between keystrokes and the signal reaching the computer skyrocketed to around 500 ms. At this point, even a $12 Walmart keyboard outperformed this expensive yet dysfunctional device.

• I attempted to roll back to firmware version 1.0.2, which slightly alleviated some issues but introduced even more pronounced delays, particularly when pressing the spacebar.

In short, while the Nuphy Halo96 V2 boasts excellent build quality, its firmware is a complete disaster, rendering the keyboard unfit for use. If the store you’re purchasing from doesn’t offer a return policy, I strongly recommend avoiding this product altogether. If returns are allowed, you might consider testing it—but only if you’re prepared for endless frustration and disappointment.

Sent to me by NuPhy themselves for a review

Hello, keyboard aficionados!

After nearly a year with the Nuphy Halo 65, I've accumulated a wealth of experiences and insights that I'm eager to share with you all. This journey with my first mechanical keyboard has been enlightening, filled with both admiration and a bit of dismay, particularly regarding its wireless functionality.

Value for Money & First Impressions

The Nuphy Halo 65 emerged as a beacon for me, an ideal entry point into the realm of mechanical keyboards. It's beautifully designed, from its build quality to the thoughtful inclusion of a switch tester kit, making it a fantastic package for its price. The keyboard's color scheme and backlighting deserve applause for their elegant subtlety, enhancing my workspace without distracting or straining my eyes.

Typing Experience & Design Praises

On a wired connection, the Halo 65 is impeccable. The tactile feedback and responsiveness have significantly boosted my productivity and enjoyment, whether I'm gaming, coding, or crafting documents. Its design and usability, particularly the non-intrusive backlighting, have made every typing session a delight.

Wireless Frustrations: A Cry for Help

However, the wireless experience has been a source of frustration since day one. Whether I connect via Bluetooth or the provided dongle, I face persistent latency issues and repeated inputs across several devices, including a MacBook Pro M1, a Lenovo ThinkBook with Arch Linux, and an older MacBook Pro 2013 running Windows 10. Despite my love for this keyboard, these challenges have tarnished its luster.

In my quest for a solution, I've updated the firmware and regularly cleaned the keyboard, yet the problem persists. This issue has left me rather disheartened, and I'm reaching out to this knowledgeable community for help. Any advice or tips to mitigate these wireless woes would be profoundly appreciated.

Concluding Thoughts

The Nuphy Halo 65 is a gem with a glaring flaw in its wireless mode. Its design, build quality, and typing experience (when wired) are top-notch, especially considering the value for money and the thoughtful inclusion of a switch tester kit. Yet, the wireless performance issues have been a significant drawback.

If anyone has navigated similar issues or has suggestions to improve the wireless experience, your input would be invaluable to me and, likely, to others facing the same predicament.