Commands  ›  Clash Manager / Solver  ›  Clash Solver Move Device To Wall

Clash Solver Move Device To Wall

Clash Manager / Solver writes to model Public API · not yet exposed

Coming soon

Before you run this

Active document; device is FamilyInstance; targetWall is Wall.

After it runs

Delegates geometric move to ClashSolverMoveDeviceToNearestHostCommand.

When to use this

Don't use this when

Ceiling / floor re-host — use MOVE_TO_HOST.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) device unique id + wall unique id required OR two-element selection.
2) WireError if target isn't Wall.
3) Instantiate ClashSolverMoveDeviceToNearestHostCommand with same resolvers.
4) Delegate Execute; pipe outputs + tag target_is_wall=true.

What you'll see in the chat

on start
Moving device onto target wall…
thinking
Checking target element is a Wall…
Delegating to MoveDeviceToNearestHostCommand…
on success
Device moved onto wall.
on failure
Move-to-wall failed: {error}

REST API

Not yet exposed

This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:

  • POST /api/v1/commands/clash_solver_move_device_to_wall
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashsolvermovedevicetowall · move device to wall · solver wall re-host

PillarClash Manager / Solver