Save 4 hours! We auto-setup your workflow! Free!

Drop your workflow.json — we handle every dependency, custom node, and model. Just open the link and run.

Auto-Setup Workflow Json (Free) Now!
ComfyUI > Nodes > ComfyUI-DaSiWa-Nodes > DaSiWa Node Status Switch

ComfyUI Node: DaSiWa Node Status Switch

Class Name

DaSiWa_NodeStatusSwitch

Category
DaSiWa/utils
Author
darksidewalker (Account age: 1999days)
Extension
ComfyUI-DaSiWa-Nodes
Latest Updated
2026-11-08
Github Stars
0.22K

How to Install ComfyUI-DaSiWa-Nodes

Install this extension via the ComfyUI Manager by searching for ComfyUI-DaSiWa-Nodes
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter ComfyUI-DaSiWa-Nodes in the search bar
After installation, click the Restart button to restart ComfyUI. Then, manually refresh your browser to clear the cache and access the updated list of nodes.

Visit ComfyUI Online for ready-to-use ComfyUI environment

  • Free trial available
  • 16GB VRAM to 80GB VRAM GPU machines
  • 400+ preloaded models/nodes
  • Freedom to upload custom models/nodes
  • 200+ ready-to-run workflows
  • 100% private workspace with up to 200GB storage
  • Dedicated Support

Run ComfyUI Online

DaSiWa Node Status Switch Description

Controls muting or bypassing up to 99 ComfyUI nodes with configurable toggles and chained switches.

DaSiWa Node Status Switch:

DaSiWa_NodeStatusSwitch is designed to control whether selected nodes are muted or bypassed in a ComfyUI workflow. You identify a target by connecting any of its outputs to a target socket on the switch. The sockets appear one at a time as you connect them, up to 99 targets. This gives you a way to manage several parts of a workflow together and to chain switches under one toggle while letting each switch make its own activation and action choices. The supplied implementation confirms how the node passes its boolean value onward; the actual muting or bypassing behavior is described by the provided context and is not demonstrated by the Python execution method alone.

DaSiWa Node Status Switch Input Parameters:

enabled

A BOOLEAN master toggle with a default of true. You can set it to true or false; there is no numeric minimum or maximum. Its value is used with trigger_on to determine which boolean state activates this switch. The node also passes this value to enabled_out, so changing it can affect any downstream switch connected to that output.

trigger_on

Choose when the switch is active. The options are true → active and false → active; the default is true → active. Choose the first option when you want the selected action associated with an enabled value of true, or the second when you want it associated with false. Each switch has its own setting, so switches receiving the same boolean can be configured for opposite states. There is no numeric minimum or maximum.

action

Choose what the switch is intended to do to its targets when active. The options are mute and bypass; the default is bypass. Use mute when you want target execution stopped, or bypass when you want targets passed through instead, as described by the node interface. There is no numeric minimum or maximum. This choice belongs to the individual switch and is not passed to chained switches.

DaSiWa Node Status Switch Output Parameters:

enabled_out

A BOOLEAN output containing the effective value of enabled: true when enabled is true and false when it is false. You can connect it to another switch’s enabled input to control a chain from one toggle. It does not report whether this particular switch is active, whether its targets were muted or bypassed, or which action was chosen. A downstream switch interprets the passed value using its own trigger_on and action settings.

DaSiWa Node Status Switch Usage Tips:

  • Connect any output from each node you want to control to a target socket on the switch. After you fill a socket, the next empty socket appears; the stated limit is 99 targets.
  • For a shared on/off control, connect enabled_out to the next switch’s enabled input. Set trigger_on and action separately on each switch to give different groups different behavior.
  • Use true → active for a group you want active when the shared toggle is true, and false → active for a group you want active in the opposite state.
  • Check whether you need mute or bypass before relying on a workflow result: the interface describes them as stopping execution and passing through, respectively, which are different intended behaviors.

DaSiWa Node Status Switch Common Errors and Solutions:

A target node does not appear to respond

  • Explanation: The intended node may not be connected to one of the switch’s target sockets, or the current enabled value may not match trigger_on. This is a troubleshooting symptom, not a quoted error message from the supplied source.
  • Solution: Confirm that an output of the intended target node is wired to a target socket. Then check enabled and trigger_on together to see whether the switch should be active in the current state.

The switch acts in the opposite state from what you expected

  • Explanation: trigger_on determines whether true or false activates this switch. Chaining does not copy another switch’s trigger_on choice.
  • Solution: Change trigger_on on the affected switch to the state you want. Check its action setting separately.

A chained switch does not use the upstream action

  • Explanation: enabled_out carries only a BOOLEAN value. It does not carry the upstream switch’s action or trigger_on setting.
  • Solution: Connect enabled_out to the downstream switch’s enabled input, then set the downstream trigger_on and action explicitly.

No additional target socket appears

  • Explanation: The provided context says that only one empty target socket is shown at a time: connecting it reveals the next, up to 99 targets. This is not an error string emitted by the shown Python class.
  • Solution: Connect the currently empty target socket before looking for another. If you have reached 99 targets, use another switch.

“Expected an active-state result from enabled_out”

  • Explanation: This describes a possible misunderstanding, not a documented software error message. enabled_out returns the boolean value of enabled; it does not change to reflect the trigger_on choice or confirm a target’s status.
  • Solution: Read enabled_out as the shared toggle value. To predict a particular switch’s intended behavior, consider that value alongside that switch’s own trigger_on and action settings.

DaSiWa Node Status Switch Related Nodes

Go back to the extension to check out more related nodes.
ComfyUI-DaSiWa-Nodes
RunComfy
Copyright 2025 RunComfy. All Rights Reserved.

RunComfy is the premier ComfyUI platform, offering ComfyUI online environment and services, along with ComfyUI workflows featuring stunning visuals. RunComfy also provides AI Models, enabling artists to harness the latest AI tools to create incredible art.

DaSiWa Node Status Switch