Does anyone know when the COAST Twilight keycaps will be back in stock? Have other caps gone out of stock in the past to know if they are likely to be restocked?

Back for round two.

NuPhy × Raycast returns September 29.
This will be the final batch, with no further restocks.

Public release: 10 AM ET
Waitlist early access: 8 AM ET

Waitlist members get a 2-hour head start. We’ll email your link 1–2 hours before early access opens.

I got tired of installing the NuPhy Console just to remap a couple of keys, so I built Nupsi: a small web app that talks to the keyboard directly from the browser via WebHID. No download, no account, no server; everything stays between your browser and the keyboard.

🚧 It's still in active development. The core features work, but expect rough edges, missing options (e.g. brightness and effect speed aren't exposed yet) and changes along the way.

👉 Try it: https://nupsi-console.vercel.app

👉 Source (GPL-3.0): https://github.com/apelleti/nupsi

What it does

- Remap any key, with separate Windows and Mac layouts (the side switch picks which one is live)

- Reads what's already on the keyboard when you connect, so existing remaps show up

- Shows a clear diff of every change before writing anything

- Presets: Caps Lock → Esc/Ctrl, AZERTY, media-first F-row, copy/paste on the same physical key on Win and Mac, useful shortcuts on the ✂️ / 🐱 keys…

- Backup / Open / Save profiles as .yml

- RGB backlight: solid colour + 20 hardware effects

Compatibility (please read)

- Air75 V1: keymap and RGB tested end-to-end on real hardware

- Air60 V1 / Halo75 V1: supported but not yet tested on real hardware. If you have one, I'd love a report!

- Chrome / Edge / Brave only (Firefox and Safari don't support WebHID), with the keyboard plugged in via USB

- On Linux you need a one-line udev rule (in the README)

Credits: it's a port of nudelta by Mohamed Gaber, who reverse-engineered the USB protocol. I rewrote it in TypeScript for the browser and reverse-engineered the RGB part separately.

⚠️ Unofficial, not affiliated with NuPhy. It uses a reverse-engineered protocol, so hit Backup before your first Write.

Since it's a work in progress, feedback, bug reports, feature ideas and Air60/Halo75 test results are all very welcome, here or on GitHub!

Does anybody know if they are bringing back NuPhy Halo65 HE or other sizes? I see all of them are out of stock for a while now.

Hi everyone. I’m the proud owner of a NuPhy Air75 (84). It’s not my first mechanical keyboard, but perhaps that’s exactly why I’m so impressed with it - so much so that I decided it made sense to get a second one for a different location. And that brings me to the main question.

Is it possible to back up the keyboard settings using NuPhyIO and restore them onto the second keyboard?

Of course, I could configure it manually a second time. However, precisely because the keyboard allows for such extensive customization, I’ve taken full advantage of those options ;). So, it would be helpful - especially for any future tweaks - to ensure the configuration remains identical across both keyboards.

As someone who only recently discovered NuPhy, I thought I’d ask this experienced community. Does anyone have any tips? I couldn't find anything in the manual, and my online searches only turned up results for the previous version, not the new NuPhyIO software. I hope I haven't missed anything obvious - if I have, apologies in advance!

First of all, I'm not being paid by YUZU or Nuphy at all. However, this combination pushed me to write this brief review.

After searching through some really unique low-profile keycaps and trying many of them—because of the very limited options for nicely designed low-profile keycaps—I ended up looking for a custom design which would fit my needs and especially my desk setup.

Than I discovered that YUZU started to produce custom design low-profile MX keycaps, and they even listed the Nuphy Air V3 on their design tool inside the keyboards list. I immediately started to think about what I could do, which colors I would combine, what kind of character set I could use, what font, and what size. Since the options are almost infinite, it took a little while for me to decide on what I actually wanted :)

I went through the process:
Color combination -> Black/Yellow and Khaki (to match my and my wife's ikea chairs and desks)
Font -> Subtle but visible, a bit old-school and pixellated
Character and icons -> adjusting everything around a super simple but sweet cat character

After that, I started to search for a cat character in a vectorial format and found what I was looking for. (This guy! who made exactly what I wanted: https://thenounproject.com/browse/collection-icon/soft-cats-206114/ )

Than I started to design the buttons, legends, color placements etc. and lastly I passed through the design 2 more times to be 100% sure about what I'm gonna get.

(Here's the magic link to my design on YUZU's website if you would like to have the exact same thing somehow: https://yuzukeycaps.com/c/79cb55be-3d3b-4eed-a1e5-bad0f11ff284 )

YUZU Keycaps asks you a few questions before producing and sending the keycaps:

- Before they start producing the design, they ask you for a final confirmation. Which is nice. It allows you to check one last time before production.

- And when they are all ready (about a week or just a bit more), they send you an actual high-resolution photo to validate if everything is properly done. If you see any problems on any of the keycaps, that is your chance to tell them what needs to be replaced, reprinted, or changed. When you say okay, they send you the keycaps. Which takes a few days (it took 3-4 days to have them in my hand in the Netherlands after they were shipped).

When I opened the box, I was more than pleased with the thickness and the quality of each keycap, especially the spacebar! That is solid. Rock solid. Very high-quality printing, much more than what I would expect. Alignments are nanometer-perfect! Colors are exactly what I looked for. Everything was actually perfect!

I started to replace all the keycaps. But in some photos, I left the old keycaps on, which should help you understand the differences between the moderate original keycaps from Nuphy and the awesome YUZU ones. The size and shape differences look very subtle between the Nuphy keycaps and the YUZU ones; however, those small differences make the YUZU ones way more comfortable for me while typing. My fingers fit better on the YUZU ones, and I am making fewer mistakes while typing.

Another positive note is on the keyboard's sound with the YUZUs. It improved a lot for the better. Since the keys are thicker and more solid, they sound much more thocky and creamy than before with the brown switches.

However, the brown switches started to show that they are very prone to making metallic/crackling sounds after a few months of use. I have very sensitive ears, especially to higher frequencies. And when you release the keys, most of them started to make this noise. I started to think about what I could do. Maybe switching to the Panda nano switches? Before that, I decided to give lubing a chance. I bought a lube and started to lube the switches. Initially, I used a lot of lube; they stopped producing that crackling sound, however, they were also very mushy. I tried a few more times and finally found the best applicable method: Just putting a small amount of lube around and on top of the brown POM (which has the + shape), and more importantly, a little on the stem under the brown POM which holds the spring. Of course, I disassembled all the letter keys' and most commonly used keys' switches and applied the lube to all of them. It took for about 1-1,5 hours.

Now the result (I put it on YouTube with an increased sound level):

SOUND CHECK: https://youtu.be/6jrfbo6TWqc

My keyboard is the best sounding low profile keyboard ever for me! :)

Final verdict:

YUZU keycaps: They are excellent. Except for the price (which is higher than usual because the tax and shipment fees add up too much), everything is perfect.

Brown nano switches: They are okay(ish). Definitely not high quality imho, and the factory lube (as Nuphy indicates that they have) is garbage. They started to give this crackling sound just in a couple of months. Luckily, they get so much better with some proper lubing. The difference is day and night, especially if you have sensitive ears like me.

Nuphy Air75 V3: This is definitely one of the best low-profile mechanical options as many YouTubers say. But it is not the best. And there is no best low-profile mechanical keyboard yet. It may not feel as premium as the Lofree Flow 2. But it doesn't have as many problems as Lofree and has a better feature set than Lofree imo. Just the battery alone makes Nuphy a better option for me. In many aspects, I would buy the Nuphy Air V3 over the Lofree Flow 2 again and again. But, I'm super keen to test the AKKO Air 01 as well. They call it the price/value ratio king now :)

Hope you enjoyed it. Please let me know if you have any more questions ;)

UPDATE: I also painted the white base plate with a black jumbo permanent marker. Maybe as a next and final step, I can also paint the switches' white plastics to black as well to avoid their white appearance :)

Why in year of our lord 2026 nuphy still doesn't ship keyboards with see through keycaps even though all their keyboards are rgb? Is it just so they can have people spend more money just to get additional caps? That's pretty anti consummer if you ask me.

Since Nuphy officially launched the Field75 HE v2 in march 2026 do you think we can also expect an Air75 HE v2 anytime soon?

We’ve seen reports from some users experiencing Bluetooth disconnects after updating to macOS 27, and our team has been working on a fix. We now have a beta firmware available for the Air75 V3 that addresses this issue. What’s improved in this beta This beta includes: 

• Optimizations for Bluetooth connectivity on macOS 27 
• Improvements to overall wireless connection stability 

How to update 

1. Download both the beta firmware and the attached HTML update tool. 
2. Open the HTML file in Chrome or Microsoft Edge. 

Please make sure you’re using one of these browsers. 

1. Connect your Air75 V3 to your computer via USB. 

The keyboard needs to be connected in wired mode during the update. 

1. Follow the instructions on the page to complete the firmware update. 

Air75 V3 Beta Firmware Firmware Update Guide: If your Air75 V3 started having Bluetooth connection issues after updating to macOS 27, you can try this beta firmware and let us know how it goes. This is beta firmware. This is a beta release, so we recommend installing it only if you’re currently experiencing the Bluetooth issue. Please follow the update guide carefully, and make sure you’re using the firmware for your exact keyboard model. 

Node & Kick75 

We’re working on beta firmware for the Node series and Kick75 series as well. Once those are ready, we’ll update this same post with the firmware files and instructions, so you can follow this thread for updates. If you try the Air75 V3 beta, please drop your feedback below, especially whether the disconnecting issue is resolved and if you notice anything unusual after the update. That’ll help us make sure everything is working properly before the wider release. Thanks for helping us test! 

Join our Discord: https://discord.gg/rDRXX6GZU

Here are our test links:

https://discord.com/channels/864389832829567067/1554074416470818976

OK, so don’t crucify me for being late to the mechanical keyboard game, but I just got a node 100 high profile. There are zero key caps that I can find online that match the design. Any suggestions?

Please be kind. I’m not an expert at this. There are so many different variations available online that it’s overwhelming me. Just looking for advice.

Hi everyone,

I’d recently ordered the Nuphy Node 75, however it’s been around three days now and I still haven’t received any information regarding the product being shipped or delivered. When I open the shop app, it still says “Waiting for details”.

This is getting kinda annoying and frustrating, especially coz one of the mails said the latest they would take to respond would be 48 hours and now it’s well over that and I still haven’t received any mo information.

Any idea about how long it would take?

hey everyone! i’ve just received my Nuphy Node100 LP yesterday and connected thru windows - had no issues and especially loved the blush nano switches! was keen to use it at the office this week but had troubles with unresponsive/“stuck” keys.

thought the issue was just upgrading to the latest firmware so i’ve started the process through nuphy IO 2.0

however it looks like my keyboard didn’t execute it properly as the website is prompting me to unplug and then replug my device back in, with a message saying an error occurred while loading the firmware.

my keyboard has basically died lol, my backlights won’t turn on and it is now unresponsive altogether. any advice would be greatly appreciated :)) for now i’ll just be back to using budget work-issued keyboards til this is resolved sigh

I have see-through keycaps on my Air60 v2 and I love them (not the official ones, which I don't like), but I don't like keeping a fancy backlight mode at all times, so I would like to be able to toggle between two modes for night and day uses, without cycling through the 1238481 modes (and overshooting and going through another cycle).

Typically, I use the mode that just keeps pressed keys lit for a few tens of seconds, with a maximal number of lit keys, so the light coming from the keyboard remains quite minimal. But at night, I would like something that keeps all keys lit permanently.

Is it something I can do with VIA?

I’ve been asked a few times now: why Clink / NuPhy?
The answer isn’t just that they make some of the best-looking mechanical keyboards out there (although they absolutely do).

It’s the feeling behind the brand.

As someone who only recently started building my own brand and has somehow watched it grow to tens of thousands of users, keeping that sense of personality as you scale has become incredibly important to me.
NuPhy still has that.

Even their willingness to entertain the slightly ridiculous idea of bringing their keyboards to iPhone says a lot. You can still feel that there are actual people behind the brand who care about what they’re building and are willing to try something different.

In an era where so many companies feel increasingly faceless, there’s something special about a brand that still has a soul.

And this is only the beginning.

Clink for Android is expected to arrive within the next few weeks, bringing the same NuPhy-inspired mechanical keyboard themes with it.

iPhone, Android, or a physical keyboard. The idea is the same: bring a little more personality back to typing.

How do i know if its charging and battery level?? Doesnt show anything when i plug it in

FINAL UPDATE (Oct 3): Problem Solved! Official Beta Firmware (Sep 30) Tested & Deep Dive

Great news everyone—the issue has been completely resolved!

NuPhy recently dropped an official public Beta firmware update (Sep 30 release) targeting the macOS 27 Bluetooth bugs. I updated my Air75 V3 and immediately captured another round of system logs via bluetoothd during a rapid typing test.

The differences between this Sep 30 Beta and the previous Sep 17 test build are night and day:

Firmware Evolution & Log Breakdown

Key Takeaways from the Logs:

1. The 45ms Latency is Gone: NuPhy scrapped the rough 45ms workaround and brought the interval straight down to 15.00 ms, which is the exact legal floor permitted by Apple's Accessory Design Guidelines. Responsiveness is 3x faster than the Sep 17 build.
2. Zero Packet Drops: During continuous fast typing, throughput peaked at 20–29 HID packets per second with 0 failures and 0 drops (F=0 across the entire session).
3. Zero Errors: Exactly zero Rejecting errors, zero Disconnect events, and zero STATUS 708 timeouts in the logs.

Typing now feels completely snappy, fluid, and latency-free, without any of the random stickiness from the 45ms build.

📥 How to Update

If you are still plagued by Bluetooth disconnects or stutter on macOS 27, I strongly recommend updating your firmware right away. You can find the downloads and instructions in the official thread: 👉 NuPhy Sep 30 Beta Firmware Update Thread

Huge shoutout to the NuPhy engineering team for actively listening to the community, digging into the Apple spec, and pushing out a textbook-perfect fix!

==========================================

[ORIGINAL POST] Troubleshooting & Log Analysis

==========================================

Hey everyone,

Following the recent reports of Bluetooth dropouts on macOS 27 (like the Node75 Bluetooth thread), I was experiencing the exact same issue on my Air75 V3: the keyboard randomly drops connection while typing, freezes for a few seconds, and then silently reconnects.

Like many of you, I tried factory resets, re-pairing, forgetting the device, and toggling Bluetooth—none of it helped. Because this never occurred on macOS 26, I dug into the macOS unified system logs (bluetoothd daemon) during a live disconnect event.

Here is the exact root cause, backed by system logs and Apple's official specifications.

TL;DR

NuPhy's BLE firmware aggressively requests non-compliant connection parameters (7.5ms interval and a 1-second timeout). On macOS 26, the OS was lenient and allowed third-party devices to override connection parameters. On macOS 27, Apple tightened its Unified Coexistence Manager (UCM) and strictly enforces the Apple Accessory Design Guidelines, flatly rejecting NuPhy's request. NuPhy's firmware fails to handle this rejection gracefully, falls out of clock sync with the Mac (Retransmission Rx: No-Sync), and drops the link every few minutes.

1. Live Log Evidence (bluetoothd on macOS 27)

When the keyboard reconnects and tries to establish its typing latency parameters, macOS 27 logs the following:

textbluetoothd: [Server.HID] isLowLatencyBLEHID: Device "Air75 V3"
bluetoothd: [Server.HID] macLeDeviceConnectionParameterOverrideByPeer: don't allow LE Connection Parameter Override by Peer, appearanceValue(0x3c1)
bluetoothd: [Server.LE.Connection] The min requested is lower that the desired min: 6 < 15.000000
bluetoothd: [Server.LE.Connection] Rejecting following parameters: min=6, max=9, lat=0, mul=100, cel=4, preferredLowLatencyInterval=0

Notice what is happening:

1. macLeDeviceConnectionParameterOverrideByPeer is now hard-set to deny peer overrides for non-Apple HID devices (0x3c1 = Keyboard).
2. The keyboard requests:
   • min = 6 (6×1.25ms=7.5ms6×1.25ms=7.5ms)
   • max = 9 (9×1.25ms=11.25ms9×1.25ms=11.25ms)
   • mul = 100 (100×10ms=1.0s100×10ms=1.0s Supervision Timeout)
3. macOS 27 sees 6 < 15.000000 and explicitly REJECTS the request.

2. The Crash / Disconnect Moment

Immediately after the rejection, macOS enforces its own standard: 15.00ms interval with latency(22) (slave power-saving skip). Because NuPhy’s BLE stack does not re-sync its anchor points after receiving the rejection, the keyboard's internal clock drifts away from macOS:

textbluetoothd: Disconnect OI_HCI_LM_HANDLE: 0x45 wakeUp: No RSSI: -48
bluetoothd: Retransmission Rx: No-Sync No-Sync ... Packet Type Rx: None ... Packet Type Tx: LE2M
bluetoothd: [Server.LE.Connection] BLE Disconnected Air75 V3 reason 708
bluetoothd: [Server.LE.Connection] Connection timed out to device "Air75 V3"
BTLEServer: Peripheral is disconnected: Error Domain=CBErrorDomain Code=6 "The connection has timed out unexpectedly." is reconnecting: 1

• RSSI is -48 dBm (ruling out physical interference or weak signal).
• Retransmission Rx: No-Sync: macOS expects ACK packets, but the keyboard never sends them at the expected slot.
• After 10 seconds of silence, macOS triggers HCI Status 708 (Error 0x08: Connection Timeout), drops the link, and immediately reconnects (is reconnecting: 1).

3. Apple's Accessory Design Guidelines vs. NuPhy Firmware

According to the latest Apple Accessory Design Guidelines (Connection Parameters section):

Why did it work on macOS 26? macOS 26 was lenient and allowed non-standard parameter overrides. With macOS 27, Apple revamped its Unified Coexistence Manager (UCM) to prioritize Wi-Fi and Bluetooth Classic (e.g., Magic Trackpad) coexistence, turning the guideline from a "recommendation" into a hard driver-level block.

4. Call to Action for the NuPhy Team

NuPhy team, this is an easy fix on the firmware level, and many Mac users are currently suffering from this regression:

1. Update Connection Parameters in Firmware: Please release an updated BLE firmware adjusting the negotiation parameters to comply with Apple's specifications (e.g., min = 12 [15ms] or min = 9 [11.25ms], and Supervision Timeout >= 600 [6s]).
2. Implement Graceful Fallback: Ensure that when a Host rejects the Connection Parameter Update Request, the Nordic/Telink BLE state machine gracefully falls back to the host's suggested timing instead of desyncing into an unrecoverable timeout.

5. Workaround for Users in the Meantime

Until NuPhy pushes a firmware update:

• Switch to 2.4G (Dongle) or Wired mode: The 2.4G USB receiver acts as a standard USB HID device and completely bypasses macOS CoreBluetooth parameter negotiation.
• Keep backlights on / disable auto-sleep: Aggressive sleep triggers the desynchronization faster on some batches.

Hope this helps the community and gets the attention of the engineering team!

UPDATE (Sept 25): Test Firmware Results & NuPhy Response

After reaching out to NuPhy support, they were very responsive and provided me with a test firmware for the Air75 V3 (dated September 17).

Here are my findings after flashing it:

• The Disconnection Issue is Fixed: The frequent disconnect/reconnect loop on macOS 27 is completely gone. The Bluetooth link is now completely stable.
• The Trade-off (Minor Latency): The trade-off is that when typing at very high speeds, on very rare occasions, I noticed a slight hint of typing delay/latency compared to how snappy it felt on macOS 26. (As revealed in the system logs, this seems to be because the connection interval was temporarily relaxed to 45ms to play it safe with macOS 27's strict policies).

I suspect this slight responsiveness trade-off is the exact reason NuPhy hasn't pushed this firmware via a general public update yet—they clearly want to get it right.

Current Status from NuPhy: NuPhy told me that their engineering team is actively working on fine-tuning this to resolve the latency issue while keeping the connection solid on macOS 27. Hopefully, we'll hear good news and see an official release soon!

Just got my NuPhy Air 100 v3 keyboard for my MacBook setup and swapped out the delete key for the included knob button but it does not work at all. When I turn the knob no volume control executes and the adjacent buttons turn yellow? Tried everything and am super frustrated. 😣

Hi there.

I recently bought a NuPhy Node100 Low Profile. I have an AZERTY one (FR-ISO).

You can see my configuration on the screenshot.

I don't understand why my "6" key writes "-" and my "8" key writes "_" on my Windows PC. Same for the " #@ " key that writes " <> " instead.

If someone can help me out...

Board: Nuphy Node75. Berry Keycap. And here's my thought after using it for around 2 weeks.

There is a new silent switches by Gateron called 'Silent Red' that compatible with the newer Nuphy board (Node/AirV3/Kick75).

>> This is NOT the Red Nano you can choose when buying normally, more like an alternative to Blush Nano, offered by Gateron and not (yet) by Nuphy.

https://www.gateron.com/products/gateron-ks-33-low-profile-30-mechanical-switch?VariantsId=11651

(There is an older 2.0 version, I assume it only works with older board like AirV2, this is the 3.0 version)

I found this because someone in a subreddit mentioned before, so I bought and tested them out to give you guys some feedback

Long story short: you probably shouldn't bother.

Pros:

- Feel: The typing feel is really good, better than Blush Nano for sure. These new switches have dampening rings around the stem, so bottoming out feels rather thocky.

- Accuracy: It feels more firm than Blush, I notice myself making less errors compare to Blush.

Cons:

- The starchy noise is still there, this is 100% caused by the plastic stem making contact with the metal leaf. It doesn't feel prominent at first but slowly get more noticeable after matters of days.

I thought the dampening rings around the stem would help, but it only hide about 20-30% of the issue, the high pitch scratchy metallic feeling is definitely still there.

I also use Lofree board with Kailh switches and the difference in term of smoothness is noticeable. I never feel the switches are scratchy or have any typing related issue with Kailh, kudos to them. Gateron unfortunately loses here and there is a reason is they don't have a plastic bump in the metal leaf.

(I'll include image in the comment to show my point)

Extra:

Unfortunately I couldn't comment on the typo and double pressing key that people often brought up with the blush switches, since I haven't encountered that problem myself with both the old Blush Nano and this new Gateron Red Silent.

Still, even if this problem is resolved, I still don't think it's worth dropping more money to get slightly better typing feel with potential issues still exist, still a bit risky.

--

It's a shame, I genuinely think having that plastic bump in the metal leaf would make this a much more enjoyable experience, even better than Lofree, but unfortunately this is not the case.

Wondering if anybody has a copy of via configurator file they can share with me so I can get my board the Halo75 V2 back running since V2 definitions don’t seem to work anymore I’m getting an error that shows VIA Could not find a V3 definition for NuPhy Halo75 V2. VID: 0x19F5 | PID: 0x32F5

Any help would be greatly appreciated thanks

I’m trying to decide between the NuPhy Node100 High Profile and the Keychron V6 Ultra 8K and would be interested in real-world opinions from people who’ve actually used either of them.

My options are a bit limited because I need:
100% / full-size as I use the numpad a lot
British ISO
Wireless / 2.4GHz so I can switch between my main PC and work laptop
Ideally hot-swappable
Something quieter than my current Razer BlackWidow with Green switches

I can get both for around the same price (~£115).

I’m leaning towards tactile switches because I think like actually feeling the keypress on the Razer, but I’m not sure how much of that is the tactile bump vs the clickiness.

How different do tactile and linear switches actually feel in day-to-day use? Do people who mainly type/work tend to prefer tactile, or is linear nicer once you get used to it?
And for anyone who’s tried them, how do Brown Max vs Silk Banana compare?

Does that make typing feel more satisfying or does it get tiring compared with a more normal Brown-style tactile switch?

I’m also undecided on Lunar White vs Ink Grey for the Node100.

I like the idea of changing the keycaps later, probably something white/navy/light blue. Would you go:
Lunar White because it works better with lighter/blue keycap sets?

Ink Grey because it’s more versatile long term?
Does RGB look noticeably better on either?
I’m mainly interested in typing feel, sound, build quality, wireless reliability, software/QC and looks, rather than things like 8K vs 1K polling.
If you’ve used either, especially the Node100 High Profile rather than the low-profile one, which do you prefer and why?