Add `manifest.json` to custom_component about zha-custom-radios

[puddly]

That's a good idea. Does this require moving the custom component into a module folder?

[Adminiuga]

Not quite sure I'm following. Maybe we should split the custom_component into it's own repo, but I think we could keep it in here for now and just re-organize ./custom_components/zha_custom_radios.py into ./custom_components/zha_custom_radios/zha_custom_radios.py and add here the __init__.py and manifest.json

If you mean that, then yeah, the custom component should become a module, but not the zigpy_znp module.

If we split into it's own repo, then we could add it to HACS for easier installation.

[puddly]

Yeah, that's fine.

No part of the custom component hard-codes zigpy-znp so it might be useful as an external module, in case someone wants to write another library for a new radio (I guess NXP and Nordic are the only ones left?) and test it with HA.

[Adminiuga]

That's a good idea!
With a minor problem of finding a volunteer to write NXP lib 😃

[Adminiuga]

Sent you the invite, should have enough permission to create a new repo if you decide so

[puddly]

Thanks. I'll probably give it a try in a couple of days.

[puddly]

There's no way to make this custom component work, I'm afraid. The manifest.json does get HA to auto-install dependencies but its presence also makes this component load way after zha to do its thing. The only way (as far as I can tell) to actually run code early is to purposefully create a legacy custom component and abuse the fact that it's imported before being loaded: https://github.com/zha-ng/zigpy-znp/blob/dev/custom_components/zha_custom_radios.py

At that point it'd be easier to have the component install zigpy-znp itself, though that's getting a little too complex for my liking.

[Adminiuga]

Ah, yep. I don't know any other way to make it user friendly.