tadpol / node-red-contrib-exosite

A node for node-red that uses the data api to talk to Exosite's OnePlatform

This repo is no longer maintained, and thus archived. Use at your own risk.

node-red-contrib-exosite

A node-red node that accesses devices on Exosite's Murano platform.

It uses the HTTP Data API to read, write, or watch aliases on a device.

Device config

The exosite nodes are configured to talk to a device instance inside Murano. This instance has a set of aliases that descibe the points where data can be read or wrote. Each device instance is defined by a product ID and serial number.

If node-red is running on a machine that also has Gateway Engine (GWE) installed, you can select 'GWE' to access the Gateway Engine's device instance.

A device instance in Murano needs to be in the 'notactivated' or 'whitelisted' state so that it can be activated by the exosite node-red node. This happens when you create a new device in Murano.

node-red-contrib-exosite's Issues

Devices activated by a 'exo-watch' node do not have the CIK saved.

Devices activated by a 'exo-watch' node do not have the CIK saved.

Adding a 'exo-read' or 'exo-write' node with the same config-node and triggering them will cause the CIK to be saved.

So this is just something with the 'exo-watch' that is unique.

Device activation of an already activated device fails poorly

Device activation of an already activated device fails poorly. It either locks up or even kills the node-red instance.

Add a node to read aliases from CIK

Please consider node-red-contrib- naming guidelines

Hi there - thanks for creating a node and sharing it with the community.

One request - as per our packaging guidelines, we ask that 3rd party nodes use the node-red-contrib- prefix to their name. This ensures they don't get mistaken for nodes maintained by the project itself.

You're under no obligation to change the name, but I hope you'll consider it.

Many thanks, Nick