/eventsAPI endpoint (exposed by the iFLUX middleware).
/actionsAPI endpoint (exposed by an iFLUX-compatible actuator or gateway.
/rulesAPI endpoint, so that users can create new rules. The payload accepted by the endpoint can be a bit tricky to write. The objective of this editor is to address this issue and to make the process easier. Using the editor involves three steps:
/rulesAPI endpoint to add the rule to your iFLUX setup.
An event source is a particular sensor (hardware or software), which is registered on the iFLUX platform and which issues event notifications.
Example: a thermometer
Event sources emit events of different types. A type is associated with a list of properties.
Example: a temperature event
An iFLUX event is defined by a source, a type, a timestamp and a list of custom properties.
Example: a temperature event may have 2 custom properties: location and temperature
An iFLUX action target implements the /actions/ endpoint defined in the iFLUX API. It accepts action payloads and executes them.
Example: a street light controller might accept actions to turn lights on and off.