It's time for our... Software Update!

Dear Waylay user,

Waylay Engine 3.16.1 has now been released

  • Waylay Engine 3.16.1
  • Dashboard 2.17.4
  • Sandbox 1.17.5
Force clear browser cache when you first login, in order to see the new features.

Digital Twin Capabilities

With an updated and extended meta model, Waylay now handles two different digital twin capabilities: 
  • Metrics configuration: describes which data can be collected on a resource
  • Commands: abstracts actuations allowed on a resource
The new meta model also supports hierarchical parent/child relations between resources. Resource inheritance (and rules execution) is achieved via the concept of "resource type", as before, while the parent/child concept is used to only define relation (and navigation).

This simplifies building custom UI applications, such as for smart buildings, where the parent/child relation can be used to group a set of resources (e.g. building A, floor 2 etc.) into buildings and floors.

More on the digital twin

New feature: Commands

The commands feature allows you to specify a generic set of actuators for a resource, which at runtime gets resolved to a specific actuator. This enables you for example to model lamps from different manufacturers with their capabilities such as (turn off/on, dimming etc..) and then at the meta level to define different actuations for different resources. This allows for much easier REST integrations with 3rd party apps.

Example: When a command is sent to the broker for the resource and command name SayHi, the engine will check the commands property of the resource’s metadata and see if there is a command SayHi mapped to an actual actuator. If such mapping exist, the Waylay engine will call the actual actuator.

We have also created a new actuator, called executeCommand. It is available on github and ready for you to download:





You can at any time check all commands sent to the resource by looking at the commands tab under the resource view:


More on Commands

New conditional sensor executions

We have aligned conditional executions of actuators and sensors. The sensor configuration panel is very similar to the actuation panel.

If you need conditional sensor execution, you have the following options:

  • always (every time previous sensor succeeds) by leaving all options empty or
  • trigger the execution on a particular sensor state or
  • use the state change trigger feature
  • via sequence number attached to the sensors, if you use periodic or cron task

Here is an example of this new capability:

More on Executions

NPM packages in the Sandbox

From sandbox version 1.17.4 onwards, you can add custom NPM packages to your environment. These packages can either reside in the public npm registry or in a private registry, in which case, please contact to configure it for you.

If you are using the same package which is already available in the sandbox in your plug (for instance another version of lodash), please be aware that the package defined in the dependencies will be used.

Other updates 

Do you have any questions? Get in touch with our support team!
Copyright © 2018 Waylay, All rights reserved.

unsubscribe from this list    update subscription preferences