Core scripts


Core scripts are generally unsafe, can crash the controller and should be written/used with care and only in cases, when there’s no alternative standard safe solution.

What are EVA ICS core scripts

  • Core scripts are Python 3 scripts, which run directly inside the core of a controller and are launched on particular events.

  • Core scripts are similar to web server modules, where request and response data are processed by the chain of module libraries. In EVA ICS core script chains process events.

  • All core scripts are always executed on all events. Core scripts are executed by alphabetical order, one by one.

  • It is possible to handle multiple events by a single core script.

  • The code of the special file is included in all core scripts.

What are core scripts for

Core scripts are not recommended for Enterprise-level configurations, it is a vehicle to quickly implement:

  • data collection from HTTP/POST and MQTT, without drivers

  • simple automation tasks without Logic Manager

  • custom API methods and extensions of EVA ICS functionality.

Core script globals and functions

  • All API functions of the current controller are directly available to call

  • print function is mapped to

  • spawn(func, *args, **kwargs) runs a target function in the background as a controller thread

  • logging, time, json (rapidjson) and eva.apikey modules are imported by default

  • dir_eva EVA ICS directory

  • event event info namespace

  • g special namespace, shared across all core scripts

  • masterkey the controller’s master key

  • product the controller info name space:

    • product.code “uc”, “lm” or “sfa”

    • current EVA ICS build

  • system_name the system name

Core script events

The special core script globals name space event contains the event info core script was called for:

State event

Triggered when any item (unit, sensor or lvar) changes its state (status or value).

event.type == CS_EVENT_STATE
  • event.source source item object

  • serialized item state (dict)

API event


API events are deprecated. Use CS_EVENT_RPC instead

Triggered when HTTP/POST request is performed on /r/cs/somepath.

event.type == CS_EVENT_API
  • event.topic relative API URI without method prefix (e.g. tests/test1 for /r/cs/tests/test1)

  • event.topic_p uri split by ‘/’ (list object)

  • JSON payload data (fields “k”, “save”, “kind” and “method” are reserved and removed)

  • event.k current call API key


Only HTTP/POST RESTful-like API calls are supported

RPC event

Replaces API events in EVA ICS 3.3.2 and above. Triggered when JSON RPC API method starting with “cs_” is called.

event.type == CS_EVENT_RPC
  • event.topic method name, without “cs_” prefix.

  • params

E.g. the following JSON RPC API request:

    "jsonrpc": "2.0",
    "method": "cs_myfunc",
            "param1": "value1",
            "param2": "value2"

generates an event with event.topic=”myfunc” and containing the params.

Core scripts can not return API responses. Also note that core scripts should handle any authentication by themselves.

Periodic event

Periodic events allow core scripts to act as scheduled jobs.

Currently periodic events are launched every minute only. However, it is highly recommended to check the event topic to have corescripts backward-compatible with the future EVA ICS releases.

event.type == CS_EVENT_PERIODIC
  • event.topic “M” for every-minute event.

  • event.iteration iteration since the controller start


if event.type == CS_EVENT_PERIODIC and event.topic == 'M':
    if event.iteration > 0 and not event.iteration % 10:
        print('another 10 minutes have passed')

MQTT event

Triggered when MQTT message is received and its topic matches subscribed.

To let core scripts react to MQTT events, they must be subscribed to MQTT topics, either with SYS API method subscribe_corescripts_mqtt or with “eva <controller> corescript mqtt-subscribe <topic>” console command (“+” and “#” MQTT masks are supported).

event.type == CS_EVENT_MQTT
  • event.topic MQTT topic

  • event.topic_p topic split by ‘/’ (list object)

  • MQTT message data

  • event.qos MQTT message QoS

  • event.retain is MQTT topic retained (1) or regular (0)

System event

Triggered on system events

event.type == CS_EVENT_SYSTEM
  • event.topic event topic:

    • startup triggered after the controller startup

    • shutdown triggered before the controller shutdown


‘shutdown’ event blocks controller shutdown process until all core scripts are completed. The script chain must finish in 30 seconds, otherwise the controller suicides itself and kills own process with SIGKILL signal.

Setting up packages

See Packages


Core script globals contain pre-defined “logger” variable, which points to eva.core logger object.

logger.warning('This is a core script')

Creating and managing core script files

  • Core scripts are available for all controllers and stored in runtime/xc/{controller}/cs (e.g. rumtime/xc/uc/cs for Universal Controller).

  • Core script files should have .py extension.

  • If core script code is modified, controller reloads it automatically. However if core script is added or deleted, it is required to either exec reload_corescripts Common methods method (or eva <controller> corescript reload console command) or restart the controller.

Code examples

Core script code should be always started with “if”, checking an event type:

# turn on the lights when the motion sensor is triggered
if event.type == CS_EVENT_STATE and \
   event.source.oid == 'sensor:security/motion1' and \['value'] == '1':
     action(k=masterkey, i='unit:light/hall', s=1)


  • Item status/value can be obtained by accessing event.source.status and event.source.value fields as well. However it is highly recommended to use dict instead - it contains the “fixed” state snapshot, as actual item state can be modified while core script is running.

  • In the core scripts, item state value is always a string

# print API payload to logs
if event.type == CS_EVENT_API:
# update the sensor state according to MQTT JSON message { "temperature": N }
if event.type == CS_EVENT_MQTT and event.topic == 'some/device/telemetry':