sharing contacts, channel list, scan groups, zones between devices

[dpocock]

I have some different devices, including handheld and mobile radios. Each of them has a different config file and it is not feasible to use the same config file or codeplug for every device.

However, it would be really useful for me if there was a way to use the GUI to maintain a list of contacts, channels, zones and scan groups and then share those things with all the device-specific YAML files.

As a workaround, it is not hard to cut-and-paste the contacts, channels and other relevant stuff between the YAML files. For those of us who are developers it is very easy to make a script for modifying the YAML files. But it would be nice to have a way to do this in the GUI.

[hmatuschek]

First of all, you can remove all device specific settings from the YAML file and keep a bare one. Writing this bare config file to any device will maintain the present radio-wide settings in the device. qdmr reads the codeplug from the device and updates it with the chosen config.

This however does not apply to element you actually write. E.g. channels. For the moment, there is means to conserve these settings across device. Hence device specific settings.

I am in the process of unifying some settings across many devices for the upcoming release. So which device specific settings are there, that can be applied to other radios that are of relevance to you?

[dpocock]

First of all, you can remove all device-specific settings from the YAML file and keep a bare one.

I wonder if there is a way these workflows could be semi-automated.

It would be useful to break the config into building-blocks. For example, to have a set of button mappings that can be shared between radios of the same brand or with the same number of buttons.

I am in the process of unifying some settings across many devices for the upcoming release. So which device specific settings are there, that can be applied to other radios that are of relevance to you?

Each radio has different buttons. Therefore, I have to keep separate YAML files with the button assignments for each radio.

[hmatuschek]

You may write a small python script that cleans the yaml files. In the end, they are just yaml files.

You can split the codeplug into parts and then import every part you need into the final one. However, I've never tested it with extensions. I usually use it to keep codeplugs for regions (e.g., home, holyday, ...), sat and PMR stuff separate and merge it as I need it.

[hmatuschek]

And yes, button settings are a mess. There is a large common set of functions for all radios but there are also very specific options for some devices.

However, the button settings are stored globally. So qdmr just maintains them when writing a codeplug without a button settings extension.