Ino Cast Any To Controlnet

ComfyUI's type system is a set of conventions, and sometimes two nodes disagree about what something is. Ino Cast Any To Controlnet is the diplomat: it takes any input and outputs it typed as control_net, a CONTROL_NET. The description is blunt: "Casts any input to a CONTROL_NET type."

That's all it does - and before you ask, yes, it's as close to a no-op as this pack ships. The value isn't transformation; it's satisfying a type check so a wire will connect.

How it works

The input is typed as * (any type), and the output is typed as CONTROL_NET. At execution it returns the input unchanged. So the "casting" is a typing claim, not a conversion - the node asserts "trust me, this is a ControlNet," and downstream nodes that require a CONTROL_NET input will accept the wire. When the underlying value genuinely is a ControlNet (say, it came from a loader node whose output typing got lost or mismatched in a chain of any-typed passthroughs), this makes the connection work.

Inputs and outputs

• input_any - anything, but realistically a value that's already a ControlNet underneath.

Output: control_net - the same value, now typed CONTROL_NET.

Where it wires in

The use case is narrow but real: fixing connection problems when an any-typed node sits between your ControlNet loader and the Apply ControlNet node. If ComfyUI refuses the wire because it can't prove the type, this node's job is to make the claim and get the graph running. It's also useful when you're building reusable sub-graphs that want a stable typed port.

Installing it

Part of ComfyUI-InoNodes. ComfyUI Manager → search "ComfyUI Ino Nodes" → install → restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/nobandegani/ComfyUI-InoNodes
cd comfyui_ino_nodes
pip install -r requirements.txt

Restart after. No keys, no models.

Common issues

The honest warning: this node does not load a ControlNet, convert a tensor to one, or build anything. If you feed it an image tensor, the output will be typed CONTROL_NET but the downstream node will blow up at execution because the value isn't really a ControlNet - you'll have satisfied the type check and broken the semantics. Cast nodes are for rerouting correctly-typed values, not for conjuring types out of thin air. If you need an actual ControlNet, load it properly (the KB's controlnet essay is the read for weights and step-gating once you do); this node just makes the wire click.