VIA is *stopped* working for NuPhy Air 75 0

[nveeser]

I bought a Nuphy Aiir75 V2 in Jan or Feb.
I used VIA to update the keyboard mapping using the specified JSON file.

Since March I have tried to use the VIA app. It recognizes the keyboard to authorize, but does not connect.
Under settings it says "Requires connected device"
The settings menu does not allow uploading a new JSON layout file.

To Reproduce
Steps to reproduce the behavior:

1. Attach Keyboard
2. Click Authorize
3. Pick NuPhy Air75 / Connect
4. Settings (tab)
5. Show Design Tab
6. Design (tab)
7. Load nuphy-air75-v2-via-2.json
8. Configure (tab)

Expected behavior
I believe the configure tab will eventually show me a keyboard with mappings.

Screenshots
If applicable, add screenshots to help explain your problem.

VIA Version

• [x ] I am using https://usevia.app/
• [x ] I am using the latest release of the desktop app from https://github.com/the-via/releases/releases/latest

Keyboard firmware VIA protocol
This can be found under Settings > Show Diagnostic Information

This shows "Requires Connected Device"

Desktop (please complete the following information):

• Desktop - 3.0.0 - MacOS (Intel)
• Browser - Chrome 125.0.6422.26 - MacOS (Intel)
• Browser - Chrome 125.0.6422.26 - MacOS (M2)
• Browser - Chrome 125.0.6422.26 - Windows

Custom json definition?

• [?] I am loading a custom json definition using the designer tab

I would if that were possible - it seems the keyboard is not detected at all

Sanity checks

• [ x] I have tried connecting the keyboard directly to the computer (i.e. not using a USB hub)
• [ x] I have flashed the latest firmware from https://www.caniusevia.com/docs/download_firmware

I have tried the 1.1.3 firmware from https://nuphy.com/pages/qmk-firmwares
I have also compiled and loaded
https://github.com/nuphy-src/qmk_firmware
https://github.com/jincao1/qmk_firmware

Additional context
Add any other context about the problem here.

[vincenthopf]

I'm currently having the exact same issue. Did you ever get a fix?

[vincenthopf]

@nveeser This is how i fixed my issue:

Ran updates for the QMK Firmware on the keyboard using QMK toolbox (How to here).
Updated to version 2.0.3.
Pairing this with the updated firmware v3 allowed me to get it to connect properly. Turns out I was using an old version of firmware paired with the new .json file.

I also found that sometimes when using usevia.app the keyboard wouldn't connect. I fixed this by re-uploading the .json file to the design tab and making sure the keyboard was unplugged when doing this. When the popup in chome comes up to select a keyboard I would then plug in the usb cable (That came with my keyboard) into the keyboard itself (Making sure it was in wired mode before hand.).

Hope this helps anyone who is having the issue.

If anyone has any questions feel free to shoot me a message using my website (Link on profile)

[cherishh]

update firmware(to v2.0.3) works for me.

[EugeneP87]

@vincenthopf Thanks, Vincent, it works! 🤝

[nveeser]

I did manage to get this to work. Here is the link that worked - specifically the last part #290 (comment) ` I also found that sometimes when using usevia.app the keyboard wouldn't connect. I fixed this by re-uploading the .json file to the design tab and making sure the keyboard was unplugged when doing this. When the popup in chome comes up to select a keyboard I would then plug in the usb cable (That came with my keyboard) into the keyboard itself (Making sure it was in wired mode before hand.). `

…

On Fri, Jun 28, 2024 at 7:24 AM Tonga52 ***@***.***> wrote: @vincenthopf <https://github.com/vincenthopf> I've been having the same issue and followed your steps to no avail. Still stuck on loading. Any other ideas? Cheers! — Reply to this email directly, view it on GitHub <#290 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAB6HA3DMIBURASAUIVNPV3ZJVWZPAVCNFSM6AAAAABHHON2IGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJXGA3DCNRVGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[stiff]

If anyone tried everything and still get Searching for devices in VIA, then open json in text editor and change V2 in name to V2.1

[kittykatmax]

Currently having this issue with the latest firmware/.json for the NuPhy Halo75 V2. Maddening!