Glossary


NMA Server

Network Mediation Application or Network Messaging Android, application that controls all connection to the Ezlo's (from UI, Portal, licensing module, etc.).


Cloud Coordnator

Application responsible for assigning NMA Server to new users and ezlo hubs.


OCS

Not important abbreviation. Long time developed software which is not needed anymore and mostly not used by anybody anymore.

OCS played important role as administrative web site in past times. It was used to manage multiple old version of NMA servers which was not based on cloud architecture.

With cloud architecture arrived OCS became redundant.

Notice: Therm defines OBSOLETE AND REDUNDANT SOFTWARE.


Ezlo or Hub or Ezlo Hub

Mini computed produced by eZLO company which connects to NMA Server and which is connection point for all the home automation devices.


DataItem

This can be ordinary HA device (switch, thermostat, etc.), service (twitter, SMTP, etc.) or camera. It can has methods, properties, can produce events and/or continious data streams (audio and video for example).


Ezlo UI

Sencha multiplatform App for ordinary everyday Ezlo usage


Ezlo Owner

Person that owns one or more Ezlo devices. Can manage the Ezlo users but can be separated from them.


Ezlo User

User that is able to login to Ezlo UI.


Portal UI

Ezlo portal where the owner can login manage Ezlo's and its users, make the payments, etc.

Notice: Therm definition is OBSOLETE.


Portal Backend

Node.js application that is connected to NMA and serve the portal UI tasks. Notice: May be obsolete and removed soon.

Notice: Therm definition is OBSOLETE.


Monitoring UI

UI for the support engineer that will help to monitor the cloud health.

Notice: Therm definition is OBSOLETE.


Monitoring Backend

Special application for gathering cloud health statistic, alarms, etc.

Notice: Therm definition is OBSOLETE.


FWUC

FirmWare Update Center, will manage the new firmwares, new Rule UI blocks, notify the Ezlo's users about new versions.


ID

Message ID. Must have field in any JSON message or answer.


_OBJECT_ID_

A MongoDB object ID like string, for instance ("5385e6e065e04a581fe9a521").

Notice: Therm definition is OBSOLETE.


_ID_

Message ID.

Notice: Therm definition is OBSOLETE.


_BASE64DATA_

Media data encoded with base64.

Notice: Therm definition is OBSOLETE.