☁️BizyAir Load ControlNet Model

This is the loader that feeds every ControlNet apply node in the pack - pick a model, get back a BIZYAIR_CONTROL_NET, wire it into whichever Apply ControlNet node matches your base architecture. Like the checkpoint and CLIP loaders elsewhere in BizyAir, there's no file on your disk involved: control_net_name is a dropdown populated from SiliconFlow's cloud catalog, and the actual ControlNet weights run on their servers.

The two ways to pick a model. control_net_name is the catalog dropdown - whatever ControlNets SiliconFlow has onboarded, which per the pack's own version history spans the modern union-style checkpoints as well as older single-condition models. model_version_id is a text field for the other path: if you've uploaded or been shared a specific ControlNet through BizyAir's model-hosting system rather than picking from the built-in list, you paste its version ID here instead. Leave it blank to just use the dropdown selection. This loader is the newer of BizyAir's two ControlNet loaders - its sibling, ControlNetLoader_Legacy, only offers the fixed dropdown with no model_version_id option, which tells you this is the one meant to keep pace with BizyAir's catalog as it grows rather than staying locked to a fixed list.

What to actually load depends entirely on your base model, and this is the part worth getting right before you even open the dropdown. ControlNet isn't portable across architectures - a ControlNet trained for SD 1.5 doesn't load on SDXL, doesn't load on Flux, doesn't load on SD3.5; every DiT-based architecture needed its own ControlNet trained essentially from scratch, because the mechanism itself changed from wrapping a UNet encoder to hooking into attention and MLP layers. Match whatever you load here to the checkpoint you're actually generating with - mismatches don't produce a clean error, they just produce a ControlNet that has no meaningful relationship to your base model's latent space.

Inputs that matter: control_net_name, required, enum populated from the cloud catalog. model_version_id, optional string, default empty - for custom/shared models by version ID instead of the catalog list.

Output: CONTROL_NET in the node's own display label, but typed BIZYAIR_CONTROL_NET - only connects to BizyAir's ControlNet apply nodes downstream, not a stock ComfyUI ControlNet apply.

Install: search "BizyAir" in ComfyUI Manager and install, or cd ComfyUI/custom_nodes && git clone https://github.com/siliconflow/BizyAir.git and restart, or comfy node install bizyair via the Comfy CLI - one pack install brings in this loader with everything else. As with every node in BizyAir, this one is a cloud call, so you need a registered account with your API key set before the dropdown will even populate, let alone run - the README states this as a hard first-use requirement, not a suggestion.

Troubleshooting. An empty or non-functional control_net_name dropdown almost always means an authentication problem - check your API key before assuming the catalog itself is broken. If the ControlNet loads fine but seems to have no effect downstream, the far more common cause is an architecture mismatch (loading a ControlNet trained for a different base model than the one you're generating with) rather than anything wrong with this loader - double-check the pairing before touching strength or step-range settings on the apply node.