Commands  ›  Clash Manager / Solver  ›  Clash Solver Find Nearest Host For Device

Clash Solver Find Nearest Host For Device

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

Coming soon

Before you run this

Active document; one FamilyInstance device resolvable.

After it runs

No mutation; audit recorded.

When to use this

Don't use this when

Actually moving the device.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) device unique id required OR single selection. Must be a FamilyInstance.
2) Inspect fi.Host: if non-null, currentHostCategory = Host.Category; else fall back to HostBehavior.Plane / HostedByFace flag: tag as "any".
3) Build pool by BuiltInCategory matching currentHostCategory (Walls / Ceilings / Floors). If unknown, union Walls + Ceilings + Floors.
4) For each candidate, compute Euclidean distance between device.Location.Point and candidate BB centroid; skip beyond max radius.
5) Skip the device's current host.
6) Sort ascending; emit top 50 (configurable).

What you'll see in the chat

on start
Listing nearest host candidates for device…
thinking
Resolving device + current host…
Collecting candidates from matching category…
Ranking by distance…
on success
{candidate_count} candidates found, top {top_count} returned.
on failure
Find-nearest-host 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_find_nearest_host_for_device
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashsolverfindnearesthostfordevice · find nearest host · solver host search

PillarClash Manager / Solver