FoundryNet / Error codes / BACnet/IP UNKNOWN_OBJECT
BACnet/IP error code

UNKNOWN_OBJECT — Error Class OBJECT, code UNKNOWN_OBJECT

The device has no object with the requested type and instance number. Object identifiers are a type plus an instance, and both must match.

Start free BACnet/IP → canonical

Diagnosis

When you hit this


Resolution

How to fix it

  1. Read the device's object list
    Property 76 (object-list) on the Device object enumerates everything present. Discover rather than assume.
  2. Do not port instance numbers between devices
    Two identical rooftop units frequently have different instance numbering.

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.


Connect

Normalize BACnet/IP telemetry

One MCP endpoint serves every protocol adapter. 16,908 curated mappings, 366 canonical fields.

# normalize telemetry from BACnet/IP — and 13 other protocols
claude mcp add --transport http forge https://mcp.foundrynet.io/mcp \
  --header 'Authorization: Bearer YOUR_FORGE_KEY'
✓ forge connected — 32 tools available

Related

Keep reading

Other BACnet/IP codes: UNKNOWN_PROPERTY WRITE_ACCESS_DENIED TIMEOUT VALUE_OUT_OF_RANGE

Equipment that speaks BACnet/IP: Chemical process Food & beverage process Pharma process (GMP)

BACnet/IP protocol hub

Other protocols: Modbus OPC UA MQTT / Sparkplug B FANUC FOCAS EtherNet/IP PROFINET / S7 J1939 (CAN) MTConnect ROS 2 (DDS) SNMP MAVLink HTTP / REST CSV ingest

All error codes · All OEMs · All protocols

Industrial AI fails at the data layer. The Machine Agent explains why, weekly. Read it →
Get the thesis behind this infrastructure — The Machine Agent, weekly.