Add support for wilba.tech wt65_h4

[MrLys]

Description

Add support for the h4 based off of h1. I have not been able to make via work after flashing this, as such via is not enabled. Usevia.app did work prior to flashing. vendorId and productId is based on use-via/keyboards.

I'm unsure of who to put as maintainer in keyboards/wilba_tech/wt65_h4/readme.md

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout/userspace (addition or update)
• Documentation

Issues Fixed or Closed by This PR

• Added support for the h4 based off of h1.

Checklist

• My code follows the code style of this project: C, Python
• I have read the PR Checklist document and have made the appropriate changes.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[waffle87]

Also, correct me if I'm wrong, but the only difference this keyboard has with wilba_tech/wt65_h1 is the layout? If so, you should simply add the layout to that keyboard's info.json, and a keymap utilising that layout if you'd like.

[MrLys]

Also, correct me if I'm wrong, but the only difference this keyboard has with wilba_tech/wt65_h1 is the layout? If so, you should simply add the layout to that keyboard's info.json, and a keymap utilising that layout if you'd like.

Not entirely sure what the exact differences are. I just used it as a baseline. But I could just as well have used the wt65_g. The productid is also different, h4 has 0x0038.
If you think that is the best approach then I’ll do that.

[waffle87]

It appears these could probably all be consolidated into one. I'll have a look at it now and incorporate your layout here and reach out if you're able to test.

[waffle87]

Can you please try my refactor/wt65 branch. You can check it out locally using:

git remote add waffle https://github.com/waffle87/qmk_firmware
git fetch waffle
git checkout refactor/wt65
qmk git-submodule
qmk clean
qmk flash -kb wilba_tech/wt65_h -km iso

edit: The PR mentioned below contains the layout you are adding here, so that PR can be used instead.

[MrLys]

Can you please try my refactor/wt65 branch. You can check it out locally using:

git remote add waffle https://github.com/waffle87/qmk_firmware
git fetch waffle
git checkout refactor/wt65
qmk git-submodule
qmk clean
qmk flash -kb wilba_tech/wt65_h -km iso

edit: The PR mentioned below contains the layout you are adding here, so that PR can be used instead.

Great! I’ll try to test it during the weekend.
Any idea how to make it via compatible? Based on the documentation on the usevia website this should work, but after flashing it is not recognised.

[drashna]

Great! I’ll try to test it during the weekend. Any idea how to make it via compatible? Based on the documentation on the usevia website this should work, but after flashing it is not recognised.

That requires via to have the proper json merged into their repo.

[MrLys]

Great! I’ll try to test it during the weekend. Any idea how to make it via compatible? Based on the documentation on the usevia website this should work, but after flashing it is not recognised.

That requires via to have the proper json merged into their repo.

I see, that it what I thought. Shouldn’t this be enough for that?

[github-actions]

Thank you for your contribution!
This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready.
For maintainers: Please label with bug, awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.