MELCloud & MELCloud Home API for Node.js - v48.2.0
    Preparing search index...

    Class EntityNotFoundError

    Thrown when a facade attempts to resolve its underlying registry entity by id and finds nothing — typically because the registry was rebuilt (re-login, re-sync, or upstream rename/deletion) and the entity no longer exists under the previously known id.

    Recovery: invalidate any cached facade reference held by the consumer and re-resolve the entity through the appropriate manager.

    try {
      await facade.fetch()
    } catch (error) {
      if (error instanceof EntityNotFoundError) {
        this.cachedFacade = undefined
        return
      }
      throw error
    }

    Hierarchy (View Summary)

    Index
    constructor
    cause? entityId message name stack? tableName stackTraceLimit
    captureStackTrace isError prepareStackTrace

    • Builds the error from the registry table and the unresolved entity id; the message bakes both into a human-readable summary.

      Parameters

      • tableName: "ClassicArea" | "ClassicBuilding" | "ClassicFloor" | "DeviceLocation" | "Device"

        Registry table the lookup was performed against.

      • options: { cause?: unknown; entityId: string | number }

        Unresolved entity id plus optional cause.

        • Optionalcause?: unknown

          Original error that triggered this one.

        • entityId: string | number

          Id that could not be resolved.

      Returns EntityNotFoundError

    cause?: unknown
    entityId: string | number

    Id that could not be resolved in the registry — a number for Classic, a GUID string for Home.

    message: string
    name: "EntityNotFoundError" = 'EntityNotFoundError'
    stack?: string
    tableName:
        | "ClassicArea"
        | "ClassicBuilding"
        | "ClassicFloor"
        | "DeviceLocation"
        | "Device"

    Registry table the lookup was performed against (e.g. 'DeviceLocation'), or 'Device' for the Home registry.

    stackTraceLimit: number

    The Error.stackTraceLimit property specifies the number of stack frames collected by a stack trace (whether generated by new Error().stack or Error.captureStackTrace(obj)).

    The default value is 10 but may be set to any valid JavaScript number. Changes will affect any stack trace captured after the value has been changed.

    If set to a non-number value, or set to a negative number, stack traces will not capture any frames.

    • Creates a .stack property on targetObject, which when accessed returns a string representing the location in the code at which Error.captureStackTrace() was called.

      const myObject = {};
      Error.captureStackTrace(myObject);
      myObject.stack;  // Similar to `new Error().stack`

      The first line of the trace will be prefixed with ${myObject.name}: ${myObject.message}.

      The optional constructorOpt argument accepts a function. If given, all frames above constructorOpt, including constructorOpt, will be omitted from the generated stack trace.

      The constructorOpt argument is useful for hiding implementation details of error generation from the user. For instance:

      function a() {
        b();
      }

      function b() {
        c();
      }

      function c() {
        // Create an error without stack trace to avoid calculating the stack trace twice.
        const { stackTraceLimit } = Error;
        Error.stackTraceLimit = 0;
        const error = new Error();
        Error.stackTraceLimit = stackTraceLimit;

        // Capture the stack trace above function b
        Error.captureStackTrace(error, b); // Neither function c, nor b is included in the stack trace
        throw error;
      }

      a();

      Parameters

      • targetObject: object
      • OptionalconstructorOpt: Function

      Returns void

    • Indicates whether the argument provided is a built-in Error instance or not.

      Parameters

      • error: unknown

      Returns error is Error

    Settings
    Member Visibility

    On This Page
    Constructors
    Properties
    Methods