This library is a Typescript interface to ACAEngine

Usage no npm install needed!

<script type="module">
  import acaengineTsClient from 'https://cdn.skypack.dev/@acaengine/ts-client';


TypeScript ACAEngine Library

This library is a Typescript interface to ACAEngine


You can build the library from source after installing the dependencies with the command

npm run build


API docs can be found here

You can install the ACAEngine Typescript client with the npm command

npm install --save-dev @acaengine/ts-client

After the package is installed you can import ACAEngine into your application

import { ACAEngine } from '@acaengine/ts-client'

Before using ACAEngine it will need to be intialised.


The init method takes a config object with the following properties

Property Description Optional Type Example
host Host name and port of the ACAEngine server Yes string "dev.acaengine.com:8080"
mock Whether to initialise ACAEngine with mock services Yes boolean true
auth_uri URI for authorising users session No string "/auth/oauth/authorize"
token_uri URI for generating new auth tokens No string "/auth/token"
redirect_uri URI to redirect user to after authorising session No string "/oauth-resp.html"
scope Scope of the user permissions needed by the application No string "admin"
storage Browser storage to use for storing user credentials Yes "local" \| "session"
handle_login Whether ACAEngine should handle user login Yes boolean true

Once initialised the ACAEngine object will expose interfaces to ACAEngine's websocket and http APIs

Websocket API

ACAEngine exposes a websocket API through the bindings service.

The bindings service is used to provide real-time interaction with modules running on ACAEngine. It provides an interface to build efficient, responsive user interfaces, monitoring systems and other extensions which require live, two-way or asynchronous interaction.

Once ACAEngine has initialised you can listen to values on modules

const my_mod = ACAEngine.bindings.module('sys-death-star', 'TestModule', 3);
const my_variable = my_mod.binding('power');
const unbind = my_variable.bind();
const sub = my_variable.listen((value) => doSomething(value));

This binds to the power status variable on the 3rd TestModule in the system sys-death-star. Any changes to the value of power on ACAEngine will then be emitted to the function passed to listen.

Other than listening to changes of values you can also remotely execute methods on modules.

const my_mod = ACAEngine.bindings.module('sys-death-star', 'DemoModule', 2);
    (resp) => handleSuccess(resp)
    (err) => handleError(err)

This will execute the method power_off on the 2nd DemoModule in the system sys-death-star. If the method doesn't exist or the system is turned off it will return an error. The response from ACAEngine can be handled using the promise returned by the exec method.


For the HTTP API, ACAEngine provides a service for each of the root endpoints available on ACAEngine's RESTful API.

Docs for the API can be found here https://docs.acaengine.com/api/control

Services are provided for drivers, modules, systems, users, and zones

Each service except for users provides CRUD methods. users provides _RUD.

// Drivers CRUD
ACAEngine.drivers.add(driver_data).then((new_driver) => doSomething(new_driver));
ACAEngine.drivers.show(driver_id).then((driver) => doSomething(driver));
ACAEngine.drivers.update(driver_id, driver_data).then((updated_driver) => doSomething(updated_driver));
ACAEngine.drivers.delete(driver_id).then(() => doSomething());

// Modules CRUD
ACAEngine.modules.add(module_data).then((new_module) => doSomething(new_module));
ACAEngine.modules.show(module_id).then((mod) => doSomething(mod));
ACAEngine.modules.update(module_id, module_data).then((updated_module) => doSomething(updated_module));
ACAEngine.modules.delete(module_id).then(() => doSomething());

// Systems CRUD
ACAEngine.systems.add(system_data).then((new_system) => doSomething(new_system));
ACAEngine.systems.show(system_id).then((system) => doSomething(system));
ACAEngine.systems.update(system_id, system_data).then((updated_system) => doSomething(updated_system));
ACAEngine.systems.delete(system_id).then(() => doSomething());

// Users CRUD
ACAEngine.users.add(user_data).then((new_user) => doSomething(new_user)); // This will error
ACAEngine.users.show(user_id).then((user) => doSomething(user));
ACAEngine.users.update(user_id, user_data).then((updated_user) => doSomething(updated_user));
ACAEngine.users.delete(user_id).then(() => doSomething());

// Zones CRUD
ACAEngine.zones.add(zone_data).then((new_zone) => doSomething(new_zone));
ACAEngine.zones.show(zone_id).then((zone) => doSomething(zone));
ACAEngine.zones.update(zone_id, zone_data).then((updated_zone) => doSomething(updated_zone));
ACAEngine.zones.delete(zone_id).then(() => doSomething());

The services also provide methods for the various item action endpoints

// Driver Actions

// Module Actions
ACAEngine.module.lookup(module_id, lookup);

// System Actions
ACAEngine.system.remove(system_id, module_name);
ACAEngine.system.execute(system_id, module_name, index, args);
ACAEngine.system.state(system_id, module_name, index, lookup);
ACAEngine.system.functionList(system_id, module_name, index);
ACAEngine.system.types(system_id, module_name);

// User Actions

Objects returned by show and query methods are immutable, though when reassigning value it will be saved under the changes property of that object. These changes can be saved using the save method which will return a promise for the new object.

ACAEngine.zones.show(zone_id).then((zone) => {
    console.log(zone.description); // Prints the current description
    zone.description = 'New description';
    console.log(zone.description); // Same a previous print
    cosnole.log(zone.changes.description) // New description
    zone.save().then((updated_zone) => {
        cosnole.log(updated_zone.description) // New description

You can find more details about endpoint action on the API docs


Writing mocks

If you don't have access to an ACAEngine server you can also write mocks so that you can still develop interfaces for ACAEngine.

To use the mock services you can pass mock: true into the initialisation object.


To write mocks for the the realtime(websocket) API you'll need to add your systems to window.control.systems before initialising ACAEngine.

window.control.systems = {
    "my-system": {
        "MyModule": [
                power: true,
                $power_on: function () { this.power = true },
                $power_off: function () { this.power = false }

Note that executable methods on mock systems are namespaced with $ as real systems in engine allow for methods to have the same name as variables.

Once initialised interactions with a system are performed in the same manner as the live system.

const my_mod = ACAEngine.bindings.module('my-system', 'MyModule', 1);
const my_variable = my_mod.binding('power');
const unbind = my_variable.bind();
const sub = my_variable.listen((value) => doSomething(value)); // Emits true
my_mod.exec('power_off'); // The listen callback will now emit false

Some methods may need access to other modules within the system, for this a property is appended on runtime called _system which allows for access to the parent system

window.control.systems = {
    "my-system": {
        "MyModule": [
                $lights_off: function () { this._system.MyOtherModule[0].lights = false; }
        "MyOtherModule": [
                lights: true,

HTTP Requests

HTTP API Requests can be mocked in a similar way to the realtime API by adding handlers to window.control.handlers

window.control.handlers = [
        path: '/api/engine/v2/systems',
        metadata: {},
        method: 'GET',
        callback: (request) => my_mock_systems

Paths allow for route parameters and will pass the value in the callback input.

window.control.handlers = [
        path: '/api/engine/v2/systems/:system_id',
        callback: (request) =>
            my_mock_systems.find(sys => sys.id === request.route_params.system_id)

Query parameters are also available on the callback input.

GET, POST, PUT, PATCH and DELETE requests can be mocked out.

If a request is made and there are no handlers it will attempt to make the live request.