NO_DEVICE — Named device does not exist on this agent

The device name in the request path is not one the agent serves.

Start free MTConnect → canonical

Diagnosis

When you hit this

Using the machine's shop-floor name rather than the name in the agent's device XML.
An agent serving several devices where the path omits or misspells one.
A device removed from the agent's configuration but still requested by a client.

Resolution

How to fix it

Read /probe first
The probe response lists every device the agent serves, with exact names. It is the authoritative source.
Match the name exactly
Device names are case-sensitive and often differ from the name painted on the machine.

Normalization

What Forge does about it

This is a configuration or addressing mistake on the wire, upstream of anything Forge sees. Where Forge helps is the step after you fix it: once the point returns data, its vendor tag name maps to a canonical field automatically, so you do not also have to hand-maintain a name table for every point you just re-addressed.