All you need to know about IoT automation, upcoming webinar and events


We're pleased to announce our latest software release:

  • Engine version: 3.19.0
  • Sandbox version: 1.17.10
  • Dashboard version: 2.18.0

Release highlights:
  • Actuation as a stream
  • Updated alarm handling service
  • Assigning roles to resources in a template

Force clear browser cache when you first login.

Watch the recording of the release webinar where we demo the new features:

Actuation as a stream

You can now pass down the actuation implementation to one or more stream consumers, external to Waylay, to implement the actuation on the device, by using a new native actuator called StreamingActuator. You may need to do that for security reasons or because the external system needs to do some additional checks or logging before performing the actuation on the device.

The new
StreamingActuator publishes data as a stream on any pub/sub broker, such as Google Pub/Sub, Kafka or Azure Event Hub. When being called, the StreamingActuator will forward the payload together with a resource ID. You can also template the payload message.

Contact support@waylay.io to activate this feature.

Alarm handling service

Depending on the type and severity of your alarms, different alarm handling logic may be needed, for example logging the minor alarms versus sending an sms for the critical alarms. Our new alarm handling feature allows you to separate the alarm handling logic from the metric handling logic, improving overall business logic readability and maintainability.

The alarm handling rules listen in on the alarm channel where your alarms are published and process them using the new
AlarmEventSensor, that can filter on resource, severity or alarm type.

You can download two demo json templates on Github.

Read more...

Assigning roles to resources in a template


If you work with multiple sensor device data feeds coming from multiple resources, chances are they all need to be logically combined before action is taken (send sms, log entry, etc.). With this new feature, you can create a master template and assign roles to each resource.

When starting a task for this (task) template, all templated resources can be assigned at runtime. Previously, if you needed to model automation logic that takes inputs from multiple resources at the same time, you needed to hardcode these resources into the template or use the dollar sign if you needed to use just one task resource as a resource on a node.


You can download a demo json template on Github.

Read more...

Other updates

  • Abstract vendor-specific command payload encoding from the business logic of the rules by using placeholders inside the parameters when defining the commands of a resource type. An example of when you would use this is if you have two devices with different firmware versions exposing the same command API but that have slightly different command encoding requirements. You can now abstract this difference from the rule builder using this feature. Read more...

  • Allocate applicable sensors to a resource or resource type in the metadata when creating it. For instance, you may have one sensor per metric, or multiple sensors for a given metric, or one sensor that is using multiple metrics. When calling the Waylay REST interface to retrieve the metadata of a resource, a graphical user interface can be dynamically built based on a set of capabilities for a resource, both for actuations (using commands) and for associating a set of sensors, next to supported metrics. Read more...

  • Create rules to receive alerts when certain platform usage metrics exceed a threshold with the new UsageStatsThreshold sensor, instead of manually checking your usage stats on your Waylay dashboard. This way you can automatically detect unexpected or abnormal usage patterns.

  • Waylay can now re-run missed cron task executions during a platform upgrade or restart maintenance window, available on demand for standard support packages or above.



Blekersdijk 33a, Ghent, 9000, Belgium