Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added alias UV-5R 8W Tripower #1222

Closed
wants to merge 2 commits into from

Conversation

ZombieEater
Copy link

Related to #11763 Alias added to model BF-F8HP for UV-5R 8W Tripower as suggested by Baofeng Support.

This UV-5R model, 8 Watt version, Tripower matches with BF-F8HP as recommended by Baofeng Support to be used in Chirp.
I just added the alias to be shown in the models list.

Copy link
Author

@ZombieEater ZombieEater left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ignore the commit of changes in requirements.txt ... my bad.

@directory.register
class BaofengBFF8HPRadio(BaofengUV5R):
VENDOR = "Baofeng"
MODEL = "BF-F8HP"
ALIASES = [RT5_TPAlias, ROGA5SAlias, UV5XPAlias, TSTIF8Alias,
TenwayUV5RPro, TSTST9Alias, TDUV5RRadio]
TenwayUV5RPro, TSTST9Alias, TDUV5RRadio, UV5R8WTri]
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the old way to do in-app aliases, which is not how they should be done anymore (I need to update the developer docs probably).

However, if this is just a straight "choose X instead of Y" as it seems from your posts on the matter, please do this in chirp/share/model_alias_map.yaml which affects the website list only.

@kk7ds
Copy link
Owner

kk7ds commented Jan 10, 2025

Also, please do not propose against the build_queue branch. Post propose against master which I push to build_queue when it's time to build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants