Hi,
This is a bit more far-reaching problem than just Netonix.
Currently, all platforms that require multiple config files packed into a binary as a backup need to be handled a bit better.
(Netonix, IgniteNet MetroLinq, etc.)
Basically, we really want to still have the text config in Unimus (which is the config.json for Netonix).
This is so you can do diffs, you can use "Config search", etc.
Also into the future, we are planning a feature when if a config is changed on a device, you get a notification.
Without having text configs, none of these features would work (since those can't really be done on a binary).
So if we only took the binary files, those features of Unimus would be useless for such vendors.
At the same time, like you say, we want to also keep the binary config file, so users can easily recover the devices.
We already have tickets for this:
https://tracker.unimus.net/browse/UN-235
https://tracker.unimus.net/browse/UN-238
https://tracker.unimus.net/browse/UN-281
So in the future, for vendors like Netonix, Unimus will take both text and binary backup.
(so all Unimus features are still useful, but user can also easily recover such devices)
As you can imagine, this will take some implementation time.
I would estimate the things described in the tickets should be ready by the end of Q3 this year.
At that point, support for vendors like Netonix will improve