Beeble Dummy Test

The dumbest node in the pack, and it's useful anyway

Beeble Dummy Test does exactly one thing: it takes a text string and hands it straight back as the status output. Type "hello", get "hello". There's no Beeble API call, no network, no API key, no image or video processing. Open the source and the entire node is a few lines that echo an input back to you.

And that's the point. When you install comfyui-beeble-switchx and the nodes don't show up, or a workflow dies at startup, the first question is always the same: did the pack even load? Every other node in this pack reaches for the network and needs a working BEEBLE_API_KEY - if it fails, you can't tell whether the problem is the install, the key, or the Beeble service. This node isolates the variable. It has a default text value of "Beeble SwitchX is loaded", so the moment it runs and returns that string, you know the pack registered, imported cleanly, and is executing. It's the smoke test you run before you start debugging anything else.

It's also the honest canary for a specific failure: if this node is missing from the node list while the rest of the pack's nodes appear, something odd is going on with registration - restart ComfyUI and re-check. If it appears but errors on run, you have an environment-level import problem, not a Beeble problem.

One quirk that'll save you confusion: the README's list of test nodes doesn't mention it. The author documented ten test nodes; this eleventh one is the debug leftover that shipped anyway. So don't go looking for documentation - the "documentation" is the default text and the fact that it echoes.

Inputs and output

• text (STRING, default "Beeble SwitchX is loaded") - the string to echo. That's the only input.
• Output: status (STRING) - the same text, verbatim.

Installing

Same as the rest of the pack - ComfyUI Manager (search "Beeble" or "SwitchX"), or:

cd ComfyUI/custom_nodes
git clone https://github.com/albert999-pixel/comfyui-beeble-switchx

Restart ComfyUI, then search for "Beeble". No API key needed for this one - which is precisely why you reach for it first.

When to use it

Use it as your install check, then forget it exists. Once the pack is confirmed loaded, the real work starts with the production nodes - Beeble SwitchX Image and Beeble SwitchX Video - or, if you're debugging an API step in isolation, one of the more purposeful test nodes like Beeble Account Info Test (which at least proves your key works). A node that just echoes text has a short shelf life; it's a diagnostic, not a workflow component.